Avibe

A workbench opens in your browser with chat, files, an editor and a terminal in it, pointed at the agent CLIs you already pay for. The deciding trait is that it is a front end and not a service: the work happens where you already work, and the browser is only the window onto it.

You are the wrong buyer if you were hoping for something hosted that a colleague can open, because there is nobody else's server in this story. Pick it if you want your agents at home. Pick a cloud harness if you want them somewhere your team can reach.

The row records no git operations. That matters more here than it would elsewhere, because sessions keep working while you are away. An agent that runs unattended for an hour leaves a changed working tree and no commit boundary describing what it did, so the only record of the work is a transcript.

What it gets right is the routing. Backends are interchangeable per project, so a repository that suits one agent is not held hostage to a global setting, and switching does not mean reinstalling anything.

1. The harness exposes four primitives, run, schedule, watch and inspect, and calls them durable, which is a specific claim: a session outlives the connection that started it. 2. Delegation is shown as a run graph, so a parent session's children are visible as structure rather than inferred from a log, and attribution has an answer.

2. No evaluation is published and none is owed, since the design claims durability rather than capability. The unusual property is that one session is addressable from several unrelated clients, which requires state to live in the harness rather than in any of them.

498 stars, a free client, and a hosted tunnel on the vendor's own domain. That last detail is the only thing here that could ever carry a price, and it is offered free today, which is the classic shape: give away the client, own the relay.

Moat: none in the software, some in the tunnel, if it ever becomes the default path to a developer's machine. Likely acquirer: a remote-development vendor that wants the last mile. Position: use the local half without hesitation, and treat the hosted half as a service that may one day arrive with a bill.

The control surface is consumer messaging. Sessions are reachable from Slack, Discord, Telegram, WeChat and Lark, which means an instruction to an agent with a shell can arrive from an account my identity provider does not manage. That is a conversation with security, not with finance.

Cost per seat is nothing, and across sixty engineers the spend is whatever their agent subscriptions already are, so the budget is unchanged. There is no SSO, no audit log and no pipeline integration. Not yet: bring me a way to restrict which chat identities reach a session.

MIT, and the install is one script I read before I ran it. What I like is where the secrets live: the keys stay on my machine and the execution does too, so this is a front door rather than a middleman. Nothing about my repository has to exist on somebody else's disk.

What I do not get is MCP, in either direction, so the servers I run are not reachable from here and an agent's tools are whatever its own CLI brought. I can fork the harness. I cannot fork the thing doing the thinking.