mirror of https://github.com/hanzoai/codex.git synced 2026-10-30 14:59:26 +00:00

Files

T

History

zeekay 284d514ac7 hanzo: one crate for Dev's names, defaults, catalog, controller and version

Upstream crates read Dev's words and defaults from crates in hanzoai/dev,
by a path out of this tree. What they read is data and an interface, so it
moves here, into codex-rs/hanzo, which absorbs hanzo-version:

- the brand strings and the TUI's defaults (hanzo-tui's constants and
  input_background), read by codex-tui;
- API_BASE, DEFAULT_MODEL, is_hanzo and the model catalog (from
  hanzo-config), read by models-manager and model-provider;
- `model::pick`, the `/model <name>` match, pure over the catalog;
- the controller interface the agent loop consults (hanzo-loop: Controller,
  Handle, Verdict, Card, Request, Shortlist), read by codex-core;
- the version hook, now `hanzo::version`.

Dev's crates depend on this one from now on, never the reverse. Kai and the
Hanzo account are behaviour, and still named from here until the next two
commits turn them into hooks a binary fills.

2026-10-15 08:10:24 -07:00

src

hanzo: one crate for Dev's names, defaults, catalog, controller and version

2026-10-15 08:10:24 -07:00

BUILD.bazel

…

Cargo.toml

hanzo: one crate for Dev's names, defaults, catalog, controller and version

2026-10-15 08:10:24 -07:00

README.md

Unify thread metadata updates above store (#22236 )

2026-05-13 00:28:15 +00:00

README.md

Thread Store

codex-thread-store is the storage boundary for Codex threads. It defines the ThreadStore trait plus local and in-memory implementations. Other storage implementations may live outside this repository.

Responsibilities

ThreadStore::append_items is the raw canonical history append API. It does not infer metadata from item contents.
ThreadStore::update_thread_metadata is the only thread metadata write API. It accepts a single literal metadata patch shape, regardless of whether the caller is applying a user/API mutation or facts derived above the store from appended history.
LiveThread is the preferred API for active session persistence. It owns a per-thread metadata sync helper, applies the rollout persistence policy, appends canonical history, and then sends metadata patches through ThreadStore::update_thread_metadata.
ThreadManager routes metadata mutations for loaded and cold threads through one entrypoint. Loaded threads use their LiveThread; cold threads go directly to the store.
LocalThreadStore persists history through codex-rollout JSONL files and persists queryable metadata through the SQLite state database when available. Local explicit metadata mutations also maintain JSONL/name-index compatibility so reading old or SQLite-less local storage keeps working.
RolloutRecorder is the local JSONL writer. It writes already-canonical items for ThreadStore::append_items; it no longer decides metadata updates for live thread-store appends.
core/session creates or resumes LiveThread handles and does not need to know whether persistence is backed by local files or another store.

Direction

New metadata observation semantics should live above ThreadStore. Stores persist explicit metadata fields, but raw history appends remain history-only.