SNAPSHOT · TIER B · CLI

Reasonix 1.22.0@6376bd4

Clean source inspection pinned to the commit whose release ledger identifies 1.22.0. This snapshot maps the CLI engine only; desktop, browser, and ACP behavior is not assumed identical unless a claim names the shared boundary. A native experiment is still required for Tier A.

reasonix-2026-08-10-sourcecurrent8 claims

looppartial

contextpartial

toolspartial

safetypartial

reliabilitypartial

extensibilitypartial

orchestrationpartial

interfacesunknown

observabilitypartial

Reasonix CLI engine source map

This page is pinned to release ledger 1.22.0 at commit 6376bd4. It is source inspection only: no binary, provider, sandbox backend, or plugin process was started.

user turn
  → delivery / permission / context state
  → frozen sampling request + cache-shape capture
  → bounded stream recovery
  → clean response commit
  → batch scheduler → per-call gate → tool
  → native event log / checkpoint / next round

1. Loop

runToolLoop divides each round into sampling, commit, and final/tool dispatch. A provider attempt enters the session only after a clean terminal result, preventing a failed speculative attempt from mutating history first. Max steps, grace rounds, steering, and final readiness are host-owned state. Claim: reasonix-source-agent-loop.

2. Context

Context maintenance uses soft, snip, compact, and force thresholds plus a fixed recent-tail budget. PrefixShape hashes the system prompt and tool schemas and records provider-visible rewrite reasons to explain cache hits or misses—not to replace correctness with cache metrics. Claim: reasonix-source-context-maintenance.

3. Tools

Batch scheduling and single-call execution are separated. The former decides parallel/sequential behavior and batch lifecycle; the latter creates per-call context, checks capabilities and policy, invokes the tool, normalizes results, and records failure state. Claim: reasonix-source-tool-dispatch.

4. Safety

Permission policy, runtime approval posture, and OS sandboxing are distinct layers. Ask/Auto/DontAsk/Yolo remain subject to explicit deny rules, fresh human decisions, and headless gates. Shell sandbox backends exist for macOS/Linux and fail closed when enforcement is requested but unavailable. The source explicitly says Windows lacks an OS-level Bash sandbox at this commit. Claim: reasonix-source-execution-policy.

5. Reliability

Sampling recovery performs bounded attempts against one frozen request and commits only the selected clean attempt. A separate guard signs semantically identical write-like failures and stops after a threshold; some stale-state failures can first run a side-effect-free recheck. Claim: reasonix-source-retry-recovery.

Checkpoint, snapshot-conflict, tail-repair, and delivery-evidence code also exists, but no end-to-end experiment has validated those paths here.

6. Extensibility

Plugin manifests can contribute hooks, MCP servers, and other resources. Lazy MCP tools use cached schemas or a connect stub to keep the provider-visible prefix stable, then start a process and reconcile live safety metadata when needed. Claim: reasonix-source-extension-runtime.

7. Orchestration

Child agents receive a private session temp, filtered tool registry, read-only profile option, and depth cap. Parent-only job/orchestration tools are hidden, and direct MCP schemas are replaced by a stable capability proxy. Claim: reasonix-source-subagents.

8. Interfaces

Multiple frontends use the engine, but this snapshot binds only the CLI. ACP's NDJSON JSON-RPC, event projection, and permission requests are reviewed in a separate snapshot; this project has no desktop/web claims yet.

9. Observability

The append-only .events.jsonl file is transcript authority. Model-visible context, event/display indexes, conflict logs, checkpoints, and jobs live in separate sidecars. This separates authoritative events from rebuildable projections instead of combining everything into one large JSON object. Claim: reasonix-source-event-log.

Result and experiment requirement

Reasonix exposes many production-oriented mechanisms in one repository, but source volume is not a maturity score. Tier A still requires at least one end-to-end path across real stream interruption, repeated failure, compaction/cache, sandbox denial, checkpoint restore, or native-trace normalization, plus external reproduction.

PINNED SOURCE MAP

github.com/esengine/DeepSeek-Reasonix

6376bd4a6d7fa97c7bdb2166af3c1d9d290b8993

internal/agent/run_loop.go
internal/agent/execute_batch.go
internal/agent/execute_one.go
internal/agent/compact.go
internal/agent/cache_shape.go
internal/agent/repeat_failure_guard.go
internal/control/approval.go
internal/sandbox/sandbox.go
internal/checkpoint/checkpoint.go
internal/agent/task.go
internal/pluginpkg/manifest_v1.go
internal/plugin/lazy.go
internal/store/session.go
internal/agent/session_events.go

sourcereviewed

reasonix-source-agent-loop

The pinned Reasonix engine runs a bounded tool-round loop that captures a cache prefix shape, streams a provider turn, commits only a clean terminal attempt, then either finalizes or dispatches the committed tool calls before the next round.

Mechanism: Agent Loop
Reviewed: 2026-08-10
Sources: 1

Reasonix run loop ↗

source + sourcereviewed

reasonix-source-context-maintenance

Reasonix treats compaction as a low-frequency cache-reset point, uses multiple context thresholds and a recent-tail budget, and records prefix-shape diagnostics that distinguish system, tool-schema, and content-rewrite changes.

Mechanism: Context Compaction
Reviewed: 2026-08-10
Sources: 2

Reasonix cache-aware compaction ↗Reasonix prefix-shape diagnostics ↗

source + sourcereviewed

reasonix-source-event-log

Reasonix designates an append-only events JSONL file as transcript authority and keeps derived context, event-index, display-index, conflict, checkpoint, and job artifacts in separate sidecars.

Mechanism: Event Stream
Reviewed: 2026-08-10
Sources: 2

Reasonix session artifact authority ↗Reasonix native session events ↗

source + sourcereviewed

reasonix-source-execution-policy

Reasonix separates permission and approval posture from OS-level shell confinement: approval modes preserve explicit deny and fresh-decision rules, while an enforced but unavailable shell sandbox fails closed instead of running unwrapped.

Mechanism: Execution Policy
Reviewed: 2026-08-10
Sources: 2

Reasonix approval manager and headless gates ↗Reasonix OS sandbox contract ↗

source + sourcereviewed

reasonix-source-extension-runtime

Reasonix plugin manifests can contribute hooks and MCP servers, while lazy MCP placeholders keep cached tool metadata stable and defer process startup or live schema reconciliation until needed.

Mechanism: Extension Runtime
Reviewed: 2026-08-10
Sources: 2

Reasonix plugin manifest contract ↗Reasonix lazy MCP toolset ↗

source + sourcereviewed

reasonix-source-retry-recovery

Reasonix replays one frozen sampling payload across bounded stream-recovery attempts, commits only the selected clean attempt, and separately breaks repeated identical write-like failures after a small threshold unless a safe state recheck clears the signature.

Mechanism: Retry and Recovery
Reviewed: 2026-08-10
Sources: 2

Reasonix sampling recovery ↗Reasonix repeated failure guard ↗

sourcereviewed

reasonix-source-subagents

Reasonix constructs a filtered child tool registry, supports a read-only child profile, caps recursive delegation by depth, hides parent-only orchestration and job tools, and gives each child a private temporary-session boundary.

Mechanism: Subagent Orchestration
Reviewed: 2026-08-10
Sources: 1

Reasonix subagent tool and context boundaries ↗

source + sourcereviewed

reasonix-source-tool-dispatch

Reasonix separates batch scheduling from single-call execution, so concurrency decisions, per-call context, capability gates, tool invocation, results, and failure bookkeeping cross explicit boundaries.

Mechanism: Tool Dispatch
Reviewed: 2026-08-10
Sources: 2

Reasonix batch tool execution ↗Reasonix single tool-call execution ↗