octo-agent

The deciding trait is how little stands between you and working. One script, one binary, no Node or Python or Ruby to install first, and the thing is answering. For anyone who has spent an evening resolving a dependency conflict before an agent would say hello, that is a genuinely different first hour.

What you should weigh is that speed of setup is not the same as quality of judgement, and this one is young. Pick it for a scratch machine and small jobs. Pick something older for the code that pays you.

Defaults are a safety decision and this one chose the other way. Every dangerous capability is switched on before a user has formed an opinion about the tool, which means the moment of highest ignorance coincides with the moment of maximum permission, and the project advertises that as the selling point rather than as a warning.

What it does right is keep the process local. Nothing is described as leaving the machine, so the exposure is bounded by the account you ran it under rather than by a vendor's retention policy.

1. The dual positioning is not a neutral choice. A coding agent can be evaluated against a compiler and a test suite; an assistant cannot, and a design that serves both tends to inherit the weaker standard rather than the stronger one. 2. Nothing in the published description closes the loop after an edit.

2. Capability breadth is documented precisely while correctness is not documented at all, which is a consistent pattern across this catalogue and worth naming each time it appears.

Under a hundred stars is the zone where a project is one person's enthusiasm and nothing more. That is not an insult, it is a forecast: the maintenance curve for a self-hosted binary is shallow but it never ends, and there is no revenue, no sponsor and no institution to absorb it when the enthusiasm moves elsewhere.

Moat: none, and Go agents are being written faster than anyone can list them. Likely path: dormancy inside a year unless adoption changes shape. Position: fine for personal use, and vendor the source if it ever touches something that matters.

The exclusions come first. Windows is unsupported, which removes a third of my desks before any other question, and the installation is a script piped from a website, which my endpoint policy declines on principle. Neither is fatal on its own and together they mean packaging work my team would own.

After that, there is nothing to govern with: no central configuration, no record of use, and a permissive licence that answers legal and nobody else. Not yet, and the shape of this is a personal tool rather than a company one.

Supporting two protocols directly rather than adapting one to the other is the correct amount of work, and it means the endpoint list is open-ended instead of being whatever the author had keys for. My servers connect through the standard protocol, skills are files, and sub-agents come from the same binary rather than a plugin system.

Permissive licence, compiled artefact, nothing calling home, and the whole thing stays on hardware I control. My only complaint is that reaching further means writing Go, which is a fine complaint to have.