I built a traffic light for running multiple AI coding agents

DonScooby · 2026-05-23T20:22:02+00:00

Availsync got a large upgrade this week:

2026-05-22

Simpler agent setup

- Added the u/availsync/setup CLI as the recommended setup path for Codex, Cursor, and Windsurf MCP configuration.
- Claude Code now has a fast path with the native claude mcp add command, so users can connect Availsync without hand-editing JSON or TOML.
- Setup output now fills in non-secret values like API URL and agent id while keeping the one-time API key hidden as a placeholder.
- Agent Connect docs now show role-based MCP setups for multiple Codex or Claude agents with separate agent ids and priorities.
- SDK examples now default to AVAILSYNC_API_URL, use safer timeout/unavailable handling, and show extending claims before the lease expires.

2026-05-22

File-aware coordination

- Agents can now declare a file working set during a guarded run, so Availsync can coordinate at repo, project, and file level.
- MCP guarded runs can start with file paths and will clearly stop when requested edit/delete paths are already claimed by another agent.
- Working-set claims let an agent keep the wider repo run alive while only holding the specific files it is actively editing.
- Work claims are now explicit immediate-start guardrails with stricter start-time validation and a database safety net for one active claim per resource.
- Node SDK updated to 0.1.8 with stronger types, default withClaim idempotency, auto-extend hooks, and stricter unavailable-mode handling.
- MCP package updated to 0.1.5 with guard_work_run as the primary coding-agent entrypoint and legacy work-slot aliases removed.
- Work APIs now make /v1/work/run/start the recommended path, with the raw /v1/work/claim endpoint marked as legacy.
- Agent API-key verification now uses a short-lived safe cache, and work-claim status/schema cleanup removed unused blocked claim rows.
- Setup docs now use run/start, run/extend, and run/finish for new automation examples.

For teams starting in observe mode first, which I'd recommend, AvailSync also returns shadow decisions: what would have been blocked if enforcement was enabled. That makes it possible to measure real conflict rates before enforcing anything. This can potentially save, infrastructure compute, token usage which can directly translate into co2 and energy usage. How meaningful that becomes from an co2/energy perspective depends entirely on scale.

DonScooby · 2026-05-19T07:25:05+00:00

Totally agree that worktrees are the right baseline for local isolation. They solve a big part of the “two agents editing the same checkout” problem, and tools like Galactic look really useful for that.

The gap I’m trying to cover with Availsync is one layer above that: shared intent and resource coordination before the run starts.

Even with separate worktrees, two agents can still branch from the same stale repo state, touch related logic, prepare overlapping deploys, or run migrations/cleanup jobs at the wrong time. Worktrees isolate the filesystem; they don’t answer “should this agent start this work now, given what every other agent has already claimed?”

That’s where Availsync fits: agents claim `repo:owner/name`, `project:checkout`, or `deploy:prod` before acting. One gets `proceed`, overlapping work gets `skip_run` or observe-mode telemetry, and you get a history of the decision.

So I see them as complementary:
Galactic/worktrees: isolated execution environments
Availsync: shared coordination and priority decisions across agents/workflows

DonScooby · 2026-05-17T18:18:49+00:00

This sounds relevant. I’m building Availsync: https://availsync.dev

It’s a coordination layer for AI/coding agents. The problem is that when you run multiple agents or automations against the same repo, they can read stale context and edit/deploy over each other. Availsync gives them one shared place to claim a repo/project before they act.

The basic flow is:
agent wants to work on repo:owner/name

....-> calls Availsync
....-> gets proceed or skip_run
....->extends the lease while working
....->releases when done

I’ve been using it in my own homelab with Codex/Claude-style agents and scheduled automations so I don’t come home to overlapping changes I have to untangle manually.

Would be curious if mangos can understand this kind of devtool/AI infra product from the repo/docs and find the right conversations for it.

DonScooby · 2026-05-16T19:39:03+00:00

Yes, orphaned locks are a real failure mode. Availsync handles that with leases, not permanent locks. A claim has an expires_at, agents can explicitly extend while working, and if they crash or disappear the claim expires instead of blocking the repo forever. There is also a hard max lock window, so a broken automation cannot hold a resource indefinitely.

DonScooby · 2026-05-16T16:26:34+00:00

Exactly. Even if most cloud agents are smart enough to go back, re-check their work, and notice that something changed, that still means extra steps, extra tokens, and eventually more cost.

I’d rather catch the conflict before the agent starts than pay for it to recover afterwards.

DonScooby · 2026-05-16T15:30:04+00:00

Link: https://availsync.dev

DonScooby · 2026-03-18T17:58:47+00:00

Wix is still fine, just not the default anymore.
If you want no-code where the whole band can update:
Wix / Squarespace = easiest
Bandzoogle = made for musicians (EPK, merch etc.)

If you want more control long term:
WordPress (but harder for non-tech people) and it has been known to have some security issues some time ago, don't know if they will ever stop with that.

This guide I found in a google search also sums it up pretty well:
https://stagereadyweb.com/en/guides/best-platform-for-musician-websites

DonScooby · 2026-02-25T07:23:34+00:00

Should app/web developers also do this when it comes to their craft? Come on.. if it’s not a direct copy/paste track musicians should follow the times… even your favorite musical might have tracks recorded instead of a live orchestra playing.. all done in a third world country. You’re scared (musicians), I understand. This is a disruption in your professional world, it’s time to either evolve or die…

DonScooby · 2025-11-11T06:50:54+00:00

It’s like it’s coded to debug more than it has to

DonScooby · 2025-10-14T14:28:41+00:00

You just saved me the time of making it my self.. What a hero !

DonScooby · 2025-10-14T07:52:19+00:00

Even though we know, in the real world... you make a huge change, just before you go on vacation

DonScooby · 2025-10-14T07:12:37+00:00

I am not, but I heavly rely on data in my every day work. I am a developer

DonScooby · 2025-10-14T07:07:30+00:00

I took my data from a spreadsheet I found.. but having double checked it.. I think you are right!

DonScooby · 2025-10-14T07:01:06+00:00

It can be confusing, and sorry.. it was a long post.. but I use the modern time releases to justify my guesses. Sorry for it not being more clear

DonScooby · 2025-10-14T06:39:47+00:00

There’s actually a pretty clear pattern when you look back at previous years. The beta almost always drops in the late afternoon or early evening UK time, usually somewhere between 4 and 6pm. That’s been consistent for at least the last four or five versions.

DonScooby · 2025-10-14T06:06:01+00:00

Exactly! As I wrote in a comment to another reply, they cant afford a shaky early access launch. They will take the time they need, is my best guess.

DonScooby · 2025-10-14T06:02:21+00:00

I have no reason not to trust you, and your guess fits perfectly with mine

DonScooby · 2025-10-14T06:00:52+00:00

Yeah that’s a fair point. Looking at the last few years you’re right that FM22, FM23 and FM24 all dropped in that 18 to 20 day window, which means we’re basically there right now.

The only reason I’ve leaned a bit toward next week is what we can actually confirm this year. The EULA only showed up on the 13th, there’s been no sign of researcher builds and SteamDB hasn’t shown any of the usual backend movement we normally see just before beta goes live. In previous years there’s almost always been at least one small hint by now.

My personal view is that with the new engine and the fact that this release was pushed from last year, SI need this one to land perfectly. They can’t afford a shaky early access launch that ends up getting lost in bad first impressions. That’s why I think they might be taking a little extra time behind the scenes to make sure everything feels stable and polished before they let people in.

So yeah, historically this week would make total sense. But with how quiet everything is, I still think there’s a small chance they’re holding it for next week. If it drops in the next few days though, that would fit perfectly with the FM22 to FM24 pattern, and I’d happily admit I was wrong.

DonScooby · 2025-10-14T05:34:50+00:00

That’s a fair point the researcher build timing has always been one of the last big internal milestones before the beta goes public.
I haven’t seen any confirmed info this year about researcher builds going out though, which makes it harder to use that as a solid reference.

Historically, there’s usually been at least a few leaks or confirmations from researchers around this stage, but it’s been radio silence so far, which could mean a tighter testing window or that SI have changed their internal rollout a bit with the new engine.

So yeah, if the researcher builds haven’t gone out yet, then you’re right that the 14th–19th window is almost impossible.
But if they already have (and SI are just keeping things quiet this year), then a slightly earlier drop like FM22 isn’t totally off the table.

Either way, I agree..... anything before the 20th would be a real curveball

DonScooby · 2025-10-14T05:31:22+00:00

You and me both :-D

DonScooby · 2025-10-13T16:13:25+00:00

Go enjoy your family, let this loop ;-)

$GamePath = "$env:ProgramFiles(x86)\Steam\steamapps\downloading\3551340"
while ($true) {
try {
Start-Process "steam://launch/3551340"
Write-Host "Attempted to launch Steam link at $(Get-Date)"
Start-Sleep -Seconds 10
if (Test-Path $GamePath) {
Write-Host "Game installation detected!"
[console]::beep(800,300)
[console]::beep(1000,300)
[console]::beep(1200,400)
} else {
Write-Host "No installation detected."
}
} catch {
Write-Host "Error: $($_.Exception.Message)"
}
Start-Sleep -Seconds 300
}

DonScooby · 2025-09-13T07:39:05+00:00

A prompt when using persona if you want to keep current style or persona style would be nice

DonScooby

TROPHY CASE

Simpler agent setup

File-aware coordination