@fibteq/altair-runner 0.3.1 → 0.4.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.
- package/README.md +9 -0
- package/dist/cli.js +43 -43
- package/dist/index.js +38 -38
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -78,6 +78,15 @@ 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.
|
|
89
|
+
|
|
81
90
|
### For apps that run it (the desktop app)
|
|
82
91
|
|
|
83
92
|
- `ALTAIR_SERVER` and `ALTAIR_RUNNER_TOKEN` override the saved pairing, and an env token is never written to disk.
|