Files

indifferentketchup f3a0197d6a feat: Claude Agent SDK backend + clean-room PostgresSessionStore (v2.7.5)

Lands the lean-SDK direction (boocode_code_review_v2 §1 #9) behind a flag.
Adds @anthropic-ai/claude-agent-sdk@0.3.159 (Commercial Terms, runtime dep).

- PostgresSessionStore: clean-room impl of the SDK's real SessionStore type
  over a new claude_session_entries table. Typechecks against the SDK type;
  8 DB-integration tests.
- ClaudeSdkBackend (implements AgentBackend): one warm query() per (chat,claude)
  in streaming-input mode via a pushable async-iterable pump, sessionStore +
  resume continuity, pure mapSdkMessage->AgentEvent, session_id from init,
  usage/cost onto agent_sessions (backend CHECK gains 'claude_sdk').
- Routing env-gated by CLAUDE_SDK_BACKEND (default off) -> PTY path UNCHANGED.
- Built against real SDK 0.3.159 types (install paid off: partial=stream_event
  needing includePartialMessages, MessageParam, result error arm).
- Fix latent test-infra deadlock: serialize DB suites (fileParallelism:false).

Coder 269 passing default / 290 with DB; tsc clean vs SDK types; builds clean.
LIVE pump + resume + actual claude turn need a host smoke (CLAUDE_SDK_BACKEND=1
+ claude binary + auth). zod peer-dep wants ^4 (workspace 3.25). Builds on v2.7.4.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-01 13:37:57 +00:00

changes

feat: Claude Agent SDK backend + clean-room PostgresSessionStore (v2.7.5)

2026-06-01 13:37:57 +00:00

README.md

v2.2-paseo-providers: Paseo provider stack + v2.2.1 pane-scoped chat fixes

2026-05-26 15:18:31 +00:00

README.md

openspec

Per-batch documentation convention adopted v1.13.15-openspec.

Agent entry point: AGENTS.md at repo root. Architecture diagram: docs/ARCHITECTURE.md.

Lift source: Fission-AI/OpenSpec directory layout. No CLI dependency — just the folder shape. Full OpenSpec lifecycle adoption is a future v1.14+ batch.

Layout

openspec/
  changes/
    <slug>/                          # one folder per shipped or planned batch
      proposal.md                    # Why + scope summary
      tasks.md                       # implementation step list
      design.md                      # architecture / data-model decisions (optional)
      specs/                         # reserved for future OpenSpec CLI adoption
    archived/                        # snapshots of pre-v1.13.15 batch docs
      <original-filename>.md
  specs/                             # global specs, future v1.14+ use

Conventions

Slugs are lowercase-hyphenated derived from the batch title (e.g. v1-13-10-per-tool-cost, file-attachments-v3-5).
Already-shipped pre-v1.13.15 batches live in changes/archived/ as single-file snapshots. They were not split into proposal/tasks because the work was already complete; archiving preserves git history.
New v1.13.15+ batches should land directly in changes/<slug>/proposal.md (+ tasks.md, + design.md when applicable).
proposal.md carries the "Why" and scope. tasks.md is the action list (numbered or checkbox). design.md is for non-trivial architectural decisions worth recording separately.
A canonical dispatch brief (matching the v1.13.9 / v1.13.10 format) is most naturally split as proposal.md (Where we are, Why this matters, rationale sections) + tasks.md (Scope items, Build + smoke) + design.md (Attribution model, Filtering, Canonical mapping).