Track OpenCode 1.18.15

[a5c-ai]

Version

• Previous graph version: 1.18.3
• Latest upstream version: 1.18.15
• Release notes: https://github.com/anomalyco/opencode/releases/tag/v1.18.15

Actual changes researched

• Chronological message ordering now uses real creation chronology even for imported/legacy IDs.
• Revert and fork actions use real message chronology instead of message ID ordering.
• Repeated compaction keeps earlier tool-call history in summaries instead of dropping orphaned results.
• Blob attachments load correctly in the web UI.
• Desktop adds broad locale coverage and full session transcript JSON export.
• Community changes include SSH/tmux clipboard copy support and TUI cursor style configuration.

Likely affected system surfaces

• session adapter: parse/order messages by chronology, not IDs.
• revert/fork workflow: use real chronology.
• compaction verifier: expect retained prior tool-call history.
• artifact/export model: add desktop JSON transcript export.
• TUI profile: add cursor style setting and SSH clipboard behavior.

Install/migration

• Install remains npm install -g opencode-ai.

Assimilation checklist

• Update session ordering assumptions to use created-at chronology.
• Add regression checks for revert/fork chronology.
• Update compaction expectations for retained tool-call history.
• Add JSON transcript export to capability metadata.

[a5c-ai]

Triage Summary

• One-line: Assimilate OpenCode 1.18.15 into the Atlas graph/catalog metadata, replacing the current recorded OpenCode 1.18.3 release snapshot with the researched 1.18.15 facts from this issue.

Critical Evaluation

• Reporter's analysis is accurate.
• This is an enhancement / graph-update tracker, not a runtime adapter bug by itself.
• The correct scope is Atlas graph/catalog metadata and evidence. Do not expand into adapter runtime changes unless implementation finds a concrete local behavior gap.

Root Cause Analysis

• The repo currently records OpenCode at 1.18.3, while this issue requests assimilation of upstream OpenCode 1.18.15.
• Primary affected record: packages/atlas/graph/agent-stack/agent-versions/upstream-current-2026-07-17.yaml currently defines agentVersion:opencode:1-18-3, currentVersion: "1.18.3", and release notes for v1.18.3.
• Matching evidence record: packages/atlas/graph/catalog-meta/evidence-sources/upstream-current-2026-07-17.yaml currently defines evidence:opencode-1-18-3-2026-07-17.
• No commit or merged PR was found for OpenCode 1.18.15 / issue #1667; issue #1677 was closed as a duplicate of this canonical issue.

Affected Components

• Packages: @a5c-ai/atlas, agent catalog graph consumers
• Components: atlas, agent-catalog
• Effort: effort:medium

Recommended Approach

1. Add or update Atlas graph records for OpenCode 1.18.15 using the facts already captured in this issue.
2. Include/update the corresponding EvidenceSource with release notes URL https://github.com/anomalyco/opencode/releases/tag/v1.18.15 and source package opencode-ai.
3. Keep install metadata unchanged: npm install remains npm install -g opencode-ai.
4. Capture the meaningful release facts: chronological message ordering, revert/fork chronology, repeated compaction history retention, blob attachment loading, desktop JSON transcript export, locale coverage, SSH/tmux clipboard, and TUI cursor style configuration.
5. Validate with:
   • npm run build:atlas
   • npm run validate:edges
   • npm run test:atlas-catalog-contracts

Reproduction

Run:

rg -n "agentVersion:opencode:1-18-3|1\.18\.15" packages/atlas/graph

Current result: the graph has OpenCode 1.18.3 metadata and no OpenCode 1.18.15 graph record.

Related Issues/PRs

• Track OpenCode 1.18.15 #1677 was closed as a duplicate of this issue, confirming Track OpenCode 1.18.15 #1667 is canonical.
• Prior analogous graph update: Track upstream agent CLI versions #1503 / commit e3b0a4ea8 tracked upstream agent CLI versions and added the current 1.18.3 OpenCode record.

Priority: medium

This affects version freshness for Atlas graph/catalog consumers and upstream release tracking, but it is not a production outage or data-loss issue.

Risk Analysis

• Risk Level: risk:medium
• Graph metadata drift or dangling edges: add AgentVersion and EvidenceSource records together, keep version_of and sourced_from edges aligned, and run edge validation.
• Over-scoping into runtime adapter changes: keep implementation limited to graph/catalog metadata unless a concrete adapter test/source path proves behavior must change.
• Generated catalog/index regressions: run Atlas build and catalog contract tests, then inspect generated graph/index changes before merge.

[a5c-ai]

Triage Summary

• One-line: Track and assimilate OpenCode 1.18.15 into Atlas graph metadata and the local adapter/session surfaces that are affected by the upstream release notes.

Critical Evaluation

• Reporter's analysis is accurate: this is a valid upstream-version assimilation tracker, not a duplicate. The exact duplicate candidate Track OpenCode 1.18.15 #1677 is already closed as a duplicate of this canonical issue.
• This is best treated as an enhancement/version-update task, not a narrow runtime bug report.

Root Cause Analysis

• The repo's OpenCode graph/version metadata currently has prior records through OpenCode 1.18.3, while this issue tracks 1.18.15.
• Relevant graph/evidence paths include:
  • packages/atlas/graph/agent-stack/agent-versions/upstream-current-2026-07-17.yaml
  • packages/atlas/graph/catalog-meta/evidence-sources/upstream-current-2026-07-17.yaml
  • packages/atlas/graph/agent-stack/versions/opencode-1-x.yaml
  • packages/atlas/graph/agent-stack/products/opencode.yaml
• Relevant adapter/session paths include:
  • packages/adapters/codecs/src/opencode-adapter.ts
  • packages/adapters/codecs/src/opencode-http-adapter.ts
  • packages/adapters/codecs/src/session-fs.ts
  • packages/adapters/codecs/tests/opencode-adapter.test.ts
  • packages/adapters/codecs/tests/opencode-http-adapter.test.ts
  • packages/adapters/codecs/tests/opencode-translation.test.ts
• The shared JSONL parser extracts row timestamps but appends messages in row order. That makes the upstream creation-chronology change relevant for imported or legacy OpenCode sessions whose IDs/order do not match creation time.
• Genty session/export/continuity/compaction surfaces may also need metadata or fixture coverage:
  • packages/genty/runtime/src/session/export.ts
  • packages/genty/runtime/src/session/tree.ts
  • packages/genty/platform/src/session/continuityState.ts
  • packages/genty/platform/src/compression/compactionStrategy.ts
  • packages/genty/tui/src/plugins/config-view.tsx
  • packages/genty/tui/src/plugins/profiles-view.tsx

Affected Components

• Packages: atlas, agent-catalog, adapters
• Effort: effort:medium

Recommended Approach

1. Update Atlas graph/evidence records for OpenCode 1.18.15, preserving the existing install method: npm install -g opencode-ai.
2. Add focused regression fixtures before runtime changes:
   • OpenCode messages whose IDs sort differently from creation timestamps.
   • Revert/fork chronology expectations using the OpenCode session path, not Babysitter run forking.
   • Repeated compaction retaining earlier tool-call history.
3. Change runtime code only where a local surface is proven affected by those fixtures.
4. Treat desktop JSON transcript export, locale coverage, SSH/tmux clipboard behavior, and TUI cursor style as metadata/profile/config updates unless a concrete local runtime path exists.

Reproduction / Validation

• Add a fixture with OpenCode messages whose IDs sort differently from creation timestamps.
• Verify session parsing, revert/fork behavior, and exported transcript order follow creation chronology.
• Add a repeated-compaction fixture containing earlier tool-call history and assert the specific prior tool-call IDs/content are retained.

Related Issues/PRs

• Track OpenCode 1.18.15 #1677 was an exact duplicate and is already closed as a duplicate of Track OpenCode 1.18.15 #1667.
• No matching commits or closed PRs were found for OpenCode 1.18.15 or #1667 during triage.
• Recent related graph/version work includes e3b0a4ea8 Track upstream agent CLI versions (#1503) and 4cf911509 chore(graph): track upstream agent versions.

Priority: medium

• This has meaningful workflow impact because stale OpenCode metadata and chronology/compaction gaps can produce incorrect session history or incomplete graph capability records.
• It is not currently reported as a production outage, and it has a clear incremental path through graph updates plus focused regression tests.

Risk Analysis

• Risk Level: risk:medium
• Chronology fixes could reorder existing transcript displays or exports.
  • Mitigation: use fixtures where ID order differs from creation time, assert creation-time ordering explicitly, and keep ordering changes localized to OpenCode/session parsing paths.
• Revert/fork tests could target the wrong abstraction.
  • Mitigation: name fixtures and tests around OpenCode session chronology, not Babysitter run forking, and trace the exact adapter/session call path before implementation.
• Compaction validation could pass while dropping prior tool-call details.
  • Mitigation: assert specific retained earlier tool-call IDs/content across repeated compactions.
• Metadata-only release-note items could become broad, unnecessary code changes.
  • Mitigation: update Atlas/evidence first, then touch runtime code only where a local surface and failing regression test exist.