teamtrail 0.32.0-next.46 → 0.33.0-next.47

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 CHANGED
@@ -75,7 +75,7 @@ tool_timeout_sec = 900
75
75
 
76
76
  ### Keep agents out of Teamtrail's config folder
77
77
 
78
- Teamtrail's config folder (`$TEAMTRAIL_CONFIG_DIR`, else `$XDG_CONFIG_HOME/teamtrail`, else `~/.config/teamtrail`) holds this machine's key, which signs your answers, your approvals and tracker credentials. `connect claude` adds deny rules for it to Claude Code's user settings (`~/.claude/settings.json`): `Read(//<folder>/**)` and `Edit(//<folder>/**)` in `permissions.deny`, and the folder in `sandbox.filesystem.denyRead` and `denyWrite` for sandboxed commands. It keeps what is already there (and the file's indentation, writing atomically and through a symlink), adds nothing twice, and prints what it added and how to remove it. The rules are best effort unless Claude Code's sandbox is on: without it they stop Claude's own file tools, but a shell command such as `cat` can still read the folder. A folder whose path has characters a rule would read as a pattern (`* ? [ ] { } ( ) \ !`) is not written; connect prints the rules to add by hand. Codex can deny a folder only through a default permissions profile, which changes how it sandboxes every folder, so `connect codex` only prints that profile as a suggestion: until you add it, Codex's commands can still read the folder, `machine.key` included. With a custom `$TEAMTRAIL_CONFIG_DIR`, the default `~/.config/teamtrail` is denied too, and a folder not created yet is named where it will really be (through a symlinked `~/.config`). Teamtrail's own MCP server is not affected: agents don't apply these rules to the MCP servers they start. Pass `--no-protect-config` to skip this.
78
+ Teamtrail's config folder (`$TEAMTRAIL_CONFIG_DIR`, else `$XDG_CONFIG_HOME/teamtrail`, else `~/.config/teamtrail`) holds this machine's key, which signs your answers, your approvals and tracker credentials. `connect claude` adds deny rules for it to Claude Code's user settings (`~/.claude/settings.json`): `Read(//<folder>/**)` and `Edit(//<folder>/**)` in `permissions.deny`, and the folder in `sandbox.filesystem.denyRead` and `denyWrite` for sandboxed commands. It keeps what is already there (and the file's indentation, writing atomically and through a symlink), adds nothing twice, and prints what it added and how to remove it. The rules are best effort unless Claude Code's sandbox is on: without it they stop Claude's own file tools, but a shell command such as `cat` can still read the folder. So `connect claude` asks whether to turn the sandbox on for the project (`"sandbox": { "enabled": true }` in `.claude/settings.local.json`; Enter is yes): `--sandbox` turns it on and `--no-sandbox` leaves it, without asking. Turning it on also sets `autoAllowBashIfSandboxed: false` unless your settings already choose, so Claude Code still asks before running commands as it did; the sandbox asks before each new network domain, and on Linux it needs `bubblewrap` and `socat` (without them Claude Code runs commands unsandboxed). Without a terminal and without a flag it changes nothing and prints how to turn it on; a sandbox your settings already turn on is left as it is, and one they turn off changes only on your yes or `--sandbox`. A folder whose path has characters a rule would read as a pattern (`* ? [ ] { } ( ) \ !`) is not written; connect prints the rules to add by hand. Codex can deny a folder only through a default permissions profile, which changes how it sandboxes every folder, so `connect codex` only prints that profile as a suggestion: until you add it, Codex's commands can still read the folder, `machine.key` included. With a custom `$TEAMTRAIL_CONFIG_DIR`, the default `~/.config/teamtrail` is denied too, and a folder not created yet is named where it will really be (through a symlinked `~/.config`). Teamtrail's own MCP server is not affected: agents don't apply these rules to the MCP servers they start. Pass `--no-protect-config` to skip this.
79
79
 
80
80
  ### Other agents
81
81