mirror of https://github.com/hanzoai/dev.git synced 2026-10-25 03:32:32 +00:00

Files

T

zeekay 7c9138a677 sync: just-every/code 00910569e0 — 31 commits, MCP + tool_search + skills

Takes the upstream delta e4fe007150..00910569e0 from just-every/code, our
proximate upstream. hanzo/dev has no merge-base with any upstream (its history
was rewritten, so every SHA differs while the root trees are identical), so
this lands as a 3-way apply of the delta rather than a merge. Zero conflicts:
the upstream delta touches 249 files, our fork diverges in 140, and the two
sets intersect in exactly 2 files (protocol.rs, chatwidget.rs), both pure
additions that leave every Hanzo identity line alone.

Carries the surface the sandbox agent needs, with the codex PR numbers intact:
  57f42a8113 tool search: no clone of immutable metadata on cache hits (#37279)
  e1831db7c3 reuse MCP handlers across sampling steps (#37273)
  bfb6a6ea22 plugin roots in the host skill loader (#37267)
  1151b23f01 start cached MCP servers lazily for subagents (#37261)
  7a0e974e08 harden network proxy MITM authorization (#37211)
  98da2c4499 reserve the `tool_search` namespace for the search tool (#37188)
  1dc93cdeb0 refresh the codex-rs mirror to codex main

codex-rs/ is a vendored mirror that just-every refreshes wholesale; patching it
directly would be overwritten by the next refresh, so we take their refresh
instead of cherry-picking from openai/codex.

2026-08-06 14:17:15 -07:00

src

sync: just-every/code 00910569e0 — 31 commits, MCP + tool_search + skills

2026-08-06 14:17:15 -07:00

BUILD.bazel

merge: just-every/code v0.6.169 (e4fe007150) — keep Hanzo identity

2026-08-05 23:09:12 -07:00

Cargo.toml

sync: just-every/code 00910569e0 — 31 commits, MCP + tool_search + skills

2026-08-06 14:17:15 -07:00

README.md

merge: just-every/code v0.6.169 (e4fe007150) — keep Hanzo identity

2026-08-05 23:09:12 -07: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.