You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 853bfa0
Browse filesBrowse the repository at this point in the historyBrowse files
fix: address review findings in the tool CLI, MCP server and workspace tools
- `daemon`: requests wait for an in-progress file release, `stop` replies
before shutting down, and the daemon key includes
`ALTIMATE_DISABLE_SCHEMA_VALUES`, `ALTIMATE_INTEGRATIONS` and
`ALTIMATE_DISABLE_WORKSPACE`.
- `permissions`: the blocked-statement check runs before the read-permission
shortcut.
- `claude-md`: a symlinked `CLAUDE.md` is left untouched.
- `workspace-tools`: workspace-authored names and descriptions render as one
inert line, skills are read through `WorkspaceClient.readSkill`, and the
workspace is labelled with `workspaceLabel`.
- MCP workspace adapter: an adapter is closed only after the operations
using it finish; `serverInstructions` releases file connections it opened.
- `outputLimits` reads organisation-managed config and preferences.
- `schema-list`: MySQL and Redshift (whose drivers ignore binds) get an
escaped schema literal; schema names are sorted before the limit.
- `registry.releaseFileConnections` keeps remote and in-memory URI stores.
- `sql_execute` batches: `truncated` reports row-limited or clipped items,
references resolve against the default warehouse, duplicate labels are
rejected, backslashes are escaped for BigQuery, Snowflake, Databricks and
ClickHouse, and an unmaterialized spill returns no table.
- `answer_commit`: integers keep every digit; coverage and number checks
stand down when the run budget is ending (one shared `budgetEnding`).
- `warehouse_add` resolves relative store paths against the project root;
`warehouse_list` skips only workspace-routed connections in discovery.
- `analyst-effort` honours SAP `modelParams` and the configured
`model.variants`.
- Workspace client: `readSkill` opens with `O_NOFOLLOW`; context lists only
skills with a regular `SKILL.md`. `releaseLocalSession` clears every
per-session map; skill withdrawal runs in `finally` on purge.
- MongoDB `listTables` checks that an empty database exists.
- Docs and `--allow-write` help match the actual policies.
- Tests for each behaviour change; new suites restore their spies.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Copy file name to clipboardExpand all lines: docs/docs/configure/mcp-servers.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ Source writes are refused by default. Without `--allow-write`, source queries re
41
41
42
42
<!-- altimate_change end -->
43
43
44
-
The server writes only MCP protocol messages to stdout and sends logs to stderr. It does not initialize telemetry and honors `ALTIMATE_TELEMETRY_DISABLED`.
44
+
The server writes only MCP protocol messages to stdout and sends logs to stderr. It honors `ALTIMATE_TELEMETRY_DISABLED`.
Copy file name to clipboardExpand all lines: docs/docs/usage/tool.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: "Call Altimate Code data tools from any shell, agent or CI job with
5
5
6
6
# Tool CLI (Headless)
7
7
8
-
Expose the data tools -- warehouse, SQL, schema, lineage, impact, PII, data-diff, FinOps and dbt -- as plain commands. No model or API key is involved, so Claude Code, Codex and CI jobs can call them directly.
8
+
Expose the data tools -- warehouse, SQL, schema, lineage, impact, PII, data-diff, FinOps and dbt -- as plain commands. The local data tools use no model or API key, so Claude Code, Codex and CI jobs can call them directly. Linked workspace tools authenticate to Altimate and `workspace_execute` may use backend models.
9
9
10
10
## List tools
11
11
@@ -14,15 +14,15 @@ altimate-code tool list # id and description
14
14
altimate-code tool list --json # id, description and JSON input schema
15
15
```
16
16
17
-
`tool` and `mcp serve` share one implementation, so compact schemas, `sql_execute` with `tables`, `query_from` chaining, spilled result files, read-only enforcement and `answer_commit` (with its `request` argument) behave the same in both. `tool` exposes the full tool list. In a project linked to a workspace it also exposes `workspace_context`, `workspace_skill` and `workspace_execute`; the link is read from the project's saved state, with no network request. Pass `--workspace-tools` to add them to an unlinked project, or `--no-workspace-tools` to leave them out of a linked one.
17
+
`tool` and `mcp serve` share one implementation, so compact schemas, `sql_execute` with `tables`, `query_from` chaining, spilled result files, read-only enforcement and `answer_commit` (with its `request` argument) are consistent in both. Their permission policies differ: the CLI requires `--allow-write` for local configuration writes such as `warehouse_add`, while `mcp serve` allows `warehouse_add` by default. `tool` exposes the full tool list. In a project linked to a workspace it also exposes `workspace_context`, `workspace_skill` and `workspace_execute`; the link is read from the project's saved state, with no network request. Pass `--workspace-tools` to add them to an unlinked project, or `--no-workspace-tools` to leave them out of a linked one.
Prints the analyst method and the connections known at startup (the same text `mcp serve` sends as its instructions), so a shell agent gets it in one call.
25
+
Prints the analyst method and the connections known at startup (the same base instructions `mcp serve` sends, plus the linked workspace's name, skills and tools when workspace tools are enabled), so a shell agent gets it in one call.
26
26
27
27
## Run a tool
28
28
@@ -64,7 +64,7 @@ altimate-code tool daemon status
64
64
altimate-code tool daemon stop
65
65
```
66
66
67
-
`status` and `stop` locate the running daemon the same way `run` does: by project directory, CLI version, the `--connections` file (if any), whether workspace tools are on, and the caller's `ALTIMATE_CODE_CONN_*`environment variables. Run them with the same flags and`ALTIMATE_CODE_CONN_*` variables as the call that started the daemon, or they will report no daemon running for this project even though one is.
67
+
`status` and `stop` locate the running daemon the same way `run` does: by project directory, CLI version, the `--connections` file (if any), whether workspace tools are on, and the caller's `ALTIMATE_CODE_CONN_*`, `ALTIMATE_DISABLE_SCHEMA_VALUES`, `ALTIMATE_INTEGRATIONS` and `ALTIMATE_DISABLE_WORKSPACE`environment variables. Run them with the same flags and variables as the call that started the daemon, or they will report no daemon running for this project even though one is.
0 commit comments