Skip to content

Commit 93685b3

Browse files
hkaltaiclaude
andcommitted
docs(analyst): name what analyst keeps instead of calling it read-only
The FAQ, quickstart, tools and permissions pages said analyst's write tools stay denied without exceptions. Only its shell and built-in write tools are re-denied after config: it still saves training entries and creates session scratch tables, and MCP or custom tools follow the user's config. Each page now says so, matching the agents table. Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent e5beb92 commit 93685b3

4 files changed

Lines changed: 4 additions & 4 deletions

File tree

‎docs/docs/configure/permissions.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ Override permissions for specific agents:
8080
}
8181
```
8282

83-
The `analyst` agent is read-only regardless of config: its shell and write tools (file edits, SQL writes, memory saves and other built-in write tools) stay denied even if its permission config allows them. Training entries remain available through `training_save` and `training_remove`. Config can still restrict analyst further.
83+
The `analyst` agent's shell and built-in write tools (file edits, SQL writes, memory saves and the other built-in tools that change state) stay denied even if its permission config allows them. Training entries remain available through `training_save` and `training_remove`, and analyst can create session scratch tables. MCP and custom tools follow your config, and config can still restrict analyst further.
8484

8585
Rules are evaluated in order and the last matching rule wins, so put a `"*"` rule before the more specific patterns it should not override.
8686

‎docs/docs/configure/tools.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ Disable a tool for a specific agent by setting its permission to `"deny"`:
7373
```
7474

7575
!!! example "Builder with file edit tools denied"
76-
The configuration above denies the builder agent's `write` and `edit` tools. The builder can read and explore the codebase. It must ask before running other shell commands, and `dbt run` is blocked entirely. An approved shell command can still modify files. The `analyst` agent is already read-only: its shell and write tools stay denied whatever its permission config says. It can still save training entries and create session scratch tables for analysis.
76+
The configuration above denies the builder agent's `write` and `edit` tools. The builder can read and explore the codebase. It must ask before running other shell commands, and `dbt run` is blocked entirely. An approved shell command can still modify files. The `analyst` agent's shell and built-in write tools are already denied whatever its permission config says. It can still save training entries and create session scratch tables for analysis, and MCP or custom tools follow your config.
7777

7878
## Tool Behavior
7979

‎docs/docs/getting-started/quickstart.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -251,7 +251,7 @@ Set tool permissions for each agent mode in `altimate-code.json`:
251251
}
252252
```
253253

254-
Analyst's shell and write tools are always denied, so config can only restrict analyst further.
254+
Analyst's shell and built-in write tools are always denied, so config cannot turn them on. It can still save training entries, and MCP or custom tools follow your config.
255255

256256
### Project rules with AGENTS.md
257257

‎docs/docs/reference/security-faq.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ Yes. Use pattern-based permissions to deny destructive SQL:
9696
}
9797
```
9898

99-
You can also configure per-agent permissions. For example, keep the `builder` agent from editing files and allow only `SELECT` shell commands. The `analyst` agent is already read-only: its shell and write tools stay denied whatever its config says.
99+
You can also configure per-agent permissions. For example, keep the `builder` agent from editing files and allow only `SELECT` shell commands. The `analyst` agent's shell and built-in write tools are already denied whatever its config says. It can still save training entries and create session scratch tables, and MCP or custom tools follow your config.
100100

101101
```json
102102
{

0 commit comments

Comments
 (0)