amenbo 13.1.0 — an AI in an app reaches the projects you pick
An AI connected over MCP can be shown a project's backlog and add tasks to it, without ever opening the folder. You choose, per app, which projects it reaches.
An AI that cannot open a folder can now reach amenbo projects. Through 13.0.0, only an AI you started inside the folder could work with amenbo.
An AI that cannot open a folder reaches your projects
amenbo is built around an AI that runs in a folder and reads and writes there. An AI inside a chat app cannot open that folder, so it could not be shown the backlog and could not add a task.
In 13.1.0 an AI in an app connected over MCP reaches the projects you chose for it. Three things reach the AI: the whole of how to work in that folder, the spec of a single command, and running a command.
bind and init are refused — those are the two that would re-point a folder at a different project. The server is started by the app, not by a command you type yourself.
You choose, per app, which projects it may reach
In the sidebar there is an entry called Connect via MCP. Eight apps are listed: Claude Desktop, Claude Code, Cursor, VS Code, Codex CLI, Gemini CLI, Antigravity, GitHub Copilot CLI.
Open a row and you tick the projects that app may reach, under “Projects this app may reach”. What you tick is what goes over. Handing it over replaces that app’s entry whole — the folders it already reaches included. With nothing ticked, the button that hands it over cannot be pressed.
There are two roads, and which one a row offers depends on the app.
| App | How it is handed over |
|---|---|
| Claude Desktop | Save the settings file — open the saved file and the server goes in, folders and all |
| The other seven | Copy the request — paste it to that app’s own AI and it edits the settings |
To take it back out there is a button labelled Copy a request to remove it.
Set up is not the same as pointing at the right folder
Each row says whether the app is Set up or Not set up, and names the folder that entry reaches. Both are read back from the app itself.
Being set up and pointing where you think it points are two different things. An entry still aimed at a folder you no longer work in used to look exactly like a correct one. An entry left behind by an older amenbo is marked as such, and can be removed from there.
No wiring asked of a folder that opens no terminal
amenbo asks you to wire the AI in a folder so that it reads amenbo at the start of a session. A folder where nothing opens a terminal does not need that wiring, so the prompt no longer appears for folders only MCP reaches.
Getting it
Open the installer for your OS from the latest release. No admin rights are needed.
- macOS —
.pkg, one for Apple silicon and one for Intel (GUI and CLI come together; first open shows a Gatekeeper prompt: right-click → Open) - Windows — setup
.exe(GUI and CLI come together) - Linux — the GUI is an AppImage; the
amenbocommand comes from the CLI installer
To update: on the GUI, the “a newer version is available” banner applies it in place. If you installed only the CLI, amenbo update --apply swaps it.
The stored data format does not change, so data from the previous version opens as it is.
New here? See Start.