Octopus CLI
Octopus CLI works with projects, agents and tasks in a shared local runtime, retaining history and results across clients.
- 760 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The runtime can execute commands and change files in its permitted environment, with admitted tasks continuing after the client exits.
Install
- Works in
Manual install
git clone https://github.com/miuuyy/Octopus-SI-OS.gitDownloads sources. From the clone, follow the terminal guide with `npm ci --prefix app` and `npm --prefix app run build:cli`.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The runtime can execute commands and change files in its permitted environment, with admitted tasks continuing after the client exits.
This is third-party code. Review the repository files before installing.
What it does
Octopus CLI opens the same projects and tasks available in the desktop client. Users select an agent, model and work scope, submit a message and read results. History persists in the shared runtime directory. Tools and execution environments are separate interfaces. Policy can let an agent create future tasks and add capabilities. The project studies this architecture; the terminal client provides access to its current implementation.
Who it is for. For developers testing Octopus from a terminal in a separate trial project.
Good fit when
- Submit an Octopus task from the terminal and inspect its result later.
- Select a separate model and permissions for a project.
- Read retained results without desktop mouse control.
- Keep tasks and future-work conditions in an experimental workflow.
Not a fit when
- You need a proven stable production platform.
- You expect demonstrated autonomous agent improvement.
- Environment tools must not access working files.
Example request
Open the test Octopus project and show agent permissions and saved tasks without running new workspace commands.Limitations
The current distribution targets macOS 14 or later with Node.js 24, Rust and Xcode Command Line Tools. Standard setup needs a ChatGPT account, whose models and limits apply. This is a research preview without demonstrated useful self-improvement or spontaneous model initiative. Working tools can execute commands and change files inside their permitted environment, so begin in a separate project with narrow permissions.
How to disable. Run `./octopus stop <task-id>` with the intended task ID and check that its stopped result is recorded. Exiting the CLI alone does not terminate the execution service or admitted tasks.
FAQ
How is the terminal client built?
After preparing dependencies, run `npm --prefix app run build:cli`, then open `./octopus`.
Must desktop run to build the CLI?
No. The command builds terminal modules and runtime without opening the desktop app.
How do I select existing history?
Pass its exact directory through `--home`. The terminal has no separate task store.
How do I find commands?
Type `/` in the terminal. `/help` lists controls; `/tasks` and `/resume` continue work.
Can work continue across clients?
Yes. Desktop and terminal share Home, projects and recorded results.
Discussion
No questions or reviews yet.
Related
CLI toolsA local web workspace with two persistent terminals: Codex sets the task and a second CLI agent writes the code.
A tmux-based TUI that runs Claude Code, Codex and other agents in one list: status, quick prompts, worktrees and diff review
CLI Agent Orchestrator
CLI Agent Orchestrator (CAO)
A CLI that coordinates several coding agents: a supervisor delegates tasks to specialists in parallel or in sequence across isolated tmux sessions
A local dashboard for many Claude Code sessions: each job gets its own context and todo, agents spawn child agents and message each other
An AI-agent workspace with parallel worktrees, cross-provider orchestration, and bots across chat channels.
A CLI starts 49 Agents IDE, bringing terminals and files from multiple machines onto one zoomable canvas.
README in short
Source changes do not automatically update packages already installed in a Home. Documentation requires matching client and package versions and preserves configured state when package checks fail.