Skip to content

Next release: thread lifecycle, storage and source control #535

Description

@Tryanks

Plan of record for the next release: bound thread history growth, give threads a real lifecycle, and add source-control (PR) support across forges.

Research inputs (Sep 2026): T3 Code origin/main f5ef0ddb9, openai/codex 7342991 plus the Codex desktop app bundled in ChatGPT.app 26.917, and read-only measurements of the maintainer's own data (Tcode data dir 9.2 GB, 2,716 thread logs; ~/.codex/sessions 6.9 GB).

Decisions

  • Storage: no SQLite. Metadata and indexes go in redb (already in Cargo.lock, zero new crates); event bodies stay in files. Compaction first, engine second.
  • Compression: flate2 (already in the tree), not zstd.
  • Automatic lifecycle: auto-settle only. Auto-archive is removed; archive is always explicit, because it now moves logs, calls provider-native archive and cleans up worktrees. Rule: automatic transitions must be losslessly reversible.
  • Settle stops the provider session (as in T3 Code).
  • Snooze and pinned are in scope.
  • Archive semantics follow the Codex app. Provider-native archive/delete is used only where the protocol has it (Codex, OpenCode, ACP when advertised). No native delete is synthesized for Claude Code or pi.
  • Process lifetime follows the provider's prompt-cache TTL measured from the last turn, not view time. No keep-alive pings.
  • PRs: linked PRs and an Open PR action across GitHub, GitLab, Gitea, Forgejo, Bitbucket and Azure DevOps, self-hosted included. No model-facing MCP tool for linking PRs. The Open PR action works during a run in two modes: the host runs it at turn end, or it sends a visible message to the agent. "Merge when CI passes" uses the forge's native auto-merge.

Work items

Phase 0: bugs and batch commands

Phase 1: storage

Phase 2: lifecycle

Phase 3: source control

Coordination

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    roadmapDirection and planning

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions