Tags · AltimateAI/altimate-code

v0.12.4

chore(release): v0.12.4 (#1387)

* fix(workspace): v0.12.4 release review — user-facing wording, adopted-binding comment

- Link / re-link messages in `link.ts` and the TUI workspace plugin no longer
  say "binding" or "pre-check" (End User review).
- `state.ts`: the `pinned` field's comment described memory mirroring to
  adopted bindings as an unfixed gap. It is intended: a project belongs to
  exactly one workspace, so new memory in a linked project belongs there; only
  the backfill of earlier memory waits for the user's Attach.
- `identity.ts`: import spacing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018fJ3X7pcGT4R9yzjsJnqsV

* release: v0.12.4

- CHANGELOG entry for 0.12.4.
- `release-v0.12.4-adversarial.test.ts`: snapshot attribution under traversal
  and lookalike segments, `snapshotCopyYields` type confusion, skip reasons and
  displayed skill ids never carrying raw errors or control characters, sync
  problem boundaries and the announce latch, the `serve` workspace route gate
  across header combinations, hidden-workspace conflicts, and the review's
  wording fixes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018fJ3X7pcGT4R9yzjsJnqsV

* fix(workspace): v0.12.4 release PR review — attach-path wording, portable tests

- The "not found" message after linking or re-linking now fits both paths:
  the chosen workspace may be gone (attach), or the project's link to it
  (re-link). It no longer sends an attach user to "pick Create". TUI picker,
  TUI inline attach, and `altimate-code link`.
- `state.ts`: the `pinned` comment no longer claims the field is unused;
  `identity.ts` reads it, and no write-permission check keys on it.
- `release-v0.12.4-adversarial.test.ts`: pass `""` for "no password" (an
  `undefined` argument selects the environment's `OPENCODE_SERVER_PASSWORD`),
  and build snapshot-path expectations from the platform's root and separator
  so the file passes on Windows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018fJ3X7pcGT4R9yzjsJnqsV

* fix(workspace): attribute a drive-root project's snapshot to `C:\`, not `C:`

`snapshotProjectOf` joined the path segments before the snapshot folder, so a
project opened at a Windows drive root came back as the bare drive `C:`, which
resolves to that drive's current directory rather than its root. It now returns
the platform's root (`/`, `C:\`, or a UNC share root) for a root-level project.
The function takes an optional path implementation so the Windows behaviour is
tested on every platform. Found in the v0.12.4 release PR review.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018fJ3X7pcGT4R9yzjsJnqsV

* docs(changelog): v0.12.4 — Windows drive-root snapshot fix

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018fJ3X7pcGT4R9yzjsJnqsV

* fix(workspace): v0.12.4 consensus review — link wording, stale comment, CHANGELOG accuracy

- The remaining user-visible link strings no longer say "bindings",
  "Binding" or "pre-check": the lookup warning and the "Workspace approved"
  spinner in `link.ts`, and the re-link guard's thrown error in both `link.ts`
  and the TUI plugin (both surfaces show a thrown error's message as-is).
- The not-found message after linking or re-linking also covers a workspace
  the account can no longer see: the server answers 404 for both.
- "Already linked — re-linking it instead" no longer stops the spinner with the
  error glyph right before a successful re-link.
- `state.ts`: the note that new memory mirrors to adopted bindings moves from
  `pinned` to `adopted`, and `resolveBinding`'s doc no longer says memory
  writes stay behind a real link — only the backfill of earlier memory does.
- CHANGELOG: the Windows drive-root bullet is removed. `path.win32.join`
  already normalised `C:` + `.altimate-code` to `C:\.altimate-code`, so no user
  could hit it; 03fbb9d is hardening for future callers that `resolve` or
  compare the value. The route-gate description now says `same-site` is refused
  too, and the TUI model fix reads "now keeps".
- Tests: the wording test covers the reworded strings and the not-found
  message's three sites; `snapshotProjectOf` pins lowercase-drive,
  forward-slash and `\\?\` long-path roots; the older root test in
  `skill.test.ts` is portable.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018fJ3X7pcGT4R9yzjsJnqsV

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Sep 29, 2026
b308fa2
zip
tar.gz
Notes
Downloads

v0.12.3

chore(release): v0.12.3 (#1362)

* fix: auto-register Altimate Base before `agent create` and `review` resolve a provider

Neither `altimate agent create` nor `altimate review` called
`FreeTier.autoRegisterWithin()` before resolving a provider, unlike the other
five entrypoints (`run`, `tui`, `serve`, `acp`, `web`). On a fresh install this
meant `agent create` leaked a raw upstream error mentioning "OpenCode" with no
remediation, and `review`'s AI lane silently produced zero findings with no
visible signal.

Found by the Chaos Gremlin (Support Engineer) persona during the v0.12.3
release review — both confirmed P0s, verified against the actual failure
path, not indirect reasoning.

Wires both call sites with the same `autoRegisterWithin(undefined, () => void
printDisclosureOnceForHeadless(true))` pattern already used by run/acp/web,
and extends the entrypoint-late-notice-wiring pin test to cover both new call
sites.

* fix: surface startup feedback during the TUI's auto-register wait

`tui.ts`'s up-to-3s auto-register wait gave zero terminal output — on a fresh
install this reads as a hang on the very first launch (End User persona,
v0.12.3 release review, P1).

Gates a "Connecting to Altimate Base…" status line behind a 300ms delay so
the common already-registered/fast path never flashes it.

* docs: fix stale consent-gate wording flagged by the v0.12.3 release review

Two independent findings (CTO and PM personas):

- `altimate-base-disclosure.ts`'s header comment still described the
  disclosure as something "a user actually consents against before any Base
  credential is minted" — stale since this release removed the consent gate
  entirely. It's now a post-registration notice, not a pre-credential prompt.
- README's "Step 1: Choose an LLM provider (required before anything works)"
  directly contradicted the next sentence, which explains a fresh install
  registers Altimate Base automatically if you skip this step.

* chore: remove a duplicate altimate_change marker in server.ts

Found while auditing the "Kilo Code Review" FAILURE check on PR #1361 (CTO
and Tech Lead personas flagged it as an open loose end): every one of the
bot's 9 findings was already fixed by a later commit in the same PR, and this
harmless leftover duplicate `// altimate_change end` was noticed in the same
import block along the way.

* test: adversarial coverage for v0.12.3 release fixes

Covers the new code from this release's review fixes: ordering/scoping
invariants for the autoRegisterWithin() wiring in agent.ts/review.ts (must
run before the provider is resolved, must stay outside review.ts's latency
timer, must be unconditional regardless of --no-ai), the tui.ts feedback
timer's delay bounds and try/finally cleanup, and a regression guard against
the duplicate marker comment.

* revert: restore the second altimate_change end marker in server.ts

Not a duplicate. The two consecutive `// altimate_change end` lines close two
separate blocks that happen to end at the same point: the outer "Altimate-only
server endpoints" block (opened at the `McpRoutes` import) and the inner
"registration must invalidate BOTH instance registries" block (opened at the
InstanceStore import). Removing one left the outer block's start unpaired,
which the marker-integrity test (test/upstream/bridge-merge.test.ts,
test/branding/upstream-merge-guard.test.ts) caught in CI on PR #1362 —
correctly, since I'd broken a real invariant while "cleaning up" what looked
like leftover cruft without running the actual test that verifies pairing.

* test: drop the mistaken duplicate-marker regression guard

Followed the previous commit's correction — the "duplicate marker" this test
pinned against was never a duplicate, so the test encoded the same wrong
assumption. Removed rather than fixed forward, since there's nothing left to
assert once the premise is gone.

* docs: changelog for v0.12.3

Sep 23, 2026
282e784
zip
tar.gz
Notes
Downloads

v0.12.2

chore(release): v0.12.2 — changelog entry for #1353 (#1355)

#1353 (synced memory blocks get a title) merged to main between the beta
and the release PR; the [0.12.2] entry now lists it. The changelog ships
inside the binary, so it has to be in the tagged commit.


Claude-Session: https://claude.ai/code/session_012Q51zFUmPg1WwtS5CrGJE6

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

Sep 22, 2026
04b8f76
zip
tar.gz
Notes
Downloads

v0.12.2-beta.1

chore(release): v0.12.2-beta.1 (#1347)

* chore(release): v0.12.2-beta.1

Beta of the six workspace-pilot and configuration fixes merged after v0.12.1
(#1341 #1342 #1343 #1344 #1345 #1346). Publishes to the npm `beta` dist-tag;
`latest` stays at 0.12.1.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012Q51zFUmPg1WwtS5CrGJE6

* chore(release): v0.12.2-beta.1 — correct the docs path in the changelog entry

(bot review)

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012Q51zFUmPg1WwtS5CrGJE6

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

Sep 21, 2026
51eda33
zip
tar.gz
Notes
Downloads

v0.12.1

chore(release): v0.12.1 (#1338)

* fix(workspace): close the v0.12.1 release-review findings on the pin/identity seam

Five-persona review of v0.12.0..main. #1320 (IDE pin) and #1330
(identity every turn) changed `resolveBindingOutcome` from opposite sides
and were never reviewed together; every item here is on that seam.

- A pin served from the offline grace window is marked `stale`, so the
identity section says "last known" for it as it already did for a
cached link. `pinValidation` is bounded like the other caches.
- Identity's memo is keyed on the credential digest as well as the
tenant and host — two accounts on one tenant no longer share an entry
(the pin cache in `state.ts` already did this).
- Under a pin, identity's deadline fallback never reaches for the
project's own cached link — the workspace the pin exists to override.
- A pinned session is described as pinned by the IDE extension, with the
caveat that warehouse tool routing still follows the project's own
link (#1337); the unknown copy no longer promises that retrying helps.
- The persistent `shell` tool strips the same host markers as `bash`
(`ALTIMATE_CODE_SERVE`, the pin trio, headless, non-interactive) via a
shared `stripHostMarkers`, so a nested `serve` cannot inherit a pin.
- `pin.ts` states the extension contract: a pin is fixed for the life of
the process; a panel switch means relaunching `serve`.
- Docs: the three pin variables and `ALTIMATE_CODE_SERVE` in cli.md, and
a note on the identity line and the pin under "Workspaces (pilot)".

Tests: pinned-session copy, pin-aware fallback, same-tenant credential
switch, grace-path stale, host-marker stripping. Each guard was deleted
once to confirm its test fails.