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 639029d
Browse filesBrowse the repository at this point in the historyBrowse files
fix(analyst): let analyst read workspace memory and steer it to workspace skills (AltimateAI#1570)
* fix(analyst): let analyst read workspace memory and steer it to workspace skills
In a linked project the read-only analyst agent could not call any memory
tool, yet the workspace identity section told it to save with
`altimate_memory_write` and check `altimate_memory_read`. Its prompt named
only the built-in data skills and required every reply to finish through
`answer_commit`, which suits data values, not a list of conventions.
- analyst may call `altimate_memory_read`, `altimate_memory_refresh` and
`altimate_memory_audit`; write, delete and extract stay denied, and
data-explorer is unchanged.
- The team-memory line names only the memory tools the session's agent can
call: a read-only agent is pointed at the read tool and told that builder
saves; an agent with neither gets no line.
- The analyst prompt loads a matching skill by source precedence, answers
questions about team conventions in plain text from skills and memory,
and keeps `answer_commit` for data questions.
FixesAltimateAI#1569
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* fix(memory): stop the empty memory-read result from naming the write tool
analyst can now call `altimate_memory_read` but not `altimate_memory_write`.
An empty read told it to "Use altimate_memory_write to save information",
steering a read-only agent toward a call it cannot make. The result now
only says that no blocks were found.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* test(analyst): pin the data-question scope of the answer_commit finalization rule
The analyst prompt now limits answer_commit to data questions and lets
workspace-knowledge answers finish in plain text; update the pinned
finalization assertion and pin the new exclusion sentence.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* fix(analyst): match the memory line to the tools the turn actually sends
- Share one removal rule (`LLM.removedTools`) between tool resolution and
the workspace identity section, so a memory tool switched off on the
request, or not registered, is not named in the prompt.
- A write-only agent gets the save line without the read-first step.
- The analyst prompt checks `altimate_memory_read` only when it has it.
- Update the analyst prompt assertion in sql-validation-e2e to the new
finalization wording.
- Cover all four read/write combinations and one cached outcome rendered
for different agents.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* fix(analyst): state what a memory reload changes, and test the prompt wiring
- The analyst permission comment now says a reload syncs like the load
every session runs and can drop a local copy of an archived block,
rather than calling it read-only.
- The prompt comment scopes the memory line to the tools the agent and
request keep; tool-free steps withhold every tool the prompt names.
- A prompt-loop test checks that the identity section is given the same
memory access the tools handed to the model call imply.
- Document analyst's memory and workspace-skill access.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* docs(analyst): list workspace memory and skills in the agents reference
Match the agent-modes page, and name the prompt-loop memory tests by
what they check.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
* docs(analyst): describe the memory audit log and what a reload changes
Add an analyst turn with no memory tools to the prompt-loop test and name
the test for what it asserts.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* fix(analyst): scope the no-save line to memory blocks and note what a reload removes
Analyst keeps training_save for corrections to its own behavior, so the
read-only memory line now refers to workspace memory blocks only and no
longer names one specific agent. The refresh tool description says it can
remove local copies of archived blocks.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
---------
Co-authored-by: Claude Opus 5.5 <[email protected]>
-**Web**: Fetch and search allowed without prompts
30
30
-**Schema/warehouse/finops**: All inspection tools available
31
+
-**Workspace knowledge**: Loads workspace and project skills; reads workspace memory and views this checkout's memory audit log. Reloading memory syncs the local copy with the workspace, which can remove a local copy of a block the workspace archived. Saving memory is done with `builder`.
31
32
32
33
!!! tip
33
34
Use `analyst` when exploring data to ensure no accidental writes. Switch to `builder` when you're ready to create or modify models.
Copy file name to clipboardExpand all lines: docs/docs/data-engineering/agent-modes.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -134,6 +134,7 @@ Estimated savings: ~60 credits/week (71% reduction on this query alone)
134
134
- Search warehouse metadata
135
135
- Detect PII columns
136
136
- Save training entries
137
+
- Read and reload workspace memory, view this checkout's memory audit log, and answer questions about team conventions from workspace skills (saving memory is done with builder)
Copy file name to clipboardExpand all lines: packages/opencode/src/altimate/prompts/analyst.txt
+5-2Lines changed: 5 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,10 @@ Treat inferred text labels as data: fixed rubric, stable IDs, coverage and dupli
10
10
Use selected columns, partition filters and LIMIT/sampling to inspect cheaply; estimates are not exact final computations. Read JSONL spill paths with `read`; spills contain returned rows, not necessarily all matches. Aggregate in SQL for exact answers. On timeout, revise the query. Report costs only from evidence.
11
11
12
12
## Skills
13
-
Use `skill` when available: /data-question, /cost-report, /query-optimize, /sql-translate, /dbt-analyze, /lineage-diff, /data-viz. File-writing steps require the builder agent.
13
+
Use `skill` when available. When the skill list in your system prompt has one matching the request, load it, following the list's source precedence; workspace and project skills are included. Built-in data skills include /data-question, /cost-report, /query-optimize, /sql-translate, /dbt-analyze, /lineage-diff and /data-viz. File-writing steps require the builder agent.
14
+
15
+
## Workspace knowledge
16
+
A question about the team's conventions, standards or past decisions is answered from workspace skills and memory, not from warehouse data: load the matching skill, check `altimate_memory_read` when it is in your tool list, and reply in plain text that states what was found or that nothing was found. Such a reply is not a data value, so do not finish it with `answer_commit`. You cannot save workspace memory blocks; when asked to save a team decision or convention, say that the builder agent can. A correction to your own behavior is still saved with `training_save`, as below.
14
17
15
18
## Teammate Training
16
19
You are a trainable AI teammate. Check the "Teammate Training" section in your system prompt for any learned patterns, rules, glossary terms, or standards. Always apply learned training when relevant.
@@ -20,4 +23,4 @@ Use `training_list` to review learned knowledge. Skills: /teach, /train, /traini
20
23
21
24
When the request supplies an output JSON schema (the `StructuredOutput` tool is available), finish with `StructuredOutput` instead of `answer_commit` or a plain-text reply; follow that schema. The text finalization rules below apply when no output schema is supplied.
22
25
23
-
Finish by calling `answer_commit` with the single chosen value(s) with one field per item the request asks for (every named item, such as an entity and its related item or count, must be its own field: when the request asks for only the answer, anything left in the basis or prose is dropped), a one-or-two-sentence basis (population, grain, source object/column), or `unresolved` with the reason, then reply with exactly the text it returns and nothing else. Always supply `basis`, even when unresolved; it is never shown when the request asks for only the answer. Never list excluded candidates or alternative answers; a top-N with a tie at the boundary still returns N concrete rows (note the tie briefly in `rows.note`); when the request asks for only the answer or a specific format, set `answer_only`. If `answer_commit` is unavailable, finish with one or two sentences of basis and a final line `**Answer:** <requested value(s), with units>`, or `**Answer:** unable to determine — <why>`; when the request asks for only the answer or a specific format, the final message is exactly the requested value(s) or table in the requested format, with no label and no basis (or `unable to determine — <why>` if unresolved); never guess.
26
+
For a data question, finish by calling `answer_commit` with the single chosen value(s) with one field per item the request asks for (every named item, such as an entity and its related item or count, must be its own field: when the request asks for only the answer, anything left in the basis or prose is dropped), a one-or-two-sentence basis (population, grain, source object/column), or `unresolved` with the reason, then reply with exactly the text it returns and nothing else. Always supply `basis`, even when unresolved; it is never shown when the request asks for only the answer. Never list excluded candidates or alternative answers; a top-N with a tie at the boundary still returns N concrete rows (note the tie briefly in `rows.note`); when the request asks for only the answer or a specific format, set `answer_only`. If `answer_commit` is unavailable, finish with one or two sentences of basis and a final line `**Answer:** <requested value(s), with units>`, or `**Answer:** unable to determine — <why>`; when the request asks for only the answer or a specific format, the final message is exactly the requested value(s) or table in the requested format, with no label and no basis (or `unable to determine — <why>` if unresolved); never guess.
0 commit comments