@hanskristoffer/agentpool 0.22.0 → 0.23.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 (2) hide show
  1. package/README.md +2 -2
  2. package/package.json +5 -5
package/README.md CHANGED
@@ -47,7 +47,7 @@ agentgate service install # launchd (macOS) or systemd --user (Linux)
47
47
 
48
48
  You can do every setup step with the CLI. To use the native app, build it with `bun run build:desktop` and open **Agentgate.app**. It connects to `http://127.0.0.1:7878` by default. On a fresh machine, **Set up this machine** installs the bundled CLI in `~/.config/agentgate/bin`, initializes the store, and starts a launchd service. Add that folder to your shell PATH to use the CLI. Closing or removing the app leaves that service and its CLI running.
49
49
 
50
- The app has Overview, Accounts, MCP servers, Skills, Projects, Machines, T3 Code, and Settings screens; request activity is a tab in Settings. **Settings → Configure coding tools** generates the Claude/Codex folders and T3 settings. The app's service and coding-tool controls apply only to its configured local daemon; remote setup and services use the CLI on that machine.
50
+ The app has Overview, Accounts, MCP servers, Skills, Projects, Machines, T3 Code, and Settings screens; request activity is a tab in Settings. **Settings → Configure coding tools** generates the Claude/Codex folders and T3 settings. The app's service and coding-tool controls apply only to its configured local daemon; remote setup and services use the CLI on that machine. The one exception is routing: Machines shows whether each machine's own Claude Code and Codex go through agentgate, and its row menu turns that on or off there.
51
51
 
52
52
  ## A second machine (e.g. an always-on server)
53
53
 
@@ -89,7 +89,7 @@ One instance per provider covers every account; the daemon switches eligible acc
89
89
 
90
90
  ### Or: your normal Claude login
91
91
 
92
- `agentgate setup --primary` adds `ANTHROPIC_BASE_URL` to `~/.claude/settings.json` and the agentgate MCP server to `~/.claude.json`, so the Claude Code you already use (and T3's default Claude instance) goes through agentgate while keeping its own login. Where Claude Code has never been signed in, such as on a new server, it also sets a placeholder `ANTHROPIC_AUTH_TOKEN`, because Claude Code won't start without a login; agentgate signs each request with a pooled account either way. Claude Desktop is not affected: it sets its own API address; see [Claude Desktop](docs/user/claude-desktop.md). For only the MCP servers, use `agentgate setup --mcp`. That, and `setup --primary`, also write `~/.cursor/mcp.json`, so Cursor and the Cursor CLI get the same servers. Start a new session to pick them up. Model requests use the pool; other requests keep your login, and your login is also the last resort when every pooled account is exhausted. Undo with `agentgate setup --primary off` (the previous base URL is restored, and later settings edits are preserved). It does the same for `~/.codex/config.toml` (or `$CODEX_HOME`): an `agentgate` model provider with `requires_openai_auth = true`, so Codex, the Codex app and T3's default Codex instance send their own ChatGPT login along as the last resort. Only do this with `agentgate service install`, or Claude Code and Codex can't reach their providers while the daemon is down.
92
+ `agentgate setup --primary` adds `ANTHROPIC_BASE_URL` to `~/.claude/settings.json` and the agentgate MCP server to `~/.claude.json`, so the Claude Code you already use (and T3's default Claude instance) goes through agentgate while keeping its own login. Where Claude Code has never been signed in, such as on a new server, it also sets a placeholder `ANTHROPIC_AUTH_TOKEN`, because Claude Code won't start without a login; agentgate signs each request with a pooled account either way. Claude Desktop is not affected: it sets its own API address; see [Claude Desktop](docs/user/claude-desktop.md). For only the MCP servers, use `agentgate setup --mcp`. That, and `setup --primary`, also write `~/.cursor/mcp.json`, so Cursor and the Cursor CLI get the same servers. Start a new session to pick them up. Model requests use the pool; other requests keep your login, and your login is also the last resort when every pooled account is exhausted. Undo with `agentgate setup --primary off` (the previous base URL is restored, and later settings edits are preserved). It does the same for `~/.codex/config.toml` (or `$CODEX_HOME`): an `agentgate` model provider with `requires_openai_auth = true`, so Codex, the Codex app and T3's default Codex instance send their own ChatGPT login along as the last resort. Where Codex has never been signed in, it writes a placeholder API key to `~/.codex/auth.json`, so `codex login status` and T3 Code see Codex as signed in; undo removes it again. Add `--node <name>` to switch a paired machine from the one you are on. Only do this with `agentgate service install`, or Claude Code and Codex can't reach their providers while the daemon is down.
93
93
 
94
94
  ### Hand threads between machines
95
95
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@hanskristoffer/agentpool",
3
- "version": "0.22.0",
3
+ "version": "0.23.0",
4
4
  "license": "UNLICENSED",
5
5
  "repository": {
6
6
  "type": "git",
@@ -22,9 +22,9 @@
22
22
  "agentgate": "bin/agentpool.js"
23
23
  },
24
24
  "optionalDependencies": {
25
- "agentpool-darwin-arm64": "0.22.0",
26
- "agentpool-darwin-x64": "0.22.0",
27
- "agentpool-linux-x64": "0.22.0",
28
- "agentpool-linux-arm64": "0.22.0"
25
+ "agentpool-darwin-arm64": "0.23.0",
26
+ "agentpool-darwin-x64": "0.23.0",
27
+ "agentpool-linux-x64": "0.23.0",
28
+ "agentpool-linux-arm64": "0.23.0"
29
29
  }
30
30
  }