@fibteq/altair-runner 0.4.0 → 0.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +16 -8
  2. package/dist/cli.js +25 -25
  3. package/dist/index.js +23 -23
  4. package/package.json +1 -1
package/README.md CHANGED
@@ -78,14 +78,22 @@ With `edit`, the CLI can change files in the folder but cannot run commands that
78
78
 
79
79
  Tasks in the same Altair thread continue the same Claude Code session (`--resume`), so follow-ups keep context.
80
80
 
81
- ### Claude Code as the thread's agent (experimental)
82
-
83
- When a project's **Thread agent** setting is "Claude Code on the computer", Claude Code does not just run tasks for
84
- Altair's agent: it is the thread's agent. Each turn of the thread is one `claude -p` run, resumed from the thread's
85
- previous session, with Altair's tools (reply, plan, decisions, artifacts, memory) added over MCP (`--mcp-config`,
86
- allowed with `--allowedTools mcp__altair`). The MCP endpoint is `<server>/api/agent-mcp/<thread>` and its token is
87
- valid only for that turn; the config file holding it is readable only by you and deleted when the run ends. The whole
88
- turn uses your own Claude Code login. Needs Claude Code as the project's CLI and altair-runner 0.4.0 or later.
81
+ ### Your CLI as the thread's agent
82
+
83
+ When a project works in one of your folders, your CLI does not just run tasks: it is the thread's agent. Each turn of
84
+ a thread is one run of the CLI (Claude Code resumes the thread's previous session), with Altair's tools (reply, plan,
85
+ decisions, artifacts, memory, routines) added over MCP:
86
+
87
+ | CLI | How the MCP server is added |
88
+ |---|---|
89
+ | Claude Code | `--mcp-config <file>`, allowed with `--allowedTools mcp__altair` |
90
+ | Codex CLI | `-c mcp_servers.altair.url=…` and `-c mcp_servers.altair.bearer_token_env_var="ALTAIR_MCP_TOKEN"` |
91
+ | Gemini CLI | its own settings file, through `GEMINI_CLI_SYSTEM_SETTINGS_PATH` |
92
+
93
+ The MCP endpoint is `<server>/api/agent-mcp/<thread>` and its token is valid only for that turn. Config files holding
94
+ it are readable only by you and deleted when the run ends; Codex gets it in its environment instead. The whole turn
95
+ uses your own CLI login. Needs altair-runner 0.4.0 or later for Claude Code, 0.5.0 or later for Codex and Gemini CLI.
96
+ Projects without a local folder are worked in the cloud by OpenCode, in the thread's own sandbox.
89
97
 
90
98
  ### For apps that run it (the desktop app)
91
99