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 d965a24
Browse filesBrowse the repository at this point in the historyBrowse files
Resolves the worker.ts conflict from main's trace-data-loss work (#895,
#901-905), which landed in parallel with this branch's trace extraction.
Both lines of work fix the same class of bug (traces losing data / being
clobbered) from different angles:
- this branch: extract the worker's inline event→trace logic into a shared
TraceConsumer and wire it into `altimate serve`, so the VS Code chat panel
(headless serve) writes traces at all (AI-6950).
- main #895+: stop finalizing on session.status=idle (idle fires every turn,
not at session end), rehydrate-from-disk on cache-miss re-creation, and a
streamGeneration guard against concurrent stream teardown.
Resolution: main's superior logic is the source of truth. The shared
TraceConsumer is now a faithful 1:1 port of main's *current* worker logic
(no idle finalize, rehydrateFromFile, streamGeneration guard, logUserMessage /
setPrompt-vs-setTitle split, synthetic/ignored skip). The worker delegates to
it; `serve` subscribes to it. This branch's earlier 2s grace-window heuristic
is dropped entirely — main's rehydrate-on-cache-miss is the deterministic fix
it was a stand-in for.
Source-grep regression guards that asserted the trace logic lived in worker.ts
are repointed at trace-consumer.ts (worker-trace-clearing, tracing-followups
#902, bridge-merge-invariants), with the guard intent preserved.
Verified: typecheck clean; trace-consumer, worker-trace-clearing, tracing-*,
and bridge-merge-invariants suites all green; host-level `serve` smoke test
writes a rich 42KB trace (session/user-message/generation spans).
Copy file name to clipboardExpand all lines: CHANGELOG.md
+35Lines changed: 35 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,41 @@ All notable changes to this project will be documented in this file.
5
5
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6
6
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
8
+
## [0.8.5] - 2026-06-06
9
+
10
+
### Fixed
11
+
12
+
-**The `github/review` composite action can be downloaded by GitHub Actions again.** The release tree contained three VS Code image symlinks whose removed targets caused GitHub's action downloader to reject the entire archive before the review step started. The images are now self-contained files and a release-critical test prevents dangling links from returning.
13
+
-**A valid dbt manifest is no longer mislabeled as a lint-only run.** Manifest availability is now checked independently from changed-model lookup, so new models and other valid manifests receive the correct full-run status.
14
+
-**The release-version lookup is rate-limit resilient and never caches a floating `latest`.** The composite action now authenticates its GitHub release-API call with the workflow token (lifting the 60→1,000 req/hr unauthenticated limit) and skips the binary cache entirely when the version resolves to `latest`, so a single rate-limited or offline lookup can no longer pin a stale binary across all subsequent runs.
15
+
-**Session traces survive worker restarts, concurrency, and long sessions without corruption or false alarms.** Three reliability follow-ups to the v0.8.4 trace-durability fix: reconstructed in-flight spans are marked `interrupted` and render with an amber "⚠" instead of red (and are excluded from the session error count) so a restart isn't misread as a failure (#901); `getOrCreateTrace` no longer resurrects a `Trace` into a cache that a concurrent stream switch already cleared, preventing an orphan writer under a dead stream (#902); and the on-disk `ses_<id>.json` projection is bounded to `MAX_SERIALIZED_SPANS` (default 5000, override via `ALTIMATE_TRACE_MAX_SPANS`), keeping head + tail and eliding the middle so long sessions no longer grow the file without bound or pay O(n²) write cost (#903).
16
+
17
+
### Added
18
+
19
+
-**Direct GitHub onboarding and a live dbt review demo.** The GitHub App installer now opens GitHub's repository-selection screen directly, and the README/docs link to the public `dbt-pr-review-demo` pull requests.
20
+
21
+
### Security
22
+
23
+
-**The hosted Altimate API key is no longer placed on the `jq` process arg list.** The credential write reads the key from the environment inside the `jq` program, keeping it out of `argv` (which is visible to other processes and printed verbatim when `ACTIONS_STEP_DEBUG` enables `set -x`).
24
+
25
+
## [0.8.4] - 2026-06-05
26
+
27
+
A trace-durability patch. Open `/traces` mid-session and you'd see a rich waterfall — then the moment the agent finished its turn the view collapsed to a single "system-prompt" span, the Summary tab's *"What was asked"* showed *"No prompt recorded"*, and the Chat tab dropped every user turn but the last. The data was genuinely gone from disk, not just hidden in the viewer. This release stops the on-disk trace from being overwritten after each turn and makes the file authoritative across worker restarts. A five-persona pre-release review drove a follow-up wording fix so a reconstructed trace isn't misread as a failed run.
28
+
29
+
### Fixed
30
+
31
+
- **Session traces no longer lose their data after every agent turn — the waterfall, summary prompt, and chat tab all stay intact.** A `session.status === "idle"` handler in the shared TUI worker fired once *per turn* (not once per session), ending the `Trace` and evicting it from cache; the next event reconstructed a fresh `Trace` whose near-empty initial state overwrote the rich `ses_<id>.json` on disk with a one-span file. Symptoms: the **Waterfall** collapsed to a lone "system-prompt" span, the **Summary** tab's *"What was asked"* went to *"No prompt recorded"*, and the **Chat** tab kept only the last user turn. The destructive idle handler is removed (sessions are long-lived — finalization happens on shutdown and `MAX_TRACES` eviction only), trace reconstruction now **rehydrates from the on-disk file** before falling back to a fresh start, and each user prompt is recorded as its own `user-message` span so multi-turn sessions render every turn in order. Authored-text scoping keeps synthetic parts (MCP banners, decoded file contents, reminders) out of the prompt and chat surfaces. Distinct from the v0.8.1 trace-corruption fix (#865), which addressed intra-instance concurrency — this is the worker-level cache lifecycle. (#895)
32
+
-**A trace reconstructed after a restart no longer reads as a failed run.** When the on-disk trace is rehydrated (worker restart or `MAX_TRACES` eviction), any generation span still in flight is closed and marked so its boundary stays visible in the waterfall. The status message now states plainly that altimate-code restarted before the step finished recording and that this is **not an agent failure** — so an on-call reader debugging from a trace isn't sent chasing a phantom incident. (#895)
33
+
34
+
## [0.8.3] - 2026-06-04
35
+
36
+
A plan-mode reliability patch for the hosted gateway and other non-Anthropic models. Ask the `plan` agent to plan something benign — *"plan a feature to add a verify-output button"* — on `altimate-backend/altimate-default` (GPT-5.x) and it could refuse outright with *"I'm sorry, but I cannot assist with that request."* This release fixes the refusal at its source, hardens the fix against prompt-injection, and rewrites a warning that was misdiagnosing the symptom.
37
+
38
+
### Fixed
39
+
40
+
- **Plan mode no longer refuses benign requests on `altimate-default` and other non-Anthropic models.** The root cause was *how* altimate-code delivers its own plan instructions: a `<system-reminder>`-wrapped block attached as user-role text. Claude is trained to read that tag as authoritative system guidance, but GPT-5.x, Gemini, and other non-Anthropic models pattern-matched the same block — carrying `STRICTLY FORBIDDEN` / `ZERO exceptions` / `MUST` language — as a **prompt-injection attempt** and declined, returning *"I'm sorry, but I cannot assist with that request."* for ordinary developer tasks. altimate-code now **hoists those self-injected reminders into proper `role:"system"` messages** for non-Anthropic models, so they arrive as instructions rather than suspect user input; Anthropic models are unchanged. The hoist is scoped by **provenance** to altimate-code's own reminder parts — user-supplied files, MCP-resource bodies, and `data:`-URL content can never gain system-role priority, even when they begin with `<system-reminder>`. Gateway models are routed by `model.family` (via a shared `familyVendor` classifier) so a Claude- or Gemini-backed gateway model lands on the right base prompt instead of an Anthropic-style fallback. (#887, #888)
41
+
- **The "plan agent used no tools" warning is accurate — and no longer false-fires.** Previously the warning blamed the model's *tool-use capability* (misleading — these models are fully tool-capable) and could fire on the final text-only step of a **successful** multi-step plan session, making a working session look broken. The trip-wire now scans the conversation history for prior tool calls, so a session that already explored the codebase isn't flagged. When it does fire, the copy describes the observed symptom only ("stopped without calling any tools"), lists the likely causes, and offers concrete recoveries — ask it to investigate first, rephrase, or, if it keeps refusing, `/model` to a tier more eager to explore. The plan agent is also now instructed to **read or search the codebase before drafting** any plan, with an explicit escape hatch for trivial, fully-specified changes. See [Plan mode](https://docs.altimate.sh/data-engineering/agent-modes/#plan) and [Troubleshooting](https://docs.altimate.sh/reference/troubleshooting/). (#888)
42
+
8
43
## [0.8.2] - 2026-06-03
9
44
10
45
A small correctness patch. The dbt PR reviewer's deterministic engine never required an altimate API key — but two tool descriptions said it did, which could push the reviewer into lint-only mode and send users chasing a key they don't need. This release corrects that and documents what "lint-only" actually means.
The curl install drops a single self-contained binary named `altimate`. The npm install exposes both `altimate` and `altimate-code` on PATH; the curl install only exposes `altimate`. Alpine Linux (musl) and Windows on ARM64 are not currently supported by the standalone binary — use `apk add gcompat` on Alpine, or use WSL on Windows-on-ARM.
38
40
41
+
For GitHub, [install the Altimate Code App](https://github.com/apps/altimate-code-agent/installations/new)
42
+
to select repositories for interactive agent tasks. Automatic dbt pull-request
43
+
reviews use the deterministic GitHub Action documented below; see the
44
+
[public demo PRs](https://github.com/AltimateAI/dbt-pr-review-demo/pulls) before
45
+
installing it in your own repository.
46
+
39
47
Then — in order:
40
48
41
49
**Step 1: Configure your LLM provider** (required before anything works):
Copy file name to clipboardExpand all lines: docs/docs/data-engineering/agent-modes.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -142,6 +142,8 @@ altimate --agent plan
142
142
143
143
Plan mode restricts the agent to reading files and editing plan files only. No SQL, no bash, no file modifications. Use this to outline an approach before switching to builder to execute it.
144
144
145
+
The plan agent investigates the repo before drafting: it makes at least one read-only call (`read`/`grep`/`glob`/`explore`) to ground the plan in your actual code, rather than guessing from the prompt alone. For a genuinely trivial, fully-specified change it will say so and skip straight to the plan.
146
+
145
147
### Two-step workflow
146
148
147
149
Plan mode uses a two-step approach to keep you in control:
Copy file name to clipboardExpand all lines: docs/docs/reference/troubleshooting.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,6 +125,15 @@ As of v0.7.1, altimate-code surfaces the **inner provider message** instead of d
125
125
```
126
126
3. No Python installation is required. All tools run natively in TypeScript.
127
127
128
+
### Plan mode refuses a benign request, or stops without exploring
129
+
130
+
**Symptoms:** In plan mode (`--agent plan`), the agent replies *"I'm sorry, but I cannot assist with that request"* to an ordinary planning ask, or you see the warning *"the `plan` agent … stopped without calling any tools."* Most common on the hosted `altimate-default` model (and other non-Anthropic models).
131
+
132
+
**Solutions:**
133
+
134
+
1.**Upgrade to v0.8.3 or later.** This was a known bug: altimate-code's internal plan instructions were delivered in a way that non-Anthropic models (GPT-5.x, Gemini, …) could mistake for a prompt-injection attempt and refuse. v0.8.3 delivers them as proper system-role messages, eliminating the refusal.
135
+
2. If you still see the agent stop without exploring, follow the in-product warning's recoveries: reply asking it to investigate first (`read`/`grep`/`glob`/`explore`), rephrase the request more concretely, or — if it keeps refusing — `/model` to a tier more eager to explore (e.g. Claude Sonnet/Opus).
136
+
128
137
### Warehouse Connection Failed
129
138
130
139
**Symptoms:** "Connection refused", authentication errors, or "No warehouse configured".
Copy file name to clipboardExpand all lines: docs/docs/usage/dbt-pr-review.md
+11-2Lines changed: 11 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,14 @@
1
1
# dbt PR Review
2
2
3
+
[**See live review PRs**](https://github.com/AltimateAI/dbt-pr-review-demo/pulls)
4
+
·
5
+
[**Install the GitHub App**](https://github.com/apps/altimate-code-agent/installations/new)
6
+
7
+
The public demo is a zero-secret DuckDB project with open PRs for broken joins,
8
+
removed tests, PII exposure, `SELECT *`, unsafe incremental models, and a safe
9
+
refactor. The GitHub App handles interactive repository tasks; the automatic
10
+
review on every pull request is installed with the Action below.
11
+
3
12
AI code review specialized for dbt/SQL. `dbt-pr-review` produces a single,
4
13
**signed** verdict on a pull request — `APPROVE`, `COMMENT`, or `REQUEST_CHANGES`
5
14
— where every **blocking** finding is backed by a deterministic engine call, not
@@ -172,7 +181,7 @@ jobs:
172
181
with: { fetch-depth: 0 }
173
182
# Produce target/manifest.json for the full verdict (adapter-specific).
Copy file name to clipboardExpand all lines: github/README.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
@@ -60,7 +60,7 @@ This will walk you through installing the GitHub app, creating the workflow, and
60
60
61
61
### Manual Setup
62
62
63
-
1. Install the GitHub apphttps://github.com/apps/altimate-code-agent. Make sure it is installed on the target repository.
63
+
1.[Install the GitHub app](https://github.com/apps/altimate-code-agent/installations/new) and select the target repository.
64
64
2. Add the following workflow file to `.github/workflows/altimate-code.yml` in your repo. Set the appropriate `model` and required API keys in `env`.
0 commit comments