Skip to content

feat: Add sequencer_memo_* tools (per-instance volatile KV)#1

Open
hanatyan128 wants to merge 2 commits into
masterfrom
feat-step-local-memo
Open

feat: Add sequencer_memo_* tools (per-instance volatile KV)#1
hanatyan128 wants to merge 2 commits into
masterfrom
feat-step-local-memo

Conversation

@hanatyan128
Copy link
Copy Markdown
Member

Summary

  • Adds sequencer_memo_set / _get / _keys / _delete MCP tools backed by an in-memory per-instance KV store (MemoStore).
  • The bucket is cleared at the top of every sequencer_next, on sequencer_close, and on TTL archive — cross-step retention is structurally impossible, which keeps the memo trivially compatible with deterministic replay (resume always starts empty).
  • Quotas: 1 MiB per value / 64 MiB per instance, overridable via AGENT_SEQUENCER_MEMO_VALUE_LIMIT / AGENT_SEQUENCER_MEMO_INSTANCE_LIMIT.
  • Intended for sub-agent IPC during one Instruction's execution; programs (run(ctx)) deliberately have no memo API to keep the determinism contract intact.
  • Bumps version to 0.1.3.

Test plan

  • uv run pytest (94 passed, including 43 new MemoStore unit tests + 18 MCP-tool layer tests + 4 env-var resolver tests)
  • uv run agent-sequencer --help (entry point intact)

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant