One requestMultiple projectsAgents working together

A request such as adding team invitations can require changes to the frontend, backend, and docs. Give it to a coordinating agent to organize work across those projects, track dependencies, and collect results, reducing the tasks and context you have to pass between sessions yourself.

Working across directories or launching a subagent does not by itself guarantee that the target project’s full configuration is loaded. When instructions or Skills depend on the parent conversation passing them along, rules can be missed or contexts mixed; loading behavior varies by tool. Octoboard starts an independent native session of the chosen agent in each project directory, so that agent loads local configuration through its own mechanisms while the coordinator organizes the work.

Projects may already depend on different agent brands, and their instructions and tools are not interchangeable. Choose Claude Code, Codex, or Grok Build independently for the coordinator and each project; each keeps its own toolchain, while Octoboard passes tasks, relevant context, and reports between sessions.

A requirement or code detail may be easier to explain directly to the project agent doing the work. You can enter its conversation to add context, adjust requirements, or review code; sessions started by the coordinator still report results, open items, and decisions needed back to it.

Ongoing conversations, project knowledge, and reports can help it understand your product and engineering structure, including which projects a request affects. That understanding depends on the context available to the session; keeping it up to date reduces repeated explanations.

Development of the macOS Apple Silicon version is complete, and its installer is coming soon on GitHub Releases. Linux, Windows, iOS, and Android versions are planned and are not yet available.

Install and sign in to the agent CLIs you want to use. Octoboard is free and open source under the MIT License; it does not provide provider accounts or model credits. Any agent or model service fees depend on the account and plan you choose and are charged by that provider. Octoboard adds no extra fees.

Octoboard stores its application data locally and does not upload code or conversations to servers run by its developer. Your configured agents and tools may send data to their providers, collaboration may share task information with multiple providers, and Git operations may contact remote repositories; see the privacy policy for details.

Not yet: remote host support is planned, so you could coordinate locally while projects and agents run on a host you choose. Connection methods, transmitted information, and data handling will be explained before release.