Compare commits

...
128 Commits
Author SHA1 Message Date
esengine 50670ee41b chore(release): 0.7.2
UX polish + two small fixes since 0.7.1:

- pickers / narrow-term reflow / multi-line indent (d6bb405)
- Wizard + SessionPicker keybinding hint unification (98f19d1)
- tool-summary suffix-match for MCP-bridged tools + write_file branch (1de2349)
- replay: align multi-line user msg under the prefix in RecordView (70e0ad1)

Tests 1264 → 1267, lint + typecheck + build clean.
2026-04-25 08:00:30 -07:00
esengine 70e0ad1aba fix(replay): align multi-line user msg under the prefix in RecordView
Same fix as EventLog ate earlier. RecordView is the read-only viewer
shared by reasonix replay and reasonix diff — multi-line transcripts
were wrapping under col 0 instead of under the body text. Continuation
indent of 6 spaces matches the 'you › ' prefix width.
2026-04-25 06:44:11 -07:00
esengine 1de2349350 fix(ui): tool-summary suffix-match bridges MCP-prefixed names
LiveRows.tsx already used `name === s || name.endsWith("_" + s)` so MCP
tools like `filesystem_read_file` picked up the same per-tool argument
summary as the bare local `read_file`. tool-summary.ts used exact-name
match only, so bridged tools fell through to the generic "first line +
size hint" path in the compact scrollback row. Switch to the same
suffix predicate; add a write_file branch while there. +3 tests
covering the bridged path + a non-underscore-prefix non-match.
2026-04-25 06:21:57 -07:00
esengine 98f19d1d47 chore(ui): unify keybinding hints in Wizard + SessionPicker
Bracket-style `[↑↓] navigate · [Enter] X · [Esc] Y` matches the Confirm
modals; Wizard and SessionPicker were the last surfaces using the older
free-form `↑/↓ move · enter X · esc Y` style. Doc-comment examples in
Select.tsx updated to match.
2026-04-25 06:18:19 -07:00
esengine d6bb4054dc feat(ui): polish pickers, narrow-term reflow, multi-line indent
- ShellConfirm border yellow→red (highest-risk gate distinct from review)
- EditConfirm border cyan→yellow (decouple from PlanConfirm cyan)
- PromptInput: extract [Esc]-to-stop into separate dim row; narrow mode
  (≤90 cols) condenses prefix `you ›`→`›` with proportional indent
- EventLog: user/warning/error multi-line text now aligns under glyph
  via indentContinuationLines helper
- Slash/At/SlashArg suggestion overlays: marginTop separates from scrollback
2026-04-25 06:15:33 -07:00
esengine 9e3c62ed1e chore(release): 0.7.1 2026-04-25 04:47:34 -07:00
esengine ee274035c6 fix(loop,prompt): storm recovery, PYTHONUTF8, recency rule
Three runtime fixes that all surfaced from a single user trace
(model looped on a broken read_file, the chat ended without
explanation, embedded GBK encoding errors, plus a separate
"PDF report on global economy" turn that wrote a 2024 report
from training memory instead of searching).

Storm-break no longer dead-ends the turn
- When the storm-breaker suppressed every tool call in a turn,
  the loop yielded `done` with empty assistant content. The user
  saw a one-line warning then silence and didn't know what to do.
  Now routes through `forceSummaryAfterIterLimit` with a new
  `"stuck"` reason: the model gets one no-tools call to explain
  what it tried, what blocked, and what would unblock — turning
  the silent stop into actionable feedback the user can act on.

PYTHONUTF8 / PYTHONIOENCODING for spawned shells
- run_command's spawn env now sets PYTHONIOENCODING=utf-8 and
  PYTHONUTF8=1. On Chinese Windows, Python's default stdout
  encoder is GBK; emoji / non-GBK output raises UnicodeEncodeError
  and the model sees a Python traceback instead of the script's
  real result, then loops trying to fix the wrong problem.
  These env vars force UTF-8 unconditionally. Harmless on
  non-Python processes (env vars they don't read).

Recency rule in default chat system prompt
- New short section in DEFAULT_SYSTEM telling the model that
  when an answer's correctness depends on something that
  changes over time (the user is asking what's *happening*,
  not what's *true*) and a search tool is available, search
  before composing. Phrased as a principle ("if I'm wrong
  about this, is it because reality moved on?") rather than
  a topic list, so it doesn't go stale or over-prescribe.
- web_search description rewritten in matching language —
  emphasis on "current state" rather than enumerating
  topics like markets / news / releases, which tied the
  description to a particular moment in time.

Tests: loop +1 (storm→summary regression). 1264 tests total,
lint + tsc + build clean.
2026-04-25 04:47:27 -07:00
esengine 500868b490 fix(ui,prompt): paste sentinels, hard /clear, multi-line nav
Several long-standing input-box and TUI annoyances fixed in one batch.

Paste handling
- Big pastes (3000-line error logs, etc.) used to be inlined into
  the buffer verbatim — surrounding typed text drowned, every
  keystroke re-rendered hundreds of rows. Replace with a sentinel
  scheme: each paste blob becomes ONE PUA codepoint in the buffer
  (`\uE100..\uE1FF`), full content lives in a side registry,
  rendered as `[paste #N · 33l · 1.0KB]` magenta block. Buffer
  stays small, cursor steps over the placeholder as one unit, a
  single Backspace removes the whole paste. On submit the
  sentinels expand back to full content for the model.
- Bracketed-paste mode (DECSET 2004) enabled at app start so
  cooperating terminals deliver one marker pair per paste action.
- For terminals where the markers don't reach Ink (PowerShell +
  ConPTY parses them out), a sub-30ms time-window + position-guard
  fallback collapses chunks of one paste into a single sentinel.
  30ms is well below human reaction for double-pasting (~100ms+),
  so two deliberate pastes never falsely merge.
- Critical fix: PowerShell+Ink fires useInput TWICE per stdin
  chunk, both with stale React closure over `value` / `cursor`.
  The merge guard read stale state and never matched the previous
  sentinel — one Ctrl+V kept producing four `[paste #N]`
  placeholders. registerPaste now reads from refs we update
  synchronously inside the function, so the second fire sees the
  first's insert.
- Pasted CR/CRLF normalize to LF; bracketed-paste markers are
  stripped if they leak through.

Multi-line cursor
- ↑/↓ at the buffer boundary (line 0 / last line) used to be
  silent NOOP — felt stuck. Now hands off to the parent's history
  recall, so users can escape into history from a multi-line
  draft without first emptying it.
- Raw-escape fallback: terminals that don't set `key.upArrow`
  and instead leak `\x1b[A` into `input` (older Windows configs)
  now get the escape rewritten into the structured key event,
  preventing the literal escape bytes from being inserted.

Buffer-wide shortcuts
- PageUp / PageDown jump to top / bottom of the WHOLE buffer
  (was NOOP).
- Ctrl+U clears the entire buffer (readline-style; necessary
  given the renderer can collapse the buffer to a few visible
  rows after a paste — backspacing N times wasn't ergonomic).
- Ctrl+W deletes the word before the cursor (eats trailing
  whitespace first, spans newlines).
- Hint row appears under the input when buffer has > 20 lines:
  `[N lines · PageUp/PageDown jump to top/bottom · Ctrl+U clear ·
  Ctrl+W del word]` so users discover the shortcuts in the
  exact moment they need them.

Visual stability
- StatsPanel pinned to `width={columns}` so each render's frame
  is exactly terminal-width — reduces (doesn't eliminate) the
  resize ghost-frame stacking from Ink's eraseLines miscount on
  re-wrapped lines.
- /help gains a "Known limitation" section about the resize
  artifact so users aren't blindsided.

`/clear` actually clears
- Used to only `setHistorical([])` (React state). Terminal
  scrollback was untouched — user kept seeing prior turns until
  they scrolled past them. Now writes CSI 2J + 3J + H so the
  viewport AND scrollback buffer are nuked. Ink's next render
  paints the TUI on the fresh screen.

Tests: paste-sentinels (new file, 18 tests), multiline-keys +57.
Total 1264 tests, lint + tsc + build clean.
2026-04-25 04:47:05 -07:00
esengine 7aa71324c4 feat(md): extended markdown rendering
Substantial expansion of the chat-output Markdown renderer.

Block-level
- Blockquote `>` with proper recursion: nested quotes (`> >`) render as
  adjacent left bars, lists / code fences / tables INSIDE a quote
  parse via the same `parseBlocks` recursively (instead of being
  flattened to text), GFM-style.
- Task lists (`- [ ]` / `- [x]`) — item text gains `task: "todo" |
  "done"`, rendered as `☐` / `☒` with strikethrough on done items.
- Diagram code blocks (mermaid / dot / graphviz / plantuml / puml /
  flowchart / sequencediagram / gantt / erdiagram) render with a
  distinct magenta double-line frame + `◇ <lang> diagram (source)`
  header + viewer-URL hint. Terminal can't draw the graph, but the
  user knows it's source-of-a-diagram and where to paste it.
- Hard line break: trailing `  ` (two-or-more spaces) on a line now
  inserts a real `\n` in the rendered paragraph instead of being
  silently collapsed into a space.

Inline
- `***bold-italic***` (added as the first INLINE_RE alternative
  before the bold and italic checks).
- `~~strikethrough~~` (with proper guards so subscript / strike
  don't fight).
- Pandoc-style `^x^` superscript and `~x~` subscript — only
  fire when every char is in the Unicode SUPERSCRIPT/SUBSCRIPT
  table; otherwise leave the markers literal so we don't drop the
  user's intent.
- Math: `$inline$` and `$$block$$` delimiters are stripped
  (delimiters only — content still flows through the existing
  LaTeX → Unicode pipeline).
- Emoji shortcodes: ~70-entry curated table covering the common
  faces / hearts / gestures / signals (`:smile:`, `:fire:`, `:+1:`,
  `:white_check_mark:`, etc.). Unknown names pass through literal.
- Autolinks: `<http://…>`, `<https://…>`, `<mailto:…>`, `<ftp://…>`
  rewrite to `[url](url)` so the existing link path renders them.
- Backslash escapes: `\*` / `\` ` ` / `\~` / `\[` / `\]` / `\`  etc.
  emit literal characters via a final INLINE_RE branch — the
  surrounding markup parsers don't get to consume the escaped
  punctuation. `stripInlineMarkup` rebuilt around a single-pass
  INLINE_RE walk so escape precedence matches the runtime.

Citation guard
- `collectCitations` now skips URLs that obviously aren't repo
  paths: anchor-only (`#foo`), bare `/`, and short placeholder
  words with no `/` `\` or `.` in them. Eliminates the false
  "broken citation" red-strikethrough on demo / non-citation
  links.

Bug fixes uncovered along the way
- `\sum_{i=1}^n` and friends were being eaten by the catch-all
  LaTeX command stripper because `\b` doesn't match between `m`
  and `_` (both are word chars). Switched the relevant rules to
  `(?![a-zA-Z])` so the specific Σ / Π / ∫ / etc. substitutions
  fire even when followed by a subscript.

Tests: markdown 60 → 173 (+113).
2026-04-25 04:45:21 -07:00
esengine e530cab7a7 chore(release): 0.7.0 2026-04-24 20:14:25 -07:00
esengine bf45687414 chore(models): retire deepseek-chat/-reasoner defaults, name v4 directly
deepseek-chat and deepseek-reasoner are now just compat aliases for
v4-flash's non-thinking and thinking modes (same underlying model,
same bill per telemetry.ts). Presets already all point at
deepseek-v4-flash / deepseek-v4-pro. Retire the old names everywhere
they were still surfacing as the default or discoverable surface:

- harvest.ts default model: deepseek-chat → deepseek-v4-flash
  (behaviorally identical — both route to v4-flash non-thinking)
- subagent tool enum: drop deepseek-chat/-reasoner; users pick
  flash vs pro now, no legacy names to distract the model
- subagent JSDoc: default was documented as pro but the actual
  constant is flash; fix the docs
- /model empty-arg hint: suggest v4 names instead of legacy aliases
- /think empty-reasoning hint: explain "thinking-mode models"
  generically instead of pinning to deepseek-reasoner

Kept legacy names in telemetry.ts (DEEPSEEK_PRICING,
DEEPSEEK_CONTEXT_TOKENS) because historical usage.jsonl rows still
reference them — the table is for pricing old sessions, not routing
new requests. Runtime `--model deepseek-chat` still works; the
isThinkingModeModel() abstraction is semantic (thinking vs
non-thinking), not version-bound, so it stays correct.
2026-04-24 20:14:20 -07:00
esengine f28d27290c fix(r1): unify reasoning_content round-trip around producing model
Prior fixes (0.5.15, 0.5.18) progressively unscoped the stamp but kept
a reasoning.length > 0 guard that silently dropped the field whenever
the model happened to return empty reasoning — legitimate on flash
thinking-mode turns with zero reasoning deltas, forced-summary paths
whose resp.reasoningContent is null, and non-streaming responses
returning reasoning_content: null. The next API call then 400'd with
"The reasoning_content in the thinking mode must be passed back."

Architectural smell: assistantMessage gated on reasoning-content
presence, while syntheticAssistantMessage gated on model type — two
different encodings of the same invariant.

Unify both around isThinkingModeModel(producingModel): the field is
present on the persisted assistant turn iff the model that generated
it runs in thinking mode, using the captured reasoning (or empty
string) as the value. Call sites pass the real producing model — not
this.model — so escalation (pro) and forced-summary (flash)
round-trip correctly.

Session-load heal: stampMissingReasoningForThinkingMode back-fills
empty reasoning_content on assistant turns from pre-fix session
files, so resuming an older session on a thinking-mode model no
longer 400s on the first request.

Tests: +5 (null-reasoning stamping on v4-flash, chat stays clean,
session-load heal for reasoner/v4-pro/chat). 1150 tests, tsc clean.
2026-04-24 20:14:05 -07:00
esengine 5453fc6dc3 refactor(plan): finish the split model started — types out, explicit barrel, per-tool helpers
The agent's live-run refactor (2c8... in the local log) correctly
split plan.ts into plan-core + plan-errors and preserved the barrel,
but stopped short of three things worth doing:

1. plan-errors.ts was mis-named — it also held the value types
   (PlanStep, PlanStepRisk, StepCompletion). Extracted those to
   a new plan-types.ts so file names match contents. Dependency
   direction is now plan-core → plan-errors → plan-types.

2. Barrel used \`export *\` from both modules, which would silently
   shadow on any future name collision. Replaced with explicit named
   re-exports so TS catches duplicates the moment they appear.

3. plan-core.ts was still ~240 lines, mostly a single
   registerPlanTool body with three inline tool-description strings.
   Split into registerSubmitPlan / registerMarkStepComplete /
   registerRevisePlan (one per screen) with descriptions hoisted to
   SCREAMING_SNAKE constants at the top and the duplicated step-item
   schema extracted to STEP_ITEM_SCHEMA. Function bodies now read as
   control flow, not prose. Public API unchanged.

1145 tests still green, typecheck + lint clean. Zero behavior change.
2026-04-24 19:55:39 -07:00
esengine 94a3c9d56e fix(choice): rewrite ask_choice guidance as one principle, not pattern list
Previous pass at tightening ask_choice guidance leaned on specific
anti-patterns — "方案 A:" headers, "你选哪个?" trailers, markdown
comparison tables. Ugly and brittle: next time the model adopts a
slightly different phrasing, we'd be patching yet another bullet.

Reframe as a single principle in both the tool description and the
code system prompt: "if the user is supposed to pick, the tool
picks — you don't enumerate the choices as prose." The model can
generalize from that.

Behavior contract is unchanged; the guidance is just cleaner and
easier to maintain. Prompt-engineering change only, no code logic.
2026-04-24 19:28:50 -07:00
esengine 4cb445b280 feat(plan): /replay — Time Travel canvas for archived plans
Atlas W2 wave 2: load an archived plan as a read-only snapshot.
'/replay' defaults to the newest archive; '/replay 2' jumps to the
second-newest; '/plans' enumerates the full set.

- SlashResult grows replayPlan field so the handler can push a
  structured payload — App.tsx mounts it as a plan-replay event
  rather than flattening to info text. Keeps the bordered box +
  step list + markdown body styling consistent with plan-resumed.
- New plan-replay DisplayRole + EventRow branch: gray border, ⏪
  icon, dim header (completed time, N/total nav, archive filename),
  markdown body rendered through the full pipeline, PlanStepList
  with every step marked done, footer hint for jumping archives.
- /replay handler in plans.ts looks up listPlanArchives(session)
  by 1-based index, validates range, carries the payload through.
  Per-session only — same project-isolation as /plans.
- /replay added to commands.ts with argsHint=[N] so slash
  autocomplete / hint surface picks it up.

Tests: 6 new slash tests cover default-newest, indexed lookup,
out-of-range rejection, empty-archive state, no-session guard, and
/plans summary label surfacing. Full suite 1145 green.
2026-04-24 19:16:18 -07:00
esengine 918ed2ca50 feat(plan): persist markdown body + add human summary field
Two schema additions that unblock Time Travel and make /plans
listings useful.

- submit_plan accepts optional \`summary\`: one-line title. Surfaces
  in the PlanConfirm header, the resume banner, and /plans so users
  identify plans by intent ('Refactor auth into signed tokens')
  rather than by filename.
- plan.json now stores the markdown \`body\` that came in with
  submit_plan. Replay will read this; previously the body only
  lived in the JSONL log, which is fine for the active session but
  hard to surface in a closed archive without re-parsing tool-call
  JSON.

Both fields are optional. Older plans without them still load and
render cleanly; /plans falls back to filename when no summary is set.

PlanProposedError carries summary through toToolResult. plan-store's
savePlanState grows an extras bag so callers don't have to care
about field proliferation. listPlanArchives surfaces both fields
on the PlanArchiveSummary type.

Tests: body+summary roundtrip, omission default, submit_plan
summary trim behavior, blank-rejection. Total: 1139 tests green.
2026-04-24 19:06:43 -07:00
esengine ebc967be35 feat(plan): /plans slash — list active + archived plans for the session
Adds a per-session history view. Active plan (from plan.json) +
archived completed plans (.done.json), newest-first. Project-local
by design — cd to another project to see its plans, no cross-project
listing.

Output:
  ▸ active plan: 2/5 steps done · last touched 1h ago

  Archived (3):
    ✓ 3d ago     5 steps · complete  code-foo.plan.2026-04-21-...done.json
    ✓ 2026-04-15 8 steps · complete  code-foo.plan.2026-04-15-...done.json
    ✓ 2026-04-10 3 steps · complete  code-foo.plan.2026-04-10-...done.json

- listPlanArchives scans sessionsDir() for the session-prefixed
  .done.json files. Sorts by stored updatedAt (with mtime fallback
  for hand-edited archives). Skips corrupt JSON / wrong-version /
  zero-steps archives instead of failing the whole list.
- /plans handler renders both views; falls back to a discovery hint
  when no plans exist yet.
- Tests: 6 new — empty state, ordering, active-only ignored,
  cross-session isolation, corrupt-resilience, mtime fallback.

Foundation for upcoming /replay <archive> + Time Travel canvas —
both will read these summaries to find replayable artifacts.
2026-04-24 18:55:42 -07:00
esengine 2e64d63c8b feat(plan): auto-archive completed plans for the artifact trail
When the model marks the final step done, the active plan.json moves
to a timestamped .done.json archive instead of lingering. Two reasons
this matters: (1) the next session starts with a clean slate — no
stale resume banner for work that's actually finished; (2) the
archive is the foundation Time Travel replay will read from in W2
wave 2 to show "what the model actually did vs what was planned".

- archivePlanState renames plan.json → plan.<ISO-stamp>-<rand>.done.json
  in sessionsDir(). Random 4-char suffix dodges within-millisecond
  collisions if two plans finalize back-to-back. Returns the archive
  path, or null when there's no active plan / rename fails.
- App.tsx mark_step_complete handler: after the progress row pushes,
  if total > 0 && completed >= total, archive and post a
  '▸ plan complete — all 5 steps done · archived' info row.
- Tests: 4 new — null-return on missing, rename verification,
  payload preservation through archive, collision-resistance.
2026-04-24 18:50:30 -07:00
esengine 6d8a2c596c feat(loop): visible reasons for auto-escalation decisions
Auto-escalation (flash → pro) was the only truly automatic per-turn
decision the user couldn't see into. The warning fired but said only
'flash requested escalation' or 'flash hit N edit failure(s)' — no
WHY. Two changes surface the rationale.

1. Self-report marker now carries an optional reason:
     <<<NEEDS_PRO>>>                    ← bare, still works
     <<<NEEDS_PRO: <reason>>>>          ← preferred, surfaces in warning

   parseEscalationMarker pulls the reason out, the warning becomes
   '⇧ flash requested escalation — <reason>'. Buffer bumped to 256
   chars so reasons aren't truncated mid-stream. The streaming
   look-ahead now uses looksLikePartialEscalationMarker so multi-
   line / colon-form markers don't flush prematurely.

2. Failure-threshold escalation tracks PER-TYPE counts (search-
   mismatch, scavenged, truncated, storm-broken). The warning now
   says 'flash hit 2× search-mismatch, 1× truncated' instead of
   '3 repair/error signals'. Same FAILURE_ESCALATION_THRESHOLD
   semantics; just better attribution.

ESCALATION_CONTRACT prompt fragment teaches both forms with examples.
Three new tests cover the reason-carrying marker, empty-reason edge,
and the unclosed-marker fallthrough (still treats as content, no
silent retry on a malformed signal).
2026-04-24 18:45:27 -07:00
esengine f6931481ba feat(plan): render full step list on resume, not just a one-liner
The W2 resume banner was a single info row — '▸ resumed plan: 2/5
steps done · last touched 3h ago'. Useful but minimal. Users had no
way to see WHICH steps were done or what's coming next without
scrolling back through the prior session's log.

New plan-resumed display role mounts a bordered box at the top of
the new session: header (badge + counter + relative time) plus
the full PlanStepList — same component used in PlanConfirm and the
checkpoint picker, with done steps dimmed + ✓, the next pending
step focused with the › cursor, and the risk gutter color-coded.

Carries the structured plan data through DisplayEvent.resumedPlan
so the renderer doesn't need access to the live planStepsRef. Pure
render layer; no new logic, no new tests needed (plan-store tests
already cover the data side).
2026-04-24 18:21:04 -07:00
esengine 15b0cfc894 feat(plan): persist structured plan state across session restarts
Atlas W2 wave 1: the plan the model submits via submit_plan (and
mutates via mark_step_complete / revise_plan) now survives terminal
close. Without this, all the structured-step / risk / checkpoint /
revise UX evaporated whenever you took a coffee break.

- New src/code/plan-store.ts: loadPlanState / savePlanState /
  clearPlanState / relativeTime. Storage path mirrors the JSONL
  convention: ~/.reasonix/sessions/<sanitized>.plan.json. Format is
  versioned (v1) with defensive parsing — corrupt files load as
  null, malformed step entries are filtered, invalid risk values
  are stripped, the rest of the plan still loads.
- App.tsx: load on mount, save after every plan-state change
  (submit_plan, mark_step_complete, revise_plan accept), clear on
  PlanConfirm cancel. The persistPlanState callback is threaded
  through all the relevant useCallback deps so React's exhaustive-
  deps rule stays clean.
- Resume banner: when an existing plan loads on startup, push
  '▸ resumed plan: 2/5 steps done · last touched 3h ago' into the
  scrollback so the user immediately sees the picked-up state.
- Tests: 15 covering save/load roundtrip, malformed-JSON recovery,
  version mismatch, partial step sanitization, completedStepIds
  filtering, path safety, and relativeTime branches.

The plan markdown body itself is NOT persisted here — it lives in
the session JSONL (it was a tool result), so resuming the session
replays it naturally. We carry forward only the live state needed
to keep mark_step_complete and revise_plan meaningful.
2026-04-24 18:16:05 -07:00
esengine 331e01fda1 feat(ui): tool duration + /tool N hint on compact rows
Compact tool rows now annotate with timing and a navigation hint:

  ▣ run_command (1.2s) → exit 0 · ✓ tests passed       /tool 12
  ▣ read_file → import { foo } · 234 lines · 4.5KB     /tool 13
  ▣ search_content (8.5s) → 5 matches · src/foo.ts:12  /tool 14

Duration is suppressed under 100ms (every read_file would scream
'47ms' otherwise — noise). Above that, formatDuration picks a tight
representation: ms → s.s → s → m+s as the magnitude grows.

The /tool N suffix makes the existing slash command discoverable
without scrolling — users can jump straight to full content via
`/tool 14` instead of guessing the position. toolIndex is captured
at push time as the 1-based length of the tool history.

App.tsx: toolStartedAtRef captures Date.now() on tool_start and
diffs at result. Single ref is enough — tools dispatch serially.
2026-04-24 18:04:07 -07:00
esengine 877a9ee03b feat(ui): compact one-line tool rendering with smart per-tool summary
Old tool rows were 6–8 vertical lines each (glyph row + blank + 400-
char body block). 10 tool calls in a session = ~70 lines of
mostly-noise content drowning the actually-interesting events
(checkpoint pickers, plan submissions, edit diffs).

New rendering: one line per tool call.

  ▣ read_file      →  import { foo } from 'bar' · 234 lines · 4.5KB
  ▣ list_directory →  17 entries
  ▣ search_content →  5 matches · src/foo.ts:12: const x = 1
  ▣ run_command    →  exit 0 · ✓ 17 tests passed
  ▥ run_command    ✗  exit 1 · TypeError: Cannot read property
  ▣ submit_plan    →  PlanProposedError — STOP, picker shown to user.

edit_file keeps its multi-line colored diff renderer (the diff IS the
value). Plan / Choice control-flow signals (PlanProposedError etc.)
render in non-error yellow even though they technically come through
the error envelope — they're picker triggers, not failures.

The summarizer is a pure function in tool-summary.ts so it tests
without Ink and can be reused by replay / transcript export later.
Full content remains accessible via `/tool N`.
2026-04-24 17:58:42 -07:00
esengine a4ff99236b feat(plan): revise_plan tool — surgical mid-flight plan edits with diff picker
Phase 2 Revise was just text-forwarding: user typed feedback, model
got a synthetic, model adjusted however it wanted with no structured
contract. Add revise_plan as the structured counterpart — the model
proposes new remainingSteps + a one-sentence reason, the TUI shows
a step-level diff, user accepts or rejects.

- New revise_plan tool (readOnly, throws PlanRevisionProposedError).
  Sanitization reuses sanitizeSteps so risk levels and malformed
  entries are handled the same as submit_plan.
- New PlanReviseConfirm modal: amber border, reason header, diff
  rows (-removed/red+strikethrough, +added/green, kept/dim), counter
  badge -N +M (K kept), Accept/Reject picker.
- App.tsx: pendingRevision state + handler. Accept splices the new
  steps onto the done-step prefix in planStepsRef (done work never
  undone), pushes an info row with -N+M counts, sends a continue
  synthetic. Reject sends a 'keep original' synthetic. Picker takes
  priority over checkpoint picker so a checkpoint-revise → revision-
  proposal flow chains naturally.
- Checkpoint Revise synthetic now nudges the model toward revise_plan
  for structural changes vs submit_plan for full reset.

Tests cover the error roundtrip, sanitization, risk preservation,
empty-input rejection, and the readOnly flag.
2026-04-24 17:38:53 -07:00
esengine c3d327e27f feat(plan): risk gutter + structured step list in plan pickers
Phase 1 structured steps were only used for post-approval progress
tallying — the user never saw them at decision time. Add risk-coded
step list to both PlanConfirm (approval) and PlanCheckpointConfirm
(mid-execution) so the plan shape is visible where it matters.

- New PlanStep.risk: "low"|"med"|"high" (optional). submit_plan
  description guides the model: high = hard-to-undo / prod / API
  changes; med = non-trivial but reversible; low = safe local.
- PlanStepList renders a compact list with 1–3 colored dots per step
  (●/●●/●●● green/yellow/red) + a ✓/▶/— glyph, a legend row, and
  a '3 steps · 1 done' counter. Steps without risk render a blank
  gutter, so pure-markdown plans degrade cleanly.
- PlanConfirm mounts the list above the approve/refine/cancel picker
  when steps are supplied.
- PlanCheckpointConfirm mounts the same list with the current step
  highlighted via a › cursor and completed steps dimmed, so the user
  can see what just finished and what's next before picking
  continue/revise/stop.

Result: a structured plan with risks looks like a real plan, not a
markdown blob. Pure-markdown plans keep working unchanged.
2026-04-24 10:14:48 -07:00
esengine acb3a3ffee fix(choice): make ask_choice reliably fire via tool desc + system prompt
Phase 1 ask_choice was technically working but models rarely called it
— the description leaned defensive ('don't misuse') with only a light
'use when genuinely user's call' nudge, so DeepSeek Flash kept writing
prose comparisons that ended with '你选哪个?' (no picker rendered).

Two-layer fix:
- Tool description leads with 'CALL THIS WHENEVER your next reply
  would end with A/B/C — 你选哪个?'. Spells out the self-detect
  triggers and the failure mode of text menus. 'When in doubt, call
  the tool' as the tiebreaker.
- Code system prompt gains a dedicated '# When to ask the user to
  pick (ask_choice)' section sibling to the submit_plan one, plus an
  inline warning in the submit_plan section against option-menu
  plans cross-referencing ask_choice.

Costs one prefix-cache miss on first turn after the update; hit rate
re-stabilizes after that. No test changes (the behavior under test
was already correct — this is pure prompt-engineering).
2026-04-24 09:15:28 -07:00
esengine 7e1695f945 feat(choice): ask_choice primitive for A/B/C branching decisions
New tool gives the model a proper home for branching questions —
submit_plan was getting misused as a route-picker and leaving users
stuck at approve/refine/cancel with no way to choose.

Tool throws ChoiceRequestedError (same toToolResult protocol as
PlanProposedError), TUI mounts ChoiceConfirm — a magenta-bordered
modal with the question, the option rows (title + dim summary), an
optional "Let me type my own answer" escape hatch, and cancel.
Picking routes a synthetic 'user picked <id>' back to the model;
custom ships whatever the user typed verbatim.

Registered in both code and chat modes so branching works anywhere.
Sanitizes malformed option arrays (DeepSeek V3/R1 occasionally drops
fields even with Pillar 3 auto-flatten) and caps at 6 options so the
model can't drown the user in choices. submit_plan's description now
cross-references ask_choice so the model learns the dispatch.

Foundation for the Atlas redesign — Fork Nodes in W2 will render
pending choices inline in the plan canvas instead of as a separate
modal.
2026-04-24 08:44:45 -07:00
esengine 248dd134ba fix(plan): forbid submit_plan from presenting A/B/C option menus
Tool description now explicitly tells the model not to use submit_plan
as a "pick one of these routes" menu. The approve/refine/cancel picker
has no branch selector, so a menu plan strands the user — hit in the
wild where the model used submit_plan to offer three project directions.

Branches belong in plain assistant text with a question; submit_plan
stays reserved for a single actionable plan.
2026-04-24 08:17:02 -07:00
esengine e5a75119cb feat(plan): mid-execution checkpoints — Continue / Revise / Stop
mark_step_complete now throws PlanCheckpointError so the loop pauses
after each step. A new PlanCheckpointConfirm picker drives what happens
next: Continue resumes the plan, Revise opens a feedback box whose
text is threaded into the next turn's context, Stop ends cleanly with
a summary.

Revise reuses PlanRefineInput's single-line UX with a new
"checkpoint-revise" mode label. Esc on the feedback input restores the
picker. The ✓ progress row from Phase 1 still renders before the
picker mounts, so the scrollback always records what was just done.

Ports the useful half of @imlingdu/reasonix-tools' dynamic-plan loop
into Reasonix's submit-plan / approval-gate model — Phase 3 will add
an LLM-driven revise helper on top.
2026-04-24 08:10:56 -07:00
esengine 11155add8a feat(plan): structured steps + mark_step_complete progress rows
submit_plan now accepts an optional steps:[{id,title,action}] array;
new mark_step_complete tool ticks them off during execution so the
scrollback shows `✓ step-1 · title — result (2/5)` instead of leaving
the user to infer progress from tool noise.

Pure-markdown plans keep working unchanged — steps and progress
rows only render when the model opted into the structured form.
2026-04-24 08:02:36 -07:00
esengine f82f93559b chore(release): 0.6.0
Cost control promoted to Pillar 4. Breaking behavior: default model
flipped from v4-pro to v4-flash; smart (default) preset no longer
auto-enables harvest; max preset no longer auto-enables branch 3.
New: /pro one-shot arming, failure-triggered auto-escalate, model
self-report <<<NEEDS_PRO>>>, turn-end auto-compaction, per-turn cost
badges. UI refactor: App.tsx -33%, slash.ts split into slash/ with
13 focused modules. See CHANGELOG for the full matrix.
2026-04-24 07:26:40 -07:00
esengine 5a7d16c24f fix(ui,prompt): dedupe edit_file result display; teach run_command its shell limits upfront
Two small papercuts from a 70-turn live run surfaced:

1. Every edit_file tool call showed the apply result TWICE — once
   as a dim info row (pushed by applyNow in the edit-mode
   interceptor), then again as a full `▣ edit_file → …` tool row
   yielded by the loop. Both with identical text. Wasted rows, made
   long sessions harder to skim.

   Fix: drop the info-row push inside applyNow. The returned string
   still becomes the tool result AND the model sees it via the tool
   event; the user sees it once via the tool row with its
   identifying header. The auto-text branch at turn-end (for
   text-form SEARCH/REPLACE blocks parsed from assistant prose)
   still pushes its own info row — there's no tool event to back
   it up.

2. The model repeatedly tried `cd dir && cmd`, `cmd1 | cmd2`,
   `cmd 2>&1`, learning only from the error reply. run_command's
   top-level description didn't spell the constraints upfront.

   Fix: front-load a "Constraints (read these before the first
   call):" block in both run_command and run_background
   descriptions. Explicit list of rejected operators, cd-doesn't-
   persist, and concrete alternatives (`npm --prefix`, `cargo -C`,
   `git -C`, `pytest tests/…` instead of `cd && …`). Also warns
   against unbounded-output commands like `netstat -ano` /
   `find /` that balloon context for no reason, with filtered
   alternatives.

Both are tool/UI changes only; 1054 tests green, typecheck + biome
clean.
2026-04-24 07:12:14 -07:00
esengine 292e51f0c2 fix(plan): render full plan body in scrollback, shrink PlanConfirm to picker only
User bug: "submit_plan" proposals were being truncated inside the
PlanConfirm modal with "(25 more lines truncated — resize the terminal
to see more)". The whole point of a plan review gate is that the user
can read the full thing before approving; the old design cut it off
at roughly 11 source lines to keep the picker on-screen.

Root cause: PlanConfirm rendered both the plan body (via Markdown)
AND the 3-option picker inside one Ink modal, with a hard line clamp
so total height never exceeded the TTY. The clamp fired unavoidably
on any non-trivial plan.

Fix: push the plan body to Static scrollback as a new display role
"plan" the moment submit_plan fires. The Static component renders
once into the terminal's permanent buffer (users can scroll back
through the terminal itself), and the PlanConfirm modal below
shrinks to a tight picker header + choice list. No truncation ever.

Changes:
- EventLog.tsx: new DisplayRole "plan" renders the plan body through
  the full Markdown pipeline inside a cyan-bordered box with a 📋
  header. Goes into <Static> so it's render-once + scrollable.
- App.tsx: on submit_plan detection, setHistorical pushes a "plan"
  row BEFORE setPendingPlan so the body is in scrollback by the
  time the modal mounts.
- PlanConfirm.tsx: dropped the embedded Markdown render, the line-
  clamp helper (clampBodyByLines), maxRenderedChars / terminalRows
  props, and the two constants that drove them. The modal is now
  just a header + open-questions hint + SingleSelect.
- tests/plan-confirm.test.ts deleted — its 5 tests were all for
  the removed clampBodyByLines helper.

Everything else (approve/refine/cancel semantics, staged-input
handoff, hasOpenQuestions hint toggle) unchanged. 1054 tests green.
2026-04-24 07:05:40 -07:00
esengine c5b0906576 fix(skill): run_skill accepts decorated names; index uses trailing [🧬 subagent] tag
Users hit \`run_skill({"name":"🧬 explore"}) → {"error":"unknown skill: \"🧬 explore\""}\`.
The Skills index wrote entries like \`- 🧬 explore — …\`, with the marker
LEADING the name. Models copied the whole thing verbatim into the
\`name\` argument and the lookup failed (VALID_SKILL_NAME regex rejects
emoji + spaces).

Two fixes, defense in depth:

1. Prompt format (primary fix). Rewrite skillIndexLine so the
   subagent marker trails the name, bracketed and labeled:
     old: \`- 🧬 explore — …\`
     new: \`- explore [🧬 subagent] — …\`
   Name comes first, unambiguous. The index intro + tool descriptions
   + CODE_SYSTEM_PROMPT all explicitly spell out "the \`name\` is ONLY
   the identifier before the tag."

2. run_skill normalization (belt-and-suspenders). If the model still
   passes a decorated name, strip \`[...]\` bracketed tags and pick
   the first whitespace-delimited token that starts with a word
   character. Handles every shape observed in the wild:
     "🧬 explore", "[🧬 subagent] explore", "[🧬] explore",
     "explore [🧬 subagent]", "  explore  "  → all resolve to "explore"

Tests:
- tests/skills.test.ts: updated to expect the trailing-tag format,
  explicit regression assertion against the old \`- 🧬 name\` pattern.
- tests/tools-skills.test.ts: new "normalizes decorated names" case
  exercising each decoration shape through run_skill dispatch.

All 1059 tests green.
2026-04-24 06:55:07 -07:00
esengine 30ca814809 feat(cost): model self-report escalation — flash emits <<<NEEDS_PRO>>>, loop retries on pro
Reactive-only escalation (wait for flash to rack up 3+ errors before
bumping to pro) burns tokens and time on tasks flash itself could
recognize as too hard upfront. Add a prompt-level contract: on flash,
the model can output `<<<NEEDS_PRO>>>` as the FIRST line of its
response to abort the current call and retry this turn on v4-pro,
one shot. Pro never self-escalates (the check short-circuits when
modelForCurrentCall === ESCALATION_MODEL).

This matters because non-expert users can't reliably predict which
tasks need the frontier tier. Letting the model self-assess catches
hard tasks upfront — design tradeoffs, architecture refactors, subtle
invariants — without auto-upgrading every prompt (which would destroy
the cost savings from flash-first defaults).

Implementation:
- loop.ts: NEEDS_PRO_MARKER constant, isEscalationRequest() helper,
  post-call retry check that sets _escalateThisTurn and re-enters
  the iter with `iter--; continue` on match. Streaming path buffers
  the first 80 chars / first line before yielding assistant_delta
  events so the marker never flickers on-screen before retry fires.
  Guarded against infinite retries by checking modelForCurrentCall
  against ESCALATION_MODEL — users who already chose /preset max
  see the marker as normal content.

- prompt-fragments.ts: new ESCALATION_CONTRACT fragment spells out
  when to use the marker (cross-file refactors, subtle correctness
  invariants, design tradeoffs) and when NOT to (small edits, clear
  bug fixes). Embedded into CODE_SYSTEM_PROMPT, DEFAULT_SYSTEM, and
  DEFAULT_SUBAGENT_SYSTEM — subagents default to flash+high too,
  so they benefit from the same escape hatch.

Tests (3 new in loop.test.ts):
- flash emits marker → retry on pro, final content is pro's response
- marker mid-text (not lead-in) → no retry
- pro emits marker → no infinite-retry loop

All 1058 tests green.
2026-04-24 06:47:31 -07:00
esengine 000e7c3ac0 docs(architecture): rewrite for v0.6 — four pillars, flash-first, new module layout
The previous ARCHITECTURE.md stopped at v0.3 (MCP + session persistence)
and read three-pillar (cache loop, harvest, tool-call repair) with a
roadmap that predates everything from v0.4 onward. After six months
of cost and refactor work the codebase is fundamentally different:
file layout reorganized, defaults flipped flash-first, branch + harvest
removed from every preset, /pro arming and failure-triggered
auto-escalation added.

New sections:
- Pillar 4 — Cost Control as a first-class subsystem: tiered defaults,
  turn-end auto-compaction, /pro one-shot arming, failure-signal
  auto-escalation, cost transparency thresholds.
- Module layout refreshed — reflects the slash/ + handlers/ split,
  the six hooks under cli/ui/, prompt-fragments.ts, and actual LOC
  counts (App.tsx 2931 → 1984).
- Design evolution replaces the stale roadmap — covers v0.0 through
  v0.6 with a line each so readers orient without reading six months
  of CHANGELOG.
- Non-goals updated to call out "automatic cost escalation without
  user-visible announcement" as explicitly rejected.

Pillar 2 (harvest) and Pillar 3 (tool-call repair) content kept intact
and marked as before. Pillar 1 unchanged.

Pure docs change — no code touched.
2026-04-24 06:32:00 -07:00
esengine a22355a2ab feat(cost): per-turn cost badge in StatsPanel + pro armed/escalated pills
Cost transparency is the last piece of the cost-control design —
users can now see at a glance how much the current turn cost and
which model it ran on, without opening /stats.

StatsPanel header picks up two new pills:
- ⇧ pro armed (yellow) — /pro queued, next turn will run on v4-pro
- ⇧ pro escalated (red) — current turn is on v4-pro (either /pro
  armed was consumed at turn start, or the failure threshold
  tripped mid-turn auto-escalation)

The cost cell now splits into two readings:
- turn $0.0042 — last turn's cost, colored by threshold
  (green <$0.05, yellow $0.05-0.20, red ≥$0.20)
- session $0.1234 — cumulative, same color scale 10× up
  (green <$0.50, yellow $0.50-5, red ≥$5)

No hard circuit-breaker that blocks turns — a mid-session pop-up
gate would be annoying. The colored thresholds are the signal;
users who notice yellow/red can /preset fast or /compact before
shipping the next message.

Plumbing:
- telemetry.ts: SessionSummary.lastTurnCostUsd added. Populated by
  SessionStats.summary() from the most recent TurnStats.cost.
- replay.ts + ReplayApp.tsx: summary-shape call sites updated.
- StatsPanel.tsx: proArmed/escalated props; CostCell refactor;
  turnCostColor/sessionCostColor threshold helpers.
- slash types: armPro / disarmPro ctx callbacks so the /pro handler
  can update App's mirror state synchronously.
- App.tsx: proArmed + turnOnPro state mirrors, turn-start/end
  transitions, warning-event sniff for "⇧" prefix flips turnOnPro.

Tests: 1055 green, typecheck + biome clean.
2026-04-24 06:27:23 -07:00
esengine 39a4e137dc feat(cost): /pro single-turn arming + auto-escalate on repeated flash failures
Two cost-aware escalation paths join the loop, keeping flash-first
as the default but letting the system (or the user) bump to v4-pro
when flash is visibly struggling — without requiring a persistent
preset switch.

1. `/pro` slash command arms pro for the NEXT turn only. Consumed
   at turn start, auto-disarms after the turn ends. Use case: the
   user knows the upcoming ask is hard and wants one-shot strength
   without typing /preset max + remembering to revert. Separate from
   /preset max (persistent, changes this.model) — armed state is
   strictly single-turn.

2. Auto-escalation on failure. The loop tracks visible "flash is
   struggling" signals per turn:
     - edit_file / write_file SEARCH-not-found errors
     - ToolCallRepair fires: scavenge, truncation-fix, storm-break
   Once the count hits FAILURE_ESCALATION_THRESHOLD (3) in one
   turn, the remainder of that turn's model calls upgrade to
   v4-pro. Announced via a yellow warning row — no silent cost
   surprises. Counter + escalation flag reset at every turn start.

Wiring:
- loop.ts: `_proArmedForNextTurn`, `_escalateThisTurn`,
  `_turnFailureCount` private state. Public `armProForNextTurn`,
  `disarmPro`, `proArmed`, `escalatedThisTurn` getters for UI.
  `modelForCurrentCall()` returns the effective model (escalated
  or this.model). `noteToolFailureSignal()` centralizes the
  increment+threshold logic.
- All three chat call sites (branch path, streaming, non-streaming)
  use `modelForCurrentCall()` instead of `this.model` directly.
- stats.record uses the actual model for cost attribution.
- Library-mode default model: v4-pro → v4-flash (aligned with CLI).
- slash/handlers/model.ts: new `pro` handler with /pro, /pro off.
- slash/commands.ts: /pro registered in SLASH_COMMANDS + /help text.

Tests: 1055 green, typecheck + biome clean.
2026-04-24 05:51:24 -07:00
esengine 0383255de2 feat(cost): auto-compact tool results at turn end + lower proactive threshold
Context bloat was the real cost driver, not model tier. A single
read_file returning 12K tokens rides every subsequent turn's prompt
at the cache-hit rate; 10 reads accumulate to 100K+ carry-cost
that each turn pays until the 60% reactive threshold kicks in.
By then the user has already paid for 20-40 turns of inflated
context.

Two changes shift us from reactive to preventive:

1. autoCompactToolResultsOnTurnEnd — fires at every `done` event
   (normal completion, abort, forced summary). Shrinks every tool
   result in the log over 3000 tokens to a tight cap. The model
   can re-read the file if it needs fresh detail — one extra
   read_file call is far cheaper than dragging 12KB through every
   future turn.

2. Proactive in-turn threshold lowered from 60% → 40%. The turn-end
   compact already handles the common case; this threshold now
   only catches multi-iter turns where one tool returned a huge
   payload mid-turn, before the turn ends. 40% triggers earlier
   without waiting for context to get tight.

Net impact on long sessions: per-turn prompt tokens stop compounding.
Expected monthly cost reduction for active users: ~3-5× on long
projects where tool results accumulate.

Constants:
- TURN_END_RESULT_CAP_TOKENS = 3000 (new)
- ARGS_COMPACT_THRESHOLD_TOKENS = 800 (unchanged; per-response args shrink)

Tests: 1055 green, typecheck + biome clean.
2026-04-24 05:22:32 -07:00
esengine b2a50d50f5 feat(cost): cheap defaults everywhere — flash-first, pro opt-in, no auto-branch/harvest
Overhauls the cost model so `reasonix code` doesn't burn pro-tier
tokens by default. Three principles:

1. The default turn runs on v4-flash, not v4-pro. Pro is a ~12× tier
   and shouldn't be implicit. Users escalate with /preset max.
2. Branch and harvest are NEVER auto-enabled by any preset. Both
   multiply per-turn cost (N× and +1 flash call respectively); both
   now require explicit /branch N or /harvest on.
3. Non-user-facing model calls (forced summary on budget exhaustion,
   subagent runs, truncation repair) route through flash+high
   regardless of the user's main-turn tier. No reason to pay pro
   rates for a wrap-up paragraph or an explore subagent's grep chain.

Preset redefinition (branch=1, harvest=false for all three):
  fast   v4-flash + effort=high   cheapest · Q&A, one-line edits
  smart  v4-flash + effort=max    default · day-to-day coding
  max    v4-pro   + effort=max    ~12× fast · hard single-shots

Default preset is now `smart` (was `fast`) — flash+max is the best
price-per-quality point for coding work. `fast` is the "I just want
a quick answer" escape hatch.

Specific changes:
- cli/ui/presets.ts — new PresetSettings shape adds `reasoningEffort`;
  PRESETS values rewritten; PRESET_DESCRIPTIONS reflect cost story;
  `resolvePreset` default is now "smart".
- cli/resolve.ts — ResolvedDefaults gains `reasoningEffort`; default
  preset is "smart".
- cli/commands/code.tsx — default model v4-pro → v4-flash.
- tools/subagent.ts — DEFAULT_SUBAGENT_MODEL v4-pro → v4-flash;
  DEFAULT_SUBAGENT_EFFORT = "high" (down from parent's "max").
  Skill frontmatter `model:` / `effort:` remain the escape hatches.
- loop.ts — forceSummaryAfterIterLimit hard-codes flash+high for the
  wrap-up call; stats.record attributes the actual summaryModel so
  /stats reflects reality.
- slash handlers — /preset rewritten (persists effort now); /harvest
  and /branch print cost-warning suffixes; /help + /keys text updated
  to match new presets and warn harvest/branch are opt-in only.
- CLI --help strings for `reasonix chat` / `reasonix code` / `--preset`
  / `--harvest` / `--branch` updated.

Tests:
- resolve.test.ts: expectations updated to new defaults (flash+max,
  no branch in max preset).
- slash.test.ts: preset test expectations updated to new combos.
- subagent.test.ts: default-model fallback expectation updated.
All 1055 tests green; typecheck + biome clean.
2026-04-24 04:59:15 -07:00
esengine e486a8e23a refactor(prompt): share TUI formatting + negative-claim rules across prompts
The TUI formatting rules (GFM tables, no Unicode box-drawing, no
decorative ┌──┐ frames, flow charts as bullet lists) were
maintained as three near-identical copies across
DEFAULT_SUBAGENT_SYSTEM, BUILTIN_EXPLORE_BODY, and
BUILTIN_RESEARCH_BODY — and missing entirely from
CODE_SYSTEM_PROMPT, even though the main code reply goes through
the same markdown renderer.

Subagents also lacked the "negative claims are the #1
hallucination shape" guardrail that the main code prompt has.
When an explore/research subagent confidently reported "X is
missing", the parent swallowed it at face value.

Changes:
- New src/prompt-fragments.ts holds TUI_FORMATTING_RULES and
  NEGATIVE_CLAIM_RULE as shared constants — single source of
  truth, embedded literally so prefix-cache hashing stays stable.
- DEFAULT_SUBAGENT_SYSTEM, BUILTIN_EXPLORE_BODY, and
  BUILTIN_RESEARCH_BODY import and interpolate both fragments
  instead of open-coding their own copies.
- CODE_SYSTEM_PROMPT imports TUI_FORMATTING_RULES and appends it
  after the Style section.
- CODE_SYSTEM_PROMPT's intro tool list now names every
  filesystem tool (read_file, write_file, edit_file,
  list_directory, directory_tree, search_files, search_content,
  get_file_info) instead of trailing off at "etc." before the
  essential search_content / edit_file were listed.

Behavior change is small and aligned: fewer hallucinated absences
from subagents, fewer Unicode-box-drawing tables to patch around
in markdown.tsx. Typecheck + biome + 1055 tests green.
2026-04-24 04:38:56 -07:00
esengine a4c1e9b478 refactor(ui): split slash.ts into per-topic handler modules
slash.ts had 1786 lines: types + SLASH_COMMANDS spec + parse
helpers + a ~800-line handleSlash switch + five private feature
handlers + utility helpers. Adding a command meant editing a
monolith; tests had to load the whole thing just to call one
handler. Layout:

    slash.ts                   20-line barrel (re-exports only)
    slash/types.ts             SlashResult / SlashContext / ...
    slash/commands.ts          SLASH_COMMANDS + parse functions
    slash/helpers.ts           git/memory/token/MCP utilities
    slash/dispatch.ts          SlashHandler type + registry +
                               handleSlash lookup
    slash/handlers/
      basic.ts     exit/clear/new/keys/help/setup/retry
      mcp.ts       mcp
      memory.ts    memory family
      skill.ts     skill/skills
      admin.ts     hooks/update/stats
      observability.ts   think/tool/context/status/compact
      edits.ts     undo/history/show/apply/discard/plan/mode/commit
      jobs.ts      jobs/kill/logs
      sessions.ts  sessions/forget
      model.ts     model/models/harvest/preset/branch/effort

Each handler is a plain (args, loop, ctx) => SlashResult function;
aliases (exit/quit, new/reset, skill/skills, apply-plan/applyplan,
hook/hooks, think/reasoning, help/?) are just duplicate keys in
the per-module handlers bag. The public import surface is
preserved via the barrel so App.tsx, tests, and sibling
components keep their existing imports.

Result: slash.ts 1786 -> 20 lines, fanned out into 13 focused
files each under 265 lines. Typecheck + biome + 1055 tests green.
2026-04-24 04:28:52 -07:00
esengine 9fdbdf738b refactor(ui): extract hooks + live components from App.tsx
App.tsx had grown to 2931 lines: streaming state, edit history,
pending-edits, shell/plan/edit confirm, @-picker, slash pickers,
subagent sink, hooks live-reload and cursor tracking all in one
function body. Split the cohesive clusters into dedicated modules
with no behavior change:

- LiveRows.tsx      StatusRow / ModeStatusBar / UndoBanner /
                    SubagentRow / OngoingToolRow + summarizeToolArgs
- edit-history.ts   EditHistoryEntry type + isEntryFullyUndone /
                    entryStatus / format{EditResults,PendingPreview,
                    UndoRows} / describeRepair
- useEditHistory    session-scoped /undo /history /show machinery
- useCompletionPickers  slash-name, @-mention, slash-arg pickers
- useSessionInfo    mount-time fetch of balance / models /
                    latestVersion + refresh callbacks
- useSubagent       subagent sink ref + live activity row

Also drops two dead helpers (formatQueuedEditPreview,
formatUndoResults) that had no callers.

Result: App.tsx 2931 -> 1984 lines (-32%). Typecheck + biome +
1055 tests green.
2026-04-24 04:28:33 -07:00
esengine f3f844b3dc fix(lint): pass biome check for 0.5.24 (format + unused template + exhaustive deps + comma/assign)
- biome format pass on EditConfirm / edit-blocks / jobs / shell /
  filesystem / compact-tokens / App / slash (auto-fixes)
- drop backtick template on a plain-string literal ("failed",
  "(already reverted — …)")
- annotate interceptor useEffect with a useExhaustiveDependencies
  ignore — the closure captures are intentional; adding the refs as
  deps would tear down the interceptor on every mode flip
- add codeHistory / codeShowEdit to handleSubmit deps
- expand comma-operator tricks in tests/tools.test.ts into
  explicit statements (biome rejects `(x = 1, "y")` and comma
  operator under lint/style/noCommaOperator + noAssignInExpressions)

prepublishOnly (lint + typecheck + test + build) now passes clean.
1055 tests, dist built.
2026-04-24 02:23:37 -07:00
esengine d65ca4f67f feat(code): review/auto edit gate, background jobs, context hygiene (0.5.24)
- EditConfirm modal for per-edit review (scrollable diff); Shift+Tab
  cycles review/auto; 5s undo banner + `u` keybind; session edit
  history with /history, /show [id] [path], /undo [id] [path]
- run_background / job_output / stop_job / list_jobs tools with
  ready-signal detection; /jobs, /kill, /logs; tree-kill (Windows
  taskkill /T /F, POSIX process.kill(-pid)) so dev servers actually
  stop; cleanup on SIGINT / SIGTERM / exit
- Bottom mode status bar always above the prompt: mode, pending
  count, Shift+Tab hint, running-jobs tag; one-time onboarding tip
  on first launch after upgrade
- Context hygiene: read_file `range:"A-B"` + auto-preview for files
  >200 lines; directory_tree default depth 4→2 + skip deps
  (node_modules / .git / dist / …) + per-directory 50-child collapse;
  auto-compact tool-call args after each tool response (>800 tok);
  /compact now covers both tool results and tool-call args
- Persist reasoningEffort to config so /effort high survives restart
  (earlier: silently reverted to max); editMode already persisted
- Prompt: scope discipline on "run/start/launch" requests so the
  model stops after verifying instead of auto-refactoring; teach
  model that run_background is for dev servers and review-mode
  rejections should not be retried with the same SEARCH/REPLACE

tests: 1055 passing (+17 new)
2026-04-24 02:17:34 -07:00
esengine ee577995d0 fix(errors): actionable messages for 401/402/422 + V4 context-overflow hint (0.5.23)
Before: DeepSeek auth/balance/parameter errors surfaced as raw
"DeepSeek 401: {\"error\":{\"message\":\"...\"}}" JSON blobs. Users
saw a wall of JSON and had to know to parse it themselves to learn
their API key was bad or they were out of credit.

formatLoopError now recognizes the per-code cases:

  401 → "Authentication failed (DeepSeek 401): <inner msg>. Your API
         key is rejected. Fix with `reasonix setup` or
         `export DEEPSEEK_API_KEY=sk-...`. Get one at
         https://platform.deepseek.com/api_keys."
  402 → "Out of balance (DeepSeek 402): <inner msg>. Top up at
         https://platform.deepseek.com/top_up — the panel header
         shows your balance once it's non-zero."
  422 → "Invalid parameter (DeepSeek 422): <inner msg>"
  400 → "Bad request (DeepSeek 400): <inner msg>"

Each unwraps `{"error":{"message":"..."}}` so the reader sees prose,
not JSON. Fallback keeps the raw body if parsing fails.

Context-overflow text also refreshed: mentions V4's 1M window AND
the legacy 131k for the chat/reasoner aliases, and drops the stale
"v0.3.0-alpha.6+" reference that's long-since rolled into the 0.5
release line. The "8k tokens per tool result" cap is current
(src/mcp/registry.ts DEFAULT_MAX_RESULT_TOKENS).

429/500/502/503/504/408 retries unchanged — fully absorbed by
retry.ts before they reach formatLoopError.

1013 tests (+6). Lint / typecheck / build clean.
2026-04-23 21:22:14 -07:00
esengine e3d6fe3a86 fix(client): bump default timeout past DeepSeek's 10-min queue cap (0.5.22)
DeepSeek's 2026-04 docs spell out that when concurrency is saturated
but the request is accepted, the connection stays open for up to 10
minutes while the request waits in the queue — non-streaming bodies
fill with empty lines, streaming bodies fill with `:` SSE keep-alive
comments. Both are invisible to our parsers (JSON.parse tolerates
leading whitespace; eventsource-parser drops `:`-prefixed comment
lines per the SSE spec), so no separate handling is needed.

What WAS broken: `timeoutMs` defaulted to 120s. A request that sat
in the queue past 2 min triggered our AbortController, which burned
the queue slot and bounced through retryWithBackoff — potentially
looping through the whole queue repeatedly and never landing.

Fix: bump default to 660_000ms (11 min). Server's own 10-min cap
closes the connection first on genuine queue overflow (clean EOF
→ our retry is normal), while still catching truly hung sockets.

Callers that want a tighter budget (short-lived CI checks, smoke
tests) keep their explicit `timeoutMs` override. No API shape change.

1007 tests. Lint / typecheck / build clean.
2026-04-23 21:17:04 -07:00
esengine bfc4cd38ee docs(readme): update for V4 models, /effort, /resource, /prompt, 1M context, !/@ shortcuts
- Tagline + /preset max + /think: V3/R1 → V4 (flash + pro)
- /model row lists v4-flash/pro as primary, chat/reasoner as compat aliases
- Add /effort, /resource, /prompt, /models, /context, /stats, /keys rows
- Context window 131k → 1M; test count 648 → 1007
- New "Prompt prefixes — !cmd and @path" section documenting the bang-
  mode shell shortcut (0.5.8, now session-durable) and @-mentions
  picker (0.5.5-0.5.7) — both are daily-use features that had no home
  in the README until now.
- Panel header example bumped from 0.4.22 to the current 0.5.21 with
  the reasoning-effort `· max` badge visible.

No code changes.
2026-04-23 21:13:00 -07:00
esengine 0ccc419d0d feat(v4): integrate DeepSeek V4 — models, pricing, thinking toggle, effort control (0.5.21)
Models & pricing (src/telemetry.ts):
- Add deepseek-v4-flash (¥0.2 / ¥1 / ¥2 per 1M hit/miss/out) and
  deepseek-v4-pro (¥1 / ¥12 / ¥24), converted at 7.2 CNY/USD.
- deepseek-chat and deepseek-reasoner now priced identically to
  v4-flash — per the 2026-04 V4 launch they're compat aliases for
  flash non-thinking / thinking modes respectively.
- Context bumped to 1M tokens across all four entries.

Defaults shifted to v4-pro (agent-class flagship):
- `reasonix code` mode, subagent DEFAULT_SUBAGENT_MODEL, loop
  constructor fallback, `max` preset all point at deepseek-v4-pro.
- `fast` / `smart` presets stay on chat/reasoner — those aliases are
  currently our only way to pin thinking ON or OFF via model name,
  so the preset system still has a cheap/fast option.
- Subagent tool enum widened to [v4-flash, v4-pro, chat, reasoner];
  description flipped to treat flash as the "cheaper opt-out" path.

Thinking-mode toggle + reasoning_effort (new API params):
- src/types.ts ChatRequestOptions gains `thinking?: "enabled" | "disabled"`
  serialized as extra_body.thinking.type, and `reasoningEffort?:
  "high" | "max"` as the top-level reasoning_effort field.
- src/loop.ts exposes thinkingModeForModel(model) and pins the
  correct value per model name (chat=disabled, reasoner=enabled,
  v4-*=enabled, unknown=undefined/server-default). Every turn now
  sets thinking + reasoningEffort explicitly — no more relying on
  server defaults to match what reasoning_content round-trip expects.
- reasoning_effort defaults to "max" because Reasonix is exactly the
  agent-class use case DeepSeek's docs call out.

UI: /effort slash + StatsPanel badge:
- `/effort [high|max]` flips the loop's reasoningEffort mid-session.
- `/effort` no-arg reports the current value.
- StatsPanel header shows a green `· max` or yellow `· high` tag next
  to harvest/branch/PLAN so users always see which tier the next turn
  will use. `/status` flags line also reports it.

Harvest cost tuning (src/harvest.ts):
- Default model reverted to deepseek-chat — harvest is a micro-
  extraction (4 small arrays of strings), not agent work.
- chat() call explicitly pins thinking=disabled + effort=high so a
  future default-model swap can't accidentally promote this micro-
  call into a multi-thousand-reasoning-token request.

1007 tests (+9 new: thinking toggle, /effort slash, v4 pricing).
Lint / typecheck / build clean.
2026-04-23 21:10:13 -07:00
esengine 7542aca687 feat(ui): show "N ready · building call M" during multi-tool turns (0.5.19)
Long assistant responses with many tool_calls used to render as a
single static "building tool call <write_file> · 37 chars" spinner
for 10–30s — user could see tokens being consumed but had no sense of
how many files were coming or how far along the stream was.

Each tool_call's `arguments` blob is now tried as JSON at every delta.
Once it first parses, the index is marked "ready" and the count goes
into subsequent `tool_call_delta` events. The UI label becomes
"building tool call (call 3) <write_file> · 127 chars · 2 ready"
so the user sees progress accumulating.

Dispatch timing is UNCHANGED — this is purely a visibility upgrade.
Mid-stream eager dispatch was considered and punted because it would
interact awkwardly with the repair step (truncation fix, storm
breaker, scavenge) that runs post-stream.

+6 tests locking down looksLikeCompleteJson (the gate that decides
when a streaming call counts as "ready"). 991 tests.
2026-04-23 20:18:10 -07:00
esengine 1e906bb577 fix(r1): round-trip reasoning_content on EVERY reasoner assistant turn (0.5.18)
0.5.15 scoped the fix too narrowly — only attached reasoning_content
when `tool_calls.length > 0`. DeepSeek's "thinking mode must be
passed back" rule applies to ANY R1-generated assistant message.

Symptom: plan approved → synthetic user message "implement it now" →
next API call 400s. The intermediate "plan submitted — awaiting
approval" plain-text R1 turn was persisted without its reasoning,
and R1 rejected the entire history the next time around.

Changes:
- assistantMessage() drops the tool_calls guard; reasoning attaches
  whenever the model emitted any (even on plain-text turns).
- Forced-summary path (no-tools fallback) now captures reasoning from
  the summary response.
- New syntheticAssistantMessage() stamps an empty-string
  reasoning_content on synthetic turns (Esc-abort notices) when the
  model is a reasoner, so R1's validator is satisfied even when no
  real reasoning exists. V3 stays clean.
- Test updated: plain-text reasoner turn now asserts reasoning
  DOES round-trip (reversed from 0.5.15's assumption).

985 tests.
2026-04-23 20:03:06 -07:00
esengine a8c367ad0c fix(citation): leading / resolves to project root, not filesystem root (0.5.17)
Symptom: user wrote a game design doc to `F:/Reasonix/game-design-doc.md`,
the model cited it as `[...](/game-design-doc.md)`, and Reasonix rendered
"✗ /game-design-doc.md → file not found" even though the file was
right there on disk.

Cause: `validateCitation` ran `isAbsolute(path)` on the raw URL. A model
writing `/foo.md` means "project-root relative" (Aider / Claude-Code
convention), but Node's isAbsolute returns true, so the validator
stat'd the literal `/foo.md` under the filesystem root and got ENOENT.

Fix: strip leading `/` or `\` before the absoluteness test. Drive-letter
paths (`C:\...`) still pass isAbsolute and are respected; plain
leading-slash paths become project-relative. Unix absolute citations
like `/etc/hosts` lose precision but are vanishingly rare in code
citations — if we need them we'll add an explicit scheme.

+2 markdown tests for the new leading-slash behavior (both `/` and `\`).
985 tests.
2026-04-23 19:57:49 -07:00
esengine 2d35cab39e fix(plan): actually stop the flicker — pause ticker, tighten clamp, stabilize onChoose (0.5.16)
0.5.14's clamp was insufficient. Three root causes the earlier fix missed:

1. TickerProvider kept pumping 120ms re-renders even while the picker
   was up — the memo'd PlanConfirm still re-evaluated on every tick
   because `onChoose` identity changed (handlePlanConfirm has `busy` in
   its deps; busy toggles during model streaming). Fix: disable the
   ticker while `pendingPlan` or `pendingShell` is set. No ticker = no
   re-render cadence to drive Ink redraws.

2. `clampBodyByLines` clamped SOURCE lines, not rendered rows.
   Markdown expands ~2× (wrap, code fences, heading blanks, list
   indent), so `rows - 18` source lines still overflowed on a 40-row
   terminal. Fix: divide by MARKDOWN_EXPANSION before clamping so the
   rendered output actually fits.

3. `handlePlanConfirm` identity churns — wrapped in a ref-stable
   `stableHandlePlanConfirm` so `React.memo(PlanConfirm)`'s shallow
   compare actually skips re-renders when `plan` + `projectRoot`
   haven't changed.

Together these pin the picker's rendered height to a known budget AND
eliminate the re-render loop that caused Ink to clear+redraw each
frame. The overflow-can't-scroll symptom is inherent to Ink's live
mode; only remedy is to make content fit, which the tightened clamp
now guarantees.
2026-04-23 19:54:19 -07:00
esengine 874d7df2f7 fix(r1): round-trip reasoning_content through tool loop (0.5.15)
DeepSeek R1 thinking mode 400s with "The reasoning_content in the
thinking mode must be passed back to the API" when a tool-loop
continuation replays an assistant message that had tool_calls but
no reasoning. Root cause: assistantMessage() stripped the field.

Fix: ChatMessage gains optional reasoning_content. Loop passes the
captured reasoning into assistantMessage; we attach it only when
the turn has tool_calls AND reasoning is non-empty — plain-text
R1 turns stay lean, deepseek-chat is unaffected.

+2 tests (loop-r1-reasoning): turn-2 body asserts the echoed
assistant message carries reasoning_content on a tool-call turn,
and does NOT carry it on a plain-text turn.
2026-04-23 19:50:18 -07:00
esengine 4d39744d99 feat(0.5.14): visible/durable/reachable + plan-flicker + pending-edit persistence
- !cmd bang output now persists via loop.appendAndPersist, so session
  resume sees the shell history the model already reasoned against.
- Subagent runs (run_skill · runAs:subagent) now emit cost/model/usage
  on their end event. App.tsx writes one row to ~/.reasonix/usage.jsonl
  per run; the completion line also shows $X inline. `/stats` and
  `reasonix stats` render a new "subagent activity" section with
  per-skill breakdown.
- `/resource [uri]` + `/prompt [name]` slashes with argument-level
  pickers (reusing 0.5.13's SlashArgPicker). No arg lists what every
  connected MCP server exposes; with arg reads via live McpClient
  stored on McpServerSummary. Display-only v1 — no loop injection.
  `/mcp` now hints toward these when servers expose resources/prompts,
  `/keys` gets an "MCP exploration" section, `/help` lists both.
- Bug A — plan picker flicker on small terminals: PlanConfirm's
  markdown body is now line-clamped to (rows − 18), and the component
  is React.memoed so tick-driven parent re-renders skip the heavy
  Markdown subtree when props are unchanged.
- Bug B — pending-edit queue wiped on crash: new
  src/code/pending-edits.ts checkpoints the queue to
  ~/.reasonix/sessions/<name>.pending.json on every parse. /apply
  and /discard clear the file; session resume restores it with a
  visible banner. deleteSession removes the sidecar too.

981 tests (+31). lint / typecheck / build clean.
2026-04-23 19:44:28 -07:00
esengine 74da4f2a92 revert /edit slash + fix picker blocking Enter on exact match (still 0.5.13)
Two small course-corrections on the 0.5.13 work-in-progress. Version
stays at 0.5.13 — these land before publish.

### 1. Remove /edit

The one-shot `/edit <file> <instruction>` slash was 99% redundant
with `@path/file.ts <instruction>`: the 0.5.5 `@`-mention already
inlines the file, and code-mode's system prompt already teaches the
model to output SEARCH/REPLACE blocks. `/edit` added only the
"output ONLY a block, no prose" hint — not worth a whole slash.

Reverted:
- case "edit" handler (slash.ts)
- SLASH_COMMANDS registry entry
- /help line
- /edit test describe block + "/help mentions /edit" + required-list
- "file" from the argCompleter union type (no consumer left; the
  `@` picker remains the single file-picker surface, avoiding two
  competing file-autocompletes)
- "file" branch in App.tsx's slashArgMatches memo + the trailing-
  space special case in pickSlashArg

Users who want one-shot edits type `@src/foo.ts fix the typo` —
clearer to read in history and the model obliges by default.

### 2. Picker blocked Enter after exact match

Typing `/preset smart` left the picker visible with one match
("smart") → Enter was intercepted and re-substituted the same value
instead of submitting the command. Fix: slashArgMatches memo now
returns null when the partial is a case-insensitive EXACT match for
an enum value (or a model id). Picker hides; Enter submits.

- Test added documenting that the detector itself remains kind-
  only — the hide-on-exact-match logic lives in the App-side memo
  so the detector stays UI-agnostic.

### Tests

946 (was 952; dropped 6 /edit-specific tests, added 1 regression
for the exact-match fix, dropped the File-picker-for-/edit detector
test since that path is gone). Lint + typecheck + build clean.
2026-04-23 19:08:14 -07:00
esengine 36f6d245f9 feat(ui): argument-level pickers for slash commands (0.5.13)
User feedback: "after I type `/edit` there's no hint about what files
exist — same for other commands with args." Fixed.

### Mechanism

SlashCommandSpec gains an `argCompleter` field:

- `"file"`    → file picker (reuses atFiles + rankPickerCandidates
                with mtime + recently-used ranking from 0.5.12)
- `"models"`  → DeepSeek model-id list fetched at startup
- `string[]`  → small enum (e.g. `["fast", "smart", "max"]`)
- omitted     → no picker, just a dim usage hint below the prompt

Attached to: /edit → file, /preset → enum, /model → models,
/plan → on/off, /harvest → on/off, /branch → off + a few N values.

`detectSlashArgContext(input, codeMode)` in slash.ts classifies the
buffer once the user has typed `/<cmd> ` — returns `{spec, partial,
partialOffset, kind}`. `kind` is "picker" (completable first-arg
position) or "hint" (past the first arg / no completer).

`src/cli/ui/SlashArgPicker.tsx` — new component mirroring the
SlashSuggestions / AtMentionSuggestions layout. Header row always
shows `/<cmd> <argsHint>  — <summary>` so even when no matches,
the user sees what's expected. Hint-only mode is a single dim row.

App.tsx: `slashArgSelected` state, `slashArgContext` memo,
`slashArgMatches` memo (dispatches on completer type), useEffect
clamp, `pickSlashArg` callback (splices at partialOffset; adds
trailing space for file picker so user can keep typing the
instruction; no trailing space for enum picks since those commands
take no further args). Wired into useInput arrow/Tab and
handleSubmit Enter intercept. Renders after SlashSuggestions +
AtMentionSuggestions.

### Tests (+11, suite 941 → 952)

tests/slash.test.ts — `detectSlashArgContext` suite covers: null
before name commit, null on unknown cmd, file picker for /edit in
code mode, contextual-command gating outside code mode, enum picker
for /preset, models completer for /model, /plan gated to code mode,
hint kind once partial has internal whitespace, picker with empty
partial (just-typed space), hint kind for free-form arg commands
like /commit.

Lint + typecheck + build clean. 952 tests, 7.5s.
2026-04-23 19:02:38 -07:00
esengine a44c23c0a8 feat(ui): @-picker recency ranking + /keys cheatsheet (0.5.12)
Two UX polishers bundled, closing out the A-E batch.

### D. `@` picker ranking by mtime + recently-used

Alphabetical sort was arbitrary on large repos — 500 files deep, the
first page was almost never what the user wanted. New ranking:

- Empty query → recently-used paths first, then mtime descending,
  then path alpha. "Recently used" = files touched by `read_file` /
  `edit_file` / `write_file` / `search_content` / etc. tool calls
  this session (20-slot LRU; resets on session change).
- Non-empty query → existing substring/prefix scoring, tiebreak by
  recently-used membership then mtime.
- Back-compat: `string[]` input with no recency list still returns
  input order (old tests pass unchanged).

Implementation:

- `listFilesWithStatsSync(root, opts)` — same walk as listFilesSync
  plus a statSync per file. Stat failures don't throw; the entry
  keeps `mtimeMs: 0` and sinks to the bottom of the recency bucket.
- `FileWithStats` / `PickerCandidate` / `RankPickerOptions` types
  exported for library callers.
- `rankPickerCandidates(files, query, limitOrOpts)` — overloaded:
  bare number still works (back-compat), or pass
  `{ limit, recentlyUsed }`.
- App.tsx: `atFiles` memo switched to listFilesWithStatsSync;
  `recentFilesRef` (useRef<string[]>) + `recordRecentFile(p)` LRU
  callback; `tool_start` event handler inspects `toolArgs` for
  `path` / `file_path` / `file` fields and feeds the LRU.

### E. `/keys` cheatsheet slash

Discoverability gap: `!` bang, `@` picker, `/` slash, Shift+Enter,
Ctrl+J, Ctrl+A/E, Esc, y/n — the kit is extensive but undocumented
in one place. `/keys` dumps a formatted table:

    Keyboard & prompt shortcuts:
      Enter                  submit the current prompt
      Shift+Enter / Ctrl+J   insert a newline
      ...

    Prompt prefixes:
      /<name>    slash command
      @<path>    inline a file (code mode)
      !<cmd>     run <cmd> as shell

    Pickers (slash + @-mention):
      ↑ / ↓      navigate
      Tab        insert without submitting
      Enter      insert + run/keep-editing

Added to SLASH_COMMANDS registry + cross-linked from `/help`.

### Tests (+9, suite 932 → 941)

- tests/at-mentions.test.ts — 5 new for rankPickerCandidates:
  mtime sort on empty query with FileWithStats, recently-used boost
  trumps mtime, non-empty query tiebreak by recent+mtime, back-compat
  input-order preservation for bare strings, numeric-limit literal
  as third arg.
- tests/slash.test.ts — 4 new for /keys: shortcuts listed, prefixes
  listed, pickers mentioned, /help cross-reference.

### Note on release cadence

A (0.5.9) + B (0.5.10) + C (0.5.11) + D + E were split across five
commits but each dist is cumulative — publishing only the final one
gets users everything. Going forward I'll bundle closer unless the
user asks otherwise.

Lint + typecheck + build clean. 941 tests, 8.3s.
2026-04-23 18:54:04 -07:00
esengine 337ded3839 feat(code): unified-diff preview for pending edit blocks (0.5.11)
Before /apply, the UI used to show only
    ▸ 2 pending edit block(s) — /apply or /discard
          src/a.ts  (-3 +4 lines)
          src/b.ts  (-1 +1 lines)
— a count summary, nothing about what was actually changing. Common
mistake shape: press y, look at git diff afterwards, discover the
model edited the wrong block / wrong file.

Now each pending block is rendered as a compact diff with ±2 lines of
context and a hard cap at 20 lines per block:

    ▸ 2 pending edit block(s) — /apply (or y) to commit · /discard (or n) to drop
          src/foo.ts  (-1 +1 lines)
            function foo() {
        -   const x = 1;
        +   const x = 2;
            return x;

      NEW src/bar.ts  (-0 +3 lines)
        + export const bar = 1;
        + export const baz = 2;
        + export default { bar, baz };

### Mechanism

`src/code/diff-preview.ts`:

- `formatEditBlockDiff(block, opts)` — shared leading/trailing lines
  collapse to context (default 2 lines each side, `… N unchanged lines
  above/below` when truncated). Middle divergence is `-old` / `+new`.
  Whole block capped at 20 lines with `… (N more diff lines — full
  content applies on /apply)` footer when exceeded. Empty-search
  (new file) case shows all-`+` lines.
- `formatAllBlockDiffs(blocks, opts)` — stitches each block's header
  (path + ±line counts, `NEW` prefix for new files) + its diff body,
  separated by blank lines.

Zero new deps. Small hand-rolled helper using prefix/suffix-compare;
sufficient for the typical SEARCH/REPLACE shape (small change inside
a function body, wrapped in a few lines of surrounding context).
Myers-diff quality is not needed — the model's SEARCH block already
minimizes context.

`formatPendingPreview` in App.tsx dropped its own summary line list
(paths now come from the per-block diff header) and its local
`countLines` helper (moved to diff-preview.ts alongside its only
consumer).

### No colors yet

Plain text, `-` / `+` / ` ` prefixes. ANSI colorization would need
Ink component plumbing that isn't worth the complexity for v1 —
the prefix convention is clear and universal (git / hunks / etc.).

### Tests (+10, suite 922 → 932)

tests/diff-preview.test.ts — new-file all-`+`, context collapse for
shared prefix/suffix, maxLines truncation with footer, leading and
trailing hidden-context annotations, single-line edits, custom
indent, multi-block formatAllBlockDiffs (path+counts headers, blank
separators, empty-input).

Lint + typecheck + build clean. 932 tests.
2026-04-23 18:47:01 -07:00
esengine 8ec6c630bd feat(slash): /edit <file> <instruction> — one-shot surgical edit (0.5.10)
One-liner shortcut for "change this one thing in this one file" —
faster than the multi-turn code-mode dance of "explain the file",
"here's my plan", "apply", etc. Code mode only.

### Mechanism

Zero new code paths. The slash is sugar: it builds a resubmit text of

    @<file> <instruction>

    Output ONLY a SEARCH/REPLACE block for this one edit. No prose,
    no explanation.

and hands that back through the normal turn machinery:

- 0.5.5's `@`-mention expansion inlines `<file>` under
  `[Referenced files]` so the model sees the current content.
- Code-mode's SEARCH/REPLACE handling already catches the output
  into `pendingEdits` (0.4.0+).
- The existing y/n confirm gate fires on the next event.

So `/edit src/foo.ts fix the typo` becomes equivalent to the user
typing `@src/foo.ts fix the typo. Output ONLY a SEARCH/REPLACE
block…` — the value is (a) discoverability via /help and slash
autocomplete, (b) the guaranteed-good prompt format without the user
having to remember it.

### Validation

- Outside code mode (no `codeRoot` in SlashContext) → refusal with a
  pointer to `reasonix code <dir>`.
- Missing file arg → usage hint.
- Missing instruction → usage hint with the file name echoed back.

### /help + discovery

Added to the slash autocomplete registry (`contextual: "code"` so
it only surfaces in code mode) and to the /help code-mode block.

### Tests (+6, suite 916 → 922)

tests/slash.test.ts — /edit describe block covers: non-code-mode
refusal, missing file, missing instruction, resubmit shape
(contains `@file` + instruction + SEARCH/REPLACE + ONLY), multi-
word instruction preservation. Plus `/help mentions /edit` and
`edit` added to the `SLASH_COMMANDS registry contains every handler`
required-list.

Lint + typecheck + build clean. 922 tests.
2026-04-23 18:41:12 -07:00
esengine a787272ceb feat(ui): collapse large user pastes in Historical display (0.5.9)
Pasting a stack trace / log dump / sample file flooded the Historical
scrollback with a massive block, hiding prior turns. Now user input
that exceeds a threshold renders as:

    ▸ pasted 2.3 KB (84 lines) — first 10 shown, full text sent to model
    line 1
    …
    line 10
    … (74 more lines)

The MODEL still receives the full text. Only the displayed row
collapses — `loop.step(modelInput)` gets the original string
(including any `@`-mention expansion) unchanged.

### Mechanism

- `src/cli/ui/paste-collapse.ts` — `formatLongPaste(text, opts)` pure
  helper. Collapse triggers when line count > 40 OR char count > 2000
  (defaults, override via opts). Head shows 10 lines; remaining
  footer reads "… (N more lines)". Byte header formats B/KB/MB.
- App.tsx — wired at the user-row push site in handleSubmit
  (between the UserPromptSubmit hook gate and the loop.step dispatch).
  The `pasteDisplay.displayText` goes to the Historical row; the
  existing `modelInput` variable (raw or `@`-expanded) goes to the
  loop.

### Scope

Affects only the regular user-message row. Separate paths for
`!`-bang commands, `@` expansions, and slash outputs are untouched.
Skipped on short messages (pass-through, no allocation overhead
beyond a `split("\n")`).

### Tests (+10, suite 906 → 916)

tests/paste-collapse.test.ts covers: short pass-through, multi-line
pass-through, line-threshold collapse, char-threshold collapse,
KB/MB formatting, 1-vs-N-more-lines pluralization, custom
thresholds, custom headLines, zero remaining (head covers all),
exported defaults.

Lint + typecheck + build clean. 916 tests.
2026-04-23 18:37:26 -07:00
esengine 0ca16d6e2d feat(ui): !cmd bash-mode prefix — user-typed shell passthrough (0.5.8)
Claude-Code-style bash mode. User types `!ls src/` or `!git status`;
Reasonix runs the command in the sandbox root, shows both the command
and its output, and appends the combined text to the conversation log
so the next model turn has the context automatically.

Faster than round-tripping through the model just to cat a file or
check git state, and closes a common UX gap vs. Claude Code.

### Mechanism

- `src/cli/ui/bang.ts` — `detectBangCommand(text)` returns the command
  body (whitespace-trimmed) or null. Only a LEADING `!` counts; `!`
  alone / `!   ` returns null; `echo !hi` doesn't trigger (the `!`
  isn't at position 0).
- `formatBangUserMessage(cmd, output)` — prepends a `[!cmd]\n`
  header so the model can distinguish user-typed shell output from
  its own `run_command` tool results (which are `role: tool`,
  structurally different).
- App.tsx handleSubmit intercept — fires AFTER the y/n fast-path (so
  pending edits still resolve cleanly) and BEFORE slash parsing:
  - Push `role: "user"` Historical row with the raw `!cmd` text.
  - `await runCommand(cmd, { cwd: codeMode?.rootDir ?? cwd,
    timeoutSec: 60, maxOutputChars: 32_000 })`.
  - Push `role: "info"` Historical row with
    `formatCommandResult(cmd, result)`.
  - `loop.log.append({ role: "user", content: formatBangUserMessage
    (cmd, formatted) })` so the next step() includes it in
    buildMessages.
  - setBusy true/false around the run so PromptInput reflects the
    in-flight state.
  - Catch errors → warning row, don't log.

### No allowlist gate

User-typed `!` is explicit consent (consistent with Claude Code; the
allowlist exists to bound what the MODEL can do with `run_command`,
not what the user chooses by hand). If someone wants stricter gating
later a `REASONIX_BANG_CONFIRM=1` toggle could layer on — out of
scope here.

### Known limitation: session durability

`loop.log.append` updates in-memory only. On session resume, the bang
output is gone (the session file didn't see it). The next actual
step() does appendAndPersist for the next user turn, and the model
sees this bang output live within the same session either way.
Treating bang as ephemeral keeps the fast-path simple; durable
capture could land later if real usage surfaces demand.

### /help + discovery

/help gains a "Shell shortcut" section documenting `!cmd` with
example commands (`!git status   !ls src/   !npm test`), plus a
"File references" section covering the `@` picker from 0.5.5 / 0.5.7
that was undocumented there.

### Tests (+9, suite 897 → 906)

tests/bang.test.ts — detectBangCommand covers: body extraction,
whitespace trim, non-bang pass-through, `!`-alone / blank body,
mid-string `!` rejection, embedded-trailing-`!` preservation,
multi-word with flags/quotes. formatBangUserMessage covers header
prepending and verbatim body preservation.

Lint + typecheck + build clean. 906 tests, 8.6s.
2026-04-23 18:31:30 -07:00
esengine ecf2ea372b feat(ui): @mentions picker + post-build bundle smoke test (0.5.7)
Two shipped, both extending 0.5's foundation:

### 1. @mentions picker UI

0.5.5 shipped `@path/to/file` inline expansion but made the user type
the full path. 0.5.7 adds a picker that mirrors the existing
/slash autocomplete: type `@` (with optional partial) in code mode,
get a filtered file list with ↑/↓ navigation and Tab/Enter pick.

- `listFilesSync(root, opts)` — sync recursive walk, skips
  node_modules / .git / dist / build / .next / etc. + any dot-dirs.
  Caps at 500 results by default. Forward-slash paths on all
  platforms. 10-50ms on moderate repos — fits the TUI's single-turn-
  per-tick model cleanly.
- `detectAtPicker(input)` — returns `{query, atOffset}` when the
  buffer ends with an in-progress mention; `null` otherwise. Distinct
  from `AT_MENTION_PATTERN` which finds completed mentions anywhere
  for expandAtMentions.
- `rankPickerCandidates(files, query, limit)` — case-insensitive
  substring filter with a boost for basename-prefix matches. Empty
  query returns the first `limit` candidates alpha.
- `AtMentionSuggestions.tsx` — same shape as `SlashSuggestions`
  (matches null = hide, empty = "no matches", array = highlight
  selected cyan/bold). Shows basename bold + dir dimmed à la
  VS Code Quick Open.
- App.tsx wiring: `atFiles` memo (walk on rootDir change), `atPicker`
  / `atMatches` memos, `atSelected` state with useEffect clamp.
  Arrow keys + Tab in useInput (before slash so they don't conflict
  — mutually exclusive by construction). Enter in handleSubmit
  substitutes at the `@` offset and appends a space (space auto-
  dismisses the picker, next Enter submits).
- Limitation intentionally not fixed: files created mid-session by
  edit tools won't appear in the picker until next launch. User can
  always type the full path. Rebuilding the list on every turn would
  be wasteful for the 95% case.

### 2. Bundle smoke test

v0.5.4 shipped to npm with a tokenizer path resolution bug that
crashed on first API call. The unit tests were fine — they load
modules from src/, which doesn't exercise the post-bundle directory
layout. These two tests close that gap:

- `dist/index.js`: dynamic import (via file:// URL on Windows),
  invoke `truncateForModelByTokens` to force a tokenizer load. ENOENT
  ⇒ fail.
- `dist/cli/index.js`: spawn with `DEEPSEEK_BASE_URL=127.0.0.1:1` so
  fetch fails fast. Preflight's tokenizer load runs BEFORE fetch, so
  if the bundled layout can't find the data file we see the ENOENT
  in stderr. If tokenizer loads fine, we see connection-refused and
  the test passes.
- Both tests skip when the bundle is absent (dev runs that haven't
  built yet). CI runs `build` before `test` → always exercised.

Would have caught 0.5.4's regression pre-publish.

### Tests (+23, suite 874 → 897)

- tests/at-mentions.test.ts — 7 new for detectAtPicker, 2 for
  AT_PICKER_PREFIX vs AT_MENTION_PATTERN sanity, 6 for
  rankPickerCandidates (empty query, substring, basename-prefix
  boost, path-prefix, no-match, limit), 6 for listFilesSync (recurse,
  forward slashes, ignore dirs, dotfile inclusion, custom ignores,
  maxResults cap, unreadable root).
- tests/bundle-smoke.test.ts — 2 tests for lib + CLI bundle
  tokenizer resolution.

Library exports: `detectAtPicker`, `listFilesSync`,
`rankPickerCandidates`, `AT_PICKER_PREFIX`, `DEFAULT_PICKER_IGNORE_DIRS`,
`ListFilesOptions`.

Lint + typecheck + build clean. 897 tests, 8.1s.
2026-04-23 18:14:46 -07:00
esengine 335de43db5 fix(tokenizer): resolve data-file path in bundled builds (0.5.6)
**Critical production bug.** Since 0.5.0 introduced the tokenizer, any
bundled `reasonix run` / `code` / `chat` crashed with ENOENT on the
first API turn after 0.5.4 put the tokenizer on the hot path.

Root cause: `resolveDataPath()` used
`join(dirname(import.meta.url), "..", "data", "deepseek-tokenizer.json.gz")`.

- In dev (`src/tokenizer.ts`) → resolves to `data/` ✓
- In the bundled CLI (`dist/cli/index.js`) → `dist/cli/` + `..` +
  `data/` = `dist/data/` ✗ — the data file ships at PACKAGE ROOT per
  package.json `files` entry; `dist/data/` doesn't exist.

Why this slipped through: before 0.5.4, `countTokens()` was only
called from the opt-in `/context` slash. Casual smoke tests and unit
tests (which run tokenizer.ts directly from src/) never hit the
bundled resolution. 0.5.4's preflight put `countTokens()` on every
step() call — so the first user-facing turn after `npm publish 0.5.4`
would have crashed.

Fix: `resolveDataPath()` now tries multiple candidate paths and
returns the first one that `existsSync`:

1. `REASONIX_TOKENIZER_PATH` env override (unchanged).
2. `../data/...` — dev + bundled `dist/index.js`.
3. `../../data/...` — bundled CLI at `dist/cli/index.js`.
4. `require.resolve("reasonix/package.json")` root — fallback for
   unusual bundlers.

Also falls back to `process.cwd() + data/...` if all candidates
missed, so readFileSync surfaces a concrete path in the error rather
than silently missing.

Caught via live `DEEPSEEK_API_KEY=... node dist/cli/index.js run
"hi"` against the actual bundled output. Unit tests alone would not
have caught this (they load src/tokenizer.ts directly, bypassing
the bundle path). Follow-up consideration: an integration test that
runs the bundled CLI against a fake API response — out of scope here.

874 tests still pass. Lint + typecheck + build clean.
2026-04-23 17:58:35 -07:00
esengine af077ddb24 feat: @file mentions in code mode + session-load heal → tokens (0.5.5)
Two shipped in one release, both closing out the 0.5 arc:

### 1. Session-load heal migrated to tokens

0.5.2 and 0.5.3 made dispatch truncation, /compact, and auto-compact
token-aware. Session load was the last char-based truncation surface;
now closed. CJK tool results in a resumed session come back at the
same effective context footprint as English instead of slipping past
the old 32k-char cap at 2× the token cost.

- `healLoadedMessagesByTokens(messages, maxTokens)` — sibling of the
  existing char-based `healLoadedMessages`.
- `fixToolCallPairing(messages)` — pure helper extracted so both
  variants reuse the structural tool_calls ↔ tool pairing pass.
- Session-resume call in loop.ts constructor switched to the token
  variant with `DEFAULT_MAX_RESULT_TOKENS`. Stderr "healed" line now
  reads "shrunk N tokens of oversized tool output" instead of chars.
- buildMessages's per-turn heal (hot path) stays on the char variant
  — avoids a per-turn tokenizer pass on every tool message.

### 2. `@file` mentions in code mode

User types `@src/loop.ts` → the model sees the file content inlined
under a "Referenced files" block:

    look at @src/loop.ts and explain

    [Referenced files]
    <file path="src/loop.ts">
    ...
    </file>

The user's original text is preserved verbatim; expansion is append-
only so the display stays clean and the model can cite the file
unambiguously.

- Regex `(?<=^|\s)@([a-zA-Z0-9_./\-]+)` — requires word boundary so
  `[email protected]` and `foo@bar` don't trigger. Trailing sentence
  period (`@foo.ts.`) is stripped before lookup.
- Sandbox: relative paths only, resolved against `rootDir`, no `..`
  escape, no absolute paths. Violations get
  `<file path="..." skipped="escape"/>` so the model sees the refusal.
- `DEFAULT_AT_MENTION_MAX_BYTES = 64 KB` (matches tool-result cap
  ballpark). Larger → skipped="too-large" with byte count.
- Missing / not-a-regular-file → skipped with reason.
- De-dupe: same file referenced twice inlines once.
- UI feedback: an info row lists inlined/skipped files so the user
  sees what reached the model.
- Only active in code mode (codeMode.rootDir). Plain chat mode
  doesn't expand — file references there are ambiguous.

### Tests (+15, suite 859 → 874)

- tests/at-mentions.test.ts — regex: boundary matching, email
  rejection, multi-mention; expansion: inline content, de-dupe,
  multiple distinct files, missing/escape/absolute/too-large skips,
  trailing-dot stripping, directory rejection.

Library exports: `expandAtMentions`, `AT_MENTION_PATTERN`,
`DEFAULT_AT_MENTION_MAX_BYTES`, `AtMentionExpansion`,
`AtMentionOptions`. Plus `healLoadedMessagesByTokens` and
`fixToolCallPairing` from loop.ts.

Lint + typecheck + build clean. 874 tests, 5.2s.
2026-04-23 17:48:50 -07:00
esengine 84ea648c84 feat(loop): preflight context-size check before each request (0.5.4)
Reactive auto-compact (60%/80% on prior prompt_tokens) keys off the
PREVIOUS turn's server usage, so a fresh resumed session — or one new
oversized tool result — can push the current turn's buildMessages
straight past 131,072 tokens and make DeepSeek 400 with "maximum
context length" before we see any usage number. Preflight closes that
hole by estimating locally before sending.

Mechanism:

- `estimateRequestTokens(messages, toolSpecs)` in src/tokenizer.ts:
  `estimateConversationTokens(messages) + countTokens(JSON.stringify
  (toolSpecs))`. Mirrors the arithmetic `/context` slash already uses
  so the two numbers don't drift.

- loop.step() injection right after buildMessages(). If the estimate
  exceeds 95% of `DEEPSEEK_CONTEXT_TOKENS[model]` (fallback
  `DEFAULT_CONTEXT_TOKENS`), run `compact(1_000)` and rebuild
  messages from the shrunk log. Warning event names the preflight
  path + tokens saved.

- When there's nothing to compact (first-ever turn with a bulky
  system prompt, for example), still yield a warning naming the
  preflight estimate + "nothing to auto-compact — DeepSeek will likely
  400". User sees the reason before the crash, can /forget or /clear.
  We don't short-circuit the request — let DeepSeek decide; its 400
  catch path already surfaces a useful hint.

- Non-branching AND branching paths share the `messages` variable
  from the outer buildMessages call, so the one injection covers
  both. Forced-summary fallback keeps its own path (a preflight
  there would be too late; the summary is the recovery step).

Tests (+3, suite 856 → 859) in tests/preflight.test.ts:

- Fires when estimate > 95%: compact runs, "pre-compacted N tool
  result(s), saved M tokens" warning appears, loop still completes.
- Stays silent when estimate is comfortably under 95%.
- Warns (but does not block) when over 95% with nothing to compact.

Per-test context budgets are set by mutating `DEEPSEEK_CONTEXT_TOKENS
[TEST_MODEL]` — the table is `Record<string, number>` so the write
is well-typed; teardown deletes the key. Seeded tool results are
properly paired with a prior assistant.tool_calls so
healLoadedMessages doesn't strip them as orphans (which would make
preflight never fire).

Lint + typecheck + build clean. 859 tests, 5.0s.
2026-04-23 17:32:09 -07:00
esengine 2d95c5787d feat(loop): token-aware /compact + auto-compact (0.5.3)
0.5.2 put the DeepSeek V3 tokenizer on the dispatch hot path to cap
NEW tool results by real tokens. 0.5.3 extends that to the live log:
/compact and auto-compact now shrink existing tool results by tokens
too, closing the last surface where CJK text slipped past a char cap
at 2× the intended context cost.

Mechanism:

- `shrinkOversizedToolResultsByTokens(messages, maxTokens)` in
  src/loop.ts — sibling of the char-based `shrinkOversizedToolResults`.
  Fast-pathes tool entries whose length ≤ cap (tokens ≤ length
  guarantee); otherwise tokenizes each candidate twice (before +
  after `truncateForModelByTokens`) to report exact tokensSaved.
  Never tokenizes the full input (same 0.5.2 guard against BPE
  O(n²) on pathological repetitive content).

- `loop.compact(maxTokens = 4000)` now shrinks by tokens and returns
  `{ healedCount, tokensSaved, charsSaved }` (was `{ healedCount,
  charsSaved }`). Persists to the session file when present.

- Auto-compact thresholds in `step()`:
  · 60%-80% band: soft compact at 4000 tokens/result (was 16k chars,
    which was 4k tokens in English but 16k tokens in CJK).
  · >80% band: hard compact at 1000 tokens/result (was 4k chars).
  Warnings report exact tokensSaved instead of `charsSaved / 4`.

- `/compact [N]` slash cap semantic flipped from chars to tokens
  (default 4000). The `info` line now reads "saved N tokens
  (M chars)". Help text + suggestion hint updated.

- Session-load heal (`healLoadedMessages`) left on the char cap so
  stored session files keep loading under their existing semantics.
  Live compaction and dispatch-time truncation are the only two
  surfaces that went token-aware.

Tests (+6, suite 850 → 856):

- tests/compact-tokens.test.ts — small-tool no-op, oversize shrink,
  input non-mutation, user/assistant protection, CJK parity, fast
  path by length.
- tests/loop.test.ts — seeded log content in the two auto-compact
  tests reshaped from `"Z".repeat(N)` to realistic log lines (was
  hitting BPE pathological path; also the 60%-80% warning now
  reads "4k tokens" instead of "16k" chars).
- tests/slash.test.ts — /compact assertions updated for token-based
  output ("saved N tokens", "N tokens each"); test content reshaped
  to realistic log lines.

Breaking change: library callers that pass an explicit number to
`loop.compact(N)` expecting chars will now get a tighter cap (4000
tokens ≈ 16k chars English, ~4k chars CJK). Fail mode is "compaction
is more aggressive than expected," which is the safe direction.

Lint + typecheck + build clean. 856 tests, 5.1s.
2026-04-23 17:21:02 -07:00
esengine 19a2b8d2be feat(tools): token-aware tool-result truncation at dispatch (0.5.2)
Before: every tool result was char-capped at 32K chars (8K English
tokens, but 16K+ tokens for CJK — Chinese/Japanese/Korean tool output
slipped past the budget at 2× the intended context cost).

After: dispatch truncates by REAL DeepSeek V3 tokens, using the
tokenizer that shipped in 0.5.0. Default 8K tokens per result, same
effective footprint regardless of char density.

Mechanism (src/mcp/registry.ts:truncateForModelByTokens):

- Fast path `s.length <= maxTokens` — every token is ≥1 char, so
  length bounds tokens. Skip tokenize entirely for small results.
- Intermediate check for moderate strings (`length <= maxTokens * 4`)
  — tokenize once to confirm it really is over budget.
- For large strings: char-slice head + tail by budget, tokenize the
  slices (NOT the full input), shrink on overshoot. 1–2 iterations per
  slice, bounded at 6. We explicitly never tokenize the whole input —
  pathological repetitive content (`"A".repeat(50_000)`) costs 30s+
  in the pure-TS BPE and is bounded to small slices.
- Dropped-tokens count in the marker is estimated from the per-slice
  char/token ratio (marker reads "~N tokens") so we don't pay a full
  tokenize just for diagnostics.

Wire-up:

- src/tools.ts — `ToolRegistry.dispatch` accepts both `maxResultChars`
  (legacy) and `maxResultTokens` (new). Both apply if both set; the
  tighter one wins. Char-only callers keep their old behavior.
- src/loop.ts — hot-path dispatch switched from
  `maxResultChars: 32_000` to `maxResultTokens: DEFAULT_MAX_RESULT_TOKENS`
  (8_000). Session-healing paths still use chars (preserves backwards
  compat on loaded session files).
- `DEFAULT_MAX_RESULT_TOKENS` and `truncateForModelByTokens` exported
  via src/index.ts for library consumers.

Tests (+9, suite 841 → 850):

- tests/truncate-tokens.test.ts — fast-path, short-string verify,
  CJK cap parity with English, head+tail preservation, zero-budget,
  empty input, marker format.
- tests/loop.test.ts — existing "pre-clips at dispatch" test reshaped
  to use realistic log-line content (was `"A".repeat(50_000)` which
  hit the BPE O(n²) pathological path, 46s+ in the suite).

Lint + typecheck clean. Suite now 5.2s total.
2026-04-23 16:52:23 -07:00
esengine ca27ca50bf fix(shell): reject shell operators (|, >, <, &, &&, ||, 2>) with a clear error (0.5.1)
Before: model writes `dir | findstr foo` → tokenizer produced `["dir",
"/b", "|", "findstr", "foo"]` → quoteForCmdExe wrapped `|` as `"|"`
(literal) → cmd.exe passed `|` as an argument to dir → no pipe, no
error, silent wrong output. The 0.4.26 memory flagged this as a known
issue; encoding fix from that release made the failure visible but
didn't address the root confusion.

After: detectShellOperator() walks the raw command with quote-tracking
and returns the first unquoted operator token at a token boundary.
runCommand rejects before spawn with:

  run_command: shell operator "|" is not supported — this tool spawns
  one process, no shell expansion. Split into separate run_command
  calls and combine the output in your reasoning...

Quoted operators (`grep "a|b" file.txt`) and chars embedded in larger
tokens (`--flag=1&2`) pass through — those are literal argv bytes.
Matches the tool's stated "no shell expansion, no pipes, no redirects"
contract; turns the silent failure into a loud, actionable one.

Tool description updated to document the rejection + the quote-it-as-
a-literal workaround so the model learns the constraint from the spec.

Tests: 841 (+13 covering pipe, redirect, fd-redirect, &&/||, stuck-
redirect, quoted operators, embedded operators).
2026-04-23 16:38:27 -07:00
esengine d4615d6e76 chore(0.5.0): fix CI + add animated SVG logo
CI fix — biome lint surfaced 9 errors on the 0.5.0 commit:
- tokenizer.ts: Infinity → Number.POSITIVE_INFINITY (style/useNumberNamespace)
- tokenizer.ts: formatter wrap on the CJS fallback branch
- StatsPanel.tsx: noArrayIndexKey on the Wordmark map — restructured to a
  module-level WORDMARK_STYLES table keyed by char+color pair, dropped
  the `i` parameter entirely (previous biome-ignore comment only
  suppressed one of two sites the rule fires on)
- various whitespace / line-wrap fixes from `biome check --write`

Animated SVG logo at docs/logo.svg, embedded at the top of README:
- Concentric diamond brand mark (◈) with three layers of motion:
  slow rotation (18s), outer-stroke pulse (2.4s), inner-fill breathing
- REASONIX wordmark in the same cyan → fuchsia gradient the TUI uses,
  so the README and the running app share one visual identity
- Tagline underneath for SEO-style context
- Colors (~4.5:1 contrast on both GitHub dark and light) — no
  prefers-color-scheme switching needed

828 tests, lint + typecheck clean.
2026-04-23 09:34:25 -07:00
esengine 9eff2e2cfc feat(0.5.0): Reasonix visual identity + DeepSeek tokenizer + models/pricing/context
Visual redesign — drop the generic vertical bars for a Reasonix-native
design language. The UI should be recognizable as ours at a glance:

- ◈ REASONIX wordmark in truecolor gradient (cyan → violet), with
  breathing animation — slow when idle, faster when the model is
  thinking, so the app's state is readable from the edge of vision.
- Geometric role glyphs replace all text labels: ◇ user · ◆ assistant ·
  ▣ tool · ▥ tool-err · ▲ warn · ✦ error. Consistent geometric family,
  distinct per role, no overlap with Claude / Cursor / Cline.
- Streaming assistant glyph pulses ◆↔◇ at ~480ms — visible heartbeat
  during R1's long (20-90s) pre-first-byte silence.
- Turn separators render "─── ◆ ───" with the Reasonix mark centered.
- Responsive StatsPanel: stacks metrics vertically on <120-col
  terminals (SSH, split-pane); inline when there's room. Context
  cell gains a 10-cell progress bar in the stacked layout.
- Cold-start cache hit ratio (turn ≤ 3) renders dim gray with a
  "(cold start)" hint instead of red — new users stopped reading
  "0% cache on turn 1" as a configuration error.
- Tool results tail-truncate by default (useful signal is usually at
  the end). ERROR-prefixed results keep the first line + a tail.
- Modal footers gain "[↑↓] navigate · [Enter] select · [Esc] cancel"
  hints; Esc actually cancels now (ShellConfirm → deny, PlanConfirm →
  cancel); SingleSelect gained an optional footer slot.
- Wait-phase messaging (pre-first-byte, R1 reasoning, branching,
  tool-call streaming) gets visible yellow italic instead of dim —
  users had been misreading the dim variant as "frozen".

New features:

- Pure-TS port of DeepSeek's V3 tokenizer (vocab + merges + pre_tokenizer
  from the official tokenizer.json). Bundled as data/deepseek-
  tokenizer.json.gz (1.74MB, slimmed + gzipped from 7.5MB). Zero new
  deps — uses built-in zlib. Encodes ~12k tokens of mixed source in
  ~40ms. scripts/prepare-tokenizer.ts regenerates the bundle from
  upstream.
- /context slash — renders a breakdown of the next request's tokens:
  system prompt, tool specs, per-turn log, top 5 heaviest tool results.
  Answers "where is my context going?" directly; closes the gap where
  StatsPanel showed ctx % without saying why.
- /models slash — fetches DeepSeek's live model catalog via
  GET /models. Renders the list with the current model marked.
- /model <id> now soft-validates against the fetched catalog (warn
  but still switch — accommodates newly-released models we haven't
  indexed). DeepSeekClient gains a listModels() method.

Loop + billing correctness:

- Tool results pre-clipped at dispatch time (default 32k chars) via
  ToolRegistry.dispatch({ maxResultChars }). Oversized results no
  longer bloat the AppendOnlyLog or the persisted session file.
- New proactive-compact tier: when promptTokens / ctxMax crosses 60%
  (before the existing 80% reactive guard), shrink oversized tool
  results to 16k chars. Catches slow-growth patterns before they
  compound into a forced summary.
- DEEPSEEK_PRICING updated to the current unified rates (¥0.2 / ¥2 /
  ¥3 per 1M at cache-hit / cache-miss / output; USD 0.028 / 0.28 /
  0.42 at 7.2 CNY/USD). chat and reasoner are now priced identically
  at source. Stats dashboard figures were systematically high under
  the old tiered constants — new sessions bill correctly.
- Context display switches to binary-K (128K) to match DeepSeek's
  marketing label. DEEPSEEK_CONTEXT_TOKENS stays at 131072 — only
  the formatter divisor changed.

OSC 8 clickable hyperlinks in markdown were attempted and reverted:
Ink 5 strips \x1b / \x07 from Text output, so file:// links never
reach the terminal. Documented as a known limit; re-visit with a
future Ink release or raw-stdout approach.

828 tests (14 new: tokenizer golden cases + /context + /models +
listModels + pricing unification + proactive compact). Lint +
typecheck + build clean.
2026-04-23 09:28:40 -07:00
esengine c2f8e9b734 feat(0.4.28): reasonix code defaults harvest OFF — opt in via --harvest
Pillar 2 harvesting fires an extra V3 call per turn to extract a typed
plan state (subgoals/hypotheses/uncertainties/rejectedPaths) from R1's
reasoning_content. Cost ~10-15% per turn. Closer audit of who actually
consumes the output:

- subgoals / hypotheses / rejectedPaths — purely cosmetic, only rendered
  in PlanStateBlock. No programmatic consumer. Can mislead users by
  giving structured-looking output extra perceived authority (today's
  citation work was triggered by hallucinated "hypotheses" that looked
  thoughtful).
- uncertainties.length — single real downstream use, drives self-
  consistency branching when count exceeds threshold. Could be replaced
  with a cheap heuristic on the raw reasoning text.

For coding tasks specifically, branching is rarely on (default budget=1)
and the cosmetic display value doesn't justify the per-turn premium.
Flip the default off; users who genuinely want the plan state surfaced
can pass --harvest. `reasonix chat` is unchanged — preset behaviour
there still controls harvest.

799 tests, lint + build clean.
2026-04-23 05:13:20 -07:00
esengine d52599ec44 feat(0.4.27): citation-first answers — validated [text](path:line) links + broken-citation surface
Anti-hallucination intervention for evaluative tasks. Two real R1 sessions
where the model invented "Resources/Prompts/Progress not implemented" gaps
that had been shipped months ago (v0.4.5, v0.4.8) motivated this — same
hallucination shape both times, across independent prefixes. The fix is
structural: force the model to ground every codebase claim in a clickable
citation, validate them, render broken ones in red so the user sees
fabrications instantly.

- markdown.tsx: parse [text](url) links (was unsupported — rendered as
  literal). External URLs (https://, mailto:, //) → blue underline.
  Citation-shaped URLs (path / path:line / path:start-end / path#L42) →
  validated against projectRoot, valid = cyan underline, broken = red
  strikethrough + ❌. Bottom-of-message BrokenCitationsBlock lists each
  failure with reason ("file not found", "line 999 > 250") so the user
  can challenge the specific claim.
- code/prompt.ts + cli/index.ts: "Cite or shut up — non-negotiable"
  section moved to TOP of system prompt (was at the end and ignored).
  Concrete ✅/❌ examples. Negative-claim rule made imperative — "STOP.
  Call search_content FIRST" instead of "qualify it" — because asserting
  absence without checking is the #1 failure mode.
- App.tsx / EventLog.tsx / PlanConfirm.tsx: thread projectRoot through
  every <Markdown /> callsite (defaults to process.cwd() for safety).

Behavioural validation: same "analyze the project" prompt that produced
5/8 hallucinations pre-fix returned 3/3 verifiable specific claims +
1 auto-detected broken citation post-fix. Citation feature working in
production.

799 tests (17 new in markdown.test.ts: parseCitationUrl, isExternalUrl,
validateCitation, collectCitations dedup + external skip, parseBlocks
no-regression). Lint + typecheck + build clean.
2026-04-23 04:47:10 -07:00
esengine 3c8669577d feat(0.4.26): subagents-via-Skills + search_content + render/shell/sandbox fixes
- Subagents-via-Skills (replaces 0.4.25's spawn_subagent user-facing
  surface; library API kept). Skills frontmatter gains runAs:subagent +
  optional model:deepseek-*. Builtin explore + research skills ship in
  src/skills.ts as constants. spawnSubagent(opts) extracted from
  registerSubagentTool — both surfaces share it via formatSubagentResult.
  registerSkillTools moved into App.tsx with subagentRunner closure;
  reasonix code no longer registers spawn_subagent in the model tool list.
  Pinned Skills index marks subagent skills with a 🧬 prefix so the model
  pattern-matches "user says explore -> use 🧬 explore" instead of
  reasoning about whether a task is "big enough" to delegate.
- search_content: real content grep tool. Skips 18 dependency / build /
  VCS dirs by default + skips binaries by extension (30+ types) and
  by content sniff (NUL byte in first 8KB). Per-file 2 MB cap, output
  capped to maxListBytes. Regex + literal fallback, glob substring
  filter, case_sensitive + include_deps options. Closes the gap that
  made subagents waste their iter budget calling search_files (which
  is filename-only) for content-grep questions.
- markdown renderer: recognizes Unicode box-drawing tables (│ ─ ┼) +
  ┌─┐ │ └─┘ frames as code blocks. Table cells now render through
  InlineMd with padTo so backticks/bold inside cells parse and column
  widths align by visible (post-strip) width. Multi-line table cell
  continuation rows fold back into the previous row's last cell.
- shell on Windows: prepareSpawn injects chcp 65001 prefix into every
  cmd.exe /c payload + injects [Console]::OutputEncoding=UTF8 into
  PowerShell -Command invocations. Fixes mojibake on CJK Windows where
  cmd builtins (dir, findstr, where) and PowerShell emit text in CP936
  / CP932 / CP949 — previously poisoned the next turn's prompt with
  garbled bytes.
- sandbox: filesystem tools' safePath strips leading / and \ so
  POSIX-absolute paths (path: "/" or "/src/foo.ts") resolve to the
  sandbox root instead of the actual filesystem root. Models routinely
  pass these intending the project root; the old behavior failed the
  escape check with a confusing error.
- loop: aborted signal in the API-call catch yields a clean done
  instead of a red error event. The "This operation was aborted" row
  was always a self-inflicted UX bug — App.tsx calls loop.abort() to
  switch turns when the user picks ShellConfirm "always allow" or
  PlanConfirm approve, and the resulting AbortError got rendered as
  a real error. Subagent layer compensates by synthesizing an error
  result when no final answer was produced (so success!=true on abort).
- prompts: dropped the fictional `grep` tool reference from
  CODE_SYSTEM_PROMPT; explicit list of available exploration tools
  (read_file, list_directory, directory_tree, search_files,
  search_content, get_file_info). New "Path conventions" section
  distinguishes filesystem-tool sandbox-relative paths from
  run_command OS-shell paths (don't use leading / in shell args).

781 tests (+26 vs 0.4.24), lint + typecheck + build clean.
2026-04-23 02:30:15 -07:00
esengine 3fee4e6883 feat: reasonix stats — cross-session cost dashboard + /stats slash (0.4.24)
Every turn run through `reasonix chat|code|run` now appends one line
to ~/.reasonix/usage.jsonl carrying tokens + cost + the equivalent
Claude Sonnet 4.6 cost. `reasonix stats` (no arg) rolls that log up
into today / week / month / all-time windows with a "saved vs
Claude" column. Pillar 1's pitch (94–97% cost reduction) becomes a
fact users can check on their own machine.

Same dashboard is available in-session via the new /stats slash,
reading from the same file and rendering through a shared pure
renderer. reasonix stats <transcript> keeps the old per-file
summary (assistant turns + tool calls) for scripts.

Privacy: only tokens, costs, session name. No prompts, completions,
or tool args. Log append is best-effort — disk failure never blocks
a turn.

New files:
  src/usage.ts                 — appendUsage, readUsageLog, aggregateUsage,
                                  bucketCacheHitRatio / SavingsFraction
  tests/usage.test.ts          — 15 tests (round-trip, malformed line,
                                  rolling windows, renderer, zero denom)

Modified:
  src/cli/commands/stats.ts    — dashboard mode + extracted renderDashboard
  src/cli/commands/run.ts      — appendUsage on assistant_final (for CI)
  src/cli/ui/App.tsx           — appendUsage on assistant_final (TUI)
  src/cli/ui/slash.ts          — /stats slash (shared renderer)
  src/cli/index.ts             — `stats <transcript>` → `stats [transcript]`
  src/index.ts                 — re-export usage module

+17 tests (suite 708 → 725). Lint + typecheck + build clean.
2026-04-22 22:24:59 -07:00
esengine 41d21f7cea feat(slash): /update shows current vs latest + shell command (0.4.23)
Adds an in-session `/update` slash that reports the running version
and the last-resolved latest from the App's background npm-registry
check. Deliberately does NOT spawn `npm install` — stdio:inherit
into a running Ink renderer corrupts the display, and on Windows
the currently-running binary can be locked. Users exit and run
`reasonix update` in a fresh shell when they actually want to
install.

Also splits App state: we now track `latestVersion` regardless of
whether it's newer (so the slash can tell "on the latest" apart
from "still fetching") and derive the yellow header badge from
that. Before this, `updateAvailable` was only set on strictly-
newer, so `/update` saw null when the user was already on the
latest — the message misleadingly said "background check in
flight or offline".

`/update` also triggers a fresh `getLatestVersion({force:true})`
when latestVersion is null, so a retry a few seconds later sees
a concrete answer.

4 new tests (suite 704 → 708). All green; lint / typecheck / build
clean.
2026-04-22 22:13:32 -07:00
esengine 715d8b5950 feat: hooks — user-defined automation at PreToolUse / PostToolUse / UserPromptSubmit / Stop (0.4.23)
Same two-scope layout as memory and skills:
  - <project>/.reasonix/settings.json (committable per-project)
  - ~/.reasonix/settings.json         (per-user)

A hook is a shell command. Reasonix invokes it with stdin = a JSON
envelope carrying the event, tool name, tool args, etc. Exit code
drives the decision:
  - 0 = pass; loop continues normally
  - 2 = block (only on PreToolUse / UserPromptSubmit); hook's stderr
    becomes the synthetic tool result the model sees, or the prompt
    is dropped entirely
  - anything else = warn; loop continues, stderr renders inline as a
    yellow row

Project hooks fire before global hooks. `match` is anchored regex on
the tool name (ignored for prompt / Stop events). Default timeouts:
5s for blocking events, 30s for logging events; per-hook `timeout`
overrides. Settings malformed? loadHooks swallows it so a typo
doesn't bring down the whole CLI.

Deliberate non-goals: no workflow DSL, no conditional chaining, no
hook templates. Hooks are shell commands — the user already has a
programming language.

New files:
  - src/hooks.ts                      (loadHooks, runHooks, decideOutcome, matchesTool, formatHookOutcomeMessage)
  - tests/hooks.test.ts               (26 unit tests)
  - tests/loop-hooks.test.ts          (6 smoke tests — loop wiring)

Modified:
  - src/loop.ts          — PreToolUse + PostToolUse dispatch around tool.dispatch
  - src/cli/ui/App.tsx   — load settings on mount, UserPromptSubmit before handleSubmit, Stop after loop.step
  - src/cli/ui/slash.ts  — /hooks list + /hooks reload
  - src/index.ts         — re-exports

+32 tests (suite 672 → 704). Lint / typecheck / build clean.
2026-04-22 22:06:29 -07:00
esengine 911f043db8 feat: version display in TUI header + reasonix update self-upgrade (0.4.22)
Two small quality-of-life additions.

The stats panel now carries the running version (`Reasonix v0.4.22 ·
model …`) so users can tell at a glance whether they're on the latest
build. A 24-hour background check against the npm registry surfaces a
yellow `update: X.Y.Z` nudge on the right side of the same row when a
newer version has been published — 2s timeout, cache at
`~/.reasonix/version-cache.json`, silent on failure.

`reasonix update` is the command form: detects global install vs npx,
spawns `npm install -g reasonix@latest` for the former or prints a
cache-refresh hint for the latter. `--dry-run` prints the plan.

Also fixes a drifted VERSION constant: `src/index.ts` hard-coded
"0.4.20" while package.json was on 0.4.21. Now re-exports from
`src/version.ts`, which walks up from import.meta.url to the
manifest on first access. A regression test pins them together.

New files: `src/version.ts`, `src/cli/commands/update.ts`,
`tests/version.test.ts`, `tests/update-command.test.ts`. +24 tests
(suite 648 → 672). Lint/typecheck/build clean.
2026-04-22 21:34:11 -07:00
esengine ce85319c9b docs(readme): promote reasonix code to the hero section, document skills
- Quick start now leads with `reasonix code` and a real SEARCH/REPLACE
  walkthrough — nobody enters through plain chat.
- New Skills section covers the SKILL.md format, project vs global
  scopes, /skill slash family, autonomous run_skill invocation, and
  the 'not tied to .claude/' stance.
- chat mode demoted to a brief 'also works as' section pointing at MCP.
- Commands table grouped by category (Core / Model / Context & tools /
  Memory & skills / Sessions / Code-mode only) instead of one flat list.
- Benchmarks promoted into their own 'verify yourself' section.
- Non-goals now names workflow DSL / DAG engine and DeepSeek-only
  positioning explicitly.
- Test count 444 → 648, Node requirement 18 → 20.10, added
  REASONIX_UI=plain to the env-var list.
2026-04-22 19:07:44 -07:00
esengine 2a9a9b386b feat: skills — project/global SKILL.md packs pinned into the prefix + shell fixes (0.4.21)
Skills are user-authored prompt packs read from `<project>/.reasonix/skills/`
and `~/.reasonix/skills/`. Pinned index (names + one-liners) lives in
the immutable prefix; bodies load lazily via the new `run_skill` tool
or `/skill <name> [args]`. Project scope wins on name collisions.
Deliberately NOT tied to any other client's dir (.claude/, .glm/) —
Reasonix is model-agnostic at the conversation layer.

No workflow DSL or DAG engine: skills are prose, the model sequences
via the existing tool-use loop. Preserves single-loop + append-only +
cache-first invariants; "no multi-agent orchestration" non-goal stands.

Shell fixes bundled in:
- ShellConfirm "always allow" now takes effect mid-session.
  extraAllowed is re-read on every dispatch via a getter, so a prefix
  saved to ~/.reasonix/config.json applies to the running tool
  without needing /new or a relaunch.
- Windows cmd.exe built-ins (dir, echo, type, ver, ...) no longer
  crash with ENOENT. prepareSpawn routes bare unresolved Windows
  commands through `cmd.exe /d /s /c` with verbatim-args quoting,
  matching the wrapping strategy for .cmd/.bat files.
2026-04-22 18:58:48 -07:00
esengine e3cfbb58dd feat: user memory — ~/.reasonix/memory/ pinned into the immutable prefix · remember/forget/recall tools · prompt cleanup (0.4.20)
- MemoryStore + applyUserMemory + applyMemoryStack (src/user-memory.ts):
  two scopes — global (cross-project) and project (per sandbox-root sha1).
  Each scope keeps a MEMORY.md index pinned into ImmutablePrefix.system;
  detail files loaded on demand via recall_memory. Byte-stable rewrite
  so identical file sets produce identical prefix hashes.
- remember / forget / recall_memory tools (src/tools/memory.ts) — chat
  mode gets global-only; reasonix code gets both scopes. remember's
  return text is imperative so R1 treats the fact as authoritative on
  the same turn.
- /memory slash extended: list | show <name> | forget <name> |
  clear <scope> confirm. Bare /memory renders REASONIX.md + both
  MEMORY.md blocks together.
- Prompt cleanup: dropped hardcoded dir enumerations, bun/npm examples,
  "待确认" CJK fallback, DSML-hallucination historical note, and
  Linear/Slack type-hint specifics. Principle-only wording + reference
  to the pinned .gitignore block. Net -tokens on every turn.
- README: new "User memory" subsection under REASONIX.md.
- scripts/smoke-memory.mts: 30-assertion end-to-end regression script.
- REASONIX_MEMORY=off now disables every memory source (REASONIX.md +
  user memory) — previous semantics was REASONIX.md only.

Tests: 542 → 624 (+82 incl. 36 memory-layer unit tests). Lint / tsc /
build clean.
2026-04-22 17:30:26 -07:00
esengine becaf487e8 fix(shell): use path.win32.join so CI tests with platform:win32 pass on Linux
CI runs on Linux, where pathMod.join defaults to POSIX (`/`). The
PATHEXT resolver mocks its isFile predicate with back-slashed keys
(`C:\tools\npm.CMD`), so join with POSIX produced `C:\tools/npm.CMD`
and lookups missed, failing 8 tests at origin. The runtime call path
is unaffected either way since the win32 branch is only active when
platform === "win32" anyway — but making the join explicitly win32
also hardens against weird PATHs on Windows where forward slashes
have historically crept in.
2026-04-22 06:38:41 -07:00
esengine 6111d8f621 fix(loop): surface StormBreaker suppression as a visible warning + reset on user turn
A silent storm-break was indistinguishable from a stalled turn — the
model would look like it gave up when really we'd suppressed its
repeat tool call. Now `step()` emits a dedicated warning event when
`report.stormsBroken > 0`, with distinct messages for the two cases:

- All calls suppressed (stuck retry): tell the user the model is
  looping on the same (tool, args) and point them at /retry or
  rewording the instruction. This is the case that used to dead-end
  the turn with nothing on screen.
- Some calls suppressed (one redundant): the rest of the turn
  proceeds; the warning is informational.

Also reset the StormBreaker's sliding window at the top of every
`step()` so a new user message doesn't inherit last turn's repeat
patterns (false-positive blocks on legitimate "try again" flows).

Part of the 0.4.19 batch — tag will be moved to this commit.
2026-04-22 06:35:13 -07:00
esengine d8ba9f9669 fix(shell): Windows — PATHEXT resolution + cmd.exe wrapping for .cmd/.bat (0.4.19)
Two layered fixes so `run_command` actually runs npm/npx/tsc/yarn/
pnpm/bun/pytest and every other Node-ecosystem wrapper on Windows:

1. resolveExecutable() walks PATH × PATHEXT manually — spawn
   with shell:false uses CreateProcess, which ignores PATHEXT, so
   bare `npm` missed `npm.cmd` and ENOENT'd.

2. prepareSpawn() wraps .cmd/.bat via `cmd.exe /d /s /c` with
   windowsVerbatimArguments + per-arg quoteForCmdExe — Node 21.7.3+/
   24 (CVE-2024-27980) refuses direct spawn of .cmd/.bat even with
   shell:false, throwing EINVAL. cmd.exe wrapping with manual
   safe-quoting keeps shell metacharacters (&, |, <, >, etc.) in
   arguments literal so the previous security posture holds.

Unix path unchanged. Suite 566 → 587.
2026-04-22 06:09:11 -07:00
esengine e409e9d8d9 feat: Plan Mode — autonomous plan proposals + /plan gate + answer-questions flow (0.4.18)
submit_plan tool: model proposes a markdown plan for large tasks
(multi-file refactors, ambiguous requests, risky changes). Picker
shows Approve / Refine / Cancel with the plan rendered as live
Markdown, not raw text. Open-questions sections ("Open questions",
"待确认", "Risks", etc.) are detected; default selection flips to
Refine and a yellow hint surfaces.

Both Approve and Refine take an inline text input afterward so the
user can answer the model's open questions or attach last-minute
instructions before the loop resumes. Empty Enter on Approve skips
the extras; empty Enter on Refine tells the model to ask concrete
clarifying questions.

/plan slash flips a dispatch-level read-only gate on the
ToolRegistry — writes + non-allowlisted shell bounce with a refusal
the model reads. Read tools, web_search/fetch, and allowlisted shell
(git status / cargo check / npm test etc.) still work during
exploration. Tool specs stay pinned across the toggle so the DeepSeek
prefix cache doesn't break.

/apply-plan is a fallback that force-approves without the picker,
for cases where the model wrote the plan in assistant text instead
of calling submit_plan.

Suite 542 → 566.
2026-04-22 05:50:28 -07:00
esengine 4d21ca4c4c feat: project memory — REASONIX.md pinned into the immutable prefix (0.4.17)
Drop a REASONIX.md in the project root and its contents are pinned
into the system prompt every session that opens there. Cache-first:
read once, hashed into the prefix fingerprint, no per-turn budget.
/memory prints what's currently pinned; REASONIX_MEMORY=off opts out.

Suite 517 → 542. Re-exported applyProjectMemory / readProjectMemory /
memoryEnabled + PROJECT_MEMORY_FILE / PROJECT_MEMORY_MAX_CHARS for
library consumers that build their own system prompt.
2026-04-22 04:55:06 -07:00
esengine 1ccc1d7e67 feat: run_command shell tool · session picker · ShellConfirm picker · backspace/markdown fixes (0.4.16) 2026-04-22 04:43:17 -07:00
esengine fd344986e8 feat: web_search via Mojeek · cursor editing in prompt · REASONIX_UI=plain · ticker consolidation (0.4.15) 2026-04-22 04:05:25 -07:00
esengine 6ceb73d367 fix(ui): consolidate timers · patchConsole:false · REASONIX_UI=plain opt-out (0.4.14) 2026-04-22 02:35:02 -07:00
esengine dee96f66a2 fix(ui): tool_call_delta progress · reset streamRef per iter · expanded README (0.4.13) 2026-04-22 01:59:44 -07:00
esengine 6b4d8652e4 fix(loop): full tool_calls↔tool pairing validator + auto-compact on context-guard (0.4.12)
Two DeepSeek 400s users hit in succession:
- "insufficient tool messages following tool_calls" on forced
  summary: context-guard appended assistant.tool_calls then bailed
  before dispatching. Fix: strip the tail before forceSummary.
- "tool must be a response to a preceding tool_calls" on the next
  message: partial heals left stray tool messages in the log.

Root fix: healLoadedMessages now runs a full tool_calls↔tool pairing
validator. Any assistant.tool_calls with an incomplete response set
is dropped (with its partial responses); any stray tool message is
dropped. Runs on session load (rewrites the file so damage doesn't
re-surface) AND on every buildMessages call (defensive).

Context-guard now auto-compacts before forcing summary. Previously
80% context meant you lost a turn immediately. Now: try shrinking
oversized tool payloads first; only fall back to forced summary
when nothing's compactable.

Split shrinkOversizedToolResults from healLoadedMessages so
`/compact` (mid-turn) doesn't strip legitimate structural state.

443 tests (+5 new, 4 reshaped).
2026-04-22 01:07:07 -07:00
esengine 5f7d8f238a feat: git-diff edit_file · /new clears context · clearer phase labels (0.4.11)
edit_file now produces a real git-diff-style output:
- LCS line-level diff (unchanged lines as ` ` context, `-/+` only
  for actual changes). Fixes the user-reported case where a one-line
  search with a multi-line replace showed the unchanged line as both
  `-` and `+`.
- Git-style @@ -start,count +start,count @@ hunk header pointing at
  the real starting line in the file.
- EventLog no longer truncates edit_file results — other tools keep
  the 400-char clip, but edit diffs always show full.

Context management:
- /new (alias /reset) drops the in-memory log AND empties the
  session file. Fresh conversation, same session/model/config.
- /clear now advertises that it only clears visible scrollback;
  users kept expecting it to clear context. Info line points at
  /new for the real clear.
- CacheFirstLoop.clearLog() is the public API.

Streaming row:
- Replaced "streaming · 391 + think 4506 chars" with explicit
  phase labels: yellow "request sent · waiting for server" pre-
  first-byte, cyan "R1 reasoning · N chars of thought" during
  reasoning-only, green "writing response · N chars · after M
  chars of reasoning" in content phase.

436 tests (+8).
2026-04-22 00:52:13 -07:00
esengine dc38c765e8 feat: status indicators · live stats · balance · in/out cost split · edit_file diff · GFM tables (0.4.10)
Major batch of UX fixes based on user reports:

Silent-wait elimination:
- New "status" loop event + StatusRow component. Fills silent
  phases with explicit magenta spinner text: "tool result uploaded
  · model thinking before next response…" between iters,
  "extracting plan state from reasoning…" before harvest,
  "summarizing what was gathered…" before forced summary. Auto-
  clears on the next primary event.
- Belt-and-suspenders "processing…" fallback when busy but none of
  streaming/ongoingTool/statusLine is visible — catches any
  micro-gap the targeted statuses don't cover.
- Strengthened pre-first-byte messaging: "(request sent · waiting
  for server)" instead of "(streaming · 0 chars)".

Stats panel:
- Live per-iter refresh — previously frozen at prior turn's
  numbers for 30-60s during multi-iter chains.
- Account balance cell. New DeepSeekClient.getBalance() hits
  /user/balance (separate endpoint, no billing impact). Refreshed
  after each turn, hidden on failure.
- In/out cost split. Panel now shows "cost $X (in $Y · out $Z)"
  so users can see where spend lands. SessionSummary gains
  totalInputCostUsd + totalOutputCostUsd; inputCostUsd() and
  outputCostUsd() exposed as library utilities.
- Dropped "vs Claude / saving" cells — the synthetic ratio looked
  like marketing, not measurement. Fields kept in summary for
  benchmark/replay compat but deprecated.

Esc coverage:
- harvest() now takes an AbortSignal and fast-paths to emptyPlanState
  when already aborted. Was the last un-signaled API call path.

edit_file visibility:
- Tool result now returns a unified-style `- search / + replace`
  inline diff in addition to the header. Long blocks are truncated
  with "… (N more lines)" marker in the middle; /tool N still shows
  the full thing.

Markdown:
- GFM tables (|col|col| + separator) render as aligned columns
  with │ dividers. CJK-width-aware padding for mixed-lang tables.
  Alignment colons, pipe-less headers, escaped \| in cells all
  handled. Stray | in prose no longer false-triggers the table
  path.

427 tests (+11).
2026-04-22 00:39:07 -07:00
esengine 59bd38b1aa feat: Esc cancels immediately · native fs tools · cursor fix · slow_count demo (0.4.9)
Three reported issues rolled into one release:

1. Esc now truly cancels in-flight work. AbortController threaded
   through every I/O path:
   - DeepSeekClient.chat/.stream signal wired at every call site
   - ToolRegistry.dispatch gets a ToolCallContext { signal }
   - McpClient.callTool({ signal }) fires notifications/cancelled
     AND rejects the pending promise immediately — no waiting on
     subprocess for a graceful finish
   - bridgeMcpTools forwards ctx.signal down

2. Built-in filesystem tools replace the
   @modelcontextprotocol/server-filesystem subprocess inside
   `reasonix code`. 10 native tools, sandboxed, R1-friendly schemas.
   The new edit_file takes a flat SEARCH/REPLACE shape instead of
   the JSON-in-string array that was the single biggest driver of
   R1 DSML hallucinations in 0.4.x. Per-call latency drops from
   ~500ms–2s (Windows subprocess IPC) to <10ms (direct fs).

3. PromptInput placeholder cursor now renders at position 0
   (before the hint text), not after it.

4. Bonus: slow_count demo tool in examples/mcp-server-demo.ts
   emits real notifications/progress frames so the progress-bar
   plumbing from 0.4.8 is testable end-to-end.

ChatOptions grows `seedTools: ToolRegistry` so callers can
pre-register tools and still layer MCP on top. ToolCallContext
is re-exported for library users writing abortable tools.

416 tests (+29: filesystem-tools +26, mcp abort +3).
2026-04-22 00:14:56 -07:00
esengine 3484c04133 feat(mcp): progress notifications — live progress bar in spinner (0.4.8)
MCP notifications/progress now route to per-call onProgress handlers.
Long-running tool calls can stream incremental progress; the spinner
row renders an ASCII bar + n/total + pct when the server reports a
total, or free-form progress+message otherwise.

- McpClient.callTool(name, args, { onProgress }) mints a fresh
  _meta.progressToken and routes progress frames back. Handler is
  dropped on completion — late frames are swallowed silently.
- bridgeMcpTools({ onProgress }) pipes per-call progress through
  with the registered (prefix-applied) tool name.
- chatCommand creates a shared progressSink ref; App.tsx wires its
  setState handler through on mount.

Other server-initiated notifications (list_changed) still dropped
— no use case yet.

387 tests (+5).
2026-04-21 23:54:11 -07:00
esengine 7075608ddc feat(ux): multi-line prompt input — Ctrl+J · Shift+Enter · '\<Enter>' (0.4.7)
Replaces ink-text-input in the main chat prompt with a custom
multi-line composer. Three newline-insertion paths in reliability
order: Ctrl+J (universal), Shift+Enter (modern terminals), trailing
"\" + Enter (portable fallback). Pasted multi-line content lands
intact instead of submitting on the first '\r'.

Pure processMultilineKey reducer keeps the keyboard semantics
testable; the React component is a thin wrapper. Parent-owned keys
(Tab, arrows, Esc) are no-ops in the reducer so the buffer never
eats a stray control sequence when both useInput listeners fire on
the same event.

Cursor-at-end model (no mid-string edits) — simple, predictable,
and doesn't collide with parent's arrow-key slash-nav + history.
ink-text-input still used by Wizard/Select/Setup — fine for
single-line forms.

382 tests (+18).
2026-04-21 23:47:04 -07:00
esengine 27a32b7b94 feat(ux+mcp): slash autocomplete · drop footer · /mcp rich view · mcp inspect CLI (0.4.6)
UX overhaul:
- Typing `/` pops an IntelliSense-style suggestion list with name +
  args hint + summary. ↑/↓ navigate, Tab completes, Enter picks +
  runs. Registry-driven (SLASH_COMMANDS) with code-mode gating.
- Static command-strip footer under the input is gone — superseded
  by the on-demand slash popup.

MCP discovery:
- /mcp in chat is now a rich per-server view: server info + spec +
  tool count + resources list + prompts list. Unsupported sections
  render "(not supported)" cleanly. Inspection runs once at
  startup and flows through SlashContext.mcpServers.
- New `reasonix mcp inspect <spec>` CLI for running the same
  discovery outside chat (CI, scripting, "does this work?"). --json
  emits the full InspectionReport.
- inspectMcpServer() + InspectionReport are public APIs; McpClient
  gains serverInfo / protocolVersion / serverInstructions getters.

364 tests (+11).
2026-04-21 23:39:48 -07:00
esengine 1391534f6c feat(repair+mcp): DSML scavenge + MCP resources/prompts (0.4.5)
Two protocol-level completions bundled:

1. DSML tool-call recovery. scavengeToolCalls gains a DSML invoke
   parser (<|DSML|invoke>/<|DSML|parameter string="true|false">).
   ToolCallRepair.process now scans both reasoning AND content
   channels — before, DSML in a regular turn was stripped from
   display but the tool never actually ran.

2. MCP resources + prompts. McpClient gains resources/list,
   resources/read, prompts/list, prompts/get with full types and
   cursor pagination. Initialize now advertises all three
   capability families.

353 tests (+13: scavenge +5, pipeline +2, mcp +6).
2026-04-21 22:13:43 -07:00
esengine 169d66d46a feat(ux): /tool slash — inspect untruncated tool output (0.4.4)
EventLog clips tool results at 400 chars for display; /tool [N]
now lets users read the full text. `/tool` lists the 10 most
recent with previews and char counts; `/tool N` dumps the
Nth-most-recent in full. Wired via new SlashContext.toolHistory
callback — pure handleSlash stays stateless.

340 tests (+8 /tool cases).
2026-04-21 21:41:30 -07:00
esengine 2836b5d406 fix(loop): Esc abort no longer blocks for 30-90s + bump to 0.4.3
User feedback: after pressing Esc, the warning fired instantly but
then the TUI blocked for the duration of a full reasoner call
(30-90s) to produce a "summary" the user hadn't asked for. Esc in a
terminal means stop. Stopping and then forcing the expensive
reasoner to wrap up is the opposite of what the user signaled.

Abort path now:
  - Emits a short warning "aborted at iter N/M — stopped without
    producing a summary (press ↑ + Enter or /retry to resume)"
  - Appends a synthetic assistant message "[aborted by user (Esc)
    — no summary produced. Ask again or /retry when ready; prior
    tool output is still in the log.]"
  - Yields assistant_final (tagged forcedSummary so edit applier
    ignores) + done
  - No API call. Takes milliseconds.

Budget and context-guard paths still call forceSummaryAfterIterLimit
because in those cases the loop stopped, not the user — leaving
them staring at nothing would be worse than one extra call. Only
user-initiated abort gets the fast path.

Test rewritten to confirm no extra API call is made (previously
asserted a "partial findings" summary from the never-needed
follow-up). Suite: 332 still passing.

Also bumps to 0.4.3 because v0.4.2 tag is already on origin at
cb2f2a5 with partial content. This release consolidates the full
0.4.2 batch + the Esc fix under one tag.
2026-04-21 21:31:59 -07:00
esengine d0bd6852c1 feat(ux): /retry · /status rich · /think · ↑↓ history · y/n · red errors · tool-row elapsed · reasoning tail · DSML strip (0.4.2)
Nine UX improvements in one batch, all surfaced from real-session
feedback while testing reasonix code against a live filesystem
project.

Added slash commands:
  - /retry — truncate log back before the last user message, resend
    it, get a fresh sample from the model. SlashResult gains a
    resubmit field the TUI honors after displaying info.
  - /status — now a labeled situation-report: model, flags
    (harvest/branch/stream), ctx ratio (42k/131k (32%)) from last
    turn's promptTokens, MCP server + tool counts, session name +
    log length + resumed count, pending edits count. One command
    shows everything.
  - /think (alias /reasoning) — dumps full R1 reasoning from
    loop.scratch.reasoning. For when the 260-char tail preview
    isn't enough. Graceful "no reasoning cached" when using
    deepseek-chat.

Added interactions:
  - ↑/↓ shell-style prompt history. App.tsx owns a ref array, cursor
    advances on arrow keys while idle. Process-scoped, no cross-run
    persistence.
  - y/n fast-path when edits are pending. Typing 'y'+Enter = /apply,
    'n'+Enter = /discard. Scoped: only when pendingEdits.length > 0,
    so plain "y" as a normal message still works when nothing's
    waiting. Preview line advertises the shortcut.

Changed:
  - Tool-running row surfaces elapsed seconds + per-tool argument
    summary. Before: ⠋ tool<filesystem_edit_file> running… {raw
    JSON}. Now: ⠋ tool<filesystem_edit_file> running… 3s / path:
    F:\... (2 edits). Summarizers for read_file, write_file,
    edit_file, list_directory, directory_tree, search_files,
    move_file, get_file_info. Matches suffix so namespaced and
    anonymous servers both work.
  - Reasoning preview shows tail (~260 chars), not head. R1 opens
    every turn with the same scaffolding that hid the actual
    decision in the (+N chars) elision; users reported reasoning
    looked identical across turns. The tail is where the model
    commits to an action.
  - Tool errors render red with ✗ marker instead of yellow with →.
    ERROR: prefix from flattenMcpResult (on isError) is detected.
    A failure needs different attention than a listing.

Fixed:
  - Forced-summary path no longer leaks DSML tool-call markup as
    prose. Passing tools: undefined wasn't enough — R1 primed for
    tool use would still emit <|DSML|function_calls>...</|DSML|
    function_calls> as plain text in content. Two layers: (1)
    inject an explicit user-role instruction at the end of the
    forced-summary message list telling the model to produce prose
    with no tool markup; (2) post-hoc strip known envelopes (DSML
    full-width/ASCII, Anthropic <function_calls>, and truncated
    un-closed DSML openers) from the model's response before
    yielding. stripHallucinatedToolMarkup exported for library
    callers. Fallback message when stripping leaves nothing points
    at /retry and /think.

Tests: +13, suite 319 -> 332.
  - tests/slash.test.ts (+8): /think empty/populated/help,
    /retry happy/empty-log/help, /status new format, /status
    pending-edit suppression at 0.
  - tests/loop-error.test.ts (+5): stripHallucinatedToolMarkup
    against live R1 DSML shape, Anthropic-style, truncated
    un-closed opener, plain prose, all-markup edge case.

Bumps to 0.4.2.
2026-04-21 21:26:42 -07:00
esengine cb2f2a550b feat(ux): tool-row elapsed + args · reasoning tail · /think (0.4.2)
Three small improvements surfaced from real-session feedback:

1. Tool-running row was just a spinner + raw-JSON args; user said
   "看不到任何的输出,就只知道再转圈". Added elapsed seconds counter
   and per-tool argument summarizer. Instead of
     tool<filesystem_edit_file> running... {"path":"..."...}
   you now see
     tool<filesystem_edit_file> running... 3s
       path: F:\testtest\index.html (2 edits)
   Summarizers for read_file / write_file / edit_file /
   list_directory / directory_tree / search_files / move_file /
   get_file_info, matching by suffix so bridgeMcpTools name prefix
   (e.g. "filesystem_") works too. Unknown tools fall back to a
   truncated raw preview.

2. ReasoningBlock showed the first 220 chars with "(+N chars)"
   elided at the end. R1 opens every turn with the same scaffolding
   ("let me look at the structure...") so the preview looked
   identical across turns and hid the actual decision in the
   truncated tail. Switched to showing the LAST ~260 chars —
   which is where R1 commits to an action.

3. /think slash command dumps the full reasoning text from
   loop.scratch.reasoning when the tail preview isn't enough.
   Alias: /reasoning. Graceful "no reasoning cached" message when
   the current model is deepseek-chat (no reasoning_content) or a
   turn hasn't completed yet.

Tests: +3 in slash.test.ts (/think empty + populated + help).
Suite: 319 -> 322.

Bumps to 0.4.2.
2026-04-21 21:05:44 -07:00
esengine e472f4cb79 feat(code): /apply gate + /undo + /commit + .gitignore + better UX signals (0.4.1)
A real-session bug report — "I asked the model to analyze the project
and it silently edited a file" — forced a rethink of v0.4.0's
auto-apply default. This release fixes the root cause plus a stack of
adjacent UX gaps surfaced during the fix.

WHY (behavior change): auto-apply was wrong because it conflated two
distinct events — "the model proposed a change" and "the user wants
to make the change." v0.4.0 treated every SEARCH/REPLACE block in
assistant output as permission to write. Analysis drifted into edits.
Preview-by-default + explicit /apply is Aider's model and it's honest.

Added (code mode):
  - /apply: writes pending edit blocks to disk, snapshots for /undo,
    reports per-block status
  - /discard: drops pending edits, no disk writes
  - /undo: rolls back the last applied edit batch (restores modified
    files, deletes ones created by the batch)
  - /commit "msg": git add -A && git commit -m "..." in code rootDir;
    surfaces git stderr on hook failure / nothing-staged / etc.
  - .gitignore awareness: reasonix code reads rootDir/.gitignore on
    launch and appends it to the system prompt as "don't traverse
    these paths unless asked"; hard-coded baseline (node_modules,
    dist, .git, .venv, __pycache__, target, ...) baked into the base
    prompt for projects without a .gitignore

Fixed:
  - Edits no longer auto-write. Each assistant turn's blocks are
    parsed and shown as a preview (filename + -N/+M line-count). No
    disk write until /apply. Pending persists across messages.
  - LoopEvent.forcedSummary flag on assistant_final events from the
    no-tools fallback (budget/aborted/context-guard). Code-mode
    applier skips tagged events — a wrap-up summary is not a plan.
  - Token-context guard replaces iter count as primary stop
    condition. promptTokens > 80% of ctx window -> yellow warning +
    skip tool exec + divert to summary (reason: "context-guard").
    Iter cap 24 -> 64 as last-resort backstop.
  - CODE_SYSTEM_PROMPT tightened: explicit rule that edits only fire
    on change/fix/add/remove/refactor intents; analyze/explain stay
    read-only.
  - Stray EditSummary/summarizeEdit reverted from edit-blocks.ts (a
    0.4.0 forced-summary run auto-wrote it; dead code).
  - SEARCH/REPLACE blocks now render as a proper diff (red -/green +)
    instead of going through the markdown paragraph path, which was
    joining lines with spaces and letting the bold/italic regex eat
    `*` chars inside JSDoc `/** ... */` comments. New parseBlocks
    exports an "edit-block" block kind.
  - R1 reasoning UX no longer looks frozen. Cyan braille-spinner
    heartbeat (500ms) + "reasoning" vs "streaming" label + explicit
    "R1 is thinking before it speaks — body text starts when
    reasoning completes (typically 20-90s)" message while body is
    empty. Replaces the misleading "(waiting for first token...)".
  - New "tool_start" event yielded immediately before
    tools.dispatch(). TUI renders a spinner row "⠋ tool<X> running…"
    with args preview while the Promise is pending — fixes the
    dead-air window between assistant_final (streaming cleared) and
    the tool result event, during which a multi-KB
    filesystem_edit_file could hang the UI visibly for 100ms-1s.

Tests: +36, suite 292 -> 319.
  - tests/edit-blocks.test.ts (+5): snapshot/restore round-trip,
    delete on undo-of-create, per-path dedup, path-escape defense.
  - tests/code-prompt.test.ts (+4, new file): .gitignore injection
    happy/absent/truncated paths, base-prompt ignore hints.
  - tests/slash.test.ts (+13): /apply /discard /undo /commit inside
    and outside code mode, usage hint on empty, double-quote
    stripping, help listing.
  - tests/loop.test.ts (+2): context-guard warning + forcedSummary
    flag when prompt > 80% of window, tool_start precedes tool.
  - tests/markdown.test.ts (+5): parseBlocks recognizes SEARCH/
    REPLACE into edit-block blocks, preserves multi-line JSDoc
    verbatim, handles new-file empty-SEARCH, rejects stray markers
    without close, multi-block + prose interleaving.

Bumps to 0.4.1.
2026-04-21 20:53:53 -07:00
esengine 14887264bb feat(code): reasonix code — SEARCH/REPLACE editing as a first-class mode (0.4.0)
A new opinionated subcommand that turns Reasonix into a coding
assistant, realizing the "cheap Claude Code" pitch. Layers on top of
the existing chat + MCP machinery rather than forking it.

What `reasonix code [dir]` does:
  - Auto-bridges @modelcontextprotocol/server-filesystem at [dir]
    (default CWD). No wizard, no config merge.
  - Uses a coding-focused system prompt that teaches Aider-style
    SEARCH/REPLACE blocks and forbids write_file for existing files.
  - Forces reasoner + harvest (coding repays R1 thinking).
  - Scopes the session name to the directory basename so projects
    don't cross-pollute.
  - Hooks codeMode into App.tsx — after each assistant_final, parses
    SEARCH/REPLACE blocks from the response and applies them to disk,
    reporting per-block results as info lines.

SEARCH/REPLACE semantics (src/code/edit-blocks.ts):
  - SEARCH must match byte-for-byte. No fuzzy matching — a silent
    wrong edit is worse than a loud rejection.
  - Empty SEARCH creates a new file (Aider convention).
  - First occurrence only; duplicate SEARCH text requires a new
    block with more surrounding context.
  - Path-escape defense: resolve + startsWith on the normalized
    rootDir, refuses paths climbing above the sandbox.

Library surface: parseEditBlocks, applyEditBlock, applyEditBlocks,
CODE_SYSTEM_PROMPT, and EditBlock/ApplyResult/ApplyStatus types.
Compose them yourself for custom UIs.

Out of scope for v1: /commit, /undo, diff preview, .gitignore
filtering. User's `git diff` + `git checkout` is the review/undo
surface; we run inside a git repo by convention.

Tests: +13 in edit-blocks.test.ts (parse: single/multi/multiline/
empty-search/stray-markers; apply: happy/new-file/not-found/
file-missing/path-escape/first-occurrence; batch: independent
results). Suite 279 -> 292.

Bumps to 0.4.0 (minor — new user-facing primitive + library surface
additions; no breaking changes for 0.3.x users).
2026-04-21 20:05:45 -07:00
esengine 63ced2fa5b feat: Esc to abort + 70% budget warning + README refresh (0.3.2)
0.3.1 gave the loop a safety net (forced summary at maxToolIters);
this release turns that safety net into an interactive budget. Users
no longer have to wait for the ceiling to hear from the model.

- Yellow warning event fires once per step when tool-iter count hits
  70% of maxToolIters. TUI renders it in the event log with an
  "Press Esc to force a summary now" hint; the command strip under
  the prompt also shows the Esc shortcut.
- CacheFirstLoop.abort() method + TUI Esc handler (useInput, guarded
  by busy state and a once-per-turn flag). On abort, the current tool
  call is allowed to finish, then the loop diverts to the 0.3.1
  no-tools summary path with a different prefix:
  "[aborted by user (Esc) - summarizing what I found so far]".
- New EventRole "warning" + DisplayRole "warning"; EventLog renders
  them yellow. Wired through App.tsx's event dispatcher.

README rewrite: hero leads with `npx reasonix` (no flags), wizard
story in prose. --mcp and --preset examples moved to "Advanced".
What-you-get table gains Setup wizard, Context safety net row, and
merges stdio + SSE into one MCP row. Non-goals and Configuration
trimmed to match.

Tests: +2 in loop.test.ts (warning fires exactly once at threshold;
abort() diverts to summary with "aborted" prefix). Suite: 277 -> 279.

Bumps to 0.3.2.
2026-04-21 19:50:52 -07:00
esengine 461e736cbc fix(loop): force summary when maxToolIters is reached (0.3.1)
Problem (reproduced live): user asked the reasoner to explore a Flutter
project via filesystem MCP. The model chained 8 list_directory /
read_file calls, the loop hit the default maxToolIters=8, quietly
yielded a "done" event with content "[max_tool_iters reached]", and
exited. The App.tsx doesn't render `done` content anywhere, so the
user saw a blank assistant reply after 8 tool calls — as if Reasonix
just stopped for no reason.

Fix:
  - When the tool-call loop exhausts its budget with tool_calls still
    pending, make one final request to DeepSeek with tools omitted.
    Forces a text-only answer based on everything in history. Yield
    as a normal assistant_final event, prefixed with
    "[tool-call budget (N) reached - forcing summary from what I found]"
    so the user knows why they got a summary instead of more drilling.
  - Default maxToolIters 8 -> 24. Eight was below the floor for any
    real filesystem exploration; 24 still caps a confused model's
    damage.

Tests: +1 in loop.test.ts with maxToolIters=2, every response wanting
tools, proving the summary call fires and assistant_final carries the
budget annotation. Suite: 276 -> 277.

Bumps to 0.3.1.
2026-04-21 19:40:15 -07:00
esengine d932c50ab3 release: v0.3.0 — context gauge + /compact + stable graduation
Drops the prerelease tag and ships 0.3.0 stable. Since 0.2.2 this
includes: MCP (stdio + SSE, multi-server, curated catalog), the
first-run wizard that replaces the --mcp flag maze, config-backed
defaults, and a three-layer context-safety net (per-tool cap +
auto-heal on session load + manual /compact).

Added this commit:
  - StatsPanel context gauge: "ctx 42k/131k (32%)" with yellow at
    50% and red + "/compact" nudge at 80%+. Reads SessionSummary's
    new lastPromptTokens field; model max comes from
    DEEPSEEK_CONTEXT_TOKENS (131072 for chat/reasoner).
  - /compact [cap] slash: re-applies truncation with a tighter 4k
    char cap (or user-supplied), rewrites the session file on disk
    so the next launch doesn't re-inherit a fat file. Reports chars
    and approximate tokens saved.
  - SessionSummary.lastPromptTokens, AppendOnlyLog.compactInPlace(),
    session.rewriteSession(), loop.compact() — all new exports.

Tests: +5 (slash /compact x4, telemetry lastPromptTokens x1).
Suite: 276 passing (up from 241 in alpha.4).

Migration note: one silent behaviour change — sessions built with
pre-alpha.6 clients auto-heal on load (oversized tool results get
truncated). The conversation is preserved; only the bloat shrinks.
2026-04-21 19:35:36 -07:00
esengine b4c461c6ad fix(mcp): cap tool-result size + annotate context-overflow errors
Problem: a single `read_file` on a big file returned ~3 MB of text
through flattenMcpResult; it landed in session history verbatim and
every subsequent turn 400'd with DeepSeek's "maximum context length
is 131072 tokens. However, you requested 929,452 tokens." The user
had no way to recover short of deleting the session file by hand.

Fix, at both ends:
  - Prevention: bridgeMcpTools now caps each result at 32k chars by
    default. truncateForModel keeps head + 1KB tail with a clear
    "[...truncated N chars...]" marker, so the model sees both
    "what the tool started returning" and "how it ended" (important
    for error messages appended at the bottom of stack traces).
    Override: bridgeMcpTools(client, { maxResultChars: N }).
  - Diagnosis: formatLoopError() detects "maximum context length"
    in the raw API error, pretty-prints the requested-token figure,
    and tells the user exactly what to do — /forget to wipe the
    session file, /clear for display-only. Other errors pass through.

Exports: DEFAULT_MAX_RESULT_CHARS, truncateForModel, FlattenOptions,
formatLoopError — so library callers get the same protection.

Tests: +3 for truncation (head+tail preserved, no-op below cap,
end-to-end dispatch), +3 for error annotation (token figure,
passthrough, figure-less overflow). Suite 262 -> 268.

Bumps to 0.3.0-alpha.6.
2026-04-21 19:22:58 -07:00
esengine 2f4e28b7cb feat(ux): setup wizard + config defaults — reasonix with no args just works
The previous UX required users to memorize a pile of flags
(`--mcp "name=npx -y @scope/pkg /path"`, `--harvest`, `--branch N`,
`--session`) before they could use any of Reasonix's power features.
That was wrong: the target audience is ordinary users, not CLI
archaeologists.

New flow:
  - `npx reasonix` — on first run opens an Ink wizard (API key →
    preset pick → MCP multi-select → per-server args → save). On
    subsequent runs launches chat with the saved defaults.
  - `reasonix setup` re-runs the wizard any time; existing selections
    are pre-checked via package-name matching against the catalog.
  - `~/.reasonix/config.json` now stores preset + mcp + session +
    setupCompleted alongside apiKey. Precedence: explicit CLI flag
    wins, then --preset, then config.preset, then hardcoded fast
    defaults. `--no-config` is the escape hatch for CI.
  - `--preset <fast|smart|max>` new on both chat and run so power
    users get the bundled settings too.
  - `/mcp` slash — lists attached servers + tool registry mid-chat.
  - `/setup` slash — prints instructions to exit and re-run
    `reasonix setup`. Live reconfig is out of scope: swapping tools
    mid-session would invalidate the byte-stable prefix.

Fixes two real bugs found during manual testing:
  - `@modelcontextprotocol/server-fetch` and `server-sqlite` were in
    the catalog but don't exist on npm (Python-only reference
    implementations). Picking either one produced a 404 that killed
    the chat. Removed.
  - One broken MCP server took down the whole chat via
    `process.exit(1)`. Now each failure prints `▸ MCP setup SKIPPED`
    pointing at `reasonix setup` and the session continues with the
    servers that worked.

Tests (+21, suite 241→262):
  - tests/resolve.test.ts (+11) — flag/preset/config precedence, cap
    and off paths, --no-config, --no-session isolation.
  - tests/config.test.ts (+2) — extended schema round-trip,
    session:null meaning ephemeral.
  - tests/slash.test.ts (+4) — /mcp empty + populated, /setup hint,
    help coverage.
  - tests/wizard.test.ts (+4) — buildSpec → parseMcpSpec round-trip
    for filesystem / memory / spaces-in-path / unknown-entry fallback.

Bumps to 0.3.0-alpha.5.
2026-04-21 19:14:59 -07:00
esengine 5f715d05ee feat(mcp): SSE transport — remote/hosted servers via --mcp "https://…"
Implements the MCP 2024-11-05 HTTP+SSE wire: GET the SSE URL, wait for
event: endpoint, POST every outgoing JSON-RPC frame to that URL, read
responses off the SSE channel. Headers (Authorization, etc.) pass
through to both the GET and POSTs so hosted servers behind auth work.

--mcp now routes anything starting with http:// or https:// to
SseTransport; everything else stays stdio. McpSpec becomes a
discriminated union { transport: "stdio" | "sse", … } — callers that
inspected spec.command/args must branch on spec.transport first.

Tests: in-process http.Server fake implementing the SSE wire —
relative endpoint resolution, absolute endpoints, a full McpClient
initialize → listTools round-trip, handshake failure propagation.
Plus parseMcpSpec SSE cases (case-insensitive scheme; ws:// stays
routed to stdio as there's no ws transport yet). Suite: 241 passing.

Bumps version to 0.3.0-alpha.4.
2026-04-21 18:55:06 -07:00
esengine b662c63894 data(mcp): multi-server live run — 2 subprocesses, 1 prefix hash,
Cache-First holds

Third MCP live data point, the ecosystem proof. Run against two MCP
servers concurrently:

  --mcp "demo=node --import tsx examples/mcp-server-demo.ts"
  --mcp "fs=npx -y @modelcontextprotocol/server-filesystem <dir>"

The model used tools from both in one conversation — computed 17+25
via demo_add, then wrote "42" to a real file on disk via
fs_write_file (with a graceful permission-denied recovery in
between).

  turns: 5, tool calls: 4
  cache: 81.1%, cost $0.00185, 95.9% cheaper than Claude
  prefix hashes: ONE across all 5 turns — byte-stable prefix
  survives two concurrent MCP subprocesses

Reference: benchmarks/tau-bench/transcripts/mcp-multi-server.jsonl
(replay offline to verify — no API key needed).

Also adds .claude/settings.local.json to .gitignore (local Claude Code
settings are personal and shouldn't be committed).
2026-04-21 18:41:29 -07:00
esengineandClaude Opus 4.7 e793c7d59d chore(release): v0.3.0-alpha.3 — multi-server MCP + mcp list discovery
Adds the last bit of UX I'd actually hand to a new user: a way to
discover what MCP servers they can try.

New:
- reasonix mcp list            curated catalog of popular official MCP
                               servers, each with a copy-pasteable
                               --mcp command. filesystem / fetch /
                               github / memory / sqlite / puppeteer /
                               everything. --json for machine output.
- --mcp repeatable             multi-server support (already in main,
                               now released on npm @alpha)
- "name=cmd args..." spec      per-server namespace prefix, tools land
                               as fs_read_file, mem_set, etc.

Packages 7cd8621 (multi-server) + new mcp list command as alpha.3.

Discovery is hardcoded not fetched: the list changes slowly, offline
users shouldn't have to wait on a network fetch to see what exists.
Updating it = one file edit + patch release.

Suite 233/233; no functional changes to the existing tested paths.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 18:31:33 -07:00
esengineandClaude Opus 4.7 7cd862194a feat(mcp): multi-server support — repeatable --mcp with per-server names
`--mcp` is now a collect-style option; pass it multiple times to attach
multiple servers to the same chat / run. Each spec can optionally name
its namespace:

  reasonix chat \
    --mcp "fs=npx -y @modelcontextprotocol/server-filesystem /tmp/safe" \
    --mcp "demo=node --import tsx examples/mcp-server-demo.ts"

Tools land in a shared ToolRegistry with the prefix baked in
(fs_read_file, demo_add, …). The model sees the flat namespace; the
registry dispatches to the right subprocess.

Spec syntax (new src/mcp/spec.ts::parseMcpSpec):
- "name=command args..."  → namespaced; `[a-zA-Z_][a-zA-Z0-9_]*` name
- "command args..."       → anonymous; tools keep their native names

The identifier regex is deliberately narrow so Windows drive letters
(`C:\...`) never accidentally look like a namespace prefix.

--mcp-prefix still exists as a global fallback, but only applies when
exactly one anonymous spec is given. With named specs, each server
brings its own name.

Also fixes a shellSplit bug: backslashes outside quotes were being
treated as POSIX escapes, which mangled every Windows path. Now they
pass through literally outside quotes (use quotes to group args with
spaces). Matches user expectation on Windows; POSIX users who want
escape-a-space can quote the arg.

+9 tests: parseMcpSpec (8 cases including Windows drive letters,
identifier-name validation, empty/malformed input) + an integration
test spawning two demo subprocesses concurrently with different
prefixes, verifying the shared registry dispatches to each correctly.
Suite: 233 passing (was 224).

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 18:22:53 -07:00
esengineandClaude Opus 4.7 407793c99e chore(release): v0.3.0-alpha.2
Packages 5e124ce's Windows fix + second live MCP data point as an
alpha. v0.3.0-alpha.1 is technically broken on Windows (--mcp "npx ..."
can't find npx.cmd), so this supersedes it on the @alpha npm tag.

No functional changes since 5e124ce — just version bump + CHANGELOG.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 18:08:27 -07:00
esengineandClaude Opus 4.7 5e124cec36 feat(mcp): cross-platform shell fix + second live data point via
official @modelcontextprotocol/server-filesystem

Two things together — the fix is what unlocked the data.

1. StdioTransport now handles Windows .cmd/.bat shims (npx.cmd,
   pnpm.cmd) without triggering Node's DEP0190 deprecation warning.
   On win32, shell defaults to true; we build a quoted command line
   ourselves (command bare so PATH lookup works, args quoted) and
   pass it as a single string, dodging the shell:true + args[]
   anti-pattern. POSIX path unchanged. New `shell?: boolean` option
   lets callers override the platform default (e.g. tests spawning
   node.exe directly).

2. Second live MCP run, this time against the *external*,
   production @modelcontextprotocol/server-filesystem:

     5 turns, 4 tool calls, cache **96.7%**, cost $0.00124,
     97% cheaper than Claude at equivalent tokens.

   The model tried list_directory on the wrong path, got an access-
   denied, self-recovered by calling list_allowed_directories, then
   list_directory + read_text_file. Messy realistic run. Byte-stable
   prefix held across every turn.

   This matters because the first MCP run (v0.3.0-alpha.1,
   mcp-demo.add.jsonl) was against our own bundled demo server.
   Someone could reasonably argue "of course it caches — you wrote
   the server". This one answers that: cache-first works on code
   we don't control.

Reference transcripts:
- benchmarks/tau-bench/transcripts/mcp-demo.add.jsonl       (own server)
- benchmarks/tau-bench/transcripts/mcp-filesystem.jsonl     (official)

README gains a two-row table with both numbers + a no-API-key
reproduction block pointing at both committed transcripts.

Tests still 224/224 green. Integration tests explicitly set
shell: false since they spawn node.exe by absolute path.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 18:04:09 -07:00
esengineandClaude Opus 4.7 7fce6e650c chore(release): v0.3.0-alpha.1 — MCP client + first live run
End-to-end MCP integration verified on live DeepSeek. Recorded run at
benchmarks/tau-bench/transcripts/mcp-demo.add.jsonl:

  ▸ spawned bundled demo MCP server (3 tools bridged)
  ▸ model chose the add tool, received the result via MCP stdio
  ▸ follow-up turn hit 96.6% cache (byte-stable prefix held across
    the tool-call round-trip)
  ▸ total cost $0.000254 — 94% cheaper than Claude at same tokens

This is the v0.1 Cache-First claim extending verbatim to arbitrary MCP
tools. The mechanism wasn't altered; the registry just serves MCP tools
as if they were native. That extension *is* the v0.3 headline.

Shipping as alpha because:
  - one real run is proof-of-concept, not proof-at-scale
  - SSE transport, resources, prompts, and progress notifications are
    still deferred
  - official external MCP servers (filesystem, github, etc.) haven't
    been exercised in CI yet

Suite: 224 passing (10 fake-transport unit, 9 shell-split, 2 real-
subprocess integration, plus the existing 203).

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 17:52:54 -07:00
esengineandClaude Opus 4.7 5941043489 feat(mcp): CLI --mcp flag + bundled demo server + subprocess integration test
End-to-end MCP integration — any MCP server's tools flow through
Reasonix's Cache-First loop now, from one CLI flag.

CLI:
  reasonix chat --mcp "<command args...>"        interactive TUI
  reasonix run "<task>" --mcp "<command args...>" one-shot
  optional: --mcp-prefix <str>                   namespace tool names

The flag takes a shell-style command. shellSplit() parses it
(respecting single/double quotes, backslash escapes, tab-space
runs). Unterminated quotes throw with a clear error instead of
silently mangling argv. chat / run both spawn + bridge before
looping, tear down on exit.

App.tsx accepts an optional `tools?: ToolRegistry` prop. When
present, its specs get folded into ImmutablePrefix and dispatch
goes through it — so MCP tools are indistinguishable from native
tools to the loop.

Bundled demo server: examples/mcp-server-demo.ts
~160 lines, no dependencies beyond what's already installed.
Exposes echo / add / get_time. Two uses:
  - users can try the whole integration with no external install:
      reasonix chat --mcp "node --import tsx examples/mcp-server-demo.ts"
  - gives the integration test a real subprocess target

Integration test: tests/mcp-integration.test.ts
Spawns the demo server (`node --import tsx ...` — cross-platform,
avoids Windows `.cmd` resolution issues), walks the full handshake,
bridges tools, dispatches through the registry. Kept in a
separate file from the fake-transport unit tests so subprocess
flakiness doesn't hide unit-test regressions.

+11 tests (9 shellSplit + 2 integration). Suite: 224 passing (was
213). src/mcp/README.md updated with CLI usage + status of what's
shipped vs deferred.

Still no version bump — next is v0.3.0-alpha, once we've seen a
real LLM call go through an MCP tool end-to-end. Everything's in
place for that now; remaining is one live run.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 17:30:33 -07:00
esengineandClaude Opus 4.7 f142f8874d feat(mcp): v0.3 foundation — stdio client + ToolRegistry bridge
Minimal MCP (Model Context Protocol) client, hand-rolled, zero
runtime deps. Lets Reasonix consume tools from any MCP server while
keeping Cache-First + repair applied to the whole thing.

Why roll-our-own instead of @modelcontextprotocol/sdk:
- zero dep cost, consistent with how we wrote the DeepSeek client
- surface tuning — only initialize / tools/list / tools/call for now
- insulation from SDK breaking changes
See src/mcp/README.md for the full reasoning.

Shipped in this pass:
- src/mcp/types.ts      JSON-RPC 2.0 + MCP message types
- src/mcp/stdio.ts      McpTransport interface + NDJSON stdio impl
- src/mcp/client.ts     connect / listTools / callTool with timeouts
                        + id correlation
- src/mcp/registry.ts   bridgeMcpTools(): MCP → Reasonix ToolRegistry,
                        so MCP tools inherit Cache-First + repair
                        automatically
- src/mcp/README.md     design choices + usage example + what's next

Deferred (each is its own follow-up commit):
- CLI wiring: `reasonix chat --mcp <cmd>` — thin layer on top of
  bridgeMcpTools + ImmutablePrefix
- resources/* and prompts/* methods — Reasonix doesn't surface those
  today
- SSE transport — stdio covers common case
- Progress notifications / streaming tool results

+10 tests using an in-process FakeMcpTransport (no child processes in
unit tests — flaky). Covers initialize handshake, pre-init refusal,
tools/list, tools/call roundtrip, server errors, bridge registration,
name prefixing, and result flattening (text / image / error cases).
Suite: 213 passing (was 203).

Public surface: McpClient / StdioTransport / bridgeMcpTools /
flattenMcpResult / MCP_PROTOCOL_VERSION + all relevant types exported
from the library barrel. No version bump — foundation, not release.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 17:04:16 -07:00
esengineandClaude Opus 4.7 fb5977743c data(harvest-bench): 18-run set + honest findings — harvest doesn't
lift accuracy on math/logic; pivot Pillar 2 positioning

Second harvest eval run, 6 tasks × 3 modes × 1 repeat = 18 runs. This
time the task set included three hard tasks chosen specifically for
known V3 failure modes (base-2 Fermat pseudoprime → 341,
derangements of 7 → 1854, Euler polynomial first-fail → n=40).

  mode              pass  cache   cost        harvest signal
  baseline          6/6   39.5%   $0.00137    —
  reasoner          6/6   74.2%   $0.00417    —
  reasoner-harvest  5/6*  61.6%   $0.00330    2.8 sg / 1.3 un

  (* one 300s timeout on pseudoprime_base2)

Honest headline: **V3 passed all six.** Including the hard ones. The
checkers specifically reject the common V3 wrong-answers (561 for
pseudoprime, 265/1855 for D_7, 41/1681 for Euler) — none of those
fired. These problems are well-enough known that V3 has them in
training and R1 has no accuracy headroom to win back.

What this means for v0.3 positioning:

- We cannot ship a "harvest improves answer quality" claim off this
  data — twice now. That's not a framework bug; it's a signal that
  Pillar 2's value is NOT in the "make math more right" story.
- Plausible actual value surfaces: dev-facing introspection of R1's
  planning, or steering tool-call sequences under uncertainty. Neither
  is exercised by this harness.
- Cache-First story DOES extend to reasoner mode (74% mean cache even
  on R1 turns). That's a Pillar 1 finding reinforcing the v0.1 data,
  not a Pillar 2 finding.

findings section updated inside report.ts's renderFindings() so future
regens preserve the analysis. Committed results.json is the full
artifact for anyone who wants to reasonix replay / diff individual
runs.

Recommendation in-report: next release is better served by MCP client
(Pillar 1 leverage across the ecosystem) than by a third harvest-bench
data push. Pillar 2 needs a reframe — likely "debug visibility" or
"tool-sequence planning", not "accuracy multiplier".

Unexpected positive signal worth noting: cross-session prompt cache.
Baseline mean cache hit was 39.5% even on mode A — the same system
prompt across many runs warmed DeepSeek's server-side cache, showing
Cache-First's value isn't purely per-session.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 09:47:01 -07:00
esengineandClaude Opus 4.7 26b50e9242 feat(harvest-bench): 3 hard tasks + --timeout flag
Post-first-run adjustments informed by 7233edd's data:

- Seed tasks bottomed out at V3 chat (3/3 pass on all easy ones), so
  harvest couldn't differentiate. Add three hard tasks picked for
  known V3 failure modes:
  - pseudoprime_base2       (341; V3 commonly says 561 — Carmichael)
  - derangements_d7         (1854; V3 hits n!/e rounding errors)
  - euler_quadratic_break   (40; V3 confuses with n²−n+41 first-fail)
  Each is a single-integer answer → reuse a new checkSingleInt helper.
  Easy tasks stay for floor reference.

- `--timeout <seconds>` flag (default 300s, was 120s client default).
  Prior run hit the 120s cap on three_hats/reasoner-harvest because R1
  alone took ~100s. 300s gives headroom without encouraging runaway
  loops.

+9 tests on new checkers and the common wrong answers (e.g., checker
rejects 561 for pseudoprime_base2, rejects 265/1855 for D_7, rejects
41/1681 for euler_quadratic). Suite: 203 passing.

CI --dry step still covers the runner. No API calls in this commit —
next run uses the expanded task set.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 09:16:18 -07:00
esengineandClaude Opus 4.7 7233eddced data(harvest-bench): first 9-run live data + honest findings
First real data from the v0.3 harvest eval harness (3 tasks × 3 modes,
1 repeat). Findings are not the marketing-friendly "harvest +N% quality"
we wanted — but they're honest, and they sharpen what v0.3 actually
needs.

Headline numbers (per-run means):

  mode              pass  cache   cost        harvest signal
  baseline          3/3   0.0%    $0.00142    —
  reasoner          3/3   79.0%   $0.00355    —
  reasoner-harvest  2/3*  59.7%   $0.00184    3.3 sg / 1.3 un

  (* one timeout, see known issues)

Three honest findings, committed to report.md:

1. V3 chat already solves all three seed tasks. The task set bottoms
   out — baseline's 3/3 pass rate means there's no headroom for R1,
   let alone R1+harvest, to win on quality.
2. Reasoner costs ~2.5× chat on these problems with identical verdicts.
   On this task set, there is no quality argument for R1. (The
   cache-hit story DOES extend — reasoner mode still gets 79% mean
   cache through the Cache-First loop, so Pillar 1 generalizes.)
3. Harvest produces real signal (3-5 subgoals, 1-2 uncertainties per
   run) AND real latency — one run hit the 120s client timeout because
   the harvest V3 call pushed past R1's own ~100s budget.

What this changes for v0.3:

- We cannot ship a "harvest pays for itself" claim off this data.
- The harness is fine; the task set is the bottleneck.
- Next iteration needs problems where V3 demonstrably fails, so R1
  gains real headroom and harvest's uncertainty signal has something
  to correlate with.

report.ts gains a renderFindings() helper so future runs can preserve
the hand-written interpretation alongside the auto-generated tables.

No release tag — this is data collection, not a version bump.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 09:09:34 -07:00
esengineandClaude Opus 4.7 3a92ba2787 feat(bench): harvest eval harness — Pillar 2 scaffold
New benchmarks/harvest/ directory alongside tau-bench/. Measures
Pillar 2 (R1 Thought Harvesting) the same way tau-bench-lite measures
Pillar 1 — isolate one variable, produce reproducible numbers.

Three modes per task, each isolates one variable:
- baseline          deepseek-chat, no Reasonix tricks — V3 floor
- reasoner          deepseek-reasoner, no harvest — raw R1 gain
- reasoner-harvest  deepseek-reasoner + harvest — incremental cost /
                    quality from the extra V3 harvest call

Seed tasks (v0.3):
- mod7_list           number theory, 29-element set — expansive plan state
- flips_until_3heads  probability, single integer — derive vs recall
- three_hats          logic puzzle, one-word answer — deduction chain

All checkers are deterministic (regex + set/value compare). No LLM
judge. Failing checker in CI catches reality drift without needing an
API key — sanity verdict is exercised on every dry-run.

Runner supports --task, --mode, --repeats, --transcripts-dir, --dry.
Transcripts reuse the same TranscriptRecord format as tau-bench, so
reasonix replay / reasonix diff work unchanged.

CI now runs the harvest harness's --dry in addition to tau-bench's,
so bench regressions get caught before a real run.

+16 tests covering checker verdicts for all three tasks, empty-input
robustness, determinism, and task-set invariants. Suite: 194 passing.

No API calls yet — next step is a live run to produce the first
harvest-bench/report.md. Expected cost for 3 tasks × 3 modes × 1
repeat: ~$0.10-0.30 (dominated by the reasoner calls).

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 08:53:01 -07:00
esengineandClaude Opus 4.7 6307b92af2 feat(cli): reasonix sessions — list + inspect saved chats
Promotes the existing /sessions slash command into a top-level CLI
command so users can audit their stored sessions without launching
the TUI. Two modes:

  reasonix sessions                list every session under
                                   ~/.reasonix/sessions/
  reasonix sessions <name>         dump messages from one session
  reasonix sessions <name> -v      include system prompts + tool-call
                                   args

Reuses listSessions / loadSessionMessages / sessionPath from
src/session.ts — no new library surface. Zero API calls; filesystem
reads only.

Use case: quickly checking "what have I been asking the assistant?"
without running chat, or piping one session's content into a tool
chain for batch analysis.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 08:39:14 -07:00
esengineandClaude Opus 4.7 2e42ae53aa feat(diff): show harvest-signal deltas in summary + markdown
When at least one side of a transcript diff has plan state (Pillar 2
harvest output), the summary now includes three extra rows: harvest
turns, subgoals, and uncertainties. Lets a harvest-on run be compared
head-to-head with its harvest-off twin — which is exactly the
comparison v0.3's eval harness will need to produce.

Rows only appear when at least one side carries planState. No-harvest
diffs render identically to v0.2.2 — zero visual noise, zero surprise
for existing callers.

+2 tests confirming the row appears when harvest is present AND
omits entirely when both sides are clean. Suite: 178 passing.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 08:36:38 -07:00
esengineandClaude Opus 4.7 5ff0ef4535 chore(ci+examples): bench dry-run in CI + programmatic replay/diff example
Two small adds that make the existing v0.2 infrastructure easier to
pick up:

1. CI now runs `npx tsx benchmarks/tau-bench/runner.ts --dry` on every
   push and PR. Catches bench harness regressions (task factories, CLI
   parsing, file IO, per-sub-call transcript emission) without needing
   a DEEPSEEK_API_KEY in CI.

2. examples/replay-and-diff.ts demonstrates the library surface
   programmatically — readTranscript, computeReplayStats,
   diffTranscripts, renderDiffSummary, plus direct report.pairs
   inspection. Runs with no API key against the committed reference
   transcripts; verifies the v0.1 numbers (94% cache, −20% cost, 1
   byte-stable prefix) fall out of the JSONL alone.

Useful for anyone wiring a CI gate or eval dashboard on top of Reasonix
— which is the main use case that justifies shipping transcripts in
the package in the first place.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 08:32:51 -07:00
esengineandClaude Opus 4.7 ce963be2e2 fix(ui): plan state colors — semantic + readable on dark terminals
The old PlanStateBlock rendered all four fields in the same magenta
text. On terminals with dark themes (which is most of them), magenta
is notoriously low-contrast — users reported not being able to read
harvest output.

Fix:
- label gets a semantic color (bold): subgoals cyan, hypotheses green,
  uncertainties yellow, rejected red-dim.
- the item list itself renders in default foreground — always
  readable on any background.
- count indicator "(N)" is dimColor so it doesn't compete with content.

Before:  all four lines identical magenta (hard to tell fields apart,
         hard to read on dark).
After:   label color communicates meaning (rejected feels negative,
         uncertainties feel like "watch out"), content stays crisp.

Used by the live chat TUI AND replay/diff TUIs, so the fix lands
everywhere harvest output shows up.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 08:28:17 -07:00
esengineandClaude Opus 4.7 e5357f0df5 feat(cli): reasonix run gains --harvest / --branch / --transcript
Parity with `reasonix chat`: lets a one-shot non-interactive call
produce a transcript with harvest signal, for quick API-backed
verification of a harvest session without firing up the Ink TUI.

Usage:
  reasonix run "your question" \
    --model deepseek-reasoner --harvest \
    --transcript /tmp/h.jsonl

Afterward:
  reasonix replay /tmp/h.jsonl     # see the planState inline

The transcript path is self-closing — the command streams output as
usual, then prints a hint pointing at replay. No other behavior change;
`reasonix run` without the new flags behaves exactly as before.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 08:15:40 -07:00
esengineandClaude Opus 4.7 c148b342fc feat(harvest): thread planState through transcripts + replay UIs
Prep work for v0.3's harvest eval harness. The Pillar 2 plan state
already exists in the live chat UI; this commit makes it persist and
display in every replay/diff surface, so future harvest data can be
audited the same way cache hit is today.

- TranscriptRecord gains optional planState (TypedPlanState).
- recordFromLoopEvent copies it from LoopEvent.planState on
  assistant_final events. Empty plan state is omitted entirely — absent
  means "no signal", indistinguishable from harvest-off, saves bytes.
- PlanStateBlock extracted from EventLog to a shared component so the
  live chat TUI, replay TUI, and (transitively) diff TUI all render
  harvest output identically.
- RecordView shows the plan state under the assistant text when present.
- replay stdout --print mode prints the same four lines (subgoals /
  hypotheses / uncertainties / rejected) under each agent turn that
  carried plan state.
- ReplayStats gains harvestedTurns, totalSubgoals, totalUncertainties.
  Surfaced in the replay summary so you can see at-a-glance whether
  harvest produced signal across the session.
- Zero cost when harvest is off — the whole path is gated on the
  presence of planState in the record.

+4 tests (round-trip, empty-state omission, aggregate counting,
no-harvest zero case). Suite: **176 passing**.

No CHANGELOG bump — this is prep, not a release.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
2026-04-21 08:11:01 -07:00
199 changed files with 45094 additions and 754 deletions

No files matched your search

+10
View File
@@ -37,3 +37,13 @@ jobs:
- name: Build (tsup)
run: npm run build
# Smoke-test the bench harnesses themselves. --dry skips all LLM
# calls, so this catches wiring regressions (task factories, CLI
# parsing, file IO, checker determinism) without needing a
# DEEPSEEK_API_KEY in CI.
- name: τ-bench harness dry-run
run: npx tsx benchmarks/tau-bench/runner.ts --dry --out /tmp/tau-dry.json
- name: Harvest-bench harness dry-run
run: npx tsx benchmarks/harvest/runner.ts --dry --out /tmp/harvest-dry.json
+2
View File
@@ -22,3 +22,5 @@ sessions/
!benchmarks/tau-bench/transcripts/
!benchmarks/tau-bench/transcripts/*.jsonl
.turbo/
# Local-only Claude Code settings — personal overrides, never committed.
.claude/settings.local.json
+2411
View File
File diff suppressed because it is too large. Load diff
+674 -129
View File
@@ -1,3 +1,11 @@
<p align="center">
<img src="docs/logo.svg" alt="Reasonix — DeepSeek-native agent framework" width="640"/>
</p>
<p align="center">
<em>Cache-first agent loop for DeepSeek V4 (flash + pro) — Ink TUI, MCP first-class, no LangChain.</em>
</p>
# Reasonix
[![npm version](https://img.shields.io/npm/v/reasonix.svg)](https://www.npmjs.com/package/reasonix)
@@ -6,147 +14,630 @@
[![downloads](https://img.shields.io/npm/dm/reasonix.svg)](https://www.npmjs.com/package/reasonix)
[![node](https://img.shields.io/node/v/reasonix.svg)](./package.json)
**The DeepSeek-native agent framework.** TypeScript. Ink TUI. No LangChain.
Reasonix is not another generic agent wrapper. Every abstraction is justified
by a DeepSeek-specific property — dirt-cheap tokens, R1 reasoning traces,
automatic prefix caching, JSON mode. Generic frameworks treat DeepSeek as
"OpenAI with a different base URL" and leave these advantages on the table.
Reasonix leans into them.
```bash
npx reasonix chat # first run prompts for your DeepSeek key
# inside the TUI, type /help for everything else
```
No flag soup. All feature toggles live behind slash commands in the TUI.
**A DeepSeek-native AI coding agent in your terminal.** Edits files as
reviewable SEARCH/REPLACE blocks. Ink TUI. MCP first-class. No
LangChain.
---
## What you get
## Quick start (60 seconds)
| Feature | How it works | Opt in |
|---|---|---|
| **Cache-First Loop** | Immutable prefix + append-only log = prefix byte-stable across turns → DeepSeek's automatic prefix cache hits at 70–95% | always on |
| **R1 Thought Harvesting** | Parses `reasoning_content` into typed `{ subgoals, hypotheses, uncertainties, rejectedPaths }` via a cheap V3 call | `--harvest` |
| **Self-Consistency Branching** | Runs N parallel samples at spread temperatures; picks the one with the fewest flagged uncertainties | `--branch <N>` |
| **Tool-Call Repair** | Auto-flattens deep/wide schemas, scavenges tool calls leaked into `<think>`, repairs truncated JSON, breaks call-storms | always on |
| **Retry layer** | Exponential backoff + jitter on 408/429/500/502/503/504 and network errors. 4xx auth errors don't retry | always on |
| **Ink TUI** | Live cache-hit / cost panel. Streams R1 thinking to a compact preview. Renders Markdown (bold / lists / code / stripped LaTeX) | always on |
**1. Get a DeepSeek API key.** Free credit on signup:
<https://platform.deepseek.com/api_keys>
**2. Point it at a project.** No install needed.
```bash
cd my-project
npx reasonix code
```
First run walks you through a 30-second wizard (paste API key → pick
preset → multi-select MCP servers). Every run after that drops you
straight in.
**3. Ask it to edit.** The model proposes edits as SEARCH/REPLACE
blocks — nothing hits disk until you `/apply`.
```
reasonix code › users.ts 里 findByEmail 对大小写敏感导致登录失败,帮我改
assistant
▸ tool<search_files> → src/users.ts, src/users.test.ts
▸ tool<read_file> → (src/users.ts, 412 chars)
▸ 找到了。findByEmail 直接用 === 比对。改成小写规范化并补一条测试。
src/users.ts
<<<<<<< SEARCH
return users.find(u => u.email === email);
=======
const needle = email.toLowerCase();
return users.find(u => u.email.toLowerCase() === needle);
>>>>>>> REPLACE
▸ 1 pending edit across 1 file — /apply to write · /discard to drop
reasonix code › /apply
▸ ✓ applied src/users.ts
```
Requires Node ≥ 20.10. macOS, Linux, Windows (PowerShell / Git Bash /
Windows Terminal). Press `Esc` anytime to abort; `/help` for the full
command list.
---
## Why not just use LangChain?
## `reasonix code` — pair programmer in your terminal
Even on the default `fast` preset (no harvest, no branching), Reasonix bakes
in five DeepSeek-specific defences that generic agent frameworks leave to you:
Scoped to the directory you launch from. The model has native
`read_file` / `write_file` / `edit_file` / `list_directory` /
`search_files` / `directory_tree` / `get_file_info` /
`create_directory` / `move_file` tools, all sandboxed — any path that
resolves outside the launch root (including `..` and symlink escapes)
is refused. Plus `run_command` with a read-only allowlist; anything
state-mutating (`npm install`, `git commit`, …) is gated behind a
confirmation picker.
| | Reasonix default | generic frameworks |
|---|---|---|
| Prefix-stable loop (→ 85–95% cache hit) | ✅ | ❌ prompts rebuilt each turn |
| Auto-flatten deep tool schemas | ✅ | ❌ DeepSeek drops args |
| Retry with jittered backoff (429/503) | ✅ | ❌ custom callbacks |
| Scavenge tool calls leaked into `<think>` | ✅ | ❌ |
| Call-storm breaker on identical-arg repeats | ✅ | ❌ |
| Live cache-hit / cost / vs-Claude panel | ✅ | ❌ |
| First-run config prompt + Markdown TUI | ✅ | ❌ |
### Walkthrough: explore before editing
Harvest and self-consistency branching are bonuses on top. The everyday
win is that **a plain chat with Reasonix already pays for ~40% less tokens
than the same chat through a naive LangChain setup**, because the prefix
actually stays byte-stable.
For "what does this code do?" questions the model uses the read-side
tools and replies in prose — no SEARCH/REPLACE blocks, no file
writes. Ask to change something only when you mean it:
## Validated numbers
**τ-bench-lite** — 8 multi-turn tool-use tasks × 3 repeats = 48 runs per
side. Same tools / same prompt / same client on both sides, sole variable
is prefix stability. Measured on live DeepSeek `deepseek-chat`:
| metric | baseline (cache-hostile) | Reasonix | delta |
|---|---:|---:|---:|
| runs | 24 | 24 | — |
| **cache hit** | 46.6% | **94.4%** | **+47.7pp** |
| cost / task | $0.002599 | $0.001579 | **−39% (×0.61)** |
| vs Claude Sonnet 4.6 (token-count estimate) | — | — | **~96% cheaper** |
| pass rate | 96% (23/24) | **100% (24/24)** | Reasonix held the guardrail on every run |
**Verify it yourself — no API key, zero cost:**
```bash
git clone https://github.com/esengine/reasonix.git && cd reasonix && npm install
npx reasonix replay benchmarks/tau-bench/transcripts/t01_address_happy.reasonix.r1.jsonl
npx reasonix diff \
benchmarks/tau-bench/transcripts/t01_address_happy.baseline.r1.jsonl \
benchmarks/tau-bench/transcripts/t01_address_happy.reasonix.r1.jsonl
```
reasonix code › 这个项目的路由是怎么组织的?
assistant
▸ tool<directory_tree> → (src/ tree, 47 entries)
▸ tool<read_file> → (src/router.ts, 1.2 KB)
▸ 路由分三层:顶层 AppRouter 注册 tab,每个 tab 用 React Router 的
nested routes 写子路径,最后 …
```
The JSONL transcripts committed in `benchmarks/tau-bench/transcripts/`
carry per-turn `usage`, `cost`, and `prefixHash`. Reasonix's prefix hash
stays byte-stable across every model call; baseline's prefix churns on
every turn. The cache delta is *mechanically* attributable to log
stability, not to a different system prompt.
If an `edit_file` SEARCH block doesn't match the file byte-for-byte,
the edit is refused loudly rather than fuzzy-matched. The model sees
the error and retries — silent wrong edits are worse than visible
rejections.
Full 48-run report: [`benchmarks/tau-bench/report.md`][r]. Reproduce
with your own API key: `npx tsx benchmarks/tau-bench/runner.ts --repeats 3`.
### Plan mode — review before executing
[r]: ./benchmarks/tau-bench/report.md
For anything bigger than a typo, the model is encouraged to propose a
markdown plan first. You'll see a picker with **Approve / Refine /
Cancel**:
```
reasonix code › 把 auth 从 JWT 迁移到 session cookies
▸ plan submitted — awaiting your review
────────────────────────────────────────
## Summary
Swap JWT middleware for session cookies, keep user table intact.
## Files
- src/auth/middleware.ts — replace `verifyJwt` with `readSession`
- src/auth/session.ts — new file, in-memory store + signed cookie
- src/routes/login.ts — return Set-Cookie instead of a token
- tests/auth/*.test.ts — update fixtures
## Risks
- Existing logged-in users get logged out (no migration).
- Session store is in-memory; restart clears sessions.
────────────────────────────────────────
▸ Approve and implement
Refine — explore more
Cancel
```
**Force it** with `/plan` — enters an explicit read-only phase where
the model *must* submit a plan before any edit or non-allowlisted
shell call will execute. Use for high-stakes changes you want to
audit before the model touches disk. `/plan off` or picker
Approve/Cancel exits.
### Prompt prefixes — `!cmd` and `@path`
Two inline shortcuts that don't need a slash:
**`!<cmd>` — run a shell command in the sandbox and feed it to the
model.** Typed at the prompt, like bash. Output lands in the visible
log AND in the session so the model's next turn reasons about it:
```
reasonix code › !git status --short
▸ M src/users.ts
▸ M src/users.test.ts
reasonix code › 把这两个文件的改动说明一下
assistant
▸ tool<read_file> → src/users.ts, src/users.test.ts
▸ …
```
No allowlist gate — user-typed shell = explicit consent. 60s timeout,
32k char cap, survives session resume since 0.5.14.
**`@path/to/file` — inline a file under "Referenced files."** Start
typing `@` and a picker appears (↑/↓ navigate, Tab/Enter to insert).
Good for "what does @src/users.ts do?" without making the model
`read_file` it first. Sandboxed: relative paths only, no `..` escape,
64KB per-file cap. Recent files rank higher.
### `/commit` — stage + commit in one step
```
reasonix code › /commit "fix: findByEmail case-insensitive"
▸ git add -A && git commit -m "fix: findByEmail case-insensitive"
[main a1b2c3d] fix: findByEmail case-insensitive
```
### Things to try
- `/tool 1` — dump the last tool call's full output (when the 400-char
inline clip isn't enough).
- `/think` — see the model's full reasoning for the last turn
(thinking-mode models: v4-flash / v4-pro / reasoner alias).
- `/undo` — roll back the last applied edit batch.
- `/new` — start fresh in the same directory without losing the
session file.
- `/effort high` — step down from the default `max` agent-class
reasoning_effort for cheaper/faster turns on simple tasks.
- `npx reasonix code --preset max` — v4-pro + 3-way self-consistency
branching for gnarly refactors.
- `npx reasonix code src/` — narrower sandbox (only `src/` is
writable).
- `npx reasonix code --no-session` — ephemeral; nothing saved.
### `reasonix stats` — how much did you actually save?
Every turn `reasonix chat|code|run` runs appends a compact record
(tokens + cost + what Claude Sonnet 4.6 would have charged) to
`~/.reasonix/usage.jsonl`. `reasonix stats` with no args rolls that
log into today / week / month / all-time windows:
```
Reasonix usage — /Users/you/.reasonix/usage.jsonl
turns cache hit cost (USD) vs Claude saved
----------------------------------------------------------------------
today 8 95.1% $0.004821 $0.1348 96.4%
week 34 93.8% $0.023104 $0.6081 96.2%
month 127 94.2% $0.081530 $2.1452 96.2%
all-time 342 94.0% $0.210881 $5.8934 96.4%
```
Privacy: only tokens, costs, and the session name you chose land
in the file. No prompts, no completions, no tool arguments.
`reasonix stats <transcript>` keeps the old per-file summary
(assistant turns + tool calls) for scripts that already use it.
### Staying current
The panel header shows the running version next to `Reasonix` (e.g.
`Reasonix v0.5.21 · deepseek-v4-pro · harvest · max …`, the trailing
`max` is the reasoning-effort badge — `/effort high` to step down).
A quiet 24-hour background check against
the npm registry surfaces a yellow `update: X.Y.Z` on the right side
of the same row when a newer version has been published. No blocking,
no nagging — the check runs once per day max and is silent on failure
(offline, firewall, etc.).
```bash
reasonix update # print current vs latest, run `npm i -g reasonix@latest`
reasonix update --dry-run # print the plan without running anything
```
Running via `npx`? The command detects that and prints a
cache-refresh hint instead — npx picks up the newest version on
its next invocation automatically.
### Project conventions — `REASONIX.md`
Drop a `REASONIX.md` in the project root and its contents are pinned
into the system prompt every launch. Committable team memory — house
conventions, domain glossary, things the model keeps forgetting:
```bash
cat > REASONIX.md <<'EOF'
# Notes for Reasonix
- Use snake_case for new Python modules; legacy camelCase modules keep their style.
- `cargo check` is in the auto-run allowlist; full `cargo test` needs confirmation.
- The `api/` dir mirrors `backend/` — keep schemas in sync.
EOF
```
Re-launch (or `/new`) to pick it up; the prefix is hashed once per
session to keep the DeepSeek cache warm. `/memory` prints what's
currently pinned. `REASONIX_MEMORY=off` disables every memory source
for CI / offline repro.
### User memory — `~/.reasonix/memory/`
A second, **private per-user** memory layer lives under your home
directory. Unlike `REASONIX.md` it's never committed, and the model
can write to it itself via the `remember` tool. Two scopes:
- `~/.reasonix/memory/global/` — cross-project (your preferences,
tooling).
- `~/.reasonix/memory/<project-hash>/` — scoped to one sandbox root
in `reasonix code` (decisions, local facts, per-repo shortcuts).
Each scope keeps an always-loaded `MEMORY.md` index of one-liners
plus zero or more `<name>.md` detail files (loaded on demand via
`recall_memory`). Writes land immediately; pinning into the system
prompt takes effect on next `/new` or launch so the cache prefix
stays stable for the current session.
```
reasonix code › 我用 bun 而不是 npm,请以后都用 bun 跑构建
assistant
▸ tool<remember> → project/bun_build saved
"Build command on this machine is `bun run build`"
```
**Slash**: `/memory` · `/memory list` · `/memory show <name>` ·
`/memory forget <name>` · `/memory clear <scope> confirm`.
**Model tools**: `remember(type, scope, name, description, content)` ·
`forget(scope, name)` · `recall_memory(scope, name)`.
Project scope is only available inside `reasonix code` (needs a real
sandbox root to hash); plain `reasonix` gets the global scope only.
### Skills — user-authored prompt packs
Skills are prose instruction blocks you drop on disk. Reasonix pins
their names + one-line descriptions into the system prompt; the
model can call `run_skill({name: "..."})` on its own when a match
fits, or you can type `/skill <name> [args]` to run one manually.
Two scopes, same layout as user memory:
- `<project>/.reasonix/skills/` — per-project skills (commit them to
share with your team, or add to `.gitignore` for personal drafts).
- `~/.reasonix/skills/` — global skills available everywhere.
Either layout works: `<name>/SKILL.md` (preferred — can bundle
additional assets alongside) or flat `<name>.md`.
```markdown
---
name: review
description: Review uncommitted changes and flag risks
---
Run `git diff` on staged and unstaged changes. Summarize what each
hunk does, call out potential regressions, and list files that might
need additional tests. Don't propose edits unless I ask.
```
Use it:
```
reasonix code › /skill review
▸ running skill: review
assistant
▸ tool<run_command> → git diff --cached
▸ 3 改动,1 个需要回归测试 …
```
Or let the model pick autonomously — because the skill's name +
description are pinned in the prefix, asking "帮我看下未提交的改动有没
有风险" triggers `run_skill({name: "review"})` without you typing the
slash command.
**Slash**: `/skill` (list) · `/skill show <name>` · `/skill <name>
[args]` (inject body as user turn).
**Deliberately not tied** to any other client's directory convention
(`.claude/skills`, etc.) — Reasonix is model-agnostic at the
conversation layer. Any SKILL.md you author works; the body is
prose, so skills authored for other tools usually port over unchanged
(Reasonix's tool names differ — `filesystem` / `shell` / `web` — but
the model reads the instructions and picks our equivalents).
### Hooks — automate around tool calls and turns
Drop a `settings.json` under `.reasonix/` (project or `~/`) and
Reasonix will fire shell commands at four well-known points in
the loop: before a tool runs, after a tool returns, before your
prompt reaches the model, and after the turn ends.
```json
// <project>/.reasonix/settings.json ← committable
// ~/.reasonix/settings.json ← per-user
{
"hooks": {
"PreToolUse": [{ "match": "edit_file|write_file", "command": "bun scripts/guard.ts" }],
"PostToolUse": [{ "match": "edit_file", "command": "biome format --write" }],
"UserPromptSubmit": [{ "command": "echo $(date +%s) >> ~/.reasonix/prompts.log" }],
"Stop": [{ "command": "bun test --run", "timeout": 60000 }]
}
}
```
Each hook is a shell command. Reasonix invokes it with stdin = a
JSON envelope describing the event:
```json
{ "event": "PreToolUse", "cwd": "/path/to/project",
"toolName": "edit_file", "toolArgs": { "path": "src/x.ts", "..." } }
```
Exit code drives the decision:
- **0** — pass; loop continues normally
- **2** — block (only on `PreToolUse` / `UserPromptSubmit`); the
hook's stderr becomes the synthetic tool result the model sees,
or the prompt is dropped entirely
- **anything else** — warn; loop continues, stderr renders as a
yellow row inline
`match` is anchored regex on the tool name; `*` or omitted matches
every tool. Project hooks fire before global hooks. Default
timeouts: 5s for blocking events, 30s for logging events; per-hook
`timeout` overrides.
**Slash**: `/hooks` (list active hooks) · `/hooks reload` (re-read
`settings.json` from disk without losing your session).
### Staying current from inside the TUI
`/update` inside a running session shows your current version, the
last-resolved latest version (from the quiet 24h background check),
and the shell command to run. The slash does *not* spawn
`npm install` — stdio:inherit into a running Ink renderer corrupts
the display. Exit the session and run `reasonix update` in a
fresh shell when you actually want to install.
---
## Usage
## `reasonix` — also works as general chat
### CLI
Same TUI, no filesystem tools unless you opt in via MCP. Good for
drafting, Q&A, schema design, architecture discussions, or driving
your own MCP servers. Sessions persist per name under
`~/.reasonix/sessions/`.
```bash
npx reasonix chat # auto-saves to session 'default'; resumes next time
npx reasonix chat --session work # use a different named session
npx reasonix chat --no-session # ephemeral — nothing persisted
npx reasonix run "ask anything" # one-shot, streams to stdout
npx reasonix stats session.jsonl # quick summary of a transcript
npx reasonix replay chat.jsonl # pretty-print a transcript + rebuild cost/cache offline
npx reasonix diff a.jsonl b.jsonl --md diff.md # compare two transcripts: cache/cost delta + first divergence
npx reasonix # uses saved config + wizard-selected MCP
npx reasonix --preset smart # reasoner + R1 harvest for this run
npx reasonix --session design # named session — resume later with --session design
```
Sessions live as JSONL under `~/.reasonix/sessions/<name>.jsonl` — every
turn's message log is appended atomically, so killing the CLI never loses
context. Inside the TUI: `/sessions` to list, `/forget` to delete the
current one.
### Inside the chat — slash commands
A command strip runs under the input box so you don't have to memorize
anything. Type `/help` for the full list. The biggest shortcut:
```
/preset fast deepseek-chat, no harvest, no branch (default)
/preset smart reasoner + harvest (~10x cost)
/preset max reasoner + harvest + branch 3 (~30x cost, slowest)
```
One-tap switch between fast daily driver, careful thinker, and max-quality
self-consistency. Individual knobs are available too:
```
/status show current model / harvest / branch / stream
/model <id> deepseek-chat or deepseek-reasoner
/harvest [on|off] Pillar 2 — parse R1 reasoning into typed plan state
/branch <N|off> run N parallel samples per turn, pick most confident
/clear clear displayed history (log is kept)
/exit quit
```
The top panel shows active flags live: `· harvest · branch3` appear next to
the model once enabled.
### Flags (for automation / CI)
The same knobs are also available as CLI flags if you're scripting:
Bridge your own MCP servers on the fly:
```bash
npx reasonix chat -m deepseek-reasoner --harvest --branch 3 --transcript session.jsonl
npx reasonix \
--mcp "fs=npx -y @modelcontextprotocol/server-filesystem /tmp/safe" \
--mcp "kb=https://mcp.example.com/sse"
```
### Library
MCP tools go through the same Cache-First + repair + context-safety
plumbing as native tools — 32k result cap, live progress-notification
rendering, retries.
---
## Commands inside the session
**Core**
| command | what it does |
|---|---|
| `/help` · `/?` | full command reference with hints |
| `/status` | current model · flags · context · session |
| `/new` · `/reset` | fresh conversation in the same session |
| `/clear` | clear visible scrollback only (log kept) |
| `/retry` | truncate and resend your last message (fresh sample) |
| `/exit` · `/quit` | quit |
**Model**
| command | what it does |
|---|---|
| `/preset <fast\|smart\|max>` | one-tap bundle (model + harvest + branch) |
| `/model <id>` | switch DeepSeek model (`deepseek-v4-flash`, `deepseek-v4-pro`, plus `deepseek-chat` / `deepseek-reasoner` compat aliases) |
| `/models` | list live models from DeepSeek `/models` endpoint |
| `/harvest [on\|off]` | toggle R1 plan-state extraction |
| `/branch <N\|off>` | run N parallel samples per turn, pick best (N ≥ 2) |
| `/effort <high\|max>` | reasoning_effort cap — `max` is the agent default, `high` is cheaper/faster |
| `/think` | dump the last turn's full thinking-mode reasoning |
**Context & tools**
| command | what it does |
|---|---|
| `/mcp` | list attached MCP servers and their tools / resources / prompts |
| `/resource [uri]` | browse + read MCP resources (no arg → list URIs; `<uri>` → fetch) |
| `/prompt [name]` | browse + fetch MCP prompts |
| `/tool [N]` | dump the Nth tool call's full output (1 = latest) |
| `/compact [tokens]` | shrink oversized tool results in the log (default 4000 tokens/result) |
| `/context` | break down where context tokens are going (system / tools / log) |
| `/stats` | cross-session cost dashboard (today / week / month / all-time) |
| `/keys` | keyboard shortcuts + prompt prefixes (`!` / `@` / `/`) cheatsheet |
**Memory & skills**
| command | what it does |
|---|---|
| `/memory` | show pinned memory (REASONIX.md + ~/.reasonix/memory) |
| `/memory list` · `show <name>` · `forget <name>` · `clear <scope> confirm` | manage the store |
| `/skill` · `/skill list` | list discovered skills (project + global) |
| `/skill show <name>` | dump one skill's body |
| `/skill <name> [args]` | run a skill (inject body as user turn) |
**Sessions**
| command | what it does |
|---|---|
| `/sessions` | list saved sessions (current marked with `▸`) |
| `/forget` | delete the current session from disk |
| `/setup` | reconfigure (exit and run `reasonix setup`) |
**Code mode only** (`reasonix code`)
| command | what it does |
|---|---|
| `/apply` | commit the pending SEARCH/REPLACE blocks to disk |
| `/discard` | drop the pending edit blocks without writing |
| `/undo` | roll back the last applied edit batch |
| `/commit "msg"` | `git add -A && git commit -m "msg"` |
| `/plan [on\|off]` | toggle read-only plan mode |
| `/apply-plan` | force-approve a pending plan |
**Keyboard**
- `Enter` — submit
- `Shift+Enter` / `Ctrl+J` — newline (multi-line paste also supported;
`\` + Enter as a portable fallback)
- `↑` / `↓` — walk prompt history while idle; navigate slash-autocomplete
- `Tab` / `Enter` on a `/foo` prefix — accept the highlighted suggestion
- `Esc` — abort the current turn (stops the API call, cancels any
in-flight tool, rejects pending MCP requests)
- `y` / `n` on confirm prompts — hotkey accept / reject
---
## Sessions and safety nets
- Sessions live as JSONL under `~/.reasonix/sessions/<name>.jsonl`
(per directory for `reasonix code`). Every message appended
atomically; `Ctrl+C` never loses context.
- Tool results are capped at 32k chars per call. Oversized sessions
self-heal on load (shrinks + rewrites the file).
- Malformed `assistant.tool_calls` / `tool` pairing is validated on
every outgoing API call so a corrupted session can't keep 400ing.
- Context gauge turns yellow at 50%, red at 80% with a `/compact`
nudge. Approaching the 1M-token window (V4 flash + pro) triggers an
automatic compaction attempt before falling back to a forced summary.
- The `reasonix code` sandbox refuses any path that resolves outside
the launch directory, including symlink escape and `..` traversal.
### Troubleshooting: duplicate rows / ghost rendering
Some Windows terminals (Git Bash / MINTTY / winpty-wrapped shells)
don't fully implement the ANSI cursor-up escapes Ink uses to repaint
the live spinner region. Symptom: spinners, streaming previews, or
tool-result rows print multiple copies into scrollback instead of
overwriting in place.
If you hit this, run with plain mode:
```bash
REASONIX_UI=plain npx reasonix code
```
Plain mode suppresses live/animated rows and disables the internal
tick timer. You lose the streaming preview and spinners but gain
stable scrollback. Windows Terminal, PowerShell 7 in Windows
Terminal, and WezTerm don't need this opt-out.
---
## Web search — on by default
The model has two web tools the moment you launch: `web_search` and
`web_fetch`. No flag, no API key, no signup. When you ask about
something the model wasn't trained on (new releases, current events,
obscure APIs), it decides to call `web_search` on its own; if a
snippet isn't enough it follows up with `web_fetch`.
Backed by **Mojeek**'s public search page — an independent web
index, bot-friendly, no cookies/sessions. Coverage on niche or very
recent queries can be thinner than Google/Bing, but it's reliable
from scripts. (DDG was the original backend but started serving
anti-bot pages in 2026.)
**Turn it off** (offline mode / privacy / CI):
```json
// ~/.reasonix/config.json
{ "apiKey": "sk-…", "search": false }
```
```bash
REASONIX_SEARCH=off npx reasonix code
```
**Bring your own** (Kagi, SearXNG, internal caches): implement the
`WebSearchProvider` interface and call
`registerWebTools(registry, { provider })` yourself, or bridge an
existing MCP search server via `--mcp`.
---
## MCP — bring your own tools
Any [MCP](https://spec.modelcontextprotocol.io/) server works. The
wizard lets you pick from a catalog, or drive it by flag:
```bash
# stdio (local subprocess)
npx reasonix --mcp "fs=npx -y @modelcontextprotocol/server-filesystem /tmp/safe"
# multiple at once
npx reasonix \
--mcp "fs=npx -y @modelcontextprotocol/server-filesystem /tmp/safe" \
--mcp "demo=npx tsx examples/mcp-server-demo.ts"
# HTTP+SSE (remote / hosted)
npx reasonix --mcp "kb=https://mcp.example.com/sse"
```
`reasonix mcp list` shows the curated catalog. `reasonix mcp inspect
<spec>` connects once and dumps the server's tools / resources /
prompts without starting a chat. Progress notifications from
long-running tools (2025-03-26 spec) render live as a progress bar
in the spinner.
Supported transports: **stdio** (local command) and **HTTP+SSE**
(remote, MCP 2024-11-05 spec).
---
## CLI reference
```bash
npx reasonix code [path] # coding mode scoped to path (default: cwd)
npx reasonix # chat (uses saved config)
npx reasonix setup # reconfigure the wizard
npx reasonix chat --session work # named session
npx reasonix chat --no-session # ephemeral
npx reasonix run "ask anything" # one-shot, streams to stdout
npx reasonix stats session.jsonl # summarize a transcript
npx reasonix replay chat.jsonl # rebuild cost/cache from a transcript
npx reasonix diff a.jsonl b.jsonl --md # compare two transcripts
npx reasonix mcp list # curated MCP catalog
npx reasonix mcp inspect <spec> # probe a single MCP server
npx reasonix sessions # list saved sessions
```
Common flags:
```bash
--preset <fast|smart|max> # bundle (model + harvest + branch)
--model <id> # explicit model id
--harvest / --no-harvest # R1 plan-state extraction
--branch <N> # self-consistency budget
--mcp "name=cmd args…" # attach an MCP server (repeatable)
--transcript path.jsonl # write a JSONL transcript on the side
--session <name> # named session (default: per-dir for code mode)
--no-session # ephemeral
--no-config # ignore ~/.reasonix/config.json (CI-friendly)
```
Env vars (win over config):
```bash
export DEEPSEEK_API_KEY=sk-...
export DEEPSEEK_BASE_URL=https://... # optional alternate endpoint
export REASONIX_MEMORY=off # disable REASONIX.md + user memory
export REASONIX_SEARCH=off # disable web_search / web_fetch
export REASONIX_UI=plain # disable live rows (ghosting workaround)
```
---
## Library usage
```ts
import {
@@ -178,7 +669,7 @@ const loop = new CacheFirstLoop({
toolSpecs: tools.specs(),
}),
harvest: true,
branch: 3, // self-consistency budget
branch: 3,
});
for await (const ev of loop.step("What is 17 + 25?")) {
@@ -187,26 +678,82 @@ for await (const ev of loop.step("What is 17 + 25?")) {
console.log(loop.stats.summary());
```
### Configuration
`ChatOptions.seedTools` accepts a pre-built `ToolRegistry` for
callers who want the `reasonix code` loop wiring without the CLI
wrapper. See [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) for
internals.
On first run the CLI prompts for your DeepSeek API key and saves it to
`~/.reasonix/config.json`. Alternatives:
---
## Benchmarks — verify the cache-hit claim yourself
Every abstraction here earns its weight against a DeepSeek-specific
property — dirt-cheap tokens, R1 reasoning traces, automatic prefix
caching, JSON mode. Generic wrappers leave these on the table.
| | Reasonix default | generic frameworks |
|---|---|---|
| Prefix-stable loop (→ 85–95% cache hit) | yes | no (prompts rebuilt each turn) |
| Auto-flatten deep tool schemas | yes | no (DeepSeek drops args) |
| Retry with jittered backoff (429/503) | yes | no (custom callbacks) |
| Scavenge tool calls leaked into `<think>` | yes | no |
| Call-storm breaker on identical-arg repeats | yes | no |
| Live cache-hit / cost / vs-Claude panel | yes | no |
On the same τ-bench-lite workload — 8 multi-turn tool-use tasks × 3
repeats = 48 runs per side, live DeepSeek `deepseek-chat`, sole
variable prefix stability:
| metric | baseline (cache-hostile) | Reasonix | delta |
|---|---:|---:|---:|
| cache hit | 46.6% | **94.4%** | +47.7 pp |
| cost / task | $0.002599 | $0.001579 | **−39%** |
| pass rate | 96% (23/24) | **100% (24/24)** | — |
**Reproduce without spending an API credit:**
```bash
export DEEPSEEK_API_KEY=sk-... # env var (wins over config file)
export DEEPSEEK_BASE_URL=https://... # optional alternate endpoint
git clone https://github.com/esengine/reasonix.git && cd reasonix && npm install
npx reasonix replay benchmarks/tau-bench/transcripts/t01_address_happy.reasonix.r1.jsonl
npx reasonix diff \
benchmarks/tau-bench/transcripts/t01_address_happy.baseline.r1.jsonl \
benchmarks/tau-bench/transcripts/t01_address_happy.reasonix.r1.jsonl
```
Get a key (free credit on signup): <https://platform.deepseek.com/api_keys>
The committed JSONL transcripts carry per-turn `usage`, `cost`, and
`prefixHash`. Reasonix's prefix hash stays byte-stable across every
model call; baseline's churns on every turn. The cache delta is
*mechanically* attributable to log stability, not to a different
system prompt.
Full 48-run report:
[`benchmarks/tau-bench/report.md`](./benchmarks/tau-bench/report.md).
Reproduce with your own API key: `npx tsx
benchmarks/tau-bench/runner.ts --repeats 3`.
MCP reference runs (one single prefix hash across all 5 turns even
with two concurrent MCP subprocesses):
| server | turns | cache hit | cost | vs Claude |
|---|---:|---:|---:|---:|
| bundled demo (`add` / `echo` / `get_time`) | 2 | **96.6%** (turn 2) | $0.000254 | −94.0% |
| official `server-filesystem` | 5 | **96.7%** | $0.001235 | −97.0% |
| **both concurrently** | 5 | **81.1%** | $0.001852 | −95.9% |
---
## Non-goals
- Multi-agent orchestration (use LangGraph).
- RAG / vector stores (use LlamaIndex or do it yourself).
- Multi-provider abstraction (use LiteLLM).
- Web UI / SaaS.
- **Multi-agent orchestration / sub-agents** (use LangGraph).
- **Workflow DSL / DAG scheduler / parallel-branch engine** — skills
are prose; the model sequences via the normal tool-use loop.
Keeps single-loop + append-only + cache-first invariants intact.
- **Multi-provider abstraction** (use LiteLLM). Reasonix is
DeepSeek-only on purpose — every pillar (cache-first loop, R1
harvesting, tool-call repair) is tuned against DeepSeek-specific
behavior and economics. Coupling to one backend is the feature.
- **RAG / vector stores** (use LlamaIndex).
- **Web UI / SaaS.**
Reasonix does DeepSeek, deeply.
@@ -218,15 +765,13 @@ Reasonix does DeepSeek, deeply.
git clone https://github.com/esengine/reasonix.git
cd reasonix
npm install
npm run dev chat # run CLI from source via tsx
npm run dev code # run CLI from source via tsx
npm run build # tsup to dist/
npm test # vitest (89 tests)
npm test # vitest (1007 tests)
npm run lint # biome
npm run typecheck # tsc --noEmit
```
See [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) for internals.
---
## License
+106
View File
@@ -0,0 +1,106 @@
# Harvest eval harness (Pillar 2)
Measures Pillar 2 (R1 Thought Harvesting) the same way `tau-bench/`
measures Pillar 1 (Cache-First Loop): isolate one variable, produce
numbers anyone can reproduce.
## What's different from τ-bench-lite?
Deliberately different task shape:
| | τ-bench-lite | harvest-bench |
|---|---|---|
| task style | multi-turn tool-use | single-turn reasoning |
| user simulator | yes (LLM) | no |
| DB state | yes | no |
| checker | DB-predicate | regex + set/value compare |
| target | Pillar 1 | Pillar 2 |
| model | deepseek-chat (default) | deepseek-reasoner (only R1 has `reasoning_content` for harvest to work on) |
The two harnesses answer different questions:
- **τ-bench-lite**: *"Does Cache-First actually cut cost on real tool-use
workflows?"* (yes — 47.7pp cache, −39% cost on 48-run data.)
- **harvest-bench**: *"Does the extra V3 harvest call add measurable
value above plain R1?"* (TBD — run it to find out.)
## Modes
Three modes isolate one variable each:
| mode | model | harvest | what it measures |
|---|---|---|---|
| `baseline` | deepseek-chat | off | floor reference — V3 at its best |
| `reasoner` | deepseek-reasoner | off | raw R1 gain over V3 on reasoning |
| `reasoner-harvest` | deepseek-reasoner | on | R1 + the extra V3 harvest call |
Deltas:
- `baseline → reasoner` answers "is R1 worth the price on these
problems?"
- `reasoner → reasoner-harvest` answers "is the harvest call worth
its incremental cost?"
## Quickstart
```bash
# Dry-run — no API, smoke-test the wiring
npx tsx benchmarks/harvest/runner.ts --dry
# Full run (live DeepSeek, costs ~$0.20-0.60 for 6 tasks × 3 modes × 1 repeat)
export DEEPSEEK_API_KEY=sk-...
npx tsx benchmarks/harvest/runner.ts
# Tighter run with 3 repeats (~$0.60-2.00)
npx tsx benchmarks/harvest/runner.ts --repeats 3
# Only the hard tasks (skip the easy floor)
npx tsx benchmarks/harvest/runner.ts --task pseudoprime_base2
npx tsx benchmarks/harvest/runner.ts --task derangements_d7
npx tsx benchmarks/harvest/runner.ts --task euler_quadratic_break
# Bump per-call timeout (reasoner + harvest occasionally blow past the 120s default)
npx tsx benchmarks/harvest/runner.ts --timeout 600
# Per-run transcripts so you can reasonix replay / diff them
npx tsx benchmarks/harvest/runner.ts --repeats 3 --transcripts-dir transcripts/
# Render report
npx tsx benchmarks/harvest/report.ts benchmarks/harvest/results-*.json
```
## Tasks (v0.3 seed)
Split into two bands:
**Easy band** — V3 chat solves these, so baseline has a real pass rate and the bench has a reference floor.
| id | shape | why |
|---|---|---|
| `mod7_list` | number theory, 29-element list | R1 often tries enumeration first, then reaches for modular arithmetic — clean rejectedPaths signal |
| `flips_until_3heads` | probability, single integer | classic recurrence; R1 either derives or recalls, harvest should see hypotheses diverge |
| `three_hats` | logic puzzle, one-word answer | pure deduction chain, tests harvest's ability to extract the nested reasoning |
**Hard band** — picked specifically for known V3 failure modes. If R1 systematically beats V3 on these, and harvest further beats R1-only, we have our Pillar 2 story.
| id | shape | why V3 tends to fail |
|---|---|---|
| `pseudoprime_base2` | smallest Fermat pseudoprime to base 2 = **341** | V3 often answers 561 (Carmichael) or some other composite it remembers — R1 actually checks 2^n mod n |
| `derangements_d7` | D_7 = **1854** | V3 approximates via n!/e and rounds wrong, or recalls D_6/D_8; R1 uses the recurrence D_n=(n−1)(D_{n−1}+D_{n−2}) |
| `euler_quadratic_break` | smallest n where n²+n+41 is composite = **40** | V3 frequently confuses with n²−n+41 (first fails at 41); R1 checks small n systematically |
Adding a new task: see `tasks.ts`. Any checker that's deterministic is
fair game — extract numeric/list/text with regex, compare with set
equality or string matching.
## Non-goals
- **No LLM-as-judge.** Brittle and expensive; defeats the point of a
reproducible bench. If a checker is too hard to write deterministically,
the task doesn't belong here.
- **No tool-use tasks.** Those live in `tau-bench/`. Different story.
- **No multi-turn.** v0.3 harness is single-turn Q/A. Multi-turn reasoning
eval is separate scope.
- **No benchmark-data cherry-picking.** When results come in, we publish
them whether they validate Pillar 2 or not. "harvest didn't help on
these 3 tasks" is still useful information.
+82
View File
@@ -0,0 +1,82 @@
# Reasonix harvest eval (Pillar 2)
**Date:** 2026-04-21T16:44:21.011Z
**Tasks:** 6 · repeats × 1 · modes: baseline, reasoner, reasoner-harvest
**Reasonix version:** 0.2.2
## Summary by mode
| mode | runs | pass rate | cache hit | cost / run | harvest turns | subgoals | uncertainties |
|---|---:|---:|---:|---:|---:|---:|---:|
| baseline | 6 | 100% | 39.5% | $0.001371 | 0.0 | 0.0 | 0.0 |
| reasoner | 6 | 100% | 74.2% | $0.004170 | 0.0 | 0.0 | 0.0 |
| reasoner-harvest | 6 | 83% | 61.6% | $0.003304 | 0.8 | 2.8 | 1.3 |
## Deltas
- **baseline → reasoner**
- pass rate: 0pp
- cost: ×3.04 (each run costs more)
- harvest signal / run: 0.0 subgoals, 0.0 uncertainties
- **baseline → reasoner-harvest**
- pass rate: -17pp
- cost: ×2.41 (each run costs more)
- harvest signal / run: 2.8 subgoals, 1.3 uncertainties
## Per-task breakdown
| task | mode | rep | verdict | cache | cost | sg | un | note |
|---|---|---:|:---:|---:|---:|---:|---:|---|
| mod7_list | baseline | 1 | ✅ | 86.5% | $0.001361 | 0 | 0 | |
| mod7_list | reasoner | 1 | ✅ | 86.5% | $0.004797 | 0 | 0 | |
| mod7_list | reasoner-harvest | 1 | ✅ | 86.5% | $0.003045 | 4 | 2 | |
| flips_until_3heads | baseline | 1 | ✅ | 92.8% | $0.001198 | 0 | 0 | |
| flips_until_3heads | reasoner | 1 | ✅ | 92.8% | $0.002830 | 0 | 0 | |
| flips_until_3heads | reasoner-harvest | 1 | ✅ | 92.8% | $0.001691 | 4 | 0 | |
| three_hats | baseline | 1 | ✅ | 57.7% | $0.001514 | 0 | 0 | |
| three_hats | reasoner | 1 | ✅ | 57.7% | $0.009340 | 0 | 0 | |
| three_hats | reasoner-harvest | 1 | ✅ | 57.7% | $0.009651 | 3 | 2 | |
| pseudoprime_base2 | baseline | 1 | ✅ | 0.0% | $0.001894 | 0 | 0 | |
| pseudoprime_base2 | reasoner | 1 | ✅ | 75.3% | $0.003128 | 0 | 0 | |
| pseudoprime_base2 | reasoner-harvest | 1 | ❌ | 0.0% | $0.000000 | 0 | 0 | This operation was aborted |
| derangements_d7 | baseline | 1 | ✅ | 0.0% | $0.001273 | 0 | 0 | |
| derangements_d7 | reasoner | 1 | ✅ | 71.9% | $0.003492 | 0 | 0 | |
| derangements_d7 | reasoner-harvest | 1 | ✅ | 71.9% | $0.002843 | 3 | 2 | |
| euler_quadratic_break | baseline | 1 | ✅ | 0.0% | $0.000985 | 0 | 0 | |
| euler_quadratic_break | reasoner | 1 | ✅ | 61.0% | $0.001431 | 0 | 0 | |
| euler_quadratic_break | reasoner-harvest | 1 | ✅ | 61.0% | $0.002594 | 3 | 2 | |
## Scope
Unlike τ-bench-lite, these tasks are single-turn reasoning problems (no user simulator, no DB, no tool calls). Checkers are deterministic — regex + set / value compare, never an LLM judge. The point is to isolate whether the Pillar 2 harvest step adds measurable value above plain reasoner usage.
Interpretation: `baseline` (chat / V3) is a floor. `reasoner` shows the raw R1 gain. `reasoner-harvest` isolates the cost + quality delta from the extra V3 harvest call.
## Findings (v0.3, 18-run set)
Two bands of tasks tried (easy: mod7 / flips / hats; hard: pseudoprime341 / D_7 / Euler quadratic). The hard band was chosen for *known V3 failure modes*. Result:
1. **V3 chat passed all six tasks, including the three "hard" ones.** DeepSeek V3 knew 341 is the smallest base-2 pseudoprime, computed D_7=1854, and identified n=40 as the first Euler-polynomial failure. The tasks are well-known enough to be in training; the trap-answer variants (561, 265, 41) that the checkers specifically reject didn't fire.
2. **Reasoner cost 3.04× baseline for identical pass rates (6/6 both sides).** On this task set, R1 adds cost and latency without measurable quality. The cache-hit story *does* extend to reasoner (74.2% mean), so Pillar 1 generalizes to R1 — but that's not a Pillar 2 story.
3. **Harvest produced real signal** (mean 2.8 subgoals, 1.3 uncertainties per run where it fired) but didn't improve outcomes. One run hit the 300s timeout (bumped from 120s), suggesting reasoner-harvest latency is still unpredictable on some problems.
### What this tells us about Pillar 2 positioning
We've now given harvest two shots at showing answer-quality value on pure reasoning tasks. Both times V3 ate its lunch. This isn't a framework bug — it's a positioning signal:
- **On well-known math / logic / counting problems, DeepSeek V3 is strong enough that paying for R1 is not justified by accuracy.** Pillar 2's "smart preset" cost multiplier (10×) quoted in the README is real but for most single-question Q/A it buys nothing.
- **Harvest's plausible value surfaces are not "better math answers".** More likely: (a) transparency / auditability for developers, (b) planning support when tools are in the mix, (c) driving branch-sampling on cases where uncertainty correlates with wrongness. None of those are tested here.
### Recommendation
Don't ship v0.3 on the "harvest makes answers more correct" claim — the data doesn't support it. Two honest paths forward:
- **Reframe Pillar 2 as a developer-facing introspection feature** (debug visibility into R1's planning). Keep harvest opt-in; stop implying it improves accuracy on end-user tasks.
- **Move harvest eval to tool-use contexts** where uncertainty matters for *which tool to call next*, not *is this math right*. That's a new task shape — different harness, not a bigger task set here.
In either case, the next Reasonix release is better served by MCP client (Pillar 1 leverage across the ecosystem) than by a bigger harvest-bench data push.
### Notes
- Cache hit on baseline runs surprised me (39.5% mean). That's DeepSeek's *cross-session* prompt cache: the same system prompt ran many times across modes and runs warmed the server-side cache. Real cross-session evidence that Cache-First's value isn't only per-session.
- 5-subgoals cap still hit uniformly. `HarvestOptions.maxItems` default is 5; harvest is truncating. Moot unless we find a setting where that matters.
+232
View File
@@ -0,0 +1,232 @@
/**
* Render a harvest-bench results.json into a markdown report.
*
* npx tsx benchmarks/harvest/report.ts benchmarks/harvest/results-<date>.json
* npx tsx benchmarks/harvest/report.ts <input.json> --out report.md
*/
import { readFileSync, writeFileSync } from "node:fs";
import { pathToFileURL } from "node:url";
import { ALL_MODES, type HarvestBenchReport, type HarvestMode, type HarvestRunResult } from "./types.js";
interface CliArgs {
input: string;
outPath: string;
}
function parseArgs(argv: string[]): CliArgs {
const out: CliArgs = { input: "", outPath: "benchmarks/harvest/report.md" };
const positional: string[] = [];
for (let i = 0; i < argv.length; i++) {
const a = argv[i];
if (a === "--out") out.outPath = argv[++i] ?? out.outPath;
else if (a && !a.startsWith("--")) positional.push(a);
}
out.input = positional[0] ?? "";
if (!out.input) {
throw new Error("usage: npx tsx benchmarks/harvest/report.ts <results.json> [--out report.md]");
}
return out;
}
interface Agg {
runs: number;
passes: number;
avgCache: number;
avgCost: number;
avgClaudeCost: number;
avgHarvestedTurns: number;
avgSubgoals: number;
avgUncertainties: number;
}
function aggregate(results: HarvestRunResult[]): Agg {
if (results.length === 0) {
return {
runs: 0,
passes: 0,
avgCache: 0,
avgCost: 0,
avgClaudeCost: 0,
avgHarvestedTurns: 0,
avgSubgoals: 0,
avgUncertainties: 0,
};
}
const passes = results.filter((r) => r.verdict === "pass").length;
const mean = (fn: (r: HarvestRunResult) => number) =>
results.reduce((s, r) => s + fn(r), 0) / results.length;
return {
runs: results.length,
passes,
avgCache: mean((r) => r.cacheHitRatio),
avgCost: mean((r) => r.costUsd),
avgClaudeCost: mean((r) => r.claudeEquivalentUsd),
avgHarvestedTurns: mean((r) => r.harvestedTurns),
avgSubgoals: mean((r) => r.totalSubgoals),
avgUncertainties: mean((r) => r.totalUncertainties),
};
}
export function renderReport(report: HarvestBenchReport): string {
const lines: string[] = [];
lines.push("# Reasonix harvest eval (Pillar 2)");
lines.push("");
lines.push(`**Date:** ${report.meta.date}`);
lines.push(
`**Tasks:** ${report.meta.taskCount} · repeats × ${report.meta.repeatsPerTask} · modes: ${report.meta.modesRun.join(", ")}`,
);
lines.push(`**Reasonix version:** ${report.meta.reasonixVersion}`);
lines.push("");
// Per-mode summary
lines.push("## Summary by mode");
lines.push("");
lines.push("| mode | runs | pass rate | cache hit | cost / run | harvest turns | subgoals | uncertainties |");
lines.push("|---|---:|---:|---:|---:|---:|---:|---:|");
for (const mode of ALL_MODES) {
const rs = report.results.filter((r) => r.mode === mode);
const a = aggregate(rs);
if (a.runs === 0) continue;
lines.push(
`| ${mode} | ${a.runs} | ${pct(a.passes, a.runs)} | ${pct1(a.avgCache)} | $${a.avgCost.toFixed(6)} | ${a.avgHarvestedTurns.toFixed(1)} | ${a.avgSubgoals.toFixed(1)} | ${a.avgUncertainties.toFixed(1)} |`,
);
}
lines.push("");
// Pairwise deltas that actually answer the question
lines.push("## Deltas");
lines.push("");
const modes = ALL_MODES.filter((m) =>
report.results.some((r) => r.mode === m),
);
if (modes.length >= 2) {
const baseline = aggregate(report.results.filter((r) => r.mode === modes[0]));
for (let i = 1; i < modes.length; i++) {
const mode = modes[i]!;
const agg = aggregate(report.results.filter((r) => r.mode === mode));
const passDelta = (agg.passes / Math.max(agg.runs, 1)) - (baseline.passes / Math.max(baseline.runs, 1));
const costRatio = baseline.avgCost > 0 ? agg.avgCost / baseline.avgCost : 0;
lines.push(`- **${modes[0]} → ${mode}**`);
lines.push(` - pass rate: ${(passDelta * 100).toFixed(0)}pp`);
lines.push(` - cost: ×${costRatio.toFixed(2)} (each run costs ${costRatio > 1 ? "more" : "less"})`);
lines.push(` - harvest signal / run: ${agg.avgSubgoals.toFixed(1)} subgoals, ${agg.avgUncertainties.toFixed(1)} uncertainties`);
lines.push("");
}
}
// Per-task breakdown
lines.push("## Per-task breakdown");
lines.push("");
const byTask = new Map<string, HarvestRunResult[]>();
for (const r of report.results) {
const list = byTask.get(r.taskId) ?? [];
list.push(r);
byTask.set(r.taskId, list);
}
lines.push("| task | mode | rep | verdict | cache | cost | sg | un | note |");
lines.push("|---|---|---:|:---:|---:|---:|---:|---:|---|");
for (const [taskId, runs] of byTask) {
for (const r of runs) {
const mark = r.verdict === "pass" ? "✅" : r.verdict === "fail" ? "❌" : "•";
lines.push(
`| ${taskId} | ${r.mode} | ${r.repeat} | ${mark} | ${pct1(r.cacheHitRatio)} | $${r.costUsd.toFixed(6)} | ${r.totalSubgoals} | ${r.totalUncertainties} | ${truncate(r.checkNote ?? "", 40)} |`,
);
}
}
lines.push("");
lines.push("## Scope");
lines.push("");
lines.push(
"Unlike τ-bench-lite, these tasks are single-turn reasoning problems (no user simulator, no DB, no tool calls). Checkers are deterministic — regex + set / value compare, never an LLM judge. The point is to isolate whether the Pillar 2 harvest step adds measurable value above plain reasoner usage.",
);
lines.push("");
lines.push(
"Interpretation: `baseline` (chat / V3) is a floor. `reasoner` shows the raw R1 gain. `reasoner-harvest` isolates the cost + quality delta from the extra V3 harvest call.",
);
return lines.join("\n");
}
/**
* Findings section is hand-written into report.md after rendering — the
* numbers don't interpret themselves, and boilerplate sections full of
* "TBD — analyse the data" are worse than nothing. Append with append().
*
* This section has been updated twice: after the first 9-run set (which
* bottomed out at V3 on easy tasks) and after this 18-run set (which
* bottomed out at V3 on *hard* tasks too).
*/
export function renderFindings(_report: HarvestBenchReport): string {
return [
"",
"## Findings (v0.3, 18-run set)",
"",
"Two bands of tasks tried (easy: mod7 / flips / hats; hard: pseudoprime341 / D_7 / Euler quadratic). The hard band was chosen for *known V3 failure modes*. Result:",
"",
"1. **V3 chat passed all six tasks, including the three \"hard\" ones.** DeepSeek V3 knew 341 is the smallest base-2 pseudoprime, computed D_7=1854, and identified n=40 as the first Euler-polynomial failure. The tasks are well-known enough to be in training; the trap-answer variants (561, 265, 41) that the checkers specifically reject didn't fire.",
"2. **Reasoner cost 3.04× baseline for identical pass rates (6/6 both sides).** On this task set, R1 adds cost and latency without measurable quality. The cache-hit story *does* extend to reasoner (74.2% mean), so Pillar 1 generalizes to R1 — but that's not a Pillar 2 story.",
"3. **Harvest produced real signal** (mean 2.8 subgoals, 1.3 uncertainties per run where it fired) but didn't improve outcomes. One run hit the 300s timeout (bumped from 120s), suggesting reasoner-harvest latency is still unpredictable on some problems.",
"",
"### What this tells us about Pillar 2 positioning",
"",
"We've now given harvest two shots at showing answer-quality value on pure reasoning tasks. Both times V3 ate its lunch. This isn't a framework bug — it's a positioning signal:",
"",
"- **On well-known math / logic / counting problems, DeepSeek V3 is strong enough that paying for R1 is not justified by accuracy.** Pillar 2's \"smart preset\" cost multiplier (10×) quoted in the README is real but for most single-question Q/A it buys nothing.",
"- **Harvest's plausible value surfaces are not \"better math answers\".** More likely: (a) transparency / auditability for developers, (b) planning support when tools are in the mix, (c) driving branch-sampling on cases where uncertainty correlates with wrongness. None of those are tested here.",
"",
"### Recommendation",
"",
"Don't ship v0.3 on the \"harvest makes answers more correct\" claim — the data doesn't support it. Two honest paths forward:",
"",
"- **Reframe Pillar 2 as a developer-facing introspection feature** (debug visibility into R1's planning). Keep harvest opt-in; stop implying it improves accuracy on end-user tasks.",
"- **Move harvest eval to tool-use contexts** where uncertainty matters for *which tool to call next*, not *is this math right*. That's a new task shape — different harness, not a bigger task set here.",
"",
"In either case, the next Reasonix release is better served by MCP client (Pillar 1 leverage across the ecosystem) than by a bigger harvest-bench data push.",
"",
"### Notes",
"",
"- Cache hit on baseline runs surprised me (39.5% mean). That's DeepSeek's *cross-session* prompt cache: the same system prompt ran many times across modes and runs warmed the server-side cache. Real cross-session evidence that Cache-First's value isn't only per-session.",
"- 5-subgoals cap still hit uniformly. `HarvestOptions.maxItems` default is 5; harvest is truncating. Moot unless we find a setting where that matters.",
"",
].join("\n");
}
function pct(num: number, denom: number): string {
if (denom === 0) return "—";
return `${((num / denom) * 100).toFixed(0)}%`;
}
function pct1(x: number): string {
return `${(x * 100).toFixed(1)}%`;
}
function truncate(s: string, n: number): string {
return s.length > n ? `${s.slice(0, n)}…` : s;
}
async function main(): Promise<void> {
const args = parseArgs(process.argv.slice(2));
const raw = readFileSync(args.input, "utf8");
const report = JSON.parse(raw) as HarvestBenchReport;
const md = renderReport(report) + renderFindings(report);
writeFileSync(args.outPath, md, "utf8");
console.log(`wrote ${args.outPath} (${report.results.length} runs)`);
}
function isMain(): boolean {
const entry = process.argv[1];
if (!entry) return false;
return import.meta.url === pathToFileURL(entry).href;
}
if (isMain()) {
main().catch((err) => {
console.error(err);
process.exit(1);
});
}
// Suppress unused import warning — kept in scope so ALL_MODES order matches renderer iteration.
export type { HarvestMode };
+305
View File
@@ -0,0 +1,305 @@
{
"meta": {
"date": "2026-04-21T16:44:21.011Z",
"repeatsPerTask": 1,
"taskCount": 6,
"modesRun": [
"baseline",
"reasoner",
"reasoner-harvest"
],
"reasonixVersion": "0.2.2"
},
"results": [
{
"taskId": "mod7_list",
"mode": "baseline",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "Alright, let's go step-by-step.\n\n---\n\n## **Step 1: Problem restatement**\nWe want positive integers \\( n \\leq 100 \\) such that \n\\[\nn^2 + n + 1 \\equiv 0 \\pmod{7}.\n\\]\n\n---\n\n## **Step 2: Try residues modulo 7**\nLet \\( n \\equiv r \\pmod{7} \\), where \\( r \\in \\{0, 1, 2, 3, 4, 5, 6\\} \\).\n\nWe compute \\( r^2 + r + 1 \\mod 7 \\):\n\n- \\( r = 0 \\): \\( 0 + 0 + 1 = 1 \\) → not divisible by 7.\n- \\( r = 1 \\): \\( 1 + 1 + 1 = 3 \\) → no.\n- \\( r = 2 \\): \\( 4 + 2 + 1 = 7 \\equiv 0 \\) → yes.\n- \\( r = 3 \\): \\( 9 + 3 + 1 = 13 \\equiv 6 \\) → no.\n- \\( r = 4 \\): \\( 16 + 4 + 1 = 21 \\equiv 0 \\) → yes.\n- \\( r = 5 \\): \\( 25 + 5 + 1 = 31 \\equiv 3 \\) → no.\n- \\( r = 6 \\): \\( 36 + 6 + 1 = 43 \\equiv 1 \\) → no.\n\nSo \\( n \\equiv 2 \\pmod{7} \\) or \\( n \\equiv 4 \\pmod{7} \\).\n\n---\n\n## **Step 3: General form**\n\\[\nn \\equiv 2 \\pmod{7} \\quad \\text{or} \\quad n \\equiv 4 \\pmod{7}.\n\\]\n\nThat means \\( n = 7k + 2 \\) or \\( n = 7k + 4 \\) for some integer \\( k \\ge 0 \\).\n\n---\n\n## **Step 4: Positive integers \\( n \\leq 100 \\)**\n**Case 1:** \\( n = 7k + 2 \\), \\( n \\leq 100 \\), \\( k \\ge 0 \\).\n\n\\( 7k + 2 \\leq 100 \\) → \\( 7k \\leq 98 \\) → \\( k \\leq 14 \\).\n\nSo \\( k = 0, 1, 2, \\dots, 14 \\) gives \\( n = 2, 9, 16, \\dots, 100 \\).\n\nCheck \\( n=100 \\): \\( 7 \\times 14 + 2 = 98 + 2 = 100 \\) okay.\n\n---\n\n**Case 2:** \\( n = 7k + 4 \\), \\( n \\leq 100 \\), \\( k \\ge 0 \\).\n\n\\( 7k + 4 \\leq 100 \\) → \\( 7k \\leq 96 \\) → \\( k \\leq 13 \\) (since \\( 7 \\times 13 = 91 \\), \\( 91+4=95 \\), \\( 7\\times14=98 \\) → \\( 98+4=102>100 \\)).\n\nSo \\( k = 0, 1, 2, \\dots, 13 \\) gives \\( n = 4, 11, 18, \\dots, 95 \\).\n\n---\n\n## **Step 5: List all such \\( n \\leq 100 \\)**\nFrom case 1: \\( 2, 9, 16, 23, 30, 37, 44, 51, 58, 65, 72, 79, 86, 93, 100 \\).\n\nFrom case 2: \\( 4, 11, 18, 25, 32, 39, 46, 53, 60, 67, 74, 81, 88, 95 \\).\n\nCombine and sort:\n\n\\[\n2, 4, 9, 11, 16, 18, 23, 25, 30, 32, 37, 39, 44, 46, 51, 53, 58, 60, 65, 67, 72, 74, 79, 81, 86, 88, 93, 95, 100.\n\\]\n\n---\n\n## **Step 6: Check count**\nEach sequence has 15 and 14 terms respectively, total \\( 15 + 14 = 29 \\) numbers.\n\nCheck: \\( n=2 \\) works? \\( 4+2+1=7 \\) yes. \\( n=4 \\) works? \\( 16+4+1=21 \\) yes. \\( n=100 \\) works? \\( 10000+100+1=10101 \\), divide by 7: \\( 10101/7 = 1443 \\) yes.\n\n---\n\n**Final answer:**\n\\[\n\\boxed{2, 4, 9, 11, 16, 18, 23, 25, 30, 32, 37, 39, 44, 46, 51, 53, 58, 60, 65, 67, 72, 74, 79, 81, 86, 88, 93, 95, 100}\n\\]\n\n---\n\nAnswer: 2, 4, 9, 11, 16, 18, 23, 25, 30, 32, 37, 39, 44, 46, 51, 53, 58, 60, 65, 67, 72, 74, 79, 81, 86, 88, 93, 95, 100",
"turns": 1,
"cacheHitRatio": 0.8648648648648649,
"costUsd": 0.0013612800000000003,
"claudeEquivalentUsd": 0.018687,
"harvestedTurns": 0,
"totalSubgoals": 0,
"totalUncertainties": 0,
"totalHypotheses": 0,
"totalRejectedPaths": 0
},
{
"taskId": "mod7_list",
"mode": "reasoner",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "The condition \\(n^2 + n + 1\\) divisible by 7 is equivalent to \\(n^2 + n + 1 \\equiv 0 \\pmod{7}\\). Testing residues modulo 7:\n\n- \\(n \\equiv 0: 0+0+1 \\equiv 1\\) \n- \\(n \\equiv 1: 1+1+1 \\equiv 3\\) \n- \\(n \\equiv 2: 4+2+1 \\equiv 7 \\equiv 0\\) \n- \\(n \\equiv 3: 9+3+1 \\equiv 13 \\equiv 6\\) \n- \\(n \\equiv 4: 16+4+1 \\equiv 21 \\equiv 0\\) \n- \\(n \\equiv 5: 25+5+1 \\equiv 31 \\equiv 3\\) \n- \\(n \\equiv 6: 36+6+1 \\equiv 43 \\equiv 1\\)\n\nThus, \\(n \\equiv 2\\) or \\(n \\equiv 4 \\pmod{7}\\) are the solutions modulo 7. For positive integers \\(n \\leq 100\\), we list all numbers congruent to 2 or 4 modulo 7 in increasing order.\n\nAnswer: 2, 4, 9, 11, 16, 18, 23, 25, 30, 32, 37, 39, 44, 46, 51, 53, 58, 60, 65, 67, 72, 74, 79, 81, 86, 88, 93, 95, 100",
"turns": 1,
"cacheHitRatio": 0.8648648648648649,
"costUsd": 0.00479742,
"claudeEquivalentUsd": 0.032982,
"harvestedTurns": 0,
"totalSubgoals": 0,
"totalUncertainties": 0,
"totalHypotheses": 0,
"totalRejectedPaths": 0
},
{
"taskId": "mod7_list",
"mode": "reasoner-harvest",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "The congruence \\(n^2 + n + 1 \\equiv 0 \\pmod{7}\\) is solved by testing residues modulo 7. The solutions are \\(n \\equiv 2\\) and \\(n \\equiv 4 \\pmod{7}\\). For positive integers \\(n \\le 100\\), these yield \\(n = 7k + 2\\) with \\(k = 0, 1, \\dots, 14\\) and \\(n = 7k + 4\\) with \\(k = 0, 1, \\dots, 13\\).\n\nAnswer: 2, 4, 9, 11, 16, 18, 23, 25, 30, 32, 37, 39, 44, 46, 51, 53, 58, 60, 65, 67, 72, 74, 79, 81, 86, 88, 93, 95, 100",
"turns": 1,
"cacheHitRatio": 0.8648648648648649,
"costUsd": 0.00304542,
"claudeEquivalentUsd": 0.020982,
"harvestedTurns": 1,
"totalSubgoals": 4,
"totalUncertainties": 2,
"totalHypotheses": 2,
"totalRejectedPaths": 2
},
{
"taskId": "flips_until_3heads",
"mode": "baseline",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "Alright, let's reason through this step-by-step.\n\n---\n\n## **Step 1: Define states**\nLet’s define states based on how many consecutive heads we have at the moment.\n\n- \\( E_0 \\): Expected flips to reach 3 heads in a row starting from 0 consecutive heads (or just starting, or after a tail).\n- \\( E_1 \\): Expected flips to reach 3 heads in a row starting from 1 consecutive head.\n- \\( E_2 \\): Expected flips to reach 3 heads in a row starting from 2 consecutive heads.\n\nWe want \\( E_0 \\).\n\n---\n\n## **Step 2: Transition equations**\nFrom \\( E_0 \\):\n- Flip H (prob \\( \\frac12 \\)) → go to state \\( E_1 \\), 1 flip used.\n- Flip T (prob \\( \\frac12 \\)) → stay in \\( E_0 \\), 1 flip used.\n\nSo:\n\\[\nE_0 = \\frac12 (1 + E_1) + \\frac12 (1 + E_0)\n\\]\n\n---\n\nFrom \\( E_1 \\) (already have 1 head):\n- Flip H (prob \\( \\frac12 \\)) → go to state \\( E_2 \\), 1 flip used.\n- Flip T (prob \\( \\frac12 \\)) → go to state \\( E_0 \\), 1 flip used.\n\nSo:\n\\[\nE_1 = \\frac12 (1 + E_2) + \\frac12 (1 + E_0)\n\\]\n\n---\n\nFrom \\( E_2 \\) (already have 2 heads):\n- Flip H (prob \\( \\frac12 \\)) → done (3 heads in a row), 1 flip used.\n- Flip T (prob \\( \\frac12 \\)) → go to state \\( E_0 \\), 1 flip used.\n\nSo:\n\\[\nE_2 = \\frac12 (1 + 0) + \\frac12 (1 + E_0)\n\\]\n\\[\nE_2 = \\frac12 \\cdot 1 + \\frac12 (1 + E_0) \\quad\\text{(Wait, careful:)}\n\\]\nActually: \nIf H: \\( 1 \\) flip and done. \nIf T: \\( 1 \\) flip and then \\( E_0 \\) more.\n\nSo:\n\\[\nE_2 = \\frac12 \\cdot 1 + \\frac12 (1 + E_0)\n\\]\nCheck: \nH: 1 flip → total 1, done. Contribution: \\( \\frac12 \\times 1 \\). \nT: 1 flip + \\( E_0 \\) more → total \\( 1 + E_0 \\). Contribution: \\( \\frac12 \\times (1 + E_0) \\).\n\nYes:\n\\[\nE_2 = \\frac12 \\cdot 1 + \\frac12 (1 + E_0) = \\frac12 + \\frac12 + \\frac12 E_0 = 1 + \\frac{E_0}{2}.\n\\]\n\n---\n\n## **Step 3: Solve system**\nWe have:\n\n(1) \\( E_0 = \\frac12 (1 + E_1) + \\frac12 (1 + E_0) \\) \nSimplify: \\( E_0 = 1 + \\frac12 E_1 + \\frac12 E_0 \\) \nMultiply by 2: \\( 2E_0 = 2 + E_1 + E_0 \\) \nSo \\( E_0 - E_1 = 2 \\) … (Eq A)\n\n---\n\n(2) \\( E_1 = \\frac12 (1 + E_2) + \\frac12 (1 + E_0) \\) \nSimplify: \\( E_1 = 1 + \\frac12 E_2 + \\frac12 E_0 \\) … (Eq B)\n\n---\n\n(3) \\( E_2 = 1 + \\frac12 E_0 \\) … (Eq C)\n\n---\n\nFrom Eq C into Eq B:\n\\[\nE_1 = 1 + \\frac12 \\left( 1 + \\frac12 E_0 \\right) + \\frac12 E_0\n\\]\n\\[\nE_1 = 1 + \\frac12 + \\frac14 E_0 + \\frac12 E_0\n\\]\n\\[\nE_1 = \\frac32 + \\frac34 E_0\n\\]\n\n---\n\nFrom Eq A: \\( E_0 - E_1 = 2 \\) \nSubstitute \\( E_1 \\):\n\\[\nE_0 - \\left( \\frac32 + \\frac34 E_0 \\right) = 2\n\\]\n\\[\nE_0 - \\frac32 - \\frac34 E_0 = 2\n\\]\n\\[\n\\frac14 E_0 - \\frac32 = 2\n\\]\n\\[\n\\frac14 E_0 = 2 + \\frac32 = \\frac72\n\\]\n\\[\nE_0 = 14\n\\]\n\n---\n\n## **Step 4: Conclusion**\nThe expected number of flips until we get 3 heads in a row is \\( 14 \\).\n\n---\n\n**Answer:** 14",
"turns": 1,
"cacheHitRatio": 0.927536231884058,
"costUsd": 0.00119823,
"claudeEquivalentUsd": 0.016467,
"harvestedTurns": 0,
"totalSubgoals": 0,
"totalUncertainties": 0,
"totalHypotheses": 0,
"totalRejectedPaths": 0
},
{
"taskId": "flips_until_3heads",
"mode": "reasoner",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "The expected number of flips required to get three consecutive heads is 14, derived from solving the system of linear equations for the Markov chain states representing the current streak of heads.\n\nAnswer: 14",
"turns": 1,
"cacheHitRatio": 0.927536231884058,
"costUsd": 0.00283024,
"claudeEquivalentUsd": 0.019512,
"harvestedTurns": 0,
"totalSubgoals": 0,
"totalUncertainties": 0,
"totalHypotheses": 0,
"totalRejectedPaths": 0
},
{
"taskId": "flips_until_3heads",
"mode": "reasoner-harvest",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "The expected number of flips until three consecutive heads appear is 14.\n\nAnswer: 14",
"turns": 1,
"cacheHitRatio": 0.927536231884058,
"costUsd": 0.00169144,
"claudeEquivalentUsd": 0.011712,
"harvestedTurns": 1,
"totalSubgoals": 4,
"totalUncertainties": 0,
"totalHypotheses": 2,
"totalRejectedPaths": 0
},
{
"taskId": "three_hats",
"mode": "baseline",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "Let's break this down step by step.\n\n---\n\n**Step 1: Understanding the setup** \nThree people: A (first), B (second), C (third). \nEach hat is red (R) or blue (B). \nThey know: at least one hat is red. \nEach sees the other two hats, not their own. \nThey are asked in order: \"Do you know your hat color?\" \nA answers no, B answers no, C answers yes. \nWe want C’s hat color.\n\n---\n\n**Step 2: From A’s perspective when asked** \nA sees B and C. \nIf A had seen two blue hats, then A would know: \"At least one red hat means my hat must be red.\" \nSo A says \"no\" → A did **not** see two blue hats. \nThus A sees at least one red hat on {B, C}.\n\nPossible cases for what A sees (B, C): \n(R, R), (R, B), (B, R) — all have at least one red.\n\n---\n\n**Step 3: B’s reasoning when asked** \nB hears A say \"no\". \nB sees A and C. \n\nLet’s consider B’s possible deductions from A’s \"no\": \nB knows: If A had seen two blues, A would have said yes. Since A said no, A saw at least one red among B and C. \nBut B sees A and C. \n\nFrom B’s viewpoint: \n- If B saw C with blue and A with blue, then B would know: \"A saw me and C both blue → impossible because A said no.\" But B doesn’t see that because if B saw A blue and C blue, then B would know his own hat must be red (since at least one red total). But then B would answer yes. \nSo B’s \"no\" means B did **not** see A and C both blue. \n\nAlso, B considers: Could my hat be blue? Let’s check: \nSuppose B sees A red, C blue. Then B thinks: \"If my hat were blue, then A would have seen (B blue, C blue) → A would have said yes. But A said no, so my hat cannot be blue.\" \nSo if B saw (A red, C blue), B would deduce: \"My hat must be red.\" Then B would answer yes. \nBut B said no → so B did **not** see (A red, C blue).\n\nSimilarly, if B saw (A blue, C red): \nThen B thinks: \"If my hat were blue, then A would have seen (B blue, C red) → that’s fine (A sees one red on C), so A would still say no. If my hat were red, then A would see (B red, C red) → A would still say no. So I don’t know.\" That’s consistent with B saying no. \n\nIf B saw (A red, C red): \nThen B thinks: \"If my hat were blue, A sees (B blue, C red) → A says no. If my hat were red, A sees (B red, C red) → A says no. So I don’t know.\" That’s also consistent with B saying no.\n\nSo B says no in cases: \nB sees (A blue, C red) or (A red, C red). \nB would say yes if B saw (A red, C blue) — but that didn’t happen. \n\n---\n\n**Step 4: C’s reasoning** \nC hears A says no, B says no. \nC sees A and B. \n\nFrom C’s viewpoint: \nLet’s list all possible (A, B, C) hat colorings with at least one red, consistent with A’s \"no\" (which we already incorporated: A sees at least one red on B/C) and B’s \"no\" (meaning B didn’t see A red, C blue — because that would make B know).\n\nPossible cases for (A, B) that C could see: \n\n1. C sees (A blue, B red): \n Then C thinks: \n - If C were blue: (A blue, B red, C blue) → A sees (B red, C blue) → A says no. B sees (A blue, C blue) → B sees two blues? Wait, B sees A blue, C blue → then B knows his own hat is red (since at least one red total) → B would say yes. But B said no → contradiction. So C cannot be blue. \n So C must be red. \n\n2. C sees (A red, B blue): \n Then C thinks: \n - If C were blue: (A red, B blue, C blue) → A sees (B blue, C blue) → A would say yes (since at least one red total means A’s hat must be red). But A said no → contradiction. So C cannot be blue. \n So C must be red. \n\n3. C sees (A red, B red): \n Then C thinks: \n - If C were blue: (A red, B red, C blue) → A sees (B red, C blue) → A says no. B sees (A red, C blue) → B sees A red, C blue → earlier we said: If B sees A red, C blue, then B would deduce his own hat is red (reasoning: if B were blue, A would have seen two blues and said yes, but A said no, so B can’t be blue) → so B would say yes. But B actually said no → contradiction. So C cannot be blue. \n - If C were red: (A red, B red, C red) → A sees (B red, C red) → A says no. B sees (A red, C red) → B says no. Works fine. \n\nSo in all cases C sees for (A, B), C can deduce C’s hat is **red** because assuming C is blue leads to contradiction with B’s \"no\" (in cases 1 and 3) or with A’s \"no\" (in case 2).\n\n---\n\n**Step 5: Conclusion** \nC answers yes, and C’s hat must be red.\n\n---\n\nAnswer: red",
"turns": 1,
"cacheHitRatio": 0.5765765765765766,
"costUsd": 0.0015142700000000003,
"claudeEquivalentUsd": 0.020748,
"harvestedTurns": 0,
"totalSubgoals": 0,
"totalUncertainties": 0,
"totalHypotheses": 0,
"totalRejectedPaths": 0
},
{
"taskId": "three_hats",
"mode": "reasoner",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "Answer: red",
"turns": 1,
"cacheHitRatio": 0.5765765765765766,
"costUsd": 0.009340119999999999,
"claudeEquivalentUsd": 0.064068,
"harvestedTurns": 0,
"totalSubgoals": 0,
"totalUncertainties": 0,
"totalHypotheses": 0,
"totalRejectedPaths": 0
},
{
"taskId": "three_hats",
"mode": "reasoner-harvest",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "The third person deduces their hat color based on the previous responses. Since the first two answer \"no,\" it implies they each see at least one red hat and cannot determine their own color. Specifically, the second person's \"no\" indicates they see the third person's hat as red; otherwise, they would have known their own hat color. Therefore, the third person's hat must be red.\n\nAnswer: red",
"turns": 1,
"cacheHitRatio": 0.5765765765765766,
"costUsd": 0.0096511,
"claudeEquivalentUsd": 0.066198,
"harvestedTurns": 1,
"totalSubgoals": 3,
"totalUncertainties": 2,
"totalHypotheses": 3,
"totalRejectedPaths": 3
},
{
"taskId": "pseudoprime_base2",
"mode": "baseline",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "Alright, let's go step-by-step.\n\n---\n\n**Step 1: Understanding the problem**\n\nWe want the smallest composite integer \\( n > 1 \\) such that\n\n\\[\n2^n \\equiv 2 \\pmod{n}.\n\\]\n\nEquivalently, \\( 2^{n-1} \\equiv 1 \\pmod{n} \\) for composite \\( n \\).\n\nThis means \\( n \\) is a **Fermat pseudoprime to base 2**.\n\nWe check composite numbers starting from the smallest.\n\n---\n\n**Step 2: Check small composites**\n\n- \\( n = 4 \\): composite. \n\\( 2^4 = 16 \\), \\( 16 \\mod 4 = 0 \\), not \\( 2 \\). So \\( 2^4 \\equiv 0 \\not\\equiv 2 \\pmod{4} \\). Fails.\n\n- \\( n = 6 \\): composite. \n\\( 2^6 = 64 \\), \\( 64 \\mod 6 = 4 \\), not \\( 2 \\). Fails.\n\n- \\( n = 8 \\): composite. \n\\( 2^8 = 256 \\), \\( 256 \\mod 8 = 0 \\), not \\( 2 \\). Fails.\n\n- \\( n = 9 \\): composite. \n\\( 2^9 = 512 \\), \\( 512 \\mod 9 \\): \n\\( 512 \\div 9 \\), \\( 9 \\times 56 = 504 \\), remainder \\( 8 \\), not \\( 2 \\). Fails.\n\n- \\( n = 10 \\): composite. \n\\( 2^{10} = 1024 \\), \\( 1024 \\mod 10 = 4 \\), not \\( 2 \\). Fails.\n\n---\n\n**Step 3: Try n = 15**\n\n\\( n = 15 \\): composite. \n\\( 2^{15} = 32768 \\). \nCheck mod 15: \nWe can use mod arithmetic: \n\\( 2^4 = 16 \\equiv 1 \\pmod{15} \\)?? Wait, check: \\( 16 \\mod 15 = 1 \\), yes. \nSo \\( 2^{15} = (2^4)^3 \\times 2^3 = 1^3 \\times 8 = 8 \\pmod{15} \\). \nSo \\( 2^{15} \\equiv 8 \\not\\equiv 2 \\pmod{15} \\). Fails.\n\n---\n\n**Step 4: Try n = 21**\n\n\\( n = 21 \\): composite. \nMod 21: \n\\( 2^6 = 64 \\equiv 1 \\pmod{21} \\)? Check: \\( 64 \\div 21 = 3 \\times 21 = 63 \\), remainder 1, yes. \nSo \\( 2^{21} = (2^6)^3 \\times 2^3 \\equiv 1^3 \\times 8 = 8 \\pmod{21} \\). Not 2. Fails.\n\n---\n\n**Step 5: Try n = 22**\n\n\\( n = 22 \\): composite. \nUse mod 22: \nEuler’s totient not needed, just check order: \n\\( 2^5 = 32 \\equiv 10 \\pmod{22} \\) \n\\( 2^{10} = (2^5)^2 \\equiv 10^2 = 100 \\equiv 12 \\pmod{22} \\) \n\\( 2^{11} \\equiv 24 \\equiv 2 \\pmod{22} \\) \nSo \\( 2^{22} = (2^{11})^2 \\equiv 2^2 = 4 \\pmod{22} \\). Not 2. Fails.\n\n---\n\n**Step 6: Try n = 25**\n\n\\( n = 25 \\): composite. \nCheck mod 25: \n\\( 2^{10} = 1024 \\equiv 24 \\pmod{25} \\) (since \\( 1000 \\equiv 0 \\), \\( 24 \\equiv -1 \\)) \nActually check: \\( 1024 - 1000 = 24 \\), yes \\( 24 \\equiv -1 \\). \nSo \\( 2^{20} \\equiv 1 \\pmod{25} \\). \nThus \\( 2^{25} = 2^{20} \\times 2^5 \\equiv 1 \\times 32 = 7 \\pmod{25} \\). Not 2. Fails.\n\n---\n\n**Step 7: Known smallest base-2 Fermat pseudoprime**\n\nFrom known number theory facts: \nThe smallest Fermat pseudoprime to base 2 is \\( n = 341 \\). \nBut let's check smaller ones just in case I’m skipping one.\n\n---\n\n**Step 8: Try n = 91**\n\n91 = 7 × 13. \nCheck mod 7: \\( 2^{91} \\equiv (2^6)^{15} \\times 2^1 \\equiv 1^{15} \\times 2 = 2 \\pmod{7} \\). \nCheck mod 13: \\( 2^{12} \\equiv 1 \\pmod{13} \\), \n\\( 91 = 12 \\times 7 + 7 \\), so \\( 2^{91} \\equiv 2^7 = 128 \\equiv 11 \\pmod{13} \\). \nFor \\( 2^{91} \\equiv 2 \\pmod{91} \\), we need \\( 2^{91} \\equiv 2 \\) mod 7 and mod 13. \nMod 13 we got 11, not 2. So fails.\n\n---\n\n**Step 9: Try n = 341**\n\n341 = 11 × 31. \nCheck mod 11: \\( 2^{10} \\equiv 1 \\pmod{11} \\), \n\\( 341 = 10 \\times 34 + 1 \\), so \\( 2^{341} \\equiv 2^1 = 2 \\pmod{11} \\). Good. \nCheck mod 31: \\( 2^5 = 32 \\equiv 1 \\pmod{31} \\), \n\\( 341 = 5 \\times 68 + 1 \\), so \\( 2^{341} \\equiv 2^1 = 2 \\pmod{31} \\). \nSo \\( 2^{341} \\equiv 2 \\) mod 11 and mod 31, hence mod 341. \nThus \\( 341 \\) works.\n\n---\n\n**Step 10: Check smaller than 341**\n\nKnown list: 341 is smallest. Let’s check a candidate like 121 = 11^2: \n\\( 2^{121} \\mod 121 \\): \nMod 11: \\( 2^{10} \\equiv 1 \\), \\( 121 = 10 \\times 12 + 1 \\), so \\( 2^{121} \\equiv 2 \\pmod{11} \\). \nBut for modulus 121, need more: \nActually, \\( 2^{110} \\equiv 1 \\pmod{121} \\) by Euler’s theorem? Not exactly, but known: 121 is not a pseudoprime base 2. Quick check: \n\\( 2^{121} - 2 \\) divisible by 121? Probably not. Let’s skip detailed check; known fact is 341 is smallest.\n\n---\n\n**Step 11: Verify no smaller composite works**\n\nFrom known sequence A001567: \nFirst few base-2 Fermat pseudoprimes: 341, 561, 645, 1105, … \nSo smallest is 341.\n\n---\n\n**Step 12: Conclusion**\n\nThe smallest composite \\( n > 1 \\) with \\( 2^n \\equiv 2 \\pmod{n} \\) is \\( n = 341 \\).\n\n---\n\n**Answer:** 341",
"turns": 1,
"cacheHitRatio": 0,
"costUsd": 0.0018940500000000002,
"claudeEquivalentUsd": 0.02577,
"harvestedTurns": 0,
"totalSubgoals": 0,
"totalUncertainties": 0,
"totalHypotheses": 0,
"totalRejectedPaths": 0
},
{
"taskId": "pseudoprime_base2",
"mode": "reasoner",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "The smallest composite integer \\(n > 1\\) satisfying \\(2^n \\equiv 2 \\pmod{n}\\) is \\(n = 341\\). This is composite (\\(341 = 11 \\times 31\\)), and it satisfies the congruence because \\(2^{341} \\equiv 2 \\pmod{11}\\) and \\(2^{341} \\equiv 2 \\pmod{31}\\) by Fermat's little theorem, implying \\(2^{341} \\equiv 2 \\pmod{341}\\). All smaller composite integers (e.g., 4, 6, 8, 9, 10, 15, 21) fail to satisfy the condition.\n\nAnswer: 341",
"turns": 1,
"cacheHitRatio": 0.7529411764705882,
"costUsd": 0.0031281200000000003,
"claudeEquivalentUsd": 0.02154,
"harvestedTurns": 0,
"totalSubgoals": 0,
"totalUncertainties": 0,
"totalHypotheses": 0,
"totalRejectedPaths": 0
},
{
"taskId": "pseudoprime_base2",
"mode": "reasoner-harvest",
"repeat": 1,
"verdict": "fail",
"checkNote": "This operation was aborted",
"finalAgentMessage": "",
"turns": 0,
"cacheHitRatio": 0,
"costUsd": 0,
"claudeEquivalentUsd": 0,
"harvestedTurns": 0,
"totalSubgoals": 0,
"totalUncertainties": 0,
"totalHypotheses": 0,
"totalRejectedPaths": 0,
"errorMessage": "This operation was aborted"
},
{
"taskId": "derangements_d7",
"mode": "baseline",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "Alright, let's go step-by-step.\n\n---\n\n**Step 1: Understanding the problem**\n\nWe want the number of permutations of \\(\\{1, 2, 3, 4, 5, 6, 7\\}\\) with **no fixed points**. \nA fixed point means \\(\\pi(i) = i\\) for some \\(i\\). \nA permutation with no fixed points is called a **derangement**. \nThe number of derangements of \\(n\\) elements is denoted \\(D_n\\) or \\(!n\\).\n\n---\n\n**Step 2: Formula for derangements**\n\nThe formula for \\(D_n\\) is:\n\n\\[\nD_n = n! \\sum_{k=0}^{n} \\frac{(-1)^k}{k!}\n\\]\n\nFor \\(n=7\\):\n\n\\[\nD_7 = 7! \\left( \\frac{1}{0!} - \\frac{1}{1!} + \\frac{1}{2!} - \\frac{1}{3!} + \\frac{1}{4!} - \\frac{1}{5!} + \\frac{1}{6!} - \\frac{1}{7!} \\right)\n\\]\n\n---\n\n**Step 3: Compute step-by-step**\n\nFirst, \\(7! = 5040\\).\n\nNow compute the sum:\n\n\\[\n\\sum_{k=0}^{7} \\frac{(-1)^k}{k!} \n= 1 - 1 + \\frac{1}{2} - \\frac{1}{6} + \\frac{1}{24} - \\frac{1}{120} + \\frac{1}{720} - \\frac{1}{5040}\n\\]\n\nLet's compute term-by-term:\n\n- \\(1 - 1 = 0\\)\n- \\(0 + 0.5 = 0.5\\)\n- \\(0.5 - \\frac{1}{6} \\approx 0.5 - 0.1666667 = 0.3333333\\)\n- \\(0.3333333 + \\frac{1}{24} \\approx 0.3333333 + 0.0416667 = 0.375\\)\n- \\(0.375 - \\frac{1}{120} \\approx 0.375 - 0.0083333 = 0.3666667\\)\n- \\(0.3666667 + \\frac{1}{720} \\approx 0.3666667 + 0.0013889 = 0.3680556\\)\n- \\(0.3680556 - \\frac{1}{5040} \\approx 0.3680556 - 0.0001984 = 0.3678572\\)\n\nSo the sum is approximately \\(0.367857142857...\\)\n\n---\n\n**Step 4: Multiply by \\(7!\\)**\n\n\\[\nD_7 = 5040 \\times 0.367857142857\\ldots\n\\]\n\nLet's compute exactly using fractions:\n\n\\[\n\\sum_{k=0}^{7} \\frac{(-1)^k}{k!} \n= \\frac{1}{2!} - \\frac{1}{3!} + \\frac{1}{4!} - \\frac{1}{5!} + \\frac{1}{6!} - \\frac{1}{7!}\n\\]\n\nWrite with common denominator \\(7! = 5040\\):\n\n- \\(\\frac{1}{2!} = \\frac{2520}{5040}\\)\n- \\(\\frac{1}{3!} = \\frac{840}{5040}\\)\n- \\(\\frac{1}{4!} = \\frac{210}{5040}\\)\n- \\(\\frac{1}{5!} = \\frac{42}{5040}\\)\n- \\(\\frac{1}{6!} = \\frac{7}{5040}\\)\n- \\(\\frac{1}{7!} = \\frac{1}{5040}\\)\n\nNow alternate signs:\n\n\\[\n\\left( \\frac{2520}{5040} - \\frac{840}{5040} \\right) \n= \\frac{1680}{5040}\n\\]\n\\[\n\\frac{1680}{5040} + \\frac{210}{5040} = \\frac{1890}{5040}\n\\]\n\\[\n\\frac{1890}{5040} - \\frac{42}{5040} = \\frac{1848}{5040}\n\\]\n\\[\n\\frac{1848}{5040} + \\frac{7}{5040} = \\frac{1855}{5040}\n\\]\n\\[\n\\frac{1855}{5040} - \\frac{1}{5040} = \\frac{1854}{5040}\n\\]\n\nSo the sum is \\(\\frac{1854}{5040}\\).\n\n---\n\n**Step 5: Multiply by \\(7!\\)**\n\n\\[\nD_7 = 5040 \\times \\frac{1854}{5040} = 1854\n\\]\n\n---\n\n**Step 6: Quick check with known derangement numbers**\n\nKnown small derangements: \n\\(D_1 = 0, D_2 = 1, D_3 = 2, D_4 = 9, D_5 = 44, D_6 = 265, D_7 = 1854\\). \nYes, matches known sequence.\n\n---\n\n**Final answer:**\n\nAnswer: 1854",
"turns": 1,
"cacheHitRatio": 0,
"costUsd": 0.00127253,
"claudeEquivalentUsd": 0.017292,
"harvestedTurns": 0,
"totalSubgoals": 0,
"totalUncertainties": 0,
"totalHypotheses": 0,
"totalRejectedPaths": 0
},
{
"taskId": "derangements_d7",
"mode": "reasoner",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "The number of derangements of \\(n\\) distinct objects, denoted \\(D_n\\), counts permutations with no fixed points. For \\(n = 7\\), this can be computed using the recurrence \\(D_n = (n-1)(D_{n-1} + D_{n-2})\\) with initial values \\(D_1 = 0\\) and \\(D_2 = 1\\). \nThus: \n\\(D_3 = 2(1+0) = 2\\), \n\\(D_4 = 3(2+1) = 9\\), \n\\(D_5 = 4(9+2) = 44\\), \n\\(D_6 = 5(44+9) = 265\\), \n\\(D_7 = 6(265+44) = 1854\\).\n\nAnswer: 1854",
"turns": 1,
"cacheHitRatio": 0.7191011235955056,
"costUsd": 0.00349167,
"claudeEquivalentUsd": 0.024027,
"harvestedTurns": 0,
"totalSubgoals": 0,
"totalUncertainties": 0,
"totalHypotheses": 0,
"totalRejectedPaths": 0
},
{
"taskId": "derangements_d7",
"mode": "reasoner-harvest",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "The number of derangements of \\(n\\) elements, denoted \\(D_n\\), counts permutations with no fixed points. For \\(n=7\\), this can be computed using the recurrence \\(D_n = (n-1)(D_{n-1} + D_{n-2})\\) with initial values \\(D_0 = 1\\) and \\(D_1 = 0\\). Applying the recurrence yields \\(D_2 = 1\\), \\(D_3 = 2\\), \\(D_4 = 9\\), \\(D_5 = 44\\), \\(D_6 = 265\\), and finally \\(D_7 = 6 \\times (265 + 44) = 1854\\).\n\nAnswer: 1854",
"turns": 1,
"cacheHitRatio": 0.7191011235955056,
"costUsd": 0.0028434299999999997,
"claudeEquivalentUsd": 0.019587,
"harvestedTurns": 1,
"totalSubgoals": 3,
"totalUncertainties": 2,
"totalHypotheses": 2,
"totalRejectedPaths": 2
},
{
"taskId": "euler_quadratic_break",
"mode": "baseline",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "Let’s check \\( f(n) = n^2 + n + 41 \\) for small \\( n \\):\n\n- \\( n = 0 \\): \\( f(0) = 41 \\) (prime) \n- \\( n = 1 \\): \\( f(1) = 1 + 1 + 41 = 43 \\) (prime) \n- \\( n = 2 \\): \\( f(2) = 4 + 2 + 41 = 47 \\) (prime) \n- \\( n = 3 \\): \\( f(3) = 9 + 3 + 41 = 53 \\) (prime) \n- \\( n = 4 \\): \\( f(4) = 16 + 4 + 41 = 61 \\) (prime) \n- \\( n = 5 \\): \\( f(5) = 25 + 5 + 41 = 71 \\) (prime) \n- \\( n = 6 \\): \\( f(6) = 36 + 6 + 41 = 83 \\) (prime) \n- \\( n = 7 \\): \\( f(7) = 49 + 7 + 41 = 97 \\) (prime) \n- \\( n = 8 \\): \\( f(8) = 64 + 8 + 41 = 113 \\) (prime) \n- \\( n = 9 \\): \\( f(9) = 81 + 9 + 41 = 131 \\) (prime) \n- \\( n = 10 \\): \\( f(10) = 100 + 10 + 41 = 151 \\) (prime) \n\nWe can keep going, but the first known counterexample for this famous Euler polynomial is \\( n = 40 \\), because \n\\[\nf(40) = 40^2 + 40 + 41 = 1600 + 40 + 41 = 1681.\n\\] \nCheck if \\( 1681 \\) is prime: \n\\( 1681 = 41^2 \\) (since \\( 41 \\times 41 = 1681 \\)), so it’s composite.\n\nBut wait — let’s check if there’s a smaller \\( n \\) where \\( f(n) \\) is composite. \nWe can test \\( n = 41 \\): \n\\( f(41) = 41^2 + 41 + 41 = 1681 + 82 = 1763 \\), which is \\( 41 \\times 43 \\) (since \\( 1763/41 = 43 \\)), so composite. But \\( n = 41 \\) is larger than \\( n = 40 \\).\n\nCheck \\( n = 39 \\): \\( f(39) = 1521 + 39 + 41 = 1601 \\). Test divisibility: not divisible by primes up to \\( \\sqrt{1601} \\approx 40 \\), seems prime. \n\nCheck \\( n = 40 \\) is indeed the first composite? Let’s check \\( n = 1 \\) to \\( 39 \\) quickly for a smaller counterexample: \nWe can note \\( f(n) = n(n+1) + 41 \\). If \\( 41 \\mid f(n) \\), then \\( 41 \\mid n(n+1) \\). \nThat happens when \\( n \\equiv 0 \\pmod{41} \\) or \\( n \\equiv 40 \\pmod{41} \\). \nThe smallest positive such \\( n \\) is \\( n = 40 \\) (since \\( n=41 \\) is larger). \nSo for \\( n = 40 \\), \\( f(40) = 40 \\times 41 + 41 = 41 \\times 41 \\) is composite. \n\nCheck \\( n = 0 \\) to \\( 39 \\): no multiple of 41 except \\( n=0 \\) (which gives 41, prime). So \\( n=40 \\) is indeed the first nonnegative integer where \\( f(n) \\) is composite.\n\nThus smallest \\( n \\) is \\( 40 \\), \\( f(40) = 1681 = 41^2 \\).\n\n**Answer:** 40",
"turns": 1,
"cacheHitRatio": 0,
"costUsd": 0.00098535,
"claudeEquivalentUsd": 0.013365,
"harvestedTurns": 0,
"totalSubgoals": 0,
"totalUncertainties": 0,
"totalHypotheses": 0,
"totalRejectedPaths": 0
},
{
"taskId": "euler_quadratic_break",
"mode": "reasoner",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "The smallest nonnegative integer \\(n\\) for which \\(f(n) = n^2 + n + 41\\) is composite is \\(n = 40\\). At this value, \\(f(40) = 40^2 + 40 + 41 = 1681 = 41^2\\), which is not prime.\n\nAnswer: 40",
"turns": 1,
"cacheHitRatio": 0.6095238095238096,
"costUsd": 0.0014309199999999998,
"claudeEquivalentUsd": 0.0099,
"harvestedTurns": 0,
"totalSubgoals": 0,
"totalUncertainties": 0,
"totalHypotheses": 0,
"totalRejectedPaths": 0
},
{
"taskId": "euler_quadratic_break",
"mode": "reasoner-harvest",
"repeat": 1,
"verdict": "pass",
"finalAgentMessage": "The polynomial \\(f(n) = n^2 + n + 41\\) is known to produce primes for \\(n = 0, 1, 2, \\dots, 39\\). At \\(n = 40\\), we have \\(f(40) = 40^2 + 40 + 41 = 1681\\), and \\(1681 = 41^2\\), which is composite. Therefore, \\(n = 40\\) is the smallest nonnegative integer where \\(f(n)\\) fails to be prime.\n\nAnswer: 40",
"turns": 1,
"cacheHitRatio": 0.6095238095238096,
"costUsd": 0.0025938099999999998,
"claudeEquivalentUsd": 0.017865,
"harvestedTurns": 1,
"totalSubgoals": 3,
"totalUncertainties": 2,
"totalHypotheses": 3,
"totalRejectedPaths": 2
}
]
}
+312
View File
@@ -0,0 +1,312 @@
/**
* Harvest-bench runner.
*
* Usage:
* npx tsx benchmarks/harvest/runner.ts # all tasks, all modes, 1 repeat
* npx tsx benchmarks/harvest/runner.ts --task mod7_list
* npx tsx benchmarks/harvest/runner.ts --mode reasoner-harvest --repeats 3
* npx tsx benchmarks/harvest/runner.ts --transcripts-dir transcripts/
* npx tsx benchmarks/harvest/runner.ts --dry # smoke test wiring, no API
*
* Writes results.json. Render report.md with `report.ts`.
*/
import { type WriteStream, mkdirSync, writeFileSync } from "node:fs";
import { join } from "node:path";
import { pathToFileURL } from "node:url";
import {
CacheFirstLoop,
DeepSeekClient,
ImmutablePrefix,
claudeEquivalentCost,
loadDotenv,
} from "../../src/index.js";
import { openTranscriptFile, recordFromLoopEvent, writeRecord } from "../../src/transcript.js";
import { TASKS } from "./tasks.js";
import type {
HarvestBenchMeta,
HarvestBenchReport,
HarvestMode,
HarvestRunResult,
HarvestTask,
} from "./types.js";
import { ALL_MODES } from "./types.js";
loadDotenv();
interface CliArgs {
taskFilter: string | null;
modes: HarvestMode[];
repeats: number;
outPath: string | null;
transcriptsDir: string | null;
/** Per-HTTP-call timeout in ms. Default 300_000 (5 min) — reasoner + harvest runs legitimately need this. */
timeoutMs: number;
dry: boolean;
verbose: boolean;
}
function parseArgs(argv: string[]): CliArgs {
const out: CliArgs = {
taskFilter: null,
modes: [...ALL_MODES],
repeats: 1,
outPath: null,
transcriptsDir: null,
timeoutMs: 300_000,
dry: false,
verbose: false,
};
for (let i = 0; i < argv.length; i++) {
const a = argv[i];
if (a === "--task") out.taskFilter = argv[++i] ?? null;
else if (a === "--mode") {
const v = (argv[++i] ?? "").toLowerCase() as HarvestMode;
if ((ALL_MODES as string[]).includes(v)) out.modes = [v];
} else if (a === "--repeats") out.repeats = Number.parseInt(argv[++i] ?? "1", 10);
else if (a === "--out") out.outPath = argv[++i] ?? null;
else if (a === "--transcripts-dir") out.transcriptsDir = argv[++i] ?? null;
else if (a === "--timeout") {
// Accept seconds for humans, convert to ms internally.
const secs = Number.parseInt(argv[++i] ?? "300", 10);
if (Number.isFinite(secs) && secs > 0) out.timeoutMs = secs * 1000;
} else if (a === "--dry") out.dry = true;
else if (a === "--verbose" || a === "-v") out.verbose = true;
}
return out;
}
// ---------- model resolution ----------
function modelForMode(mode: HarvestMode): string {
if (mode === "baseline") return "deepseek-chat";
return "deepseek-reasoner";
}
function harvestForMode(mode: HarvestMode): boolean {
return mode === "reasoner-harvest";
}
// ---------- run one task in one mode ----------
async function runOnce(
task: HarvestTask,
mode: HarvestMode,
rep: number,
client: DeepSeekClient,
transcriptStream: WriteStream | null,
): Promise<HarvestRunResult> {
const model = modelForMode(mode);
const harvest = harvestForMode(mode);
const prefix = new ImmutablePrefix({ system: task.systemPrompt });
const loop = new CacheFirstLoop({
client,
prefix,
model,
harvest,
stream: false,
});
const prefixHash = prefix.fingerprint;
let harvestedTurns = 0;
let totalSubgoals = 0;
let totalUncertainties = 0;
let totalHypotheses = 0;
let totalRejectedPaths = 0;
let finalText = "";
let errorMessage: string | undefined;
if (transcriptStream) {
writeRecord(transcriptStream, {
ts: new Date().toISOString(),
turn: 1,
role: "user",
content: task.prompt,
});
}
try {
for await (const ev of loop.step(task.prompt)) {
if (transcriptStream && ev.role !== "assistant_delta") {
writeRecord(transcriptStream, recordFromLoopEvent(ev, { model, prefixHash }));
}
if (ev.role === "assistant_final") {
finalText = ev.content;
if (ev.planState) {
if (
ev.planState.subgoals.length +
ev.planState.hypotheses.length +
ev.planState.uncertainties.length +
ev.planState.rejectedPaths.length >
0
) {
harvestedTurns++;
totalSubgoals += ev.planState.subgoals.length;
totalHypotheses += ev.planState.hypotheses.length;
totalUncertainties += ev.planState.uncertainties.length;
totalRejectedPaths += ev.planState.rejectedPaths.length;
}
}
} else if (ev.role === "done") {
finalText = ev.content || finalText;
break;
} else if (ev.role === "error") {
throw new Error(ev.error ?? "loop error");
}
}
} catch (err) {
errorMessage = (err as Error).message;
}
const verdict = errorMessage ? { verdict: "fail" as const, note: errorMessage } : task.check(finalText);
return {
taskId: task.id,
mode,
repeat: rep + 1,
verdict: verdict.verdict,
checkNote: verdict.note,
finalAgentMessage: finalText,
turns: loop.stats.turns.length,
cacheHitRatio: loop.stats.aggregateCacheHitRatio,
costUsd: loop.stats.totalCost,
claudeEquivalentUsd: loop.stats.turns.reduce((s, t) => s + claudeEquivalentCost(t.usage), 0),
harvestedTurns,
totalSubgoals,
totalUncertainties,
totalHypotheses,
totalRejectedPaths,
errorMessage,
};
}
// ---------- dry mode ----------
function runDry(args: CliArgs): HarvestBenchReport {
const tasks = filterTasks(args.taskFilter);
const results: HarvestRunResult[] = [];
for (const task of tasks) {
// Exercise each checker with a deliberately wrong reply so we know
// the wiring is live — not a pass on empty.
const sanity = task.check("Answer: this is not the right answer at all");
console.log(`[${task.id}] checker exercises ok (sanity verdict=${sanity.verdict})`);
for (const mode of args.modes) {
results.push({
taskId: task.id,
mode,
repeat: 1,
verdict: "inconclusive",
checkNote: "dry-run (no model call)",
finalAgentMessage: "[dry-run]",
turns: 0,
cacheHitRatio: 0,
costUsd: 0,
claudeEquivalentUsd: 0,
harvestedTurns: 0,
totalSubgoals: 0,
totalUncertainties: 0,
totalHypotheses: 0,
totalRejectedPaths: 0,
});
}
}
return { meta: buildMeta(args, tasks.length), results };
}
// ---------- main ----------
function filterTasks(filter: string | null): HarvestTask[] {
if (!filter) return TASKS;
const t = TASKS.find((x) => x.id === filter);
if (!t) throw new Error(`unknown task: ${filter}`);
return [t];
}
function buildMeta(args: CliArgs, taskCount: number): HarvestBenchMeta {
return {
date: new Date().toISOString(),
repeatsPerTask: args.repeats,
taskCount,
modesRun: args.modes,
reasonixVersion: "0.2.2",
};
}
async function main(): Promise<void> {
const args = parseArgs(process.argv.slice(2));
if (args.dry) {
const report = runDry(args);
writeReport(report, args.outPath);
return;
}
const client = new DeepSeekClient({ timeoutMs: args.timeoutMs });
const tasks = filterTasks(args.taskFilter);
if (args.transcriptsDir) mkdirSync(args.transcriptsDir, { recursive: true });
const results: HarvestRunResult[] = [];
for (const task of tasks) {
for (let rep = 0; rep < args.repeats; rep++) {
for (const mode of args.modes) {
let stream: WriteStream | null = null;
if (args.transcriptsDir) {
const fname = `${task.id}.${mode}.r${rep + 1}.jsonl`;
stream = openTranscriptFile(join(args.transcriptsDir, fname), {
version: 1,
source: `harvest-bench/${mode}`,
model: modelForMode(mode),
task: task.id,
mode,
repeat: rep + 1,
startedAt: new Date().toISOString(),
});
}
const started = Date.now();
let result: HarvestRunResult;
try {
result = await runOnce(task, mode, rep, client, stream);
} finally {
stream?.end();
}
const elapsed = ((Date.now() - started) / 1000).toFixed(1);
console.log(
`[${task.id}/${mode}/r${rep + 1}] verdict=${result.verdict}` +
` cache=${(result.cacheHitRatio * 100).toFixed(1)}%` +
` cost=$${result.costUsd.toFixed(6)}` +
` harvest=${result.harvestedTurns}:${result.totalSubgoals}s/${result.totalUncertainties}u` +
` (${elapsed}s)` +
(result.checkNote ? ` ${result.checkNote}` : ""),
);
results.push(result);
}
}
}
const report: HarvestBenchReport = { meta: buildMeta(args, tasks.length), results };
writeReport(report, args.outPath);
}
function writeReport(report: HarvestBenchReport, outPath: string | null): void {
const path =
outPath ?? `benchmarks/harvest/results-${new Date().toISOString().replace(/[:.]/g, "-")}.json`;
writeFileSync(path, `${JSON.stringify(report, null, 2)}\n`, "utf8");
console.log(`wrote ${path}`);
}
function isMain(): boolean {
const entry = process.argv[1];
if (!entry) return false;
return import.meta.url === pathToFileURL(entry).href;
}
if (isMain()) {
main().catch((err) => {
console.error(err);
process.exit(1);
});
}
export { main as runHarvestBench };
+171
View File
@@ -0,0 +1,171 @@
/**
* Seed reasoning tasks for the harvest eval harness.
*
* Each task has:
* - a minimal system prompt (so the comparison is about the model, not
* the prompt)
* - a single user question
* - a deterministic checker (regex + set/value compare)
*
* When adding a new task, prefer problems where:
* - the answer has a clean shape (a number, a small set, a yes/no +
* explanation) — easier to check
* - reasoning actually matters (so harvest has signal to extract);
* trivia questions are out of scope
* - there's a known-good answer; judgment calls are out of scope
*/
import type { HarvestTask } from "./types.js";
const CONCISE_SYSTEM = `You are a precise reasoner. Think carefully, then state your final answer on a clearly-labeled line starting with "Answer:".`;
/**
* Parse all non-negative integers out of a string. Handles commas,
* ranges written as "2-4" (expands to 2,3,4), and ignores numbers that
* look like formula references (e.g. "n^2", "mod 7") by only accepting
* integers after we strip common LaTeX decorations.
*/
function extractIntegers(text: string): number[] {
// Strip LaTeX delimiters so n_1 / n^2 / \{ ... \} don't confuse us.
const cleaned = text
.replace(/\\[a-zA-Z]+/g, " ") // \frac, \mod etc.
.replace(/[{}\\]/g, " ")
.replace(/[_^]\d+/g, " "); // subscript/superscript numbers
// Expand ranges: "2-4" → "2,3,4" (only for small gaps)
const rangeExpanded = cleaned.replace(/(\d+)\s*[-–]\s*(\d+)/g, (_, a, b) => {
const lo = Number.parseInt(a, 10);
const hi = Number.parseInt(b, 10);
if (!Number.isFinite(lo) || !Number.isFinite(hi) || hi - lo > 50) return `${a} ${b}`;
const out: number[] = [];
for (let i = Math.min(lo, hi); i <= Math.max(lo, hi); i++) out.push(i);
return out.join(" ");
});
const matches = rangeExpanded.match(/-?\d+/g) ?? [];
return matches.map((m) => Number.parseInt(m, 10)).filter((n) => Number.isFinite(n));
}
/** Extract content after the last "Answer:" label (case-insensitive). */
function extractAnswerLine(text: string): string {
const matches = [...text.matchAll(/answer\s*[::]\s*([^\n]+)/gi)];
if (matches.length === 0) return text;
return matches[matches.length - 1]![1]!.trim();
}
// ---------- expected answers ----------
/** Positive n ≤ 100 such that n^2 + n + 1 ≡ 0 (mod 7). */
const MOD7_EXPECTED: number[] = (() => {
const out: number[] = [];
for (let n = 1; n <= 100; n++) {
if ((n * n + n + 1) % 7 === 0) out.push(n);
}
return out;
})();
/**
* Single-integer checker. Pulls the first plausible integer from the last
* "Answer:" line; compares for exact equality.
*/
function checkSingleInt(expected: number) {
return (reply: string) => {
const answerLine = extractAnswerLine(reply);
const nums = extractIntegers(answerLine);
if (nums.length === 0) return { verdict: "fail" as const, note: "no number in Answer line" };
const n = nums[0]!;
if (n === expected) return { verdict: "pass" as const };
return { verdict: "fail" as const, note: `got ${n}, expected ${expected}` };
};
}
// ---------- tasks ----------
export const TASKS: HarvestTask[] = [
{
id: "mod7_list",
description:
"Number theory — find all positive n ≤ 100 with n^2+n+1 ≡ 0 (mod 7). 29-element set. Classic R1 scratch-work territory.",
systemPrompt: CONCISE_SYSTEM,
prompt:
"Find all positive integers n with n ≤ 100 such that n^2 + n + 1 is divisible by 7. Briefly justify, then end with the full list on a line starting with \"Answer:\".",
check: (reply) => {
const answerLine = extractAnswerLine(reply);
const found = new Set(extractIntegers(answerLine).filter((n) => n >= 1 && n <= 100));
const expected = new Set(MOD7_EXPECTED);
if (found.size === 0) {
return { verdict: "fail", note: "no integers extracted from Answer line" };
}
// Exact set equality — both containment directions.
for (const n of expected) if (!found.has(n)) return { verdict: "fail", note: `missing n=${n}` };
for (const n of found) if (!expected.has(n)) return { verdict: "fail", note: `extra n=${n}` };
return { verdict: "pass" };
},
},
{
id: "flips_until_3heads",
description:
"Probability — expected coin flips until 3 consecutive heads. Answer: 14. Tests whether R1 derives via recurrence or via memorized result.",
systemPrompt: CONCISE_SYSTEM,
prompt:
"A fair coin is flipped repeatedly until you see 3 heads in a row. What is the expected number of total flips? Give a single integer on a line starting with \"Answer:\".",
check: (reply) => {
const answerLine = extractAnswerLine(reply);
const nums = extractIntegers(answerLine);
if (nums.length === 0) return { verdict: "fail", note: "no number in Answer line" };
// Accept the first sensible number — sometimes agents write "Answer: 14 flips".
const n = nums[0]!;
if (n === 14) return { verdict: "pass" };
return { verdict: "fail", note: `got ${n}, expected 14` };
},
},
{
id: "three_hats",
description:
"Logic — three people wear red/blue hats, at least one red, they're asked in order. First two say no, third says yes. What color? Answer: red (deducible because if third were blue, the first two could see one red + one unknown and wouldn't have said no on their full first round, for most configurations the third can only be certain if red).",
systemPrompt: CONCISE_SYSTEM,
prompt:
'Three people wear hats that are each red or blue. They are told at least one hat is red. Each can see the other two hats but not their own. They are asked in order: "Do you know your hat color?" The first two answer no. The third answers yes. What color is the third person\'s hat? Give a one-word answer on a line starting with "Answer:".',
check: (reply) => {
const answerLine = extractAnswerLine(reply).toLowerCase();
// Accept "red" as a standalone word (not "redirected" etc).
if (/\bred\b/.test(answerLine) && !/\bblue\b/.test(answerLine)) {
return { verdict: "pass" };
}
if (/\bblue\b/.test(answerLine)) return { verdict: "fail", note: "answered blue" };
return { verdict: "fail", note: "no clear color in Answer line" };
},
},
// ---------- hard tasks (picked for known V3 failure modes) ----------
{
id: "pseudoprime_base2",
description:
"Number theory — smallest composite n > 1 such that 2^n ≡ 2 (mod n). This is the smallest Fermat pseudoprime to base 2. Answer: 341 (= 11·31). V3 frequently answers 561 (Carmichael / wrong base-2 property) or 9 (not actually a pseudoprime to base 2, verifying the model isn't computing). R1 usually gets this right.",
systemPrompt: CONCISE_SYSTEM,
prompt:
'Find the smallest composite integer n > 1 such that 2^n is congruent to 2 modulo n (i.e., n is a Fermat pseudoprime to base 2). Briefly justify, then give a single integer on a line starting with "Answer:".',
check: checkSingleInt(341),
},
{
id: "derangements_d7",
description:
"Combinatorics — number of derangements of 7 elements. Answer: 1854 (D_7 = 7! · (1 − 1/1! + 1/2! − 1/3! + … ± 1/7!) = 5040 · 0.367857… = 1854). V3 sometimes approximates via n!/e and rounds wrong, or confuses with D_6=265 or D_8=14833. R1's explicit recurrence D_n = (n-1)(D_{n-1}+D_{n-2}) avoids the mistake.",
systemPrompt: CONCISE_SYSTEM,
prompt:
'How many permutations of {1, 2, 3, 4, 5, 6, 7} have no fixed points? (This is D_7, the derangement number.) Briefly justify, then give a single integer on a line starting with "Answer:".',
check: checkSingleInt(1854),
},
{
id: "euler_quadratic_break",
description:
"Number theory — smallest nonneg integer n where n^2 + n + 41 is NOT prime. Euler's prime-generating polynomial famously produces primes for n = 0..39 and first fails at n = 40 (40²+40+41 = 1681 = 41²). V3 often confuses this with the related n²-n+41 (first fails at 41) or cites the wrong threshold. R1 checks small n systematically.",
systemPrompt: CONCISE_SYSTEM,
prompt:
'Consider the polynomial f(n) = n^2 + n + 41 for n = 0, 1, 2, …. What is the smallest nonneg integer n at which f(n) fails to be prime? Briefly justify (including the value of f(n) at that point), then give just the integer n on a line starting with "Answer:".',
check: checkSingleInt(40),
},
];
+82
View File
@@ -0,0 +1,82 @@
/**
* Types for the harvest eval harness.
*
* Scope: this is deliberately NOT τ-bench-lite. These tasks:
* - are single-turn Q/A (no user simulator, no DB)
* - target reasoning-heavy problems (math, logic, planning)
* - use deterministic checkers (regex extraction + set/value compare),
* never an LLM judge
*
* The point is to measure Pillar 2 (harvest) the same way τ-bench-lite
* measures Pillar 1 (cache-first): isolate one variable, produce numbers
* anyone can reproduce.
*/
export type HarvestMode =
/** deepseek-chat, no Reasonix tricks. Floor reference for answer quality on reasoning tasks (V3 at its best). */
| "baseline"
/** deepseek-reasoner, no harvest. Isolates "does reasoner help over chat on these problems?" */
| "reasoner"
/** deepseek-reasoner + harvest. Isolates "does the extra V3 harvest call add quality / change behavior?" */
| "reasoner-harvest";
export const ALL_MODES: HarvestMode[] = ["baseline", "reasoner", "reasoner-harvest"];
/**
* Checker verdict. We don't use boolean directly because "maybe" is real
* — e.g. "answer in the right shape but can't verify without running the
* program". For v0.3 we only use {pass, fail}, but the shape leaves room.
*/
export type CheckVerdict = "pass" | "fail" | "inconclusive";
export interface HarvestTask {
id: string;
/** One-line human description, not shown to the model. */
description: string;
/** System prompt. Kept minimal so harvest signal can be attributed to the model, not to prompt engineering. */
systemPrompt: string;
/** The single question. */
prompt: string;
/**
* Check the agent's final reply. Returns pass/fail/inconclusive plus an
* optional one-line explanation the report can surface.
*
* IMPORTANT: must be pure and deterministic. No LLM calls, no file I/O.
*/
check: (agentReply: string) => { verdict: CheckVerdict; note?: string };
}
export interface HarvestRunResult {
taskId: string;
mode: HarvestMode;
repeat: number;
verdict: CheckVerdict;
checkNote?: string;
finalAgentMessage: string;
/** Turns the loop completed (usually 1 for a single-shot Q/A, > 1 if tool-calls happen). */
turns: number;
cacheHitRatio: number;
costUsd: number;
claudeEquivalentUsd: number;
/** Harvest-specific — only non-zero on reasoner-harvest mode. */
harvestedTurns: number;
totalSubgoals: number;
totalUncertainties: number;
totalHypotheses: number;
totalRejectedPaths: number;
/** Optional error message if the run crashed (model down, timeout, etc). */
errorMessage?: string;
}
export interface HarvestBenchMeta {
date: string;
repeatsPerTask: number;
taskCount: number;
modesRun: HarvestMode[];
reasonixVersion: string;
}
export interface HarvestBenchReport {
meta: HarvestBenchMeta;
results: HarvestRunResult[];
}
@@ -11,6 +11,9 @@ verify the cache-hit / cost claims *without running the bench*.
| `t01_address_happy.baseline.r1.jsonl` | Naive cache-hostile agent's record of the run |
| `t01_address_happy.reasonix.r1.jsonl` | Reasonix's record of the same task |
| `t01_address_happy.diff.md` | Output of `reasonix diff` on the two above |
| `mcp-demo.add.jsonl` | End-to-end run through the bundled demo MCP server. DeepSeek called the `add` tool; the second turn hit 96.6% cache, 94% cheaper than Claude at same token counts |
| `mcp-filesystem.jsonl` | End-to-end run through the **official external** `@modelcontextprotocol/server-filesystem`. 5 turns, 4 tool calls including a permission-denied recovery. Overall cache 96.7%, 97% cheaper than Claude. Proof that Cache-First generalizes to third-party MCP servers without any code change on our side |
| `mcp-multi-server.jsonl` | End-to-end run with **two MCP servers concurrently** — bundled demo (`demo_add`) + official `@modelcontextprotocol/server-filesystem` (`fs_write_file`). Model computed 17+25 on one server, wrote the result to a real file via the other. 5 turns, 4 tool calls across two subprocesses. **1 distinct prefix hash** held across all turns — Cache-First byte-stability survives running two MCP servers at once. Cache 81.1%, cost $0.00185, 95.9% cheaper than Claude |
## Verify for yourself
@@ -0,0 +1,6 @@
{"role":"_meta","meta":{"version":1,"source":"reasonix run","model":"deepseek-chat","startedAt":"2026-04-22T00:50:25.468Z"}}
{"ts":"2026-04-22T00:50:25.469Z","turn":1,"role":"user","content":"Use the add tool to compute 17+25, then briefly confirm the result."}
{"ts":"2026-04-22T00:50:28.556Z","turn":1,"role":"assistant_final","content":"I'll compute 17 + 25 using the add tool.","usage":{"prompt_tokens":442,"completion_tokens":70,"total_tokens":512,"prompt_cache_hit_tokens":0,"prompt_cache_miss_tokens":442},"cost":0.00019634,"model":"deepseek-chat","prefixHash":"585d4a0a16fe84b7"}
{"ts":"2026-04-22T00:50:28.557Z","turn":1,"role":"tool","content":"42","tool":"add","args":"{\"a\": 17, \"b\": 25}"}
{"ts":"2026-04-22T00:50:29.858Z","turn":1,"role":"assistant_final","content":"The result is 42. 17 + 25 = 42.","usage":{"prompt_tokens":530,"completion_tokens":15,"total_tokens":545,"prompt_cache_hit_tokens":512,"prompt_cache_miss_tokens":18},"cost":0.0000572,"model":"deepseek-chat","prefixHash":"585d4a0a16fe84b7"}
{"ts":"2026-04-22T00:50:29.858Z","turn":1,"role":"done","content":"The result is 42. 17 + 25 = 42."}
@@ -0,0 +1,24 @@
{"role":"_meta","meta":{"version":1,"source":"reasonix run","model":"deepseek-chat","startedAt":"2026-04-22T00:57:35.368Z"}}
{"ts":"2026-04-22T00:57:35.369Z","turn":1,"role":"user","content":"List the files here, then read README.md and summarize it in one sentence."}
{"ts":"2026-04-22T00:57:38.133Z","turn":1,"role":"assistant_final","content":"I'll start by listing the files in the current directory, then read the README.md file and summarize it.","usage":{"prompt_tokens":2218,"completion_tokens":64,"total_tokens":2282,"prompt_cache_hit_tokens":256,"prompt_cache_miss_tokens":1962},"cost":0.0006180599999999999,"model":"deepseek-chat","prefixHash":"6a7fff6a15fd5def"}
{"ts":"2026-04-22T00:57:38.136Z","turn":1,"role":"tool","content":"ERROR: Access denied - path outside allowed directories: F:\\Reasonix not in C:\\Users\\yuhuahui\\AppData\\Local\\Temp\\mcp-fs-demo","tool":"list_directory","args":"{\"path\": \".\"}"}
{"ts":"2026-04-22T00:57:40.282Z","turn":1,"role":"assistant_final","content":"Let me first check what directories are allowed:","usage":{"prompt_tokens":2337,"completion_tokens":39,"total_tokens":2376,"prompt_cache_hit_tokens":2240,"prompt_cache_miss_tokens":97},"cost":0.00022589000000000002,"model":"deepseek-chat","prefixHash":"6a7fff6a15fd5def"}
{"ts":"2026-04-22T00:57:40.285Z","turn":1,"role":"tool","content":"Allowed directories:\nC:\\Users\\yuhuahui\\AppData\\Local\\Temp\\mcp-fs-demo","tool":"list_allowed_directories","args":"{}"}
{"ts":"2026-04-22T00:57:43.982Z","turn":1,"role":"assistant_final","content":"Now let me list the files in the allowed directory:","usage":{"prompt_tokens":2418,"completion_tokens":74,"total_tokens":2492,"prompt_cache_hit_tokens":2304,"prompt_cache_miss_tokens":114},"cost":0.00027346000000000006,"model":"deepseek-chat","prefixHash":"6a7fff6a15fd5def"}
{"ts":"2026-04-22T00:57:43.983Z","turn":1,"role":"tool","content":"[FILE] a.txt\n[FILE] b.txt\n[FILE] README.md","tool":"list_directory","args":"{\"path\": \"C:\\\\Users\\\\yuhuahui\\\\AppData\\\\Local\\\\Temp\\\\mcp-fs-demo\"}"}
{"ts":"2026-04-22T00:57:47.317Z","turn":1,"role":"assistant_final","content":"Now let me read the README.md file:","usage":{"prompt_tokens":2526,"completion_tokens":77,"total_tokens":2603,"prompt_cache_hit_tokens":2432,"prompt_cache_miss_tokens":94},"cost":0.00028031999999999997,"model":"deepseek-chat","prefixHash":"6a7fff6a15fd5def"}
{"ts":"2026-04-22T00:57:47.322Z","turn":1,"role":"tool","content":"# Sample","tool":"read_text_file","args":"{\"path\": \"C:\\\\Users\\\\yuhuahui\\\\AppData\\\\Local\\\\Temp\\\\mcp-fs-demo\\\\README.md\"}"}
{"ts":"2026-04-22T00:57:49.096Z","turn":1,"role":"assistant_final","content":"**Summary:** The directory contains three files (a.txt, b.txt, and README.md), and the README.md file simply contains the word \"Sample\".","usage":{"prompt_tokens":2622,"completion_tokens":33,"total_tokens":2655,"prompt_cache_hit_tokens":2560,"prompt_cache_miss_tokens":62},"cost":0.00023224000000000004,"model":"deepseek-chat","prefixHash":"6a7fff6a15fd5def"}
{"ts":"2026-04-22T00:57:49.096Z","turn":1,"role":"done","content":"**Summary:** The directory contains three files (a.txt, b.txt, and README.md), and the README.md file simply contains the word \"Sample\"."}
{"role":"_meta","meta":{"version":1,"source":"reasonix run","model":"deepseek-chat","startedAt":"2026-04-22T01:00:29.520Z"}}
{"ts":"2026-04-22T01:00:29.521Z","turn":1,"role":"user","content":"List the files here, then read README.md and summarize it in one sentence."}
{"ts":"2026-04-22T01:00:32.502Z","turn":1,"role":"assistant_final","content":"I'll start by listing the files in the current directory and then read the README.md file.","usage":{"prompt_tokens":2218,"completion_tokens":61,"total_tokens":2279,"prompt_cache_hit_tokens":2176,"prompt_cache_miss_tokens":42},"cost":0.00023076000000000005,"model":"deepseek-chat","prefixHash":"6a7fff6a15fd5def"}
{"ts":"2026-04-22T01:00:32.505Z","turn":1,"role":"tool","content":"ERROR: Access denied - path outside allowed directories: F:\\Reasonix not in C:\\Users\\yuhuahui\\AppData\\Local\\Temp\\mcp-fs-demo","tool":"list_directory","args":"{\"path\": \".\"}"}
{"ts":"2026-04-22T01:00:34.833Z","turn":1,"role":"assistant_final","content":"Let me first check what directories are allowed:","usage":{"prompt_tokens":2334,"completion_tokens":39,"total_tokens":2373,"prompt_cache_hit_tokens":2240,"prompt_cache_miss_tokens":94},"cost":0.00022508,"model":"deepseek-chat","prefixHash":"6a7fff6a15fd5def"}
{"ts":"2026-04-22T01:00:34.834Z","turn":1,"role":"tool","content":"Allowed directories:\nC:\\Users\\yuhuahui\\AppData\\Local\\Temp\\mcp-fs-demo","tool":"list_allowed_directories","args":"{}"}
{"ts":"2026-04-22T01:00:38.039Z","turn":1,"role":"assistant_final","content":"Now let me list the files in the allowed directory:","usage":{"prompt_tokens":2415,"completion_tokens":74,"total_tokens":2489,"prompt_cache_hit_tokens":2304,"prompt_cache_miss_tokens":111},"cost":0.00027265000000000004,"model":"deepseek-chat","prefixHash":"6a7fff6a15fd5def"}
{"ts":"2026-04-22T01:00:38.042Z","turn":1,"role":"tool","content":"[FILE] a.txt\n[FILE] b.txt\n[FILE] README.md","tool":"list_directory","args":"{\"path\": \"C:\\\\Users\\\\yuhuahui\\\\AppData\\\\Local\\\\Temp\\\\mcp-fs-demo\"}"}
{"ts":"2026-04-22T01:00:41.597Z","turn":1,"role":"assistant_final","content":"Now I'll read the README.md file:","usage":{"prompt_tokens":2523,"completion_tokens":77,"total_tokens":2600,"prompt_cache_hit_tokens":2432,"prompt_cache_miss_tokens":91},"cost":0.00027951,"model":"deepseek-chat","prefixHash":"6a7fff6a15fd5def"}
{"ts":"2026-04-22T01:00:41.601Z","turn":1,"role":"tool","content":"# Sample","tool":"read_text_file","args":"{\"path\": \"C:\\\\Users\\\\yuhuahui\\\\AppData\\\\Local\\\\Temp\\\\mcp-fs-demo\\\\README.md\"}"}
{"ts":"2026-04-22T01:00:43.759Z","turn":1,"role":"assistant_final","content":"**Files in the directory:** a.txt, b.txt, README.md\n\n**README.md summary:** This is a sample README file.","usage":{"prompt_tokens":2619,"completion_tokens":29,"total_tokens":2648,"prompt_cache_hit_tokens":2560,"prompt_cache_miss_tokens":59},"cost":0.00022703000000000003,"model":"deepseek-chat","prefixHash":"6a7fff6a15fd5def"}
{"ts":"2026-04-22T01:00:43.759Z","turn":1,"role":"done","content":"**Files in the directory:** a.txt, b.txt, README.md\n\n**README.md summary:** This is a sample README file."}
@@ -0,0 +1,12 @@
{"role":"_meta","meta":{"version":1,"source":"reasonix run","model":"deepseek-chat","startedAt":"2026-04-22T01:39:54.789Z"}}
{"ts":"2026-04-22T01:39:54.790Z","turn":1,"role":"user","content":"First use the add tool to compute 17+25, then use write_file to save the result to a file called answer.txt in the current working directory."}
{"ts":"2026-04-22T01:39:58.843Z","turn":1,"role":"assistant_final","content":"I'll help you with that. First, I'll compute 17+25 using the add tool, then write the result to answer.txt.","usage":{"prompt_tokens":2404,"completion_tokens":87,"total_tokens":2491,"prompt_cache_hit_tokens":256,"prompt_cache_miss_tokens":2148},"cost":0.0006935800000000001,"model":"deepseek-chat","prefixHash":"ea71560eab18d572"}
{"ts":"2026-04-22T01:39:58.844Z","turn":1,"role":"tool","content":"42","tool":"demo_add","args":"{\"a\": 17, \"b\": 25}"}
{"ts":"2026-04-22T01:40:02.898Z","turn":1,"role":"assistant_final","content":"Now I'll write the result (42) to a file called answer.txt in the current working directory:","usage":{"prompt_tokens":2509,"completion_tokens":81,"total_tokens":2590,"prompt_cache_hit_tokens":2432,"prompt_cache_miss_tokens":77},"cost":0.00028013,"model":"deepseek-chat","prefixHash":"ea71560eab18d572"}
{"ts":"2026-04-22T01:40:02.900Z","turn":1,"role":"tool","content":"ERROR: Access denied - path outside allowed directories: F:\\Reasonix\\answer.txt not in C:\\Users\\yuhuahui\\AppData\\Local\\Temp\\mcp-fs-demo","tool":"fs_write_file","args":"{\"path\": \"answer.txt\", \"content\": \"42\"}"}
{"ts":"2026-04-22T01:40:05.263Z","turn":1,"role":"assistant_final","content":"I need to check which directories are allowed first. Let me check the allowed directories:","usage":{"prompt_tokens":2648,"completion_tokens":48,"total_tokens":2696,"prompt_cache_hit_tokens":2560,"prompt_cache_miss_tokens":88},"cost":0.00025576,"model":"deepseek-chat","prefixHash":"ea71560eab18d572"}
{"ts":"2026-04-22T01:40:05.270Z","turn":1,"role":"tool","content":"Allowed directories:\nC:\\Users\\yuhuahui\\AppData\\Local\\Temp\\mcp-fs-demo","tool":"fs_list_allowed_directories","args":"{}"}
{"ts":"2026-04-22T01:40:09.422Z","turn":1,"role":"assistant_final","content":"Now I'll write the file to the allowed directory:","usage":{"prompt_tokens":2738,"completion_tokens":94,"total_tokens":2832,"prompt_cache_hit_tokens":2624,"prompt_cache_miss_tokens":114},"cost":0.00031786,"model":"deepseek-chat","prefixHash":"ea71560eab18d572"}
{"ts":"2026-04-22T01:40:09.426Z","turn":1,"role":"tool","content":"Successfully wrote to C:\\Users\\yuhuahui\\AppData\\Local\\Temp\\mcp-fs-demo\\answer.txt","tool":"fs_write_file","args":"{\"path\": \"C:\\\\Users\\\\yuhuahui\\\\AppData\\\\Local\\\\Temp\\\\mcp-fs-demo\\\\answer.txt\", \"content\": \"42\"}"}
{"ts":"2026-04-22T01:40:13.689Z","turn":1,"role":"assistant_final","content":"Perfect! I've completed both tasks:\n\n1. **Computed 17+25**: The result is 42\n2. **Saved to answer.txt**: Created the file `answer.txt` in the allowed directory with the content \"42\"\n\nThe file has been successfully written to `C:\\Users\\yuhuahui\\AppData\\Local\\Temp\\mcp-fs-demo\\answer.txt`.","usage":{"prompt_tokens":2878,"completion_tokens":83,"total_tokens":2961,"prompt_cache_hit_tokens":2816,"prompt_cache_miss_tokens":62},"cost":0.00030516,"model":"deepseek-chat","prefixHash":"ea71560eab18d572"}
{"ts":"2026-04-22T01:40:13.689Z","turn":1,"role":"done","content":"Perfect! I've completed both tasks:\n\n1. **Computed 17+25**: The result is 42\n2. **Saved to answer.txt**: Created the file `answer.txt` in the allowed directory with the content \"42\"\n\nThe file has been successfully written to `C:\\Users\\yuhuahui\\AppData\\Local\\Temp\\mcp-fs-demo\\answer.txt`."}
Binary file not shown.
+166 -62
View File
@@ -6,7 +6,11 @@ Reasonix is **opinionated, not general**. Every abstraction is justified by a
DeepSeek-specific behavior or economic property. If it's generic, we don't
ship it.
## The three pillars
The product north star: **coding agent that stays cheap enough to leave on**.
A tool that quietly burns $200/month on a background project is one nobody
uses. Every subsystem below is answerable to that goal.
## The four pillars
### Pillar 1 — Cache-First Loop
@@ -37,49 +41,29 @@ timestamps each turn — cache hit rate in practice: <20%.
into the log.
**Metric.** `prompt_cache_hit_tokens / (hit + miss)` exposed per-turn and
aggregated per-session. This is the user-visible proof of Pillar 1's value.
aggregated per-session. Visible in the TUI's top-bar cache cell.
### Pillar 2 — R1 Thought Harvesting *(v0.0.3, opt-in)*
### Pillar 2 — R1 Thought Harvesting *(opt-in)*
**Problem.** R1 emits extensive `reasoning_content`. DeepSeek's own docs
recommend *not* feeding it back to the next turn. Most frameworks display it
to the user and discard. The planning signal inside is lost.
**Problem.** R1 / V4-thinking emits extensive `reasoning_content`. DeepSeek's
own docs recommend *not* feeding it back to the next turn. Most frameworks
display it to the user and discard. The planning signal inside is lost.
**Solution.** A two-stage process:
```
R1 output → Harvester (V3, cheap) → TypedPlanState
├─ subgoals: string[]
├─ hypotheses: string[]
├─ uncertainties: string[]
└─ rejectedPaths: string[]
R1 output → Harvester (v4-flash, thinking off) → TypedPlanState
├─ subgoals: string[]
├─ hypotheses: string[]
├─ uncertainties: string[]
└─ rejectedPaths: string[]
```
The harvester is a cheap V3 call with a strict JSON schema. Output is
validated at runtime. The typed state is queryable by the orchestrator — e.g.
"if `uncertainties.length > 2`, trigger branch sampling."
The harvester is a cheap flash call with a strict JSON schema. Output is
validated at runtime. **Not enabled in any preset** (see Pillar 4) — the
additional round-trip rarely pays back, so it's `/harvest on` opt-in.
### Branch-and-Select *(v0.0.5, opt-in, builds on Pillar 2)*
**Why now.** DeepSeek is cheap enough that running N=3 R1 samples is still
cheaper than a single Claude call. What was research luxury (self-consistency
sampling) becomes a practical default.
**How.** When `--branch N` (or `{ branch: N }` in code) is passed:
1. The turn is forced non-streaming (N samples must complete before we can
compare).
2. `runBranches` fires N `client.chat` calls in parallel, spreading
temperatures across `[0, 1]` to diversify reasoning paths.
3. Each sample's `reasoning_content` is piped through Pillar 2's harvest.
4. The default selector picks the sample with the fewest `uncertainties`;
ties are broken by shorter answer length (Occam).
5. The loop emits a `branch_summary` alongside the winning `assistant_final`.
**Cost.** 3× R1 on a hard math problem ≈ \$0.02 — still dominates Claude on
cost/quality for agentic work.
### Pillar 3 — Tool-Call Repair *(v0.0.1 ships complete)*
### Pillar 3 — Tool-Call Repair
**Problem.** Empirical DeepSeek failure modes:
- Tool-call JSON emitted inside `<think>`, missing from the final message.
@@ -92,7 +76,6 @@ cost/quality for agentic work.
1. **`flatten`** — schemas with >10 leaf params or depth >2 are auto-detected
on `ToolRegistry.register()` and presented to the model in dot-notation
form. `dispatch()` re-nests the args before calling the user's `fn`.
Opt out with `new ToolRegistry({ autoFlatten: false })`.
2. **`scavenge`** — regex + JSON parser sweeps `reasoning_content` for any tool
call the model forgot to emit in `tool_calls`.
3. **`truncation`** — detect unbalanced JSON and repair by closing braces or
@@ -100,48 +83,169 @@ cost/quality for agentic work.
4. **`storm`** — identical `(tool, args)` tuple within a sliding window →
suppress the call, inject a reflection turn.
### Pillar 4 — Cost Control *(v0.6)*
**Problem.** Coding agents that default to the frontier model (v4-pro, ~12×
flash cost) and accumulate full tool results in context are $150-$250/month
for active users. Most turns don't need frontier reasoning; most sessions
re-pay for tool results that were only useful once.
**Solution.** Four complementary mechanisms, none of which require manual
tuning in the common case:
#### 4.1 Tiered defaults (flash-first)
The three presets now trade only **model tier** and **reasoning effort**:
| Preset | Model | Effort | Harvest | Branch | Cost |
|---|---|---|---|---|---:|
| `fast` | `v4-flash` | `high` | off | 1 | 1× |
| `smart` (default) | `v4-flash` | `max` | off | 1 | ~1.5× |
| `max` | `v4-pro` | `max` | off | 1 | ~12× |
**Branching and harvest are never in a preset.** Both multiply cost and
rarely pay back; `/branch N` and `/harvest on` are pure opt-ins. A user can
run for weeks without ever touching them.
All auxiliary calls — `forceSummaryAfterIterLimit`, subagent spawns,
truncation repair retries — hard-code `v4-flash + effort=high` regardless
of the user's preset. There's no reason to pay pro rates for "paraphrase
these tool results into prose" or for an `explore` subagent's grep chain.
#### 4.2 Turn-end auto-compaction
Every tool result in the log exceeding `TURN_END_RESULT_CAP_TOKENS` (3000)
is shrunk to that cap when a turn ends. The model had the full text for
the turn that read it; subsequent turns see a compact summary and can
re-read if needed. One extra `read_file` call is vastly cheaper than
dragging 12KB through every future prompt.
A proactive 40% context-ratio threshold runs the same shrink pre-emptively
inside long multi-iter turns before the 80% emergency threshold fires.
#### 4.3 `/pro` single-turn arming
Users who predict a hard task type `/pro`; the **next** turn runs on
`v4-pro`, then auto-disarms. No preset churn, no forgotten revert. Armed
state is visible as a yellow `⇧ pro armed` pill in the header.
#### 4.4 Failure-signal auto-escalation
The loop counts visible "flash is struggling" events per turn:
- `edit_file` / `write_file` SEARCH-not-found errors
- ToolCallRepair fires (scavenge / truncation-fix / storm-break)
Once the count hits `FAILURE_ESCALATION_THRESHOLD` (3), the **remainder of
the current turn** runs on `v4-pro`. Announced via a yellow warning row —
no silent cost surprises. Counter + escalation flag reset at every turn
start.
Header shows a red `⇧ pro escalated` pill while the turn is on pro.
#### Cost transparency
Per-turn and session cost are colored in the StatsPanel:
- `turn $0.003` — green <$0.05, yellow $0.05–0.20, red ≥$0.20
- `session $0.12` — same scale ×10
## Module layout
```
src/
├── client.ts # httpx-equivalent DeepSeek client (fetch + SSE)
├── loop.ts # Pillar 1: Cache-First Loop (async iterator)
├── harvest.ts # Pillar 2 stub (v0.0.1 surface only)
├── repair/
│ ├── index.ts # Pillar 3 pipeline
├── client.ts # DeepSeek client (fetch + SSE)
├── loop.ts # Pillar 1 + 4 — CacheFirstLoop
├── harvest.ts # Pillar 2 — flash-backed plan-state extraction
├── repair/ # Pillar 3 pipeline
│ ├── index.ts
│ ├── scavenge.ts
│ ├── flatten.ts
│ ├── truncation.ts
│ └── storm.ts
├── tools.ts # Tool registry + dispatch
├── memory.ts # Prefix / Log / Scratch primitives
├── telemetry.ts # Cost & cache-hit accounting
├── types.ts # Shared type definitions
├── index.ts # Library barrel export
├── prompt-fragments.ts # TUI_FORMATTING_RULES, NEGATIVE_CLAIM_RULE —
│ # reused by main + subagent + skill prompts
├── code/prompt.ts # reasonix code main system prompt
├── tools/ # Tool implementations
│ ├── filesystem.ts # read / list / search / edit / write
│ ├── shell.ts # run_command + run_background (JobRegistry)
│ ├── jobs.ts # background-process registry
│ ├── memory.ts # remember / forget / list user memories
│ ├── skills.ts # list + invoke SKILL.md playbooks
│ ├── subagent.ts # spawn_subagent — flash+high by default
│ ├── plan.ts # submit_plan (review gate)
│ └── web.ts # web_search, web_fetch
├── mcp/ # MCP client + bridge (stdio + SSE)
├── memory.ts # ImmutablePrefix / AppendOnlyLog / VolatileScratch
├── project-memory.ts # REASONIX.md loader
├── user-memory.ts # ~/.reasonix/memory/ store (project + global)
├── skills.ts # built-in explore + research skills
├── session.ts # JSONL session persistence
├── telemetry.ts # cost + cache-hit accounting + SessionSummary
├── tokenizer.ts # DeepSeek V3 tokenizer (ported)
├── usage.ts # ~/.reasonix/usage.jsonl roll-up
├── types.ts # ChatMessage, ToolCall, ToolSpec
├── index.ts # library barrel
└── cli/
├── index.ts # commander entry
├── commands/ # chat, run, stats, version
└── ui/ # Ink React components (App, StatsPanel, EventLog, PromptInput)
├── index.ts # commander entry
├── resolve.ts # config + CLI flag precedence
├── commands/ # chat, code, run, stats, sessions, ...
└── ui/
├── App.tsx # root Ink component (~1984 LOC, was 2931)
├── LiveRows.tsx # spinner rows (OngoingTool / Status / ...)
├── EventLog.tsx # Historical row rendering
├── StatsPanel.tsx # top bar + cost badges
├── PromptInput.tsx # cursor-aware multi-line input
├── PlanConfirm.tsx # submit_plan review modal
├── ShellConfirm.tsx # run_command approval modal
├── EditConfirm.tsx # per-edit review modal
├── markdown.tsx # Ink-native markdown renderer
├── edit-history.ts # EditHistoryEntry + formatters
├── useEditHistory.ts # /undo, /history, /show state machine
├── useCompletionPickers.ts # slash, @, slash-arg pickers
├── useSessionInfo.ts # balance + models + updates fetch
├── useSubagent.ts # subagent sink wiring
└── slash/ # /-command implementation
├── types.ts # SlashContext, SlashResult, ...
├── commands.ts # SLASH_COMMANDS data + parse + suggest
├── helpers.ts # git, memory, token formatters
├── dispatch.ts # registry + handleSlash lookup
└── handlers/ # per-topic: basic, mcp, memory,
# skill, admin, observability, edits,
# jobs, sessions, model (/pro lives here)
```
## Roadmap
Files kept small by design: the largest module under `cli/ui/` is 2K
lines (App.tsx), every handler under `slash/handlers/` is ≤200 lines,
every hook under `cli/ui/` is ≤310 lines. Adding a new slash command
means editing one handler file and one registry line.
- **v0.0.1** — Pillar 1 end-to-end, Pillar 3 complete, Ink TUI, τ-bench scaffold.
- **v0.0.2** — First-run key prompt, saved to `~/.reasonix/config.json`.
- **v0.0.3** — Pillar 2 MVP (opt-in harvest), retry layer, TextInput fix.
- **v0.0.4** — Schema flatten auto-applied in ToolRegistry (closes Pillar 3).
- **v0.0.5** — Self-consistency branching (`--branch N`) driven by Pillar 2
plan-state uncertainty count.
- **v0.0.6** — Named session persistence (`--session <name>`), JSONL log
stored under `~/.reasonix/sessions/`, restored into the append-only log
on resume.
## Design evolution
- **v0.0.x** — Pillar 1 end-to-end, Pillar 3 complete, Ink TUI scaffold.
- **v0.1** — τ-bench numbers published, streaming polish, transcript replay.
- **v0.2** — Self-consistency / branch-budget sampling driven by plan state.
- **v0.3** — MCP client, session persistence.
- **v0.3** — MCP client (stdio + SSE), session persistence.
- **v0.4.x** — `reasonix code` with SEARCH/REPLACE edits, review/auto
gate, background jobs, hooks.
- **v0.5.x** — V4 model support, skills, memory, subagents, actionable
error messages.
- **v0.6** *(current)* —
- **Pillar 4 cost control** (flash-first defaults, auto-compaction,
`/pro` one-shot, failure-triggered escalation, cost badges).
- `deepseek-chat` / `deepseek-reasoner` scheduled for deprecation —
all user-facing surfaces updated to `v4-flash` / `v4-pro`.
- `branch` + `harvest` removed from every preset; manual opt-in only.
- Shared prompt fragments (`TUI_FORMATTING_RULES`, `NEGATIVE_CLAIM_RULE`).
- UI refactor: App.tsx split into 6 hooks/components, slash.ts split
into 13 per-topic modules.
## Explicit non-goals
- Multi-agent orchestration.
- Multi-agent orchestration as a first-class concept (subagents are a
cost-reduction mechanism, not a coordination primitive).
- RAG / vector retrieval.
- Support for non-DeepSeek backends.
- Support for non-DeepSeek backends (an OpenAI-compatible shim would
work today via `--model` override, but is not tested).
- Web UI / SaaS.
- Automatic cost escalation without user-visible announcement. Every
pro-tier model call is surfaced; silent escalation was considered
and rejected.
+95
View File
@@ -0,0 +1,95 @@
<svg xmlns="http://www.w3.org/2000/svg" width="760" height="170" viewBox="0 0 760 170" role="img" aria-label="Reasonix — DeepSeek-native agent framework">
<title>Reasonix</title>
<defs>
<!-- Signature cyan → violet → fuchsia gradient used across the TUI wordmark
and the brand mark. Renders well on both GitHub dark and light bg. -->
<linearGradient id="rx-grad" x1="0%" y1="0%" x2="100%" y2="0%">
<stop offset="0%" stop-color="#5eead4"/>
<stop offset="15%" stop-color="#67e8f9"/>
<stop offset="30%" stop-color="#7dd3fc"/>
<stop offset="45%" stop-color="#93c5fd"/>
<stop offset="60%" stop-color="#a5b4fc"/>
<stop offset="75%" stop-color="#c4b5fd"/>
<stop offset="90%" stop-color="#d8b4fe"/>
<stop offset="100%" stop-color="#f0abfc"/>
</linearGradient>
<linearGradient id="rx-grad-mark" x1="0%" y1="0%" x2="100%" y2="100%">
<stop offset="0%" stop-color="#5eead4"/>
<stop offset="50%" stop-color="#93c5fd"/>
<stop offset="100%" stop-color="#c4b5fd"/>
</linearGradient>
<filter id="glow" x="-50%" y="-50%" width="200%" height="200%">
<feGaussianBlur stdDeviation="3" result="blur"/>
<feMerge>
<feMergeNode in="blur"/>
<feMergeNode in="SourceGraphic"/>
</feMerge>
</filter>
</defs>
<!-- ◈ brand mark: concentric diamonds. Outer stroke pulses,
inner fill breathes, whole group rotates slowly. The rotation
is subtle (12s / full turn) so it feels like a heartbeat, not a
spinner. -->
<g transform="translate(90, 85)" filter="url(#glow)">
<g>
<animateTransform attributeName="transform" type="rotate"
from="0" to="360" dur="18s" repeatCount="indefinite"/>
<!-- Outer hollow diamond -->
<path d="M 0,-46 L 46,0 L 0,46 L -46,0 Z"
fill="none"
stroke="url(#rx-grad-mark)"
stroke-width="3.5"
stroke-linejoin="round">
<animate attributeName="stroke-width"
values="3.5;5.5;3.5"
dur="2.4s"
repeatCount="indefinite"/>
</path>
<!-- Middle hollow diamond -->
<path d="M 0,-26 L 26,0 L 0,26 L -26,0 Z"
fill="none"
stroke="url(#rx-grad-mark)"
stroke-width="2"
stroke-linejoin="round"
opacity="0.7">
<animate attributeName="opacity"
values="0.4;0.9;0.4"
dur="2.4s"
begin="0.8s"
repeatCount="indefinite"/>
</path>
<!-- Inner solid diamond -->
<path d="M 0,-11 L 11,0 L 0,11 L -11,0 Z"
fill="url(#rx-grad-mark)">
<animate attributeName="opacity"
values="0.75;1;0.75"
dur="2.4s"
repeatCount="indefinite"/>
</path>
</g>
</g>
<!-- REASONIX wordmark with shifting gradient. The x1 offset animates
so the gradient crawls left-to-right across the letters — a
slow rainbow sweep that gives the logo life without being noisy. -->
<text x="170" y="102"
font-family="ui-monospace, SFMono-Regular, 'Cascadia Code', Menlo, Consolas, 'DejaVu Sans Mono', monospace"
font-size="68"
font-weight="800"
fill="url(#rx-grad)"
letter-spacing="6">REASONIX
<animate attributeName="opacity"
values="0.9;1;0.9"
dur="3.2s"
repeatCount="indefinite"/>
</text>
<!-- Tagline sits just below the wordmark. Slate-500 reads well on
both GitHub dark and light themes (~4.5:1 contrast either way). -->
<text x="172" y="136"
font-family="ui-monospace, SFMono-Regular, 'Cascadia Code', Menlo, Consolas, 'DejaVu Sans Mono', monospace"
font-size="15"
fill="#64748b"
letter-spacing="0.5">DeepSeek-native agent framework · cache-first loop · Ink TUI</text>
</svg>

After

Width:  |  Height:  |  Size: 3.8 KiB

+238
View File
@@ -0,0 +1,238 @@
/**
* Bundled demo MCP server.
*
* A minimal stdio MCP server that exposes three tools: echo, add, get_time.
* Useful for:
* - running the MCP integration end-to-end without installing
* an external server
* - giving the integration tests a real subprocess to spawn
* - showing the minimal shape of a server for folks writing their own
*
* Usage:
* npx tsx examples/mcp-server-demo.ts # speaks MCP on stdin/stdout
* reasonix chat --mcp "npx tsx examples/mcp-server-demo.ts"
*
* Spec reference: https://spec.modelcontextprotocol.io/ (2024-11-05)
* Only the subset this demo needs is implemented — initialize, tools/list,
* tools/call, notifications/initialized (no-op).
*/
import { createInterface } from "node:readline";
const PROTOCOL_VERSION = "2024-11-05";
interface JsonRpcRequest {
jsonrpc: "2.0";
id?: string | number;
method: string;
params?: unknown;
}
interface JsonRpcSuccess {
jsonrpc: "2.0";
id: string | number;
result: unknown;
}
interface JsonRpcError {
jsonrpc: "2.0";
id: string | number | null;
error: { code: number; message: string; data?: unknown };
}
const TOOLS = [
{
name: "echo",
description: "Echoes the provided message back.",
inputSchema: {
type: "object",
properties: { msg: { type: "string", description: "What to echo" } },
required: ["msg"],
},
},
{
name: "add",
description: "Adds two integers and returns the sum.",
inputSchema: {
type: "object",
properties: {
a: { type: "integer" },
b: { type: "integer" },
},
required: ["a", "b"],
},
},
{
name: "get_time",
description: "Returns the server's current ISO-8601 timestamp.",
inputSchema: { type: "object", properties: {} },
},
{
name: "slow_count",
description:
"Counts from 1 to n with a ~300 ms pause between steps, emitting notifications/progress frames along the way. Useful for demonstrating Reasonix's progress-bar UI.",
inputSchema: {
type: "object",
properties: {
n: { type: "integer", description: "Final number to count to (default 5, max 20)" },
},
},
},
];
interface JsonRpcNotification {
jsonrpc: "2.0";
method: string;
params?: unknown;
}
function send(msg: JsonRpcSuccess | JsonRpcError | JsonRpcNotification): void {
// Stdio MCP framing: one JSON per line.
process.stdout.write(`${JSON.stringify(msg)}\n`);
}
async function handleRequest(
req: JsonRpcRequest,
): Promise<JsonRpcSuccess | JsonRpcError | null> {
const id = req.id ?? null;
switch (req.method) {
case "initialize": {
return {
jsonrpc: "2.0",
id: id ?? 0,
result: {
protocolVersion: PROTOCOL_VERSION,
serverInfo: { name: "reasonix-demo-mcp", version: "0.0.1" },
capabilities: { tools: { listChanged: false } },
},
};
}
case "notifications/initialized":
// No response for notifications.
return null;
case "tools/list": {
return { jsonrpc: "2.0", id: id ?? 0, result: { tools: TOOLS } };
}
case "tools/call": {
const params = (req.params ?? {}) as {
name?: string;
arguments?: Record<string, unknown>;
_meta?: { progressToken?: string | number };
};
const name = params.name ?? "";
const args = params.arguments ?? {};
const progressToken = params._meta?.progressToken;
const out = await callTool(name, args, progressToken);
if (out.error) {
return {
jsonrpc: "2.0",
id: id ?? 0,
result: {
content: [{ type: "text", text: out.error }],
isError: true,
},
};
}
return {
jsonrpc: "2.0",
id: id ?? 0,
result: { content: [{ type: "text", text: out.text }] },
};
}
default:
return {
jsonrpc: "2.0",
id,
error: { code: -32601, message: `method not found: ${req.method}` },
};
}
}
async function callTool(
name: string,
args: Record<string, unknown>,
progressToken: string | number | undefined,
): Promise<{ text: string; error?: string }> {
if (name === "echo") {
const msg = typeof args.msg === "string" ? args.msg : "";
return { text: `echo: ${msg}` };
}
if (name === "add") {
const a = typeof args.a === "number" ? args.a : Number(args.a);
const b = typeof args.b === "number" ? args.b : Number(args.b);
if (!Number.isFinite(a) || !Number.isFinite(b)) {
return { text: "", error: "add: both a and b must be numbers" };
}
return { text: String(a + b) };
}
if (name === "get_time") {
return { text: new Date().toISOString() };
}
if (name === "slow_count") {
// Cap at 20 so an over-eager model can't make the demo run for
// minutes. Default 5 gives ~1.5s which is plenty to see the bar.
const raw = typeof args.n === "number" ? args.n : Number(args.n);
const n = Number.isFinite(raw) && raw >= 1 ? Math.min(Math.floor(raw), 20) : 5;
for (let i = 1; i <= n; i++) {
await new Promise((r) => setTimeout(r, 300));
if (progressToken !== undefined) {
send({
jsonrpc: "2.0",
method: "notifications/progress",
params: {
progressToken,
progress: i,
total: n,
message: `counting ${i} of ${n}`,
},
});
}
}
return { text: `counted to ${n}` };
}
return { text: "", error: `unknown tool: ${name}` };
}
function main(): void {
const rl = createInterface({ input: process.stdin, crlfDelay: Number.POSITIVE_INFINITY });
rl.on("line", (line) => {
const trimmed = line.trim();
if (!trimmed) return;
let req: JsonRpcRequest;
try {
req = JSON.parse(trimmed) as JsonRpcRequest;
} catch {
// malformed input — respond with parse error
send({
jsonrpc: "2.0",
id: null,
error: { code: -32700, message: "parse error" },
});
return;
}
// Fire-and-forget: handleRequest is async so slow tools (slow_count
// and any future streamed-progress tools) can emit notifications
// between in-flight requests without blocking the reader loop. Any
// unexpected throw lands as an internal-error response so malformed
// tool logic doesn't silently hang the client.
handleRequest(req)
.then((resp) => {
if (resp) send(resp);
})
.catch((err) => {
send({
jsonrpc: "2.0",
id: req.id ?? null,
error: { code: -32603, message: `internal: ${(err as Error).message}` },
});
});
});
rl.on("close", () => process.exit(0));
}
main();
+70
View File
@@ -0,0 +1,70 @@
/**
* Library example: programmatic replay + diff.
*
* This example runs with no API key and no DeepSeek calls — it reads the
* reference transcripts committed at benchmarks/tau-bench/transcripts/ and
* reconstructs the v0.1 cache-hit / cost numbers offline.
*
* Run from the repo root:
* npx tsx examples/replay-and-diff.ts
*
* Anything you can do with `reasonix replay` / `reasonix diff` is available
* here as a function you can drive from your own scripts (CI gates, eval
* dashboards, blog post generation, etc.).
*/
import {
computeReplayStats,
diffTranscripts,
readTranscript,
renderDiffSummary,
} from "../src/index.js";
const BASELINE = "benchmarks/tau-bench/transcripts/t01_address_happy.baseline.r1.jsonl";
const REASONIX = "benchmarks/tau-bench/transcripts/t01_address_happy.reasonix.r1.jsonl";
// ---------- 1. Replay a single transcript as pure data ----------
const parsed = readTranscript(REASONIX);
const stats = computeReplayStats(parsed.records);
console.log("=== Reasonix side, computed from transcript alone ===");
console.log(` model calls: ${stats.turns}`);
console.log(` cache hit: ${(stats.cacheHitRatio * 100).toFixed(1)}%`);
console.log(` total cost: $${stats.totalCostUsd.toFixed(6)}`);
console.log(` vs claude estimate: $${stats.claudeEquivalentUsd.toFixed(6)}`);
console.log(` savings: ${stats.savingsVsClaudePct.toFixed(1)}%`);
console.log(` prefix hashes: ${stats.prefixHashes.length} distinct`);
if (stats.prefixHashes.length === 1) {
console.log(` → byte-stable: ${stats.prefixHashes[0]?.slice(0, 16)}…`);
}
console.log();
// ---------- 2. Diff two transcripts ----------
const aParsed = readTranscript(BASELINE);
const bParsed = readTranscript(REASONIX);
const report = diffTranscripts(
{ label: "baseline", parsed: aParsed },
{ label: "reasonix", parsed: bParsed },
);
// renderDiffSummary returns a monochrome stdout-ready string. Equivalent to
// what `reasonix diff --print` outputs.
console.log(renderDiffSummary(report));
// ---------- 3. Direct programmatic access to pairs ----------
//
// You can also inspect report.pairs directly — useful for writing custom
// filters like "show me only the turns where tool calls differed".
console.log("\n=== Turns where A and B took different paths ===");
const divergent = report.pairs.filter((p) => p.kind !== "match");
if (divergent.length === 0) {
console.log(" (none — both agents followed the same path on every turn)");
} else {
for (const p of divergent) {
console.log(` turn ${p.turn}: ${p.kind}${p.divergenceNote ? ` — ${p.divergenceNote}` : ""}`);
}
}
+3 -2
View File
@@ -1,7 +1,7 @@
{
"name": "reasonix",
"version": "0.2.2",
"description": "DeepSeek-native agent framework: cache-first loop, R1 thought harvesting, tool-call repair.",
"version": "0.7.2",
"description": "DeepSeek-native coding agent: cache-first loop, flash-first cost control, tool-call repair.",
"type": "module",
"bin": {
"reasonix": "dist/cli/index.js"
@@ -17,6 +17,7 @@
},
"files": [
"dist",
"data/deepseek-tokenizer.json.gz",
"README.md",
"LICENSE"
],
+34
View File
@@ -0,0 +1,34 @@
#!/usr/bin/env node
/**
* Regenerate `data/deepseek-tokenizer.json.gz` from an upstream
* `tokenizer.json` (as shipped in DeepSeek's deepseek_v3_tokenizer.zip).
*
* Why slim+gz: the full tokenizer.json is 7.5MB; we only need four
* fields (vocab, merges, pre_tokenizer, added_tokens). Strip + gzip
* drops the committed artifact to ~1.7MB with no loss of fidelity
* for encode-side token counting.
*
* Usage: `node --experimental-strip-types scripts/prepare-tokenizer.ts <path/to/tokenizer.json>`
* (or via `tsx` / `ts-node`.)
*/
import { readFileSync, writeFileSync } from "node:fs";
import { join } from "node:path";
import { gzipSync } from "node:zlib";
const src = process.argv[2];
if (!src) {
process.stderr.write("usage: prepare-tokenizer.ts <tokenizer.json>\n");
process.exit(2);
}
const raw = JSON.parse(readFileSync(src, "utf8"));
const slim = {
added_tokens: raw.added_tokens,
pre_tokenizer: raw.pre_tokenizer,
model: { type: raw.model.type, vocab: raw.model.vocab, merges: raw.model.merges },
};
const gz = gzipSync(Buffer.from(JSON.stringify(slim)), { level: 9 });
const outPath = join(process.cwd(), "data", "deepseek-tokenizer.json.gz");
writeFileSync(outPath, gz);
process.stdout.write(`wrote ${outPath} (${(gz.length / 1024).toFixed(1)} KB)\n`);
+192
View File
@@ -0,0 +1,192 @@
/**
* End-to-end smoke test for the memory layer. Runs against a temp
* homeDir so the developer's real ~/.reasonix/memory/ is never touched.
* Exercises: write → index regeneration → prefix assembly →
* recall → delete → REASONIX_MEMORY=off short-circuit.
*
* Run: npx tsx scripts/smoke-memory.mts
* Exit code 0 on success, 1 on any assertion failure.
*/
import { existsSync, mkdtempSync, readFileSync, rmSync, writeFileSync } from "node:fs";
import { tmpdir } from "node:os";
import { join } from "node:path";
import { ToolRegistry } from "../src/tools.js";
import { registerMemoryTools } from "../src/tools/memory.js";
import {
MemoryStore,
applyMemoryStack,
applyUserMemory,
projectHash,
} from "../src/user-memory.js";
let failures = 0;
function check(label: string, cond: unknown, detail?: string) {
if (cond) {
process.stdout.write(` ✓ ${label}\n`);
} else {
failures++;
process.stdout.write(` ✗ ${label}${detail ? ` — ${detail}` : ""}\n`);
}
}
async function main() {
const home = mkdtempSync(join(tmpdir(), "reasonix-smoke-home-"));
const projectRoot = mkdtempSync(join(tmpdir(), "reasonix-smoke-proj-"));
process.stdout.write(`home: ${home}\nproject: ${projectRoot}\n\n`);
try {
// ── 1. MemoryStore write + index regeneration ────────────────────
process.stdout.write("1. MemoryStore write → index regen\n");
const store = new MemoryStore({ homeDir: home, projectRoot });
store.write({
name: "bun_build",
type: "project",
scope: "project",
description: "Build command on this machine is `bun run build`",
body: "On this machine, no npm — always `bun run build` / `bun run test`.",
});
store.write({
name: "tabs_not_spaces",
type: "user",
scope: "global",
description: "Use tabs for indentation across all projects",
body: "Rule.\n\n**Why:** muscle memory, editor config across machines.\n\n**How to apply:** always tabs.",
});
const hash = projectHash(projectRoot);
const projectFile = join(home, "memory", hash, "bun_build.md");
const globalFile = join(home, "memory", "global", "tabs_not_spaces.md");
check("project-scoped file landed in <hash>/ dir", existsSync(projectFile));
check("global-scoped file landed in global/ dir", existsSync(globalFile));
check("no cross-contamination project ⇒ global", !existsSync(join(home, "memory", "global", "bun_build.md")));
const projectIndex = readFileSync(join(home, "memory", hash, "MEMORY.md"), "utf8");
check("project MEMORY.md points at bun_build.md", projectIndex.includes("[bun_build](bun_build.md)"));
const globalIndex = readFileSync(join(home, "memory", "global", "MEMORY.md"), "utf8");
check("global MEMORY.md points at tabs_not_spaces.md", globalIndex.includes("[tabs_not_spaces](tabs_not_spaces.md)"));
const raw = readFileSync(projectFile, "utf8");
check("frontmatter has name/type/scope/created", /^---\nname: bun_build\n/.test(raw) && /type: project/.test(raw) && /scope: project/.test(raw) && /created: \d{4}-\d{2}-\d{2}/.test(raw));
// ── 2. Prefix assembly via applyMemoryStack (+ REASONIX.md) ────────
process.stdout.write("\n2. Prefix assembly (REASONIX.md + user memory)\n");
writeFileSync(join(projectRoot, "REASONIX.md"), "# Project notes\nPrefer explicit types over inference.\n", "utf8");
const BASE = "You are a test assistant.";
const withProjOnly = applyUserMemory(BASE, { homeDir: home, projectRoot });
check("applyUserMemory contains global block", withProjOnly.includes("# User memory — global"));
check("applyUserMemory contains project block", withProjOnly.includes("# User memory — this project"));
check("bun_build description present in prefix", withProjOnly.includes("bun run build"));
check("tabs_not_spaces description present in prefix", withProjOnly.includes("Use tabs for indentation"));
// Order: base → (REASONIX.md would go first via applyMemoryStack) → global → project
const ordered = applyUserMemory(BASE, { homeDir: home, projectRoot });
const iGlobalBlock = ordered.indexOf("# User memory — global");
const iProjBlock = ordered.indexOf("# User memory — this project");
check("global block precedes project block (stable for cache)", iGlobalBlock > 0 && iGlobalBlock < iProjBlock);
// Determinism — two calls with same state produce byte-identical prompts.
const a = applyUserMemory(BASE, { homeDir: home, projectRoot });
const b = applyUserMemory(BASE, { homeDir: home, projectRoot });
check("applyUserMemory is deterministic (byte-stable)", a === b);
// ── 3. The `remember` / `recall_memory` / `forget` tools ───────────
process.stdout.write("\n3. Tool dispatch (remember / recall / forget)\n");
const reg = new ToolRegistry();
registerMemoryTools(reg, { homeDir: home, projectRoot });
check("remember tool registered", reg.has("remember"));
check("forget tool registered", reg.has("forget"));
check("recall_memory tool registered", reg.has("recall_memory"));
check("recall_memory is readOnly (plan-mode safe)", reg.get("recall_memory")?.readOnly === true);
check("remember is NOT readOnly (plan-mode blocked)", reg.get("remember")?.readOnly !== true);
const remOut = await reg.dispatch("remember", {
type: "feedback",
scope: "global",
name: "prefers_short_replies",
description: "User wants terse answers, no trailing summaries",
content: "Default to terse. If the user wants detail they'll ask.",
});
check("remember returns a confirmation (not an error)", remOut.includes("REMEMBERED (global/prefers_short_replies)"), remOut);
const recallOut = await reg.dispatch("recall_memory", {
scope: "global",
name: "prefers_short_replies",
});
check("recall_memory returns the body", recallOut.includes("Default to terse"));
const forgetOut = await reg.dispatch("forget", {
scope: "global",
name: "prefers_short_replies",
});
check("forget returns a confirmation", forgetOut.includes("forgot (global/prefers_short_replies)"));
check("recall_memory after forget returns an error", (await reg.dispatch("recall_memory", { scope: "global", name: "prefers_short_replies" })).includes("error"));
// ── 4. Project scope refused when projectRoot is absent ────────────
process.stdout.write("\n4. Chat-mode (no projectRoot) refuses project scope\n");
const chatReg = new ToolRegistry();
registerMemoryTools(chatReg, { homeDir: home });
const projInChat = await chatReg.dispatch("remember", {
type: "project",
scope: "project",
name: "should_fail",
description: "d",
content: "c",
});
check("scope='project' in chat mode → error payload", projInChat.includes("error") && projInChat.includes("project"));
const globalInChat = await chatReg.dispatch("remember", {
type: "user",
scope: "global",
name: "global_from_chat",
description: "works across projects",
content: "body",
});
check("scope='global' in chat mode → writes successfully", globalInChat.includes("REMEMBERED (global/"));
// ── 5. REASONIX_MEMORY=off short-circuit ───────────────────────────
process.stdout.write("\n5. REASONIX_MEMORY=off opt-out\n");
process.env.REASONIX_MEMORY = "off";
try {
const silenced = applyUserMemory(BASE, { homeDir: home, projectRoot });
check("applyUserMemory returns BASE unchanged when off", silenced === BASE);
const fullStack = applyMemoryStack(BASE, projectRoot);
check("applyMemoryStack returns BASE unchanged when off (REASONIX.md also skipped)", fullStack === BASE);
} finally {
delete process.env.REASONIX_MEMORY;
}
// ── 6. Delete regeneration: MEMORY.md matches current file set ─────
process.stdout.write("\n6. Delete + index regeneration\n");
store.delete("global", "tabs_not_spaces");
store.delete("global", "global_from_chat");
const globalIdxAfter = join(home, "memory", "global", "MEMORY.md");
check("global MEMORY.md removed when last file deleted", !existsSync(globalIdxAfter));
const projectIdxStill = readFileSync(join(home, "memory", hash, "MEMORY.md"), "utf8");
check("project MEMORY.md untouched (different scope)", projectIdxStill.includes("bun_build"));
// ── 7. Name-sanitization boundary ──────────────────────────────────
process.stdout.write("\n7. Name sanitization (path-traversal refused)\n");
const badOut = await reg.dispatch("remember", {
type: "user",
scope: "global",
name: "../../etc/passwd",
description: "d",
content: "c",
});
check("remember refuses path-traversal name", badOut.includes("invalid memory name"));
const outsideFile = join(home, "etc", "passwd.md");
check("no file written outside the memory dir", !existsSync(outsideFile));
process.stdout.write(`\n${failures === 0 ? "✅ all smoke checks passed" : `❌ ${failures} failure(s)`}\n`);
} finally {
rmSync(home, { recursive: true, force: true });
rmSync(projectRoot, { recursive: true, force: true });
}
process.exit(failures === 0 ? 0 : 1);
}
main().catch((err) => {
console.error(err);
process.exit(1);
});
+397
View File
@@ -0,0 +1,397 @@
/**
* Expand `@path/to/file` mentions in a user prompt to inline file
* content.
*
* Why: most interactive coding sessions start with "look at X, then
* change Y". Typing `@src/loop.ts` reads faster and cheaper than
* "look at src/loop.ts (and the model fires read_file, and we pay for
* the round trip)" — the model sees the file content from turn 1
* instead of round-tripping a tool call for it.
*
* Shape: the user's text is kept verbatim. Expanded file contents are
* appended in a "Referenced files" block at the end, each wrapped in
* `<file path="...">...</file>` so the model can cite them back
* unambiguously.
*
* Safety: paths must resolve inside `rootDir` (no `..` escape, no
* absolute paths), must exist as a regular file, and must be under
* `maxBytes`. Missing / too-large / escaping paths get a short note
* appended instead of content so the user sees why it was skipped.
*/
import { type Dirent, existsSync, readFileSync, readdirSync, statSync } from "node:fs";
import { isAbsolute, join, relative, resolve } from "node:path";
/** Caps match tool-result dispatch truncation (0.5.2). */
export const DEFAULT_AT_MENTION_MAX_BYTES = 64 * 1024;
/**
* Default directory names skipped when listing files for the picker.
* Matches what most repos gitignore AND keeps the picker off the
* hottest bloat — `node_modules` alone can be 100k+ entries.
*/
export const DEFAULT_PICKER_IGNORE_DIRS: readonly string[] = [
"node_modules",
".git",
"dist",
"build",
".next",
"out",
"coverage",
".cache",
".vscode",
".idea",
"target",
".venv",
"venv",
"__pycache__",
];
export interface ListFilesOptions {
/** Cap the walk once we've collected this many entries. Default 500. */
maxResults?: number;
/** Directory names to skip entirely. Defaults to {@link DEFAULT_PICKER_IGNORE_DIRS}. */
ignoreDirs?: readonly string[];
}
/**
* Walk `root` recursively and return relative file paths (forward-slash
* separator, regardless of platform) for the `@` picker.
*
* Synchronous on purpose: this runs once at App mount (and on each turn
* so newly-created files show up) and blocks the render thread for a
* predictable ~10-50ms on a moderate repo. An async variant would need
* to coordinate with the Ink render loop; sync fits the rest of the
* TUI's single-turn-per-tick model cleanly.
*
* Skips:
* - directories in `ignoreDirs` (default: DEFAULT_PICKER_IGNORE_DIRS)
* - any directory whose name starts with `.` (covers `.git`,
* `.vscode`, dotfile vendors). Dotfile REGULAR FILES (`.env`,
* `.gitignore`, `.prettierrc`) are kept — users reference them.
* - entries the walker can't read (permission errors, broken links).
*/
export function listFilesSync(root: string, opts: ListFilesOptions = {}): string[] {
return listFilesWithStatsSync(root, opts).map((e) => e.path);
}
export interface FileWithStats {
/** Relative path with forward-slash separator. */
path: string;
/** Modification time (Date.getTime() / ms since epoch). 0 when stat failed. */
mtimeMs: number;
}
/**
* Same walk as {@link listFilesSync} but also statS each file for
* modification time. Used by the `@` picker to surface recently-
* edited files first — matches VS Code Quick Open / similar UX.
*
* Stat failures don't throw: the entry is kept with `mtimeMs: 0` so
* it still appears in the picker (just sinks to the bottom of the
* recency sort).
*/
export function listFilesWithStatsSync(root: string, opts: ListFilesOptions = {}): FileWithStats[] {
const maxResults = Math.max(1, opts.maxResults ?? 500);
const ignore = new Set(opts.ignoreDirs ?? DEFAULT_PICKER_IGNORE_DIRS);
const rootAbs = resolve(root);
const out: FileWithStats[] = [];
const walk = (dirAbs: string, dirRel: string) => {
if (out.length >= maxResults) return;
let entries: Dirent[];
try {
entries = readdirSync(dirAbs, { withFileTypes: true });
} catch {
return;
}
entries.sort((a, b) => a.name.localeCompare(b.name));
for (const ent of entries) {
if (out.length >= maxResults) return;
const relPath = dirRel ? `${dirRel}/${ent.name}` : ent.name;
if (ent.isDirectory()) {
if (ent.name.startsWith(".") || ignore.has(ent.name)) continue;
walk(join(dirAbs, ent.name), relPath);
} else if (ent.isFile()) {
let mtimeMs = 0;
try {
mtimeMs = statSync(join(dirAbs, ent.name)).mtimeMs;
} catch {
/* stat failed (permission / EAGAIN) — keep the entry with mtime=0 */
}
out.push({ path: relPath, mtimeMs });
}
}
};
walk(rootAbs, "");
return out;
}
/**
* Prefix pattern used by the `@` picker to detect an IN-PROGRESS
* mention at the END of the input buffer. Captures the partial path
* (which may be empty — just `@`) so the picker can use it as a
* substring filter.
*
* Distinct from {@link AT_MENTION_PATTERN} (which finds completed
* mentions anywhere in the text for expansion-at-submit). This one
* fires on the trailing token only, anchored at end-of-input.
*/
export const AT_PICKER_PREFIX = /(?:^|\s)@([a-zA-Z0-9_./\\-]*)$/;
/**
* Return the picker state for a given input buffer: the partial query
* (may be empty string — just `@`) and the buffer offset of the `@`
* character. `null` when the buffer doesn't end in a mention-in-
* progress.
*/
export function detectAtPicker(input: string): { query: string; atOffset: number } | null {
const m = AT_PICKER_PREFIX.exec(input);
if (!m) return null;
const query = m[1] ?? "";
// `m.index` is the offset of the capture group's SURROUNDING match —
// which starts at either ^ or the preceding whitespace. The `@`
// itself is at `end-of-input - query.length - 1`.
const atOffset = input.length - query.length - 1;
return { query, atOffset };
}
/** A candidate accepted by the picker ranker — either a bare path or a path with mtime. */
export type PickerCandidate = string | FileWithStats;
export interface RankPickerOptions {
/** Upper bound on returned entries. Default 40. */
limit?: number;
/**
* Paths the user or model has touched recently (via tool calls like
* `read_file` / `edit_file`). Matching paths get a recency boost so
* the picker surfaces "stuff I just looked at" near the top.
*/
recentlyUsed?: readonly string[];
}
/**
* Filter and rank candidate files against the picker's partial query.
*
* Empty query:
* - Sort by "recently used" bucket first (if provided), then mtime
* descending (newer first), then path alpha.
* - Pure-string input (no mtime data) falls back to alpha since
* recency info isn't available.
*
* Non-empty query:
* - Case-insensitive substring match, with a basename-prefix boost
* so `lo` floats `loop.ts`-shaped paths to the top.
* - Ties broken first by recently-used membership, then mtime.
*
* Back-compat: passes `string[]` through the same logic (mtime = 0,
* recently-used still honored).
*/
export function rankPickerCandidates(
files: readonly PickerCandidate[],
query: string,
limitOrOpts?: number | RankPickerOptions,
): string[] {
const opts: RankPickerOptions =
typeof limitOrOpts === "number" ? { limit: limitOrOpts } : (limitOrOpts ?? {});
const limit = opts.limit ?? 40;
const recent = new Set(opts.recentlyUsed ?? []);
const entries: FileWithStats[] = files.map((f) =>
typeof f === "string" ? { path: f, mtimeMs: 0 } : f,
);
if (!query) {
// Only re-sort when we actually have signal to sort by. If input
// is bare strings (mtime = 0 everywhere) AND there's no recent-
// used list, preserve input order so callers keep their existing
// layout. Passing FileWithStats or a non-empty recentlyUsed opts
// you into mtime+recency ranking.
const anyMtime = entries.some((e) => e.mtimeMs > 0);
if (!anyMtime && recent.size === 0) {
return entries.slice(0, limit).map((e) => e.path);
}
const sorted = [...entries].sort((a, b) => {
const aRecent = recent.has(a.path) ? 1 : 0;
const bRecent = recent.has(b.path) ? 1 : 0;
if (aRecent !== bRecent) return bRecent - aRecent;
if (a.mtimeMs !== b.mtimeMs) return b.mtimeMs - a.mtimeMs;
return a.path.localeCompare(b.path);
});
return sorted.slice(0, limit).map((e) => e.path);
}
const needle = query.toLowerCase();
const scored: Array<{ path: string; score: number; mtimeMs: number; recent: boolean }> = [];
for (const e of entries) {
const lower = e.path.toLowerCase();
const hit = lower.indexOf(needle);
if (hit < 0) continue;
const slash = lower.lastIndexOf("/");
const base = slash >= 0 ? lower.slice(slash + 1) : lower;
let score = 2;
if (base.startsWith(needle)) score = 0;
else if (lower.startsWith(needle)) score = 1;
scored.push({
path: e.path,
score: score * 10_000 + hit,
mtimeMs: e.mtimeMs,
recent: recent.has(e.path),
});
}
scored.sort((a, b) => {
if (a.score !== b.score) return a.score - b.score;
// Tie-break: recently-used, then mtime (newer first).
if (a.recent !== b.recent) return a.recent ? -1 : 1;
return b.mtimeMs - a.mtimeMs;
});
return scored.slice(0, limit).map((s) => s.path);
}
/**
* Matches `@` at a word boundary (start-of-string or preceded by
* whitespace) followed by a path-like token. Deliberately rejects `@`
* embedded in longer words (email addresses, mentions on social sites)
* by requiring the word boundary.
*
* Path charset keeps it to the characters that appear in real repo
* paths — letters, digits, `_` `-` `.` `/` `\`. Trailing `.` (e.g.
* `@foo.ts.`) is stripped before lookup so a sentence-terminating
* period doesn't break the mention.
*/
export const AT_MENTION_PATTERN = /(?<=^|\s)@([a-zA-Z0-9_./\\-]+)/g;
export interface AtMentionExpansion {
/** The raw `@path` token as it appeared in the text. */
token: string;
/** The relative path, as resolved against rootDir. */
path: string;
/** True if the content was inlined. False = skipped (reason in `skip`). */
ok: boolean;
/** Bytes read (only for ok=true). */
bytes?: number;
/** Why the mention was skipped. Set when ok=false. */
skip?: "missing" | "not-file" | "too-large" | "escape" | "read-error";
}
export interface AtMentionOptions {
/** Max file size in bytes before a mention is skipped. */
maxBytes?: number;
/**
* Optional file-system overrides for tests. Real callers omit these;
* the helper falls through to `node:fs`.
*/
fs?: {
exists: (path: string) => boolean;
isFile: (path: string) => boolean;
size: (path: string) => number;
read: (path: string) => string;
};
}
/**
* Expand `@path` mentions in `text`. Returns the (possibly augmented)
* text plus a per-mention report so the caller can surface expansions
* in the UI.
*/
export function expandAtMentions(
text: string,
rootDir: string,
opts: AtMentionOptions = {},
): { text: string; expansions: AtMentionExpansion[] } {
const maxBytes = opts.maxBytes ?? DEFAULT_AT_MENTION_MAX_BYTES;
const fs = opts.fs ?? defaultFs;
const root = resolve(rootDir);
// De-dupe by token so `@file.ts` referenced twice inlines once.
const seen = new Map<string, AtMentionExpansion>();
const expansions: AtMentionExpansion[] = [];
for (const match of text.matchAll(AT_MENTION_PATTERN)) {
const rawPath = match[1] ?? "";
// Strip trailing dot (sentence terminator): `@foo.ts.` → `@foo.ts`.
// Keep internal dots intact.
const cleaned = rawPath.replace(/\.+$/, "");
if (!cleaned) continue;
const token = `@${cleaned}`;
if (seen.has(token)) continue;
const expansion = resolveMention(cleaned, root, maxBytes, fs);
seen.set(token, expansion);
expansions.push(expansion);
}
if (expansions.length === 0) return { text, expansions };
// Build the trailing "Referenced files" block. Keep successful
// inlines and skipped ones (with their reason) so the model sees
// both what's here and what's missing.
const blocks: string[] = [];
for (const ex of expansions) {
if (ex.ok) {
const content = readSafe(root, ex.path, fs);
blocks.push(`<file path="${ex.path}">\n${content}\n</file>`);
} else {
blocks.push(`<file path="${ex.path}" skipped="${ex.skip}" />`);
}
}
const augmented = `${text}\n\n[Referenced files]\n${blocks.join("\n\n")}`;
return { text: augmented, expansions };
}
function resolveMention(
rawPath: string,
root: string,
maxBytes: number,
fs: NonNullable<AtMentionOptions["fs"]>,
): AtMentionExpansion {
// Reject absolute paths — `@/etc/passwd` should not inline.
if (isAbsolute(rawPath)) {
return { token: `@${rawPath}`, path: rawPath, ok: false, skip: "escape" };
}
const resolved = resolve(root, rawPath);
// Sandbox escape: after resolution the path must still be inside root.
const rel = relative(root, resolved);
if (rel.startsWith("..") || isAbsolute(rel)) {
return { token: `@${rawPath}`, path: rawPath, ok: false, skip: "escape" };
}
if (!fs.exists(resolved)) {
return { token: `@${rawPath}`, path: rawPath, ok: false, skip: "missing" };
}
if (!fs.isFile(resolved)) {
return { token: `@${rawPath}`, path: rawPath, ok: false, skip: "not-file" };
}
const size = fs.size(resolved);
if (size > maxBytes) {
return { token: `@${rawPath}`, path: rawPath, ok: false, skip: "too-large", bytes: size };
}
return { token: `@${rawPath}`, path: rawPath, ok: true, bytes: size };
}
function readSafe(root: string, rawPath: string, fs: NonNullable<AtMentionOptions["fs"]>): string {
const resolved = resolve(root, rawPath);
try {
return fs.read(resolved);
} catch {
return "(read failed)";
}
}
const defaultFs: NonNullable<AtMentionOptions["fs"]> = {
exists: (p) => existsSync(p),
isFile: (p) => {
try {
return statSync(p).isFile();
} catch {
return false;
}
},
size: (p) => {
try {
return statSync(p).size;
} catch {
return 0;
}
},
read: (p) => readFileSync(p, "utf8"),
};
+254 -7
View File
@@ -1,9 +1,34 @@
import { existsSync, statSync } from "node:fs";
import { render } from "ink";
import React, { useState } from "react";
import { loadApiKey } from "../../config.js";
import { loadApiKey, searchEnabled } from "../../config.js";
import { loadDotenv } from "../../env.js";
import { McpClient } from "../../mcp/client.js";
import { type InspectionReport, inspectMcpServer } from "../../mcp/inspect.js";
import { bridgeMcpTools } from "../../mcp/registry.js";
import { parseMcpSpec } from "../../mcp/spec.js";
import { SseTransport } from "../../mcp/sse.js";
import { type McpTransport, StdioTransport } from "../../mcp/stdio.js";
import {
loadSessionMessages,
rewriteSession,
sessionPath as sessionPathOf,
} from "../../session.js";
import { ToolRegistry } from "../../tools.js";
import { registerChoiceTool } from "../../tools/choice.js";
import { registerMemoryTools } from "../../tools/memory.js";
import { registerWebTools } from "../../tools/web.js";
import { App } from "../ui/App.js";
import { SessionPicker } from "../ui/SessionPicker.js";
import { Setup } from "../ui/Setup.js";
import type { McpServerSummary } from "../ui/slash.js";
export interface ProgressInfo {
toolName: string;
progress: number;
total?: number;
message?: string;
}
export interface ChatOptions {
model: string;
@@ -12,14 +37,59 @@ export interface ChatOptions {
harvest?: boolean;
branch?: number;
session?: string;
/** Zero or more MCP server specs. Each: `"name=cmd args..."` or `"cmd args..."`. */
mcp?: string[];
/** Global prefix — only used when a single anonymous server is given. */
mcpPrefix?: string;
/**
* Pre-built ToolRegistry used as a seed. MCP bridges (if any) are
* layered on top of whatever's already registered. Used by
* `reasonix code` to register native filesystem tools in place of
* the old `npx -y @modelcontextprotocol/server-filesystem` subprocess.
*/
seedTools?: ToolRegistry;
/**
* Enable SEARCH/REPLACE edit-block processing after each assistant turn.
* Set by `reasonix code`; plain `reasonix chat` leaves this off.
*/
codeMode?: { rootDir: string; jobs?: import("../../tools/jobs.js").JobRegistry };
/** Skip the session picker — assume "Resume" (backwards-compatible auto-continue). */
forceResume?: boolean;
/** Skip the session picker — assume "New" (wipe the session file and start fresh). */
forceNew?: boolean;
}
interface RootProps extends ChatOptions {
initialKey: string | undefined;
tools: ToolRegistry | undefined;
mcpSpecs: string[];
mcpServers: McpServerSummary[];
/**
* Shared ref the bridge's `onProgress` callback writes through.
* App sets `.current` to its own handler on mount so every
* progress frame from any bridged tool lands in the UI's
* `OngoingToolRow`. Ref keeps the wire-up synchronous with
* React reconciliation (no effect-timing surprises).
*/
progressSink: { current: ((info: ProgressInfo) => void) | null };
/** Present when the session has prior messages; drives the picker. */
sessionPreview?: { messageCount: number; lastActive: Date };
}
function Root({ initialKey, ...appProps }: RootProps) {
function Root({
initialKey,
tools,
mcpSpecs,
mcpServers,
progressSink,
sessionPreview,
...appProps
}: RootProps) {
const [key, setKey] = useState<string | undefined>(initialKey);
// `null` once the picker is resolved (or was never needed). Starts as
// the preview so we can render the picker once before mounting App.
const [pending, setPending] = useState<typeof sessionPreview>(sessionPreview);
if (!key) {
return (
<Setup
@@ -30,8 +100,27 @@ function Root({ initialKey, ...appProps }: RootProps) {
/>
);
}
// Ensure the loop's DeepSeekClient picks up the key when it lazy-instantiates.
process.env.DEEPSEEK_API_KEY = key;
if (pending && appProps.session) {
return (
<SessionPicker
sessionName={appProps.session}
messageCount={pending.messageCount}
lastActive={pending.lastActive}
onChoose={(choice) => {
if (choice === "new" || choice === "delete") {
// Wipe the session file. "new" and "delete" do the same thing
// at this step — the distinction is only in the picker's
// wording. A future enhancement could archive on "new".
rewriteSession(appProps.session!, []);
}
setPending(undefined);
}}
/>
);
}
return (
<App
model={appProps.model}
@@ -40,6 +129,11 @@ function Root({ initialKey, ...appProps }: RootProps) {
harvest={appProps.harvest}
branch={appProps.branch}
session={appProps.session}
tools={tools}
mcpSpecs={mcpSpecs}
mcpServers={mcpServers}
progressSink={progressSink}
codeMode={appProps.codeMode}
/>
);
}
@@ -47,8 +141,161 @@ function Root({ initialKey, ...appProps }: RootProps) {
export async function chatCommand(opts: ChatOptions): Promise<void> {
loadDotenv();
const initialKey = loadApiKey();
const { waitUntilExit } = render(<Root initialKey={initialKey} {...opts} />, {
exitOnCtrlC: true,
});
await waitUntilExit();
const requestedSpecs = opts.mcp ?? [];
const clients: McpClient[] = [];
const successfulSpecs: string[] = [];
const failedSpecs: Array<{ spec: string; reason: string }> = [];
const mcpServers: McpServerSummary[] = [];
// Shared progress sink: the bridge's onProgress callback writes
// through `progressSink.current`, which App.tsx sets to its UI
// updater on mount. Started null so early progress frames (before
// the App has mounted) are dropped rather than buffered.
const progressSink: { current: ((info: ProgressInfo) => void) | null } = { current: null };
// Seed registry from the caller (e.g. reasonix code's native
// filesystem tools) — MCP bridges layer on top rather than
// replacing. When no seed AND no MCP, tools stays undefined and
// the loop runs as a bare chat.
let tools: ToolRegistry | undefined = opts.seedTools;
if (requestedSpecs.length > 0) {
if (!tools) tools = new ToolRegistry();
for (const raw of requestedSpecs) {
try {
const spec = parseMcpSpec(raw);
const prefix = spec.name
? `${spec.name}_`
: requestedSpecs.length === 1 && opts.mcpPrefix
? opts.mcpPrefix
: "";
const transport: McpTransport =
spec.transport === "sse"
? new SseTransport({ url: spec.url })
: new StdioTransport({ command: spec.command, args: spec.args });
const mcp = new McpClient({ transport });
await mcp.initialize();
const bridge = await bridgeMcpTools(mcp, {
registry: tools,
namePrefix: prefix,
onProgress: (info) => progressSink.current?.(info),
});
// Collect resources + prompts once at startup so the /mcp
// slash can render them synchronously. Servers that don't
// support these fall through as `{supported: false}` instead
// of throwing — see inspectMcpServer.
let report: InspectionReport;
try {
report = await inspectMcpServer(mcp);
} catch {
// If the inspect call itself fails (rare — shouldn't happen
// since inspectMcpServer swallows -32601), synthesize a
// minimal report so `/mcp` still has something to render.
report = {
protocolVersion: mcp.protocolVersion,
serverInfo: mcp.serverInfo,
capabilities: mcp.serverCapabilities ?? {},
tools: { supported: true, items: [] },
resources: { supported: false, reason: "inspect failed" },
prompts: { supported: false, reason: "inspect failed" },
};
}
const label = spec.name ?? "anon";
const source =
spec.transport === "sse" ? spec.url : `${spec.command} ${spec.args.join(" ")}`;
process.stderr.write(
`▸ MCP[${label}]: ${bridge.registeredNames.length} tool(s) from ${source}\n`,
);
clients.push(mcp);
successfulSpecs.push(raw);
mcpServers.push({
label,
spec: raw,
toolCount: bridge.registeredNames.length,
report,
client: mcp,
});
} catch (err) {
// Per-server failure is non-fatal: one broken server shouldn't
// kill a chat that has working servers configured. We record
// the failure, show a visible warning, and keep going. User
// can fix via `reasonix setup` (unchecks the broken entry)
// without losing their other servers.
const reason = (err as Error).message;
failedSpecs.push({ spec: raw, reason });
process.stderr.write(
`▸ MCP setup SKIPPED for "${raw}": ${reason}\n → this server will not be available this session. Run \`reasonix setup\` to remove it, or fix the underlying issue (missing npm package, network, etc.).\n`,
);
}
}
// If every requested server failed AND no seed registry was
// provided, drop the empty registry so the loop still runs as a
// bare chat instead of advertising zero tools. If the caller
// passed seedTools we keep the registry — the seed tools are
// still there and usable.
if (successfulSpecs.length === 0 && !opts.seedTools) {
tools = undefined;
}
}
const mcpSpecs = successfulSpecs;
// Register web search/fetch tools unless explicitly disabled. DDG
// backs them with no key required; the model invokes them whenever
// a question needs info fresher than its training data.
if (searchEnabled()) {
if (!tools) tools = new ToolRegistry();
registerWebTools(tools);
}
// Memory tools — available in every session, not just code mode.
// Chat-mode callers get global scope only; project scope requires
// the seedTools path from `reasonix code` (which registers its own
// MemoryStore bound to rootDir before chatCommand runs).
// `run_skill` is registered later in App.tsx (where the client
// exists) so it can wire the subagent runner for runAs:subagent
// skills.
if (!opts.seedTools) {
if (!tools) tools = new ToolRegistry();
registerMemoryTools(tools, {});
// `ask_choice` — branching primitive, useful in chat too (stylistic
// preferences, doc language, library picks). Independent of plan
// mode, which chat doesn't have anyway.
registerChoiceTool(tools);
}
// Decide whether to show the session picker. It's gated on: session
// persistence is on, the session file already has prior messages, and
// the caller didn't pre-commit to one of the choices via --resume /
// --new flags. `--new` wipes the file now (before the loop opens),
// so the App mounts against a fresh log.
let sessionPreview: { messageCount: number; lastActive: Date } | undefined;
if (opts.session && !opts.forceResume && !opts.forceNew) {
const prior = loadSessionMessages(opts.session);
if (prior.length > 0) {
const p = sessionPathOf(opts.session);
const mtime = existsSync(p) ? statSync(p).mtime : new Date();
sessionPreview = { messageCount: prior.length, lastActive: mtime };
}
} else if (opts.session && opts.forceNew) {
rewriteSession(opts.session, []);
}
const { waitUntilExit } = render(
<Root
initialKey={initialKey}
tools={tools}
mcpSpecs={mcpSpecs}
mcpServers={mcpServers}
progressSink={progressSink}
sessionPreview={sessionPreview}
{...opts}
/>,
// patchConsole:false — we never log to console during the TUI, and the
// patch is a known redraw-glitch source on winpty/MINTTY terminals.
{ exitOnCtrlC: true, patchConsole: false },
);
try {
await waitUntilExit();
} finally {
for (const c of clients) await c.close();
}
}
+134
View File
@@ -0,0 +1,134 @@
/**
* `reasonix code [dir]` — opinionated wrapper around `reasonix chat` for
* code-editing workflows.
*
* What it does differently from plain chat:
* - Registers native filesystem tools rooted at the given directory
* (CWD by default). No subprocess, no `npx install` step, R1-
* friendly schemas. Replaced the old `@modelcontextprotocol/server-filesystem`
* subprocess in 0.4.9 because its `edit_file` argv shape was the
* biggest driver of R1 DSML hallucinations.
* - Uses a coding-focused system prompt (src/code/prompt.ts) that
* teaches the model to propose edits as SEARCH/REPLACE blocks.
* - Defaults to the `smart` preset (reasoner + harvest) because
* coding tasks pay back R1 thinking.
* - Scopes its session to the directory so projects don't share
* conversation history.
* - Hooks `codeMode` into the TUI so assistant replies get parsed
* for SEARCH/REPLACE blocks and applied on disk after each turn.
*/
import { basename, resolve } from "node:path";
import { loadProjectShellAllowed } from "../../config.js";
import { sanitizeName } from "../../session.js";
import { ToolRegistry } from "../../tools.js";
import { registerChoiceTool } from "../../tools/choice.js";
import { registerFilesystemTools } from "../../tools/filesystem.js";
import { JobRegistry } from "../../tools/jobs.js";
import { registerMemoryTools } from "../../tools/memory.js";
import { registerPlanTool } from "../../tools/plan.js";
import { registerShellTools } from "../../tools/shell.js";
import { chatCommand } from "./chat.js";
export interface CodeOptions {
/** Directory to root the filesystem tools at. Defaults to process.cwd(). */
dir?: string;
/** Override the default `smart` model. */
model?: string;
/** Disable session persistence. */
noSession?: boolean;
/** Transcript file for replay/diff. */
transcript?: string;
/** Skip the session picker — always resume prior messages. */
forceResume?: boolean;
/** Skip the session picker — always wipe prior messages and start fresh. */
forceNew?: boolean;
/**
* Opt into Pillar 2 harvesting (extracts a typed plan state from R1
* reasoning via an extra V3 call). Default OFF in code mode — the
* displayed subgoals/hypotheses/rejectedPaths have no programmatic
* consumer, only `uncertainties.length` feeds branching, and the
* extra V3 call adds ~10-15% per-turn cost. Users who want the
* reasoning surfaced explicitly can pass `--harvest`.
*/
harvest?: boolean;
}
export async function codeCommand(opts: CodeOptions = {}): Promise<void> {
const { codeSystemPrompt } = await import("../../code/prompt.js");
const rootDir = resolve(opts.dir ?? process.cwd());
// Per-directory session so switching projects doesn't mix histories.
// `code-<sanitized-basename>` fits the session name rules without
// truncating most project names.
const session = opts.noSession ? undefined : `code-${sanitizeName(basename(rootDir))}`;
// Native filesystem tools. No subprocess, ~50-200 ms faster per call
// than the MCP server was, and `edit_file` takes a flat SEARCH/REPLACE
// shape instead of the `string="false"` JSON-in-string array that
// triggered R1's DSML hallucinations all through 0.4.x.
const tools = new ToolRegistry();
registerFilesystemTools(tools, { rootDir });
// Background-process registry shared between the shell tools and the
// TUI's /jobs + /kill slashes + exit cleanup. One per `reasonix code`
// run — orphan prevention on SIGINT / process exit kills everything
// it owns, so dev servers don't outlive the Reasonix process.
const jobs = new JobRegistry();
registerShellTools(tools, {
rootDir,
// Per-project "always allow" list persisted from prior ShellConfirm
// choices; merged on top of the built-in allowlist in shell.ts.
// GETTER form — re-read every dispatch so a prefix the user adds
// via ShellConfirm mid-session takes effect on the next shell call
// instead of waiting for `/new` or a relaunch.
extraAllowed: () => loadProjectShellAllowed(rootDir),
jobs,
});
// `submit_plan` is always in the spec list so the prefix cache stays
// stable across plan-mode toggles (Pillar 1). The tool itself is a
// no-op outside plan mode and throws `PlanProposedError` when the
// user has `/plan`-enabled the session.
registerPlanTool(tools);
// `ask_choice` — branching primitive. Independent of plan mode: the
// model uses it to put a 2–4 way choice in front of the user
// (strategy, style, library pick) without trying to squeeze the
// menu into a submit_plan body. Keeping it always-registered
// preserves the prefix cache across plan-mode toggles.
registerChoiceTool(tools);
// `remember` / `forget` / `recall_memory` — cross-session user memory.
// Project scope hashes off rootDir so switching projects gets a fresh
// per-project memory store; the global scope is shared across runs.
registerMemoryTools(tools, { projectRoot: rootDir });
// `run_skill` is intentionally NOT registered here — App.tsx wires it
// up with the subagent runner attached, so `runAs: subagent` skills
// can spawn isolated child loops. Doing it here would mean the App's
// re-registration would shadow the no-runner version, which works
// (last write wins) but obscures the wiring.
process.stderr.write(
`▸ reasonix code: rooted at ${rootDir}, session "${session ?? "(ephemeral)"}" · ${tools.size} native tool(s)\n`,
);
// Belt-and-suspenders cleanup: even though spawn(detached:false)
// should tie child processes to the parent's lifetime, Windows cmd.exe
// wrappers occasionally leak. Kill everything on both clean and
// signal-driven exits. 'exit' fires too late for async I/O but is our
// only guaranteed last word; the signal handlers do the heavy lifting.
const sigShutdown = () => {
void jobs.shutdown();
};
process.once("SIGINT", sigShutdown);
process.once("SIGTERM", sigShutdown);
process.once("exit", sigShutdown);
await chatCommand({
model: opts.model ?? "deepseek-v4-flash",
harvest: opts.harvest ?? false,
system: codeSystemPrompt(rootDir),
transcript: opts.transcript,
session,
seedTools: tools,
codeMode: { rootDir, jobs },
forceResume: opts.forceResume,
forceNew: opts.forceNew,
});
}
+1
View File
@@ -51,6 +51,7 @@ export async function diffCommand(opts: DiffOptions): Promise<void> {
if (wantTui) {
const { waitUntilExit } = render(React.createElement(DiffApp, { report }), {
exitOnCtrlC: true,
patchConsole: false,
});
await waitUntilExit();
return;
+107
View File
@@ -0,0 +1,107 @@
/**
* `reasonix mcp inspect <spec>` — connect to one MCP server, list
* everything it exposes (tools, resources, prompts), print a
* human-readable summary. Useful as:
* - a diagnostic tool for "does my MCP server even work?"
* - a discovery tool for "what can this server do?"
* - the only CLI surface for the resources+prompts methods added
* in 0.4.5 (chat mode consumes tools but hasn't wired up the
* other two families yet).
*/
import { McpClient } from "../../mcp/client.js";
import { inspectMcpServer } from "../../mcp/inspect.js";
import type { InspectionReport } from "../../mcp/inspect.js";
import { parseMcpSpec } from "../../mcp/spec.js";
import { SseTransport } from "../../mcp/sse.js";
import { type McpTransport, StdioTransport } from "../../mcp/stdio.js";
export interface McpInspectOptions {
/** The raw --mcp spec string (e.g. `fs=npx -y @modelcontextprotocol/server-filesystem .`). */
spec: string;
/** Emit JSON on stdout instead of the human-readable table. */
json?: boolean;
}
export async function mcpInspectCommand(opts: McpInspectOptions): Promise<void> {
const spec = parseMcpSpec(opts.spec);
const transport: McpTransport =
spec.transport === "sse"
? new SseTransport({ url: spec.url })
: new StdioTransport({ command: spec.command, args: spec.args });
const client = new McpClient({ transport });
try {
await client.initialize();
const report = await inspectMcpServer(client);
if (opts.json) {
console.log(JSON.stringify(report, null, 2));
} else {
console.log(formatReport(spec.name ?? "(anon)", report));
}
} finally {
await client.close();
}
}
function formatReport(nsName: string, r: InspectionReport): string {
const lines: string[] = [];
lines.push(`MCP server [${nsName}]`);
lines.push(
` server ${r.serverInfo.name || "(unknown)"}${r.serverInfo.version ? ` v${r.serverInfo.version}` : ""}`,
);
lines.push(` protocol ${r.protocolVersion}`);
const capKeys = Object.keys(r.capabilities);
lines.push(` caps ${capKeys.length > 0 ? capKeys.join(", ") : "(none advertised)"}`);
if (r.instructions) {
lines.push(` notes ${r.instructions.trim().slice(0, 200)}`);
}
lines.push("");
lines.push(formatSection("Tools", r.tools, toolLine));
lines.push(formatSection("Resources", r.resources, resourceLine));
lines.push(formatSection("Prompts", r.prompts, promptLine));
return lines.join("\n");
}
function formatSection<T>(
title: string,
section: { supported: true; items: T[] } | { supported: false; reason: string },
render: (item: T) => string,
): string {
if (!section.supported) {
return `${title}: (not supported — ${section.reason})`;
}
if (section.items.length === 0) {
return `${title}: (none)`;
}
const lines = [`${title} (${section.items.length}):`];
for (const item of section.items) lines.push(` ${render(item)}`);
return lines.join("\n");
}
function toolLine(t: { name: string; description?: string }): string {
const desc = t.description ? ` — ${oneLine(t.description, 80)}` : "";
return `· ${t.name}${desc}`;
}
function resourceLine(r: { uri: string; name: string; mimeType?: string }): string {
const mime = r.mimeType ? ` [${r.mimeType}]` : "";
return `· ${r.name}${mime} ${r.uri}`;
}
function promptLine(p: {
name: string;
description?: string;
arguments?: Array<{ name: string; required?: boolean }>;
}): string {
const argPart =
p.arguments && p.arguments.length > 0
? ` (${p.arguments.map((a) => (a.required ? a.name : `${a.name}?`)).join(", ")})`
: "";
const desc = p.description ? ` — ${oneLine(p.description, 80)}` : "";
return `· ${p.name}${argPart}${desc}`;
}
function oneLine(s: string, max: number): string {
const flat = s.replace(/\s+/g, " ").trim();
return flat.length <= max ? flat : `${flat.slice(0, max - 1)}…`;
}
+41
View File
@@ -0,0 +1,41 @@
/**
* `reasonix mcp <subcmd>` — the MCP discovery / helper surface.
*
* Currently one subcommand: `list`. Prints a curated catalog of popular
* MCP servers with their `--mcp` commands ready to copy-paste. More
* subcommands (`init`, `try`, etc.) may land in later alphas.
*/
import { MCP_CATALOG, mcpCommandFor } from "../../mcp/catalog.js";
export interface McpListOptions {
/** Emit JSON on stdout instead of the human-readable table. */
json?: boolean;
}
export function mcpListCommand(opts: McpListOptions): void {
if (opts.json) {
console.log(JSON.stringify(MCP_CATALOG, null, 2));
return;
}
console.log("Popular MCP servers you can bridge into Reasonix:");
console.log("");
for (const entry of MCP_CATALOG) {
console.log(` ${pad(entry.name, 12)} ${entry.summary}`);
console.log(` ${mcpCommandFor(entry)}`);
if (entry.note) console.log(` · ${entry.note}`);
console.log("");
}
console.log("Usage: reasonix chat <one-of-the---mcp-lines-above>");
console.log(
"Docs: https://github.com/modelcontextprotocol/servers — Anthropic's official server repo",
);
console.log(
" https://mcp.so — community-maintained catalog",
);
}
function pad(s: string, width: number): string {
return s.length >= width ? s : s + " ".repeat(width - s.length);
}
+21
View File
@@ -31,6 +31,7 @@ export async function replayCommand(opts: ReplayOptions): Promise<void> {
const pages = groupRecordsByTurn(parsed.records);
const { waitUntilExit } = render(React.createElement(ReplayApp, { meta: parsed.meta, pages }), {
exitOnCtrlC: true,
patchConsole: false,
});
await waitUntilExit();
}
@@ -74,6 +75,11 @@ function printReplay(opts: ReplayOptions): void {
} else if (stats.prefixHashes.length > 1) {
console.log(" (prefix churned — cache-hostile session)");
}
if (stats.harvestedTurns > 0) {
console.log(`harvest (Pillar 2): ${stats.harvestedTurns} turn(s) produced plan state`);
console.log(` subgoals: ${stats.totalSubgoals}`);
console.log(` uncertainties: ${stats.totalUncertainties}`);
}
}
function sliceRecords(records: TranscriptRecord[], opts: ReplayOptions): TranscriptRecord[] {
@@ -100,6 +106,21 @@ function renderRecord(rec: TranscriptRecord): void {
})()
: "";
console.log(`${turn} AGENT:${cost}${cache} ${oneLine(rec.content)}`);
if (rec.planState) {
const ps = rec.planState;
if (ps.subgoals.length)
console.log(` ‹ subgoals (${ps.subgoals.length}): ${ps.subgoals.join(" · ")}`);
if (ps.hypotheses.length)
console.log(` ‹ hypotheses (${ps.hypotheses.length}): ${ps.hypotheses.join(" · ")}`);
if (ps.uncertainties.length)
console.log(
` ‹ uncertainties(${ps.uncertainties.length}): ${ps.uncertainties.join(" · ")}`,
);
if (ps.rejectedPaths.length)
console.log(
` ‹ rejected (${ps.rejectedPaths.length}): ${ps.rejectedPaths.join(" · ")}`,
);
}
} else if (rec.role === "tool") {
const args = rec.args ? ` args=${oneLine(rec.args, 80)}` : "";
console.log(`${turn} TOOL ${rec.tool ?? "?"}:${args} → ${oneLine(rec.content, 120)}`);
+122 -9
View File
@@ -1,13 +1,32 @@
import type { WriteStream } from "node:fs";
import { stdin, stdout } from "node:process";
import { createInterface } from "node:readline/promises";
import { defaultConfigPath, isPlausibleKey, loadApiKey, saveApiKey } from "../../config.js";
import { loadDotenv } from "../../env.js";
import { CacheFirstLoop, DeepSeekClient, ImmutablePrefix } from "../../index.js";
import { McpClient } from "../../mcp/client.js";
import { bridgeMcpTools } from "../../mcp/registry.js";
import { parseMcpSpec } from "../../mcp/spec.js";
import { SseTransport } from "../../mcp/sse.js";
import { type McpTransport, StdioTransport } from "../../mcp/stdio.js";
import { ToolRegistry } from "../../tools.js";
import { openTranscriptFile, recordFromLoopEvent, writeRecord } from "../../transcript.js";
import { appendUsage } from "../../usage.js";
export interface RunOptions {
task: string;
model: string;
system: string;
/** Opt into Pillar 2 plan-state harvesting. Adds a cheap V3 call per turn. */
harvest?: boolean;
/** Self-consistency budget. > 1 runs N parallel samples and picks the best. */
branch?: number;
/** JSONL transcript path — lets `reasonix replay` / `diff` audit this run. */
transcript?: string;
/** Zero or more MCP server specs. Each: `"name=cmd args..."` or `"cmd args..."`. */
mcp?: string[];
/** Global prefix — only honored when a single anonymous server is given. */
mcpPrefix?: string;
}
async function ensureApiKey(): Promise<string> {
@@ -48,19 +67,113 @@ export async function runCommand(opts: RunOptions): Promise<void> {
const apiKey = await ensureApiKey();
process.env.DEEPSEEK_API_KEY = apiKey;
const client = new DeepSeekClient();
const prefix = new ImmutablePrefix({ system: opts.system });
const loop = new CacheFirstLoop({ client, prefix, model: opts.model });
for await (const ev of loop.step(opts.task)) {
if (ev.role === "assistant_delta" && ev.content) process.stdout.write(ev.content);
if (ev.role === "tool") process.stdout.write(`\n[tool ${ev.toolName}] ${ev.content}\n`);
if (ev.role === "error") process.stderr.write(`\n[error] ${ev.error}\n`);
if (ev.role === "done") process.stdout.write("\n");
// Optional MCP setup — mirrors chat's flow. Must happen before loop
// construction so the tools make it into the prefix.
const requestedSpecs = opts.mcp ?? [];
const clients: McpClient[] = [];
let tools: ToolRegistry | undefined;
let successCount = 0;
if (requestedSpecs.length > 0) {
tools = new ToolRegistry();
for (const raw of requestedSpecs) {
try {
const spec = parseMcpSpec(raw);
const prefix = spec.name
? `${spec.name}_`
: requestedSpecs.length === 1 && opts.mcpPrefix
? opts.mcpPrefix
: "";
const transport: McpTransport =
spec.transport === "sse"
? new SseTransport({ url: spec.url })
: new StdioTransport({ command: spec.command, args: spec.args });
const mcp = new McpClient({ transport });
await mcp.initialize();
const bridge = await bridgeMcpTools(mcp, { registry: tools, namePrefix: prefix });
const source =
spec.transport === "sse" ? spec.url : `${spec.command} ${spec.args.join(" ")}`;
process.stderr.write(
`▸ MCP[${spec.name ?? "anon"}]: ${bridge.registeredNames.length} tool(s) from ${source}\n`,
);
clients.push(mcp);
successCount++;
} catch (err) {
// Non-fatal — skip and continue, same as `reasonix chat`. A
// one-shot `run` invocation with a broken MCP server otherwise
// fails the whole run over a side-concern tool the task might
// not even touch.
process.stderr.write(
`▸ MCP setup SKIPPED for "${raw}": ${(err as Error).message}\n → run \`reasonix setup\` to remove broken entries from your saved config.\n`,
);
}
}
if (successCount === 0) tools = undefined;
}
const client = new DeepSeekClient();
const prefix = new ImmutablePrefix({
system: opts.system,
toolSpecs: tools?.specs(),
});
const loop = new CacheFirstLoop({
client,
prefix,
tools,
model: opts.model,
harvest: opts.harvest,
branch: opts.branch,
});
const prefixHash = prefix.fingerprint;
let transcriptStream: WriteStream | null = null;
if (opts.transcript) {
transcriptStream = openTranscriptFile(opts.transcript, {
version: 1,
source: "reasonix run",
model: opts.model,
startedAt: new Date().toISOString(),
});
// Also persist the user turn itself (the loop's event stream starts with
// assistant output, not the prompt we're about to send).
writeRecord(transcriptStream, {
ts: new Date().toISOString(),
turn: 1,
role: "user",
content: opts.task,
});
}
try {
for await (const ev of loop.step(opts.task)) {
if (ev.role === "assistant_delta" && ev.content) process.stdout.write(ev.content);
if (ev.role === "tool") process.stdout.write(`\n[tool ${ev.toolName}] ${ev.content}\n`);
if (ev.role === "error") process.stderr.write(`\n[error] ${ev.error}\n`);
if (ev.role === "done") process.stdout.write("\n");
if (ev.role === "assistant_final" && ev.stats?.usage) {
// `reasonix run` is often used in CI / scripting — we want
// those turns to show up in `reasonix stats` too so the
// dashboard reflects all DeepSeek spend, not just TUI sessions.
appendUsage({ session: null, model: ev.stats.model, usage: ev.stats.usage });
}
// Persist every non-streaming event — deltas would flood the file and
// aren't useful for replay (replay renders final content, not keystrokes).
if (transcriptStream && ev.role !== "assistant_delta") {
writeRecord(transcriptStream, recordFromLoopEvent(ev, { model: opts.model, prefixHash }));
}
}
} finally {
transcriptStream?.end();
}
const s = loop.stats.summary();
process.stdout.write(
`\n— turns:${s.turns} cache:${(s.cacheHitRatio * 100).toFixed(1)}% ` +
`cost:$${s.totalCostUsd.toFixed(6)} save-vs-claude:${s.savingsVsClaudePct.toFixed(1)}%\n`,
);
if (opts.transcript) {
process.stdout.write(`\ntranscript: ${opts.transcript}\n`);
process.stdout.write(` → npx reasonix replay ${opts.transcript}\n`);
}
for (const c of clients) await c.close();
}
+107
View File
@@ -0,0 +1,107 @@
/**
* `reasonix sessions` — CLI equivalent of the `/sessions` slash command.
*
* Two modes:
* - `reasonix sessions` list every session under ~/.reasonix/sessions/
* - `reasonix sessions <name>` dump one session's messages in readable form
*
* Neither needs an API key — pure filesystem reads of JSONL files written
* by previous chat runs.
*/
import { listSessions, loadSessionMessages, sessionPath } from "../../index.js";
import type { ChatMessage } from "../../index.js";
export interface SessionsOptions {
/** When present, inspect that session instead of listing. */
name?: string;
/** Include assistant tool-call metadata in the inspect output. */
verbose?: boolean;
}
export function sessionsCommand(opts: SessionsOptions): void {
if (opts.name) {
inspectSession(opts.name, !!opts.verbose);
} else {
listAll();
}
}
function listAll(): void {
const items = listSessions();
if (items.length === 0) {
console.log(
"no saved sessions yet — run `reasonix chat` (sessions are auto-saved unless --no-session).",
);
return;
}
console.log("Saved sessions (~/.reasonix/sessions/):");
console.log("");
console.log(` ${"name".padEnd(22)} ${"msgs".padStart(6)} ${"size".padStart(8)} modified`);
console.log(` ${"─".repeat(60)}`);
for (const s of items) {
const sizeKb = `${(s.size / 1024).toFixed(1)} KB`;
const when = s.mtime.toISOString().replace("T", " ").slice(0, 16);
console.log(
` ${s.name.padEnd(22)} ${String(s.messageCount).padStart(6)} ${sizeKb.padStart(8)} ${when}`,
);
}
console.log("");
console.log("Inspect: reasonix sessions <name>");
console.log("Resume: reasonix chat --session <name>");
}
function inspectSession(name: string, verbose: boolean): void {
const path = sessionPath(name);
const messages = loadSessionMessages(name);
if (messages.length === 0) {
console.error(`no session named "${name}" (or it's empty).`);
console.error(`looked at: ${path}`);
process.exit(1);
}
console.log(`[session] ${name} ${messages.length} messages ${path}`);
console.log("");
let turnIndex = 0;
for (const msg of messages) {
renderMessage(msg, turnIndex, verbose);
// Roughly bump "turn" after each user message so the reader can follow
// the conversation shape without the transcript's richer turn numbering.
if (msg.role === "user") turnIndex++;
}
}
function renderMessage(msg: ChatMessage, turnIdx: number, verbose: boolean): void {
const turn = turnIdx > 0 ? `[t${turnIdx}]` : "[start]";
const content = typeof msg.content === "string" ? msg.content : "";
const flat = oneLine(content);
if (msg.role === "user") {
console.log(`${turn} USER: ${flat}`);
} else if (msg.role === "assistant") {
console.log(`${turn} AGENT: ${flat || "(tool call only)"}`);
if (verbose && msg.tool_calls?.length) {
for (const tc of msg.tool_calls) {
console.log(
` → call ${tc.function?.name} ${truncate(tc.function?.arguments ?? "", 80)}`,
);
}
}
} else if (msg.role === "tool") {
console.log(`${turn} TOOL ${msg.name ?? "?"}: ${truncate(flat, 160)}`);
} else if (msg.role === "system") {
if (verbose) console.log(`${turn} SYSTEM: ${truncate(flat, 160)}`);
// otherwise suppress — session's system prompt is usually session-wide
// boilerplate.
}
}
function oneLine(s: string, max = 200): string {
const collapsed = s.replace(/\s+/g, " ").trim();
return collapsed.length > max ? `${collapsed.slice(0, max)}…` : collapsed;
}
function truncate(s: string, max: number): string {
return s.length <= max ? s : `${s.slice(0, max)}…`;
}
+45
View File
@@ -0,0 +1,45 @@
/**
* `reasonix setup` — re-mount the first-run wizard on demand so users
* can reconfigure (add/remove MCP servers, switch preset) without
* editing JSON by hand.
*
* Invoked both explicitly (`reasonix setup`) and implicitly (the no-args
* entry point when `setupCompleted` is false).
*/
import { render } from "ink";
import React from "react";
import { loadApiKey, readConfig } from "../../config.js";
import { loadDotenv } from "../../env.js";
import { Wizard } from "../ui/Wizard.js";
export interface SetupOptions {
/**
* When true, bypass the API-key step even if no key is saved — useful
* from test harnesses. Normal CLI use always pushes through the key
* step when missing.
*/
skipKeyStep?: boolean;
}
export async function setupCommand(_opts: SetupOptions = {}): Promise<void> {
loadDotenv();
const existingKey = loadApiKey();
const existing = readConfig();
const { waitUntilExit, unmount } = render(
<Wizard
existingApiKey={existingKey}
initial={{ preset: existing.preset, mcp: existing.mcp }}
onComplete={() => {
// Ink handles its own enter-to-exit inside the "saved" step; we
// just wait for the app to exit naturally.
}}
onCancel={() => {
unmount();
}}
/>,
{ exitOnCtrlC: true, patchConsole: false },
);
await waitUntilExit();
}
+163 -5
View File
@@ -1,15 +1,60 @@
/**
* `reasonix stats` — two modes, decided by whether the user passed
* a transcript path.
*
* - `reasonix stats` → cross-session usage dashboard
* (reads `~/.reasonix/usage.jsonl`)
* - `reasonix stats <path>` → summary of a single JSONL transcript
* (original v0.1 behavior, kept so
* existing scripts don't break)
*
* The dashboard is the new story: for every turn `reasonix chat|code|run`
* has ever executed on this machine, we aggregate tokens + cost + the
* equivalent Claude spend, and print rolling-window totals (today /
* week / month / all-time). The savings column is the Pillar 1 pitch
* made concrete — "you paid $X; Claude would have charged $Y, a N%
* reduction."
*/
import { existsSync, readFileSync } from "node:fs";
import {
type UsageAggregate,
type UsageBucket,
aggregateUsage,
bucketCacheHitRatio,
bucketSavingsFraction,
defaultUsageLogPath,
formatLogSize,
readUsageLog,
} from "../../usage.js";
export interface StatsOptions {
transcript: string;
/** Optional transcript path. Absent → dashboard mode. */
transcript?: string;
/** Override usage log location (tests). */
logPath?: string;
/** Inject a fixed timestamp (tests) so rolling windows are deterministic. */
now?: number;
}
export function statsCommand(opts: StatsOptions): void {
if (!existsSync(opts.transcript)) {
console.error(`no such transcript: ${opts.transcript}`);
if (opts.transcript) {
transcriptSummary(opts.transcript);
return;
}
dashboard(opts);
}
// ---------------------------------------------------------------------
// Transcript summary — legacy v0.1 behavior, preserved verbatim.
// ---------------------------------------------------------------------
function transcriptSummary(path: string): void {
if (!existsSync(path)) {
console.error(`no such transcript: ${path}`);
process.exit(1);
}
const lines = readFileSync(opts.transcript, "utf8").split(/\r?\n/).filter(Boolean);
const lines = readFileSync(path, "utf8").split(/\r?\n/).filter(Boolean);
let assistantTurns = 0;
let toolCalls = 0;
let lastTurn = 0;
@@ -23,8 +68,121 @@ export function statsCommand(opts: StatsOptions): void {
/* skip */
}
}
console.log(`transcript: ${opts.transcript}`);
console.log(`transcript: ${path}`);
console.log(`assistant turns: ${assistantTurns}`);
console.log(`tool invocations: ${toolCalls}`);
console.log(`last turn index: ${lastTurn}`);
}
// ---------------------------------------------------------------------
// Dashboard — aggregates ~/.reasonix/usage.jsonl.
// ---------------------------------------------------------------------
function dashboard(opts: StatsOptions): void {
const path = opts.logPath ?? defaultUsageLogPath();
const records = readUsageLog(path);
if (records.length === 0) {
console.log("no usage data yet.");
console.log("");
console.log(` ${path}`);
console.log("");
console.log("run `reasonix chat`, `reasonix code`, or `reasonix run <task>` — every turn");
console.log("appends one line to the log and `reasonix stats` will roll it up.");
return;
}
const agg = aggregateUsage(records, { now: opts.now });
console.log(renderDashboard(agg, path));
}
/** Pure renderer — pulled out so tests can assert on the string directly. */
export function renderDashboard(agg: UsageAggregate, logPath: string): string {
const lines: string[] = [];
const size = formatLogSize(logPath);
lines.push(`Reasonix usage — ${logPath}${size ? ` (${size})` : ""}`);
lines.push("");
lines.push(header());
lines.push(divider());
for (const b of agg.buckets) {
lines.push(bucketRow(b));
}
lines.push("");
// Model + session breakdown — both trim to top 3 so a user with 20
// sessions doesn't drown the table.
if (agg.byModel.length > 0) {
const totalTurns = agg.buckets[agg.buckets.length - 1]?.turns ?? 0;
const top = agg.byModel[0];
if (top && totalTurns > 0) {
const pct = ((top.turns / totalTurns) * 100).toFixed(0);
lines.push(`most used model: ${top.model} (${pct}% of turns)`);
}
}
if (agg.bySession.length > 0) {
const top = agg.bySession[0];
if (top) lines.push(`top session: ${top.session} (${top.turns} turns)`);
}
if (agg.firstSeen) {
lines.push(`tracked since: ${new Date(agg.firstSeen).toISOString().slice(0, 10)}`);
}
if (agg.subagents) {
lines.push("");
lines.push(renderSubagentSection(agg.subagents));
}
return lines.join("\n");
}
function renderSubagentSection(sub: NonNullable<UsageAggregate["subagents"]>): string {
const lines: string[] = [];
const seconds = (sub.totalDurationMs / 1000).toFixed(1);
lines.push(
`subagent activity: ${sub.total} run(s) · $${sub.costUsd.toFixed(6)} · ${seconds}s total`,
);
// Show at most 5 skills so the section never dwarfs the main table.
const top = sub.bySkill.slice(0, 5);
for (const s of top) {
const sec = (s.durationMs / 1000).toFixed(1);
lines.push(
` ${pad(s.skillName, 18)} ${pad(`${s.count}`, 4, "right")} $${s.costUsd.toFixed(6)} ${sec}s`,
);
}
if (sub.bySkill.length > top.length) {
lines.push(` (+${sub.bySkill.length - top.length} more)`);
}
return lines.join("\n");
}
function header(): string {
// Fixed column widths so alignment works in any TTY.
return [
pad("", 10),
pad("turns", 8, "right"),
pad("cache hit", 10, "right"),
pad("cost (USD)", 14, "right"),
pad("vs Claude", 14, "right"),
pad("saved", 10, "right"),
].join(" ");
}
function divider(): string {
return "-".repeat(70);
}
function bucketRow(b: UsageBucket): string {
const hit = bucketCacheHitRatio(b);
const savings = bucketSavingsFraction(b);
return [
pad(b.label, 10),
pad(b.turns.toString(), 8, "right"),
pad(b.turns > 0 ? `${(hit * 100).toFixed(1)}%` : "—", 10, "right"),
pad(b.turns > 0 ? `$${b.costUsd.toFixed(6)}` : "—", 14, "right"),
pad(b.turns > 0 ? `$${b.claudeEquivUsd.toFixed(4)}` : "—", 14, "right"),
pad(b.turns > 0 && savings > 0 ? `${(savings * 100).toFixed(1)}%` : "—", 10, "right"),
].join(" ");
}
function pad(s: string, width: number, align: "left" | "right" = "left"): string {
if (s.length >= width) return s;
const fill = " ".repeat(width - s.length);
return align === "right" ? `${fill}${s}` : `${s}${fill}`;
}
+143
View File
@@ -0,0 +1,143 @@
/**
* `reasonix update` — self-upgrade command.
*
* Talks to the npm registry, compares against the running version,
* and either runs `npm install -g reasonix@latest` (global install)
* or advises how to refresh the npx cache (ephemeral install).
*
* The decision logic is factored into `planUpdate()` so it can be
* unit-tested without spawning child processes or hitting the
* network. `updateCommand()` is the thin CLI wrapper that calls
* `getLatestVersion`, passes the result into `planUpdate`, and
* executes any suggested command.
*/
import { spawn } from "node:child_process";
import { VERSION, compareVersions, getLatestVersion, isNpxInstall } from "../../version.js";
export type UpdateAction = "up-to-date" | "newer-local" | "npx-hint" | "run-npm-install";
export interface UpdatePlan {
action: UpdateAction;
/** Human-readable summary; the CLI prints this verbatim. */
message: string;
/**
* Argv for the install command when `action === "run-npm-install"`.
* Absent otherwise. Kept as array so the CLI can pass it straight
* to `spawn` without re-parsing shell syntax.
*/
command?: string[];
}
export interface PlanUpdateInput {
current: string;
latest: string;
/** Overrides `isNpxInstall()` (tests). */
npx?: boolean;
}
/**
* Pure decision function: given current + latest + install kind,
* decide what the CLI should do. No I/O.
*
* newer-local — current > latest (dev build, local publish)
* up-to-date — current === latest
* npx-hint — current < latest AND running under npx
* run-npm-install — current < latest AND running as a real install
*/
export function planUpdate(input: PlanUpdateInput): UpdatePlan {
const diff = compareVersions(input.current, input.latest);
if (diff > 0) {
return {
action: "newer-local",
message: `current (${input.current}) is newer than the published ${input.latest} — nothing to do.`,
};
}
if (diff === 0) {
return { action: "up-to-date", message: `reasonix ${input.current} is up to date.` };
}
if (input.npx) {
return {
action: "npx-hint",
message: [
`reasonix ${input.latest} is available.`,
"you're running via npx — the next `npx reasonix ...` launch will auto-fetch",
"the latest (npx caches packages for a short window). to force a refresh",
"sooner, clear the cache: `npm cache clean --force`.",
].join("\n"),
};
}
return {
action: "run-npm-install",
message: `upgrading reasonix ${input.current} → ${input.latest}`,
command: ["npm", "install", "-g", "reasonix@latest"],
};
}
export interface UpdateCommandOptions {
/** Skip spawning npm; print the decision only. */
dryRun?: boolean;
/** Test seam: override the registry lookup. Returns null = offline. */
fetchLatest?: () => Promise<string | null>;
/** Test seam: override the npx detector. */
isNpx?: () => boolean;
/** Test seam: override the spawner. Must return exit code. */
spawnInstall?: (argv: string[]) => Promise<number>;
/** Test seam: stdout writer. */
write?: (msg: string) => void;
/** Test seam: process exit — tests don't want to tear down vitest. */
exit?: (code: number) => void;
}
function defaultSpawn(argv: string[]): Promise<number> {
return new Promise((resolve, reject) => {
// `shell: true` on Windows is what lets `npm` resolve to `npm.cmd`
// without routing through our `prepareSpawn` helper. The args here
// are literal strings under our control — no user input flows in,
// so injection is not a concern. Avoiding `prepareSpawn` keeps
// this command free of a dep on the shell tools module.
const child = spawn(argv[0]!, argv.slice(1), {
stdio: "inherit",
shell: process.platform === "win32",
});
child.once("error", reject);
child.once("exit", (code) => resolve(code ?? 1));
});
}
/**
* Run the update command. Prints a banner, resolves the latest
* version, prints the plan, and (unless `--dry-run`) executes the
* install when applicable.
*/
export async function updateCommand(opts: UpdateCommandOptions = {}): Promise<void> {
const write = opts.write ?? ((m: string) => process.stdout.write(m));
const exit = opts.exit ?? ((c: number) => process.exit(c));
const fetchLatest = opts.fetchLatest ?? (() => getLatestVersion({ force: true }));
const isNpx = opts.isNpx ?? isNpxInstall;
const doSpawn = opts.spawnInstall ?? defaultSpawn;
write(`current: reasonix ${VERSION}\n`);
const latest = await fetchLatest();
if (!latest) {
write("could not reach registry.npmjs.org — check your network.\n");
exit(1);
return;
}
write(`latest: reasonix ${latest}\n`);
const plan = planUpdate({ current: VERSION, latest, npx: isNpx() });
write(`\n${plan.message}\n`);
if (plan.action !== "run-npm-install" || !plan.command) return;
if (opts.dryRun) {
write(`(dry run) would run: ${plan.command.join(" ")}\n`);
return;
}
write(`\nrunning: ${plan.command.join(" ")}\n`);
const code = await doSpawn(plan.command);
if (code !== 0) {
write(`\nnpm exited with code ${code}. upgrade did not complete.\n`);
exit(code);
}
}
+217 -33
View File
@@ -1,14 +1,43 @@
import { Command } from "commander";
import { readConfig } from "../config.js";
import { VERSION } from "../index.js";
import { ESCALATION_CONTRACT } from "../prompt-fragments.js";
import { applyMemoryStack } from "../user-memory.js";
import { chatCommand } from "./commands/chat.js";
import { codeCommand } from "./commands/code.js";
import { diffCommand } from "./commands/diff.js";
import { mcpInspectCommand } from "./commands/mcp-inspect.js";
import { mcpListCommand } from "./commands/mcp.js";
import { replayCommand } from "./commands/replay.js";
import { runCommand } from "./commands/run.js";
import { sessionsCommand } from "./commands/sessions.js";
import { setupCommand } from "./commands/setup.js";
import { statsCommand } from "./commands/stats.js";
import { updateCommand } from "./commands/update.js";
import { versionCommand } from "./commands/version.js";
import { resolveDefaults } from "./resolve.js";
const DEFAULT_SYSTEM =
"You are Reasonix, a helpful DeepSeek-powered assistant. Be concise and accurate. Use tools when available.";
const DEFAULT_SYSTEM = `You are Reasonix, a helpful DeepSeek-powered assistant. Be concise and accurate. Use tools when available.
# Cite or shut up — non-negotiable
Every factual claim about a codebase must be backed by evidence. Reasonix VALIDATES your citations — broken paths render in **red strikethrough with ❌** in front of the user.
**Positive claims** — append a markdown link:
- ✅ \`The MCP client supports listResources [listResources](src/mcp/client.ts:142).\`
- ❌ \`The MCP client supports listResources.\` ← unverifiable, do not write.
**Negative claims** ("X is missing", "Y isn't implemented", "lacks Z") are the #1 hallucination shape. STOP before writing them. If you have a search tool, call it first; if the search returns nothing, cite the search itself as evidence (\`No matches for "foo" in src/\`). If you have no tool, qualify hard: "I haven't verified — this is a guess."
Asserting absence without checking is how evaluative answers go wrong. Treat the urge to write "missing" as a red flag in your own reasoning.
# Don't invent what changes — search instead
Your training data has a cutoff. When an answer's correctness depends on something that changes over time (the user is asking what's happening, not what's true) and a search tool is available, search first. Inventing currently-correct values from training memory is the most common way these answers go wrong, and the user usually can't tell until much later.
The signal isn't a topic list — it's: "if I'm wrong about this, is it because reality moved on?". If yes, ground the answer in fresh evidence; if no (definitions, mechanisms, well-established APIs), answer from memory.
${ESCALATION_CONTRACT}`;
const program = new Command();
program
@@ -16,64 +45,182 @@ program
.description("DeepSeek-native agent framework — built for cache hits and cheap tokens.")
.version(VERSION);
// `reasonix` with no subcommand → launch the friendliest flow.
// First run (no config yet) → interactive setup wizard.
// Otherwise → chat with saved defaults. This is the "one command to
// rule them all" entry for non-power-users: they don't need to learn
// `chat` / `setup` / `--mcp` — just type `reasonix`.
program.action(async () => {
const cfg = readConfig();
if (!cfg.setupCompleted) {
await setupCommand({});
return;
}
const defaults = resolveDefaults({});
await chatCommand({
model: defaults.model,
system: applyMemoryStack(DEFAULT_SYSTEM, process.cwd()),
harvest: defaults.harvest,
branch: defaults.branch,
session: defaults.session,
mcp: defaults.mcp,
});
});
program
.command("chat")
.description("Interactive Ink TUI with live cache/cost panel.")
.option("-m, --model <id>", "DeepSeek model id", "deepseek-chat")
.option("-s, --system <prompt>", "System prompt (pinned in the immutable prefix)", DEFAULT_SYSTEM)
.command("setup")
.description("Interactive wizard — API key, preset, MCP servers. Re-run any time to reconfigure.")
.action(async () => {
await setupCommand({});
});
program
.command("code [dir]")
.description(
"Code-editing chat — filesystem tools rooted at <dir> (default: cwd), coding system prompt, v4-flash. Model proposes SEARCH/REPLACE blocks; Reasonix applies them to disk. Use /preset max or /pro to escalate to v4-pro on hard tasks.",
)
.option("-m, --model <id>", "Override default model (v4-flash)")
.option("--no-session", "Disable session persistence for this run")
.option("-r, --resume", "Skip the session picker — always continue prior messages")
.option("-n, --new", "Skip the session picker — always wipe prior messages and start fresh")
.option("--transcript <path>", "Write a JSONL transcript to this path")
.option(
"--harvest",
"Extract typed plan state from R1 reasoning (Pillar 2, adds a cheap V3 call per turn)",
"Opt-in Pillar-2 plan-state extraction. Adds one flash call per turn; off by default (no preset enables it).",
)
.action(async (dir: string | undefined, opts) => {
await codeCommand({
dir,
model: opts.model,
noSession: opts.session === false,
transcript: opts.transcript,
forceResume: !!opts.resume,
forceNew: !!opts.new,
harvest: !!opts.harvest,
});
});
program
.command("chat")
.description("Interactive Ink TUI with live cache/cost panel.")
.option("-m, --model <id>", "DeepSeek model id (overrides preset)")
.option("-s, --system <prompt>", "System prompt (pinned in the immutable prefix)", DEFAULT_SYSTEM)
.option("--transcript <path>", "Write a JSONL transcript to this path")
.option(
"--preset <name>",
"Model + effort bundle. One of: fast (flash·high), smart (flash·max, default), max (pro·max). Overrides config.preset.",
)
.option(
"--harvest",
"Opt-in Pillar-2 plan-state extraction. Off by default — no preset enables it.",
)
.option(
"--branch <n>",
"Self-consistency: run N parallel samples per turn and pick the most confident (disables streaming; enables harvest)",
"Self-consistency: run N parallel samples per turn (N× cost). Manual only — never auto-enabled.",
(v) => Number.parseInt(v, 10),
)
.option(
"--session <name>",
"Use a named session (default: 'default'). Resume the same session next time.",
)
.option("--session <name>", "Use a named session (default: from config, usually 'default').")
.option("--no-session", "Disable session persistence for this run (ephemeral chat)")
.option("-r, --resume", "Skip the session picker — always continue prior messages")
.option("-n, --new", "Skip the session picker — always wipe prior messages and start fresh")
.option(
"--mcp <spec>",
'MCP server spec; repeatable. "name=cmd args...", "cmd args...", or a URL (http/https → SSE transport). Overrides config.mcp when provided.',
(value: string, previous: string[] = []) => [...previous, value],
[] as string[],
)
.option(
"--mcp-prefix <str>",
"Global prefix applied to every MCP tool (only honored when no per-spec name is set; avoids collisions with a single anonymous server)",
)
.option("--no-config", "Ignore `~/.reasonix/config.json` — useful for CI or reproducing issues")
.action(async (opts) => {
// Default behavior: every chat is auto-saved to a session named 'default'
// and auto-resumed next launch. Pass --no-session to opt out, or
// --session <name> to use a different session.
let session: string | undefined;
if (opts.session === false) {
session = undefined; // --no-session
} else if (typeof opts.session === "string" && opts.session.length > 0) {
session = opts.session;
} else {
session = "default";
}
await chatCommand({
const defaults = resolveDefaults({
model: opts.model,
system: opts.system,
harvest: opts.harvest,
branch: opts.branch,
mcp: opts.mcp as string[],
session: opts.session,
preset: opts.preset,
noConfig: opts.config === false,
});
await chatCommand({
model: defaults.model,
system: applyMemoryStack(opts.system, process.cwd()),
transcript: opts.transcript,
harvest: !!opts.harvest,
branch: Number.isFinite(opts.branch) && opts.branch > 1 ? opts.branch : undefined,
session,
harvest: defaults.harvest,
branch: defaults.branch,
session: defaults.session,
mcp: defaults.mcp,
mcpPrefix: opts.mcpPrefix,
forceResume: !!opts.resume,
forceNew: !!opts.new,
});
});
program
.command("run <task>")
.description("Run a single task non-interactively, streaming output.")
.option("-m, --model <id>", "DeepSeek model id", "deepseek-chat")
.option("-m, --model <id>", "DeepSeek model id (overrides preset)")
.option("-s, --system <prompt>", "System prompt", DEFAULT_SYSTEM)
.option("--preset <name>", "Bundle of model + harvest + branch: fast | smart | max")
.option("--harvest", "Extract typed plan state from R1 reasoning (Pillar 2)")
.option(
"--branch <n>",
"Self-consistency: run N parallel samples per turn and pick the most confident",
(v) => Number.parseInt(v, 10),
)
.option("--transcript <path>", "Write a JSONL transcript to this path for replay/diff")
.option(
"--mcp <spec>",
'MCP server spec; repeatable. "name=cmd args...", "cmd args...", or a URL (http/https → SSE).',
(value: string, previous: string[] = []) => [...previous, value],
[] as string[],
)
.option(
"--mcp-prefix <str>",
"Global prefix (only honored when no per-spec name is set; for a single anonymous server)",
)
.option("--no-config", "Ignore `~/.reasonix/config.json` — useful for CI or reproducing issues")
.action(async (task: string, opts) => {
await runCommand({ task, model: opts.model, system: opts.system });
const defaults = resolveDefaults({
model: opts.model,
harvest: opts.harvest,
branch: opts.branch,
mcp: opts.mcp as string[],
preset: opts.preset,
noConfig: opts.config === false,
});
await runCommand({
task,
model: defaults.model,
system: applyMemoryStack(opts.system, process.cwd()),
harvest: defaults.harvest,
branch: defaults.branch,
transcript: opts.transcript,
mcp: defaults.mcp,
mcpPrefix: opts.mcpPrefix,
});
});
program
.command("stats <transcript>")
.description("Summarize a JSONL transcript produced by `reasonix chat --transcript`.")
.action((transcript: string) => {
.command("stats [transcript]")
.description(
"Show usage dashboard (today / week / month / all-time · turns · cache hit · cost · savings vs Claude). " +
"Pass a transcript path to fall back to the per-file summary (assistant turns + tool calls).",
)
.action((transcript: string | undefined) => {
statsCommand({ transcript });
});
program
.command("sessions [name]")
.description("List saved chat sessions, or inspect one by name.")
.option("-v, --verbose", "Include system prompts + tool-call metadata when inspecting")
.action((name: string | undefined, opts) => {
sessionsCommand({ name, verbose: !!opts.verbose });
});
program
.command("replay <transcript>")
.description(
@@ -113,8 +260,45 @@ program
});
});
const mcp = program
.command("mcp")
.description("Model Context Protocol helpers — discover servers, test your setup.");
mcp
.command("list")
.description("Show a curated catalog of popular MCP servers with ready-to-use --mcp commands.")
.option("--json", "Emit the catalog as JSON instead of the human-readable table")
.action((opts) => {
mcpListCommand({ json: !!opts.json });
});
mcp
.command("inspect <spec>")
.description(
'Connect to one MCP server and print its server info + tools/resources/prompts. <spec> takes the same forms as --mcp ("name=cmd args", "cmd args", or an SSE URL).',
)
.option("--json", "Emit the full inspection report as JSON instead of the human-readable summary")
.action(async (spec: string, opts) => {
try {
await mcpInspectCommand({ spec, json: !!opts.json });
} catch (err) {
process.stderr.write(`mcp inspect failed: ${(err as Error).message}\n`);
process.exit(1);
}
});
program.command("version").description("Print Reasonix version.").action(versionCommand);
program
.command("update")
.description(
"Check the npm registry for a newer Reasonix and install it. Detects npx vs global install; for npx users, prints a cache-refresh hint instead of running `npm i -g`.",
)
.option("--dry-run", "Print the plan without executing the install")
.action(async (opts: { dryRun?: boolean }) => {
await updateCommand({ dryRun: !!opts.dryRun });
});
program.parseAsync(process.argv).catch((err) => {
console.error(err);
process.exit(1);
+91
View File
@@ -0,0 +1,91 @@
/**
* Merge config defaults with CLI flags into the concrete options that
* `chatCommand` / `runCommand` need.
*
* Precedence (highest wins):
* 1. Explicit per-setting CLI flag (`--model`, `--harvest`, `--branch`, `--mcp`)
* 2. Explicit `--preset <name>` CLI flag
* 3. `config.preset` from `~/.reasonix/config.json` (set by `reasonix setup`)
* 4. Hardcoded "smart" preset defaults (flash + effort=max)
*
* Keeping this logic in one place — rather than duplicating across
* `chat` and `run` — means the precedence rule only lives in one unit
* test and the shape of the merge is identical for both commands.
*/
import { type PresetName, type ReasonixConfig, readConfig } from "../config.js";
import { PRESETS } from "./ui/presets.js";
export interface ResolvedDefaults {
model: string;
reasoningEffort: "high" | "max";
harvest: boolean;
branch: number | undefined;
mcp: string[];
session: string | undefined;
}
export interface RawCliFlags {
model?: string;
harvest?: boolean;
/** From `commander`; already parseInt'd. */
branch?: number;
mcp?: string[];
/** Commander's `--no-session` surfaces as `false`; `--session X` as a string. */
session?: string | false;
/** `--preset <name>`. */
preset?: string;
/** When true, ignore config entirely (power-user escape hatch). */
noConfig?: boolean;
}
export function resolveDefaults(flags: RawCliFlags): ResolvedDefaults {
const cfg: ReasonixConfig = flags.noConfig ? {} : readConfig();
const preset = pickPreset(flags.preset, cfg.preset);
const presetSettings = PRESETS[preset];
const model = flags.model ?? presetSettings.model;
const reasoningEffort = presetSettings.reasoningEffort;
const harvest = flags.harvest === true ? true : presetSettings.harvest;
const branchFromFlag = normalizeBranch(flags.branch);
const branch = branchFromFlag ?? (presetSettings.branch > 1 ? presetSettings.branch : undefined);
// `--mcp` accumulator is [] when absent. Treat empty from flags as
// "user didn't pass" → fall through to config. Users who explicitly
// want zero MCP servers can pass `--no-config` or edit the file.
const mcp = flags.mcp && flags.mcp.length > 0 ? flags.mcp : (cfg.mcp ?? []);
const session = resolveSession(flags.session, cfg.session);
return { model, reasoningEffort, harvest, branch, mcp, session };
}
function pickPreset(
flagPreset: string | undefined,
configPreset: PresetName | undefined,
): PresetName {
if (flagPreset && isPresetName(flagPreset)) return flagPreset;
if (configPreset) return configPreset;
return "smart";
}
function isPresetName(s: string): s is PresetName {
return s === "fast" || s === "smart" || s === "max";
}
function normalizeBranch(raw: number | undefined): number | undefined {
if (raw === undefined) return undefined;
if (!Number.isFinite(raw) || raw <= 1) return undefined;
return Math.min(raw, 8);
}
function resolveSession(
flag: string | false | undefined,
configSession: string | null | undefined,
): string | undefined {
if (flag === false) return undefined; // --no-session
if (typeof flag === "string" && flag.length > 0) return flag;
if (configSession === null) return undefined; // config opted out
if (typeof configSession === "string" && configSession.length > 0) return configSession;
return "default";
}
+2508 -70
View File
File diff suppressed because it is too large. Load diff
+86
View File
@@ -0,0 +1,86 @@
import { Box, Text } from "ink";
// biome-ignore lint/style/useImportType: tsconfig.jsx = "react" needs React in value scope for JSX compilation
import React from "react";
export interface AtMentionSuggestionsProps {
/**
* Current matching file paths, ranked by the picker. `null` means
* "not in @-prefix mode" — render nothing. Empty array means "in @
* mode but no files match that partial" — render a hint.
*/
matches: readonly string[] | null;
/** Index (within `matches`) of the currently highlighted row. */
selectedIndex: number;
/** The partial query the user typed after `@`. Shown in the hint row. */
query: string;
}
/**
* Floating `@`-mention picker. Rendered below the input box when the
* user is typing an `@…` prefix in code mode. Navigation state lives
* in the parent (App.tsx owns `atSelected`) — this component is pure
* display. Mirrors {@link SlashSuggestions} shape so the keybindings
* and layout feel identical across the two pickers.
*/
export function AtMentionSuggestions({
matches,
selectedIndex,
query,
}: AtMentionSuggestionsProps): React.ReactElement | null {
if (matches === null) return null;
if (matches.length === 0) {
return (
<Box paddingX={1} marginTop={1}>
<Text color="yellow">no files match "@{query}"</Text>
<Text dimColor>
{" "}
— keep typing, or Backspace to edit. Paths resolve from the code root.
</Text>
</Box>
);
}
const MAX = 8;
const total = matches.length;
const windowStart =
total <= MAX ? 0 : Math.max(0, Math.min(selectedIndex - Math.floor(MAX / 2), total - MAX));
const shown = matches.slice(windowStart, windowStart + MAX);
const hiddenAbove = windowStart;
const hiddenBelow = total - windowStart - shown.length;
return (
<Box flexDirection="column" paddingX={1} marginTop={1}>
{hiddenAbove > 0 ? <Text dimColor> ↑ {hiddenAbove} more above</Text> : null}
{shown.map((path, i) => (
<FileRow key={path} path={path} isSelected={windowStart + i === selectedIndex} />
))}
{hiddenBelow > 0 ? <Text dimColor> ↓ {hiddenBelow} more below</Text> : null}
<Text dimColor> [↑↓] navigate · [Tab]/[Enter] pick · file content inlined on send</Text>
</Box>
);
}
function FileRow({ path, isSelected }: { path: string; isSelected: boolean }) {
const marker = isSelected ? "▸" : " ";
// Split the path so the basename visually pops — same dropdown
// affordance as VS Code's Quick Open.
const slash = path.lastIndexOf("/");
const dir = slash >= 0 ? `${path.slice(0, slash)}/` : "";
const base = slash >= 0 ? path.slice(slash + 1) : path;
if (isSelected) {
return (
<Box>
<Text bold color="cyan">
{marker} {base}
</Text>
<Text color="cyan">{dir ? ` ${dir}` : ""}</Text>
</Box>
);
}
return (
<Box>
<Text dimColor>
{marker} {base}
{dir ? ` ${dir}` : ""}
</Text>
</Box>
);
}
+82
View File
@@ -0,0 +1,82 @@
/**
* Modal picker shown when the model calls `ask_choice`. Renders the
* question + 2–4 option rows (title + dimmed summary) + an optional
* "Let me type my own answer" escape hatch when `allowCustom` is true.
*
* The escape hatch matters because DeepSeek flash sometimes misframes
* the alternatives — none actually fit the user's intent. Without a
* bailout the user would have to cancel, type feedback, and wait for
* another round-trip. With it they just type and ship.
*
* Border color: magenta — deliberately distinct from cyan (plan),
* green (checkpoint), red (shell) so the user's eye learns the modes
* without reading headers.
*/
import { Box, Text } from "ink";
import React from "react";
import type { ChoiceOption } from "../../tools/choice.js";
import { SingleSelect } from "./Select.js";
export type ChoiceConfirmChoice =
| { kind: "pick"; optionId: string }
| { kind: "custom" }
| { kind: "cancel" };
export interface ChoiceConfirmProps {
question: string;
options: ChoiceOption[];
allowCustom: boolean;
onChoose: (choice: ChoiceConfirmChoice) => void;
}
const CUSTOM_VALUE = "__custom__";
const CANCEL_VALUE = "__cancel__";
function ChoiceConfirmInner({ question, options, allowCustom, onChoose }: ChoiceConfirmProps) {
const items: Array<{ value: string; label: string; hint?: string }> = options.map((opt) => ({
value: opt.id,
label: `${opt.id} · ${opt.title}`,
hint: opt.summary,
}));
if (allowCustom) {
items.push({
value: CUSTOM_VALUE,
label: "Let me type my own answer",
hint: "None of the above fits — type a free-form reply. The model reads it verbatim.",
});
}
items.push({
value: CANCEL_VALUE,
label: "Cancel — drop the question",
hint: "Model stops and asks what you want instead.",
});
return (
<Box flexDirection="column" borderStyle="round" borderColor="magenta" paddingX={1} marginY={1}>
<Box>
<Text bold color="magenta">
🔀 the model is asking you to pick
</Text>
</Box>
<Box marginTop={1}>
<Text>{question}</Text>
</Box>
<Box marginTop={1}>
<SingleSelect
initialValue={options[0]?.id}
items={items}
onSubmit={(v) => {
if (v === CUSTOM_VALUE) onChoose({ kind: "custom" });
else if (v === CANCEL_VALUE) onChoose({ kind: "cancel" });
else onChoose({ kind: "pick", optionId: v });
}}
onCancel={() => onChoose({ kind: "cancel" })}
footer="[↑↓] navigate · [Enter] select · [Esc] cancel"
/>
</Box>
</Box>
);
}
export const ChoiceConfirm = React.memo(ChoiceConfirmInner);
+220
View File
@@ -0,0 +1,220 @@
import { Box, Text, useInput, useStdout } from "ink";
import React, { useMemo, useState } from "react";
import { formatEditBlockDiff } from "../../code/diff-preview.js";
import type { EditBlock } from "../../code/edit-blocks.js";
/**
* Choice surfaced to the interceptor when the user resolves the modal:
* - `apply` → apply this edit, keep prompting on next.
* - `reject` → tell the model the user refused; do NOT
* retry the same edit.
* - `apply-rest-of-turn` → apply this edit AND every remaining edit
* this turn without further prompts. Resets
* at the next user turn.
* - `flip-to-auto` → apply this edit + persistently switch the
* session to AUTO mode (survives restart).
*/
export type EditReviewChoice = "apply" | "reject" | "apply-rest-of-turn" | "flip-to-auto";
export interface EditConfirmProps {
block: EditBlock;
onChoose: (choice: EditReviewChoice) => void;
}
/**
* Overhead reserved for non-diff UI inside the modal: border (2),
* title (1), separator (1), file-header (1), scroll-indicator rows
* (up to 2), footer + margin (3), plus breathing room for the host
* TUI's chrome above (stats panel ≈ 4, historical live rows, prompt
* input ≈ 2). 18 rows absorbed before the diff gets any budget.
*/
const MODAL_OVERHEAD_ROWS = 18;
/**
* Absolute floor on the diff viewport. If the terminal is absurdly
* short (< 26 rows total) we still show at least 8 diff lines so the
* modal is usable; the user scrolls more aggressively but can't end up
* with a zero-height viewport.
*/
const MIN_DIFF_ROWS = 8;
/**
* Modal-style approval for a single model-proposed file edit.
*
* Why per-edit instead of end-of-turn batch: users reported they can't
* tell if the model is about to make one small change or seven sprawling
* ones until the turn is over. Per-edit prompts let the user intervene
* early — reject a bad direction before the model builds on it, or
* approve the first few and hit `a` to let the rest land.
*
* Diff viewport: we compute the UNCAPPED diff once, then slice to a
* height budget derived from terminal rows. Large diffs (100+ lines)
* are scrollable via j/k/↑/↓/Space/PgUp/PgDn/g/G — the user can page
* through the whole change before deciding, and the action footer
* never scrolls off the bottom. Before the scroll support a 97-line
* scene.ts diff truncated at "… 67 more …" which was unreviewable.
*/
export function EditConfirm({ block, onChoose }: EditConfirmProps) {
const { stdout } = useStdout();
const rows = stdout?.rows ?? 40;
const budget = Math.max(MIN_DIFF_ROWS, rows - MODAL_OVERHEAD_ROWS);
// Full diff — maxLines pushed high enough that the diff-preview
// renderer never inserts its own truncation marker. Context trimming
// (contextLines) still applies for tight scan.
const allLines = useMemo(
() => formatEditBlockDiff(block, { contextLines: 2, maxLines: 100_000, indent: " " }),
[block],
);
const [scroll, setScroll] = useState(0);
const maxScroll = Math.max(0, allLines.length - budget);
// Clamp scroll if budget shrinks (terminal resized) after a previous
// keypress drove the offset past the new ceiling.
const effectiveScroll = Math.min(scroll, maxScroll);
useInput((input, key) => {
// Action keys first — decision wins over scroll so a user who
// hammered PgDn can still hit `y` at the end without a stray
// extra scroll.
if (key.return || input === "y") {
onChoose("apply");
return;
}
if (input === "n") {
onChoose("reject");
return;
}
if (input === "a") {
onChoose("apply-rest-of-turn");
return;
}
if (input === "A") {
onChoose("flip-to-auto");
return;
}
// Scroll navigation — vim-ish (j/k) and emacs-ish (arrows) both
// work. Space for "next page" is the pager convention.
if (key.downArrow || input === "j") {
setScroll((s) => Math.min(maxScroll, s + 1));
return;
}
if (key.upArrow || input === "k") {
setScroll((s) => Math.max(0, s - 1));
return;
}
if (key.pageDown || input === " " || input === "f") {
setScroll((s) => Math.min(maxScroll, s + Math.max(1, budget - 2)));
return;
}
if (key.pageUp || input === "b") {
setScroll((s) => Math.max(0, s - Math.max(1, budget - 2)));
return;
}
if (input === "g") {
setScroll(0);
return;
}
if (input === "G") {
setScroll(maxScroll);
return;
}
// Esc falls through to the parent abort handler.
});
const isNew = block.search === "";
const removed = isNew ? 0 : (block.search.match(/\n/g)?.length ?? 0) + 1;
const added = block.replace === "" ? 0 : (block.replace.match(/\n/g)?.length ?? 0) + 1;
const tag = isNew ? "NEW" : "EDIT";
const visibleLines = allLines.slice(effectiveScroll, effectiveScroll + budget);
const hiddenAbove = effectiveScroll;
const hiddenBelow = Math.max(0, allLines.length - effectiveScroll - budget);
const totalLines = allLines.length;
const showScrollHud = hiddenAbove + hiddenBelow > 0;
return (
<Box flexDirection="column" borderStyle="round" borderColor="yellow" paddingX={1} marginY={1}>
<Box>
<Text bold color="yellow">
{"▸ model wants to edit a file"}
</Text>
</Box>
<Box>
<Text color="yellow" dimColor>
{"──────────────────────────────────────────"}
</Text>
</Box>
<Box marginTop={1}>
<Text>
<Text color={isNew ? "green" : "yellow"} bold>{`[${tag}] `}</Text>
<Text color="cyan">{block.path}</Text>
<Text dimColor>{` (-${removed} +${added} lines)`}</Text>
{showScrollHud ? (
<Text dimColor>
{` · viewing ${effectiveScroll + 1}-${effectiveScroll + visibleLines.length}/${totalLines}`}
</Text>
) : null}
</Text>
</Box>
{hiddenAbove > 0 ? (
<Text
dimColor
>{` ↑ ${hiddenAbove} line${hiddenAbove === 1 ? "" : "s"} above (↑/k or PgUp)`}</Text>
) : null}
<Box marginTop={hiddenAbove > 0 ? 0 : 1} flexDirection="column">
{visibleLines.map((line, i) => {
const trimmed = line.trimStart();
const color = trimmed.startsWith("+")
? "green"
: trimmed.startsWith("-")
? "red"
: undefined;
const dim = !color;
return (
<Text
// Stable-enough: slice only shifts by scroll; React keys only
// need to be unique within the current render.
// biome-ignore lint/suspicious/noArrayIndexKey: list is static per render
key={`diff-${effectiveScroll}-${i}`}
color={color}
dimColor={dim}
>
{line}
</Text>
);
})}
</Box>
{hiddenBelow > 0 ? (
<Text
dimColor
>{` ↓ ${hiddenBelow} line${hiddenBelow === 1 ? "" : "s"} below (↓/j or Space/PgDn)`}</Text>
) : null}
<Box marginTop={1}>
<Text dimColor>
{"["}
<Text color="cyan" bold>
y
</Text>
{"/Enter] apply · ["}
<Text color="cyan" bold>
n
</Text>
{"] reject · ["}
<Text color="cyan" bold>
a
</Text>
{"] apply rest · ["}
<Text color="cyan" bold>
A
</Text>
{"] flip AUTO · ["}
<Text color="cyan" bold>
↑↓/Space
</Text>
{"] scroll · [Esc] abort"}
</Text>
</Box>
</Box>
);
}
+592 -89
View File
@@ -1,11 +1,51 @@
import { Box, Text } from "ink";
import React, { useEffect, useState } from "react";
import { Box, Text, useStdout } from "ink";
import React from "react";
import { type TypedPlanState, isPlanStateEmpty } from "../../harvest.js";
import type { BranchProgress, BranchSummary } from "../../loop.js";
import type { TurnStats } from "../../telemetry.js";
import type { PlanStep } from "../../tools/plan.js";
import { PlanStateBlock } from "./PlanStateBlock.js";
import { PlanStepList } from "./PlanStepList.js";
import { Markdown } from "./markdown.js";
import { useElapsedSeconds, useTick } from "./ticker.js";
import { formatDuration, summarizeToolResult } from "./tool-summary.js";
export type DisplayRole = "user" | "assistant" | "tool" | "system" | "error" | "info";
export type DisplayRole =
| "user"
| "assistant"
| "tool"
| "system"
| "error"
| "info"
| "warning"
/**
* A plan body pushed to scrollback when the model calls `submit_plan`.
* Rendered through the full markdown pipeline (not truncated), so the
* user reads the whole thing in the permanent Static log and the
* PlanConfirm modal below it stays a tight picker.
*/
| "plan"
/**
* One step of an approved plan ticked off via `mark_step_complete`.
* Rendered as a compact `✓ step-id · title — result (N/M)` row so
* the user can glance at the scrollback and see how far along the
* execution is without scrolling through every tool call.
*/
| "step-progress"
/**
* Pushed once at session startup when an existing plan was loaded
* from disk. Renders as a bordered box with the step list and
* progress so the user sees exactly where they left off — much
* more useful than the bare "2/5 done" info line it replaced.
*/
| "plan-resumed"
/**
* Read-only snapshot of an archived (completed) plan, pushed by
* the `/replay` slash. Visually distinct from `plan-resumed` —
* dim border + ⏪ icon — so the user immediately sees this is
* historical, not the active plan.
*/
| "plan-replay";
export interface DisplayEvent {
id: string;
@@ -16,19 +56,125 @@ export interface DisplayEvent {
branch?: BranchSummary;
branchProgress?: BranchProgress;
toolName?: string;
/**
* 1-based position in the session's tool-call history. Rendered as a
* dim `/tool N` suffix on compact rows so the user can quickly jump
* to the full output via the existing `/tool` slash command.
*/
toolIndex?: number;
/** Wall-clock duration in ms between tool_start and result. */
durationMs?: number;
stats?: TurnStats;
repair?: string;
streaming?: boolean;
toolCallBuild?: { name: string; chars: number; index?: number; readyCount?: number };
/**
* Populated on `step-progress` rows: the step id, optional title,
* completion counter, and optional notes. Rendered into the compact
* single-row layout — no other role reads these fields.
*/
stepProgress?: {
stepId: string;
title?: string;
completed: number;
total: number;
notes?: string;
};
/**
* Populated on `plan-resumed` rows: the structured plan loaded from
* disk + the set of step ids the user had already completed +
* a relative-time hint for the header. Rendered as a bordered
* snapshot so the user picks back up immediately.
*/
resumedPlan?: {
steps: PlanStep[];
completedStepIds: string[];
relativeTime: string;
/** Optional human-friendly title; rendered in the banner header when set. */
summary?: string;
};
/**
* Populated on `plan-replay` rows: the archived plan plus enough
* navigation context (index / total) for the user to know where
* they are in the archive history.
*/
replayPlan?: {
summary?: string;
body?: string;
steps: PlanStep[];
completedStepIds: string[];
relativeTime: string;
archiveBasename: string;
index: number;
total: number;
};
/**
* Render a thin horizontal rule above this event. Used to mark
* "start of a new user turn" so long scrollbacks get visual
* pacing — without it, five-turn sessions read as one wall of
* text. Only the *first* user message in a session should leave
* this off; App.tsx sets it based on whether history is empty.
*/
leadSeparator?: boolean;
}
export const EventRow = React.memo(function EventRow({ event }: { event: DisplayEvent }) {
/**
* Reasonix visual language: every event is anchored by a geometric
* glyph in its role color. Together they form a consistent alphabet
* (◇ ◆ ▣ ▥ ▲ ✦) the eye learns fast — no text labels needed after
* the first couple of turns. `◈` is the brand mark, reserved for
* the app header.
*/
const ROLE_GLYPH = {
user: "◇",
assistant: "◆",
assistantPulse: "◇", // pulse alternate for streaming state
toolOk: "▣",
toolErr: "▥",
warning: "▲",
error: "✦",
} as const;
function RoleGlyph({
glyph,
color,
}: {
glyph: string;
color: "cyan" | "green" | "yellow" | "red" | "magenta" | "blue";
}) {
return (
<Text color={color} bold>
{glyph}
</Text>
);
}
/**
* Pad continuation lines so wrapped multi-line text aligns under the
* glyph indent instead of jumping back to column 0. Header is `glyph
* (1 col) + " " (2 cols)`, so subsequent lines need 3 leading spaces
* to land under the body's first character.
*/
function indentContinuationLines(text: string): string {
if (!text.includes("\n")) return text;
return text.split("\n").join("\n ");
}
export const EventRow = React.memo(function EventRow({
event,
projectRoot,
}: {
event: DisplayEvent;
projectRoot?: string;
}) {
if (event.role === "user") {
return (
<Box>
<Text bold color="cyan">
you ›{" "}
<Box marginTop={event.leadSeparator ? 1 : 0}>
<RoleGlyph glyph={ROLE_GLYPH.user} color="cyan" />
<Text>
{" "}
{indentContinuationLines(event.text)}
</Text>
<Text>{event.text}</Text>
</Box>
);
}
@@ -37,36 +183,85 @@ export const EventRow = React.memo(function EventRow({ event }: { event: Display
return (
<Box flexDirection="column" marginTop={1}>
<Box>
<Text bold color="green">
assistant
</Text>
<RoleGlyph glyph={ROLE_GLYPH.assistant} color="green" />
{event.stats ? <Text dimColor>{` ${event.stats.model}`}</Text> : null}
</Box>
<Box flexDirection="column" paddingLeft={2} marginTop={1}>
{event.branch ? <BranchBlock branch={event.branch} /> : null}
{event.reasoning ? <ReasoningBlock reasoning={event.reasoning} /> : null}
{!isPlanStateEmpty(event.planState) ? (
<PlanStateBlock planState={event.planState!} />
) : null}
{event.text ? (
<Markdown text={event.text} projectRoot={projectRoot} />
) : (
<Text dimColor>(no content)</Text>
)}
{event.stats ? <StatsLine stats={event.stats} /> : null}
{event.repair ? <Text color="magenta">{event.repair}</Text> : null}
</Box>
{event.branch ? <BranchBlock branch={event.branch} /> : null}
{event.reasoning ? <ReasoningBlock reasoning={event.reasoning} /> : null}
{!isPlanStateEmpty(event.planState) ? (
<PlanStateBlock planState={event.planState!} />
) : null}
{event.text ? <Markdown text={event.text} /> : <Text dimColor>(no content)</Text>}
{event.stats ? <StatsLine stats={event.stats} /> : null}
{event.repair ? <Text color="magenta">{event.repair}</Text> : null}
</Box>
);
}
if (event.role === "tool") {
// `edit_file` results get a dedicated multi-line diff renderer —
// colored line-by-line so `-` removals show red, `+` additions
// show green, unchanged context lines dim. Always full, never
// truncated: users need to see the whole change to trust /apply.
const isExplicitError = event.text.startsWith("ERROR:");
const isEditFile =
(event.toolName === "edit_file" || event.toolName?.endsWith("_edit_file")) &&
!isExplicitError;
if (isEditFile) {
return (
<Box flexDirection="column" marginTop={1}>
<Box>
<RoleGlyph glyph={ROLE_GLYPH.toolOk} color="yellow" />
<Text color="yellow" bold>{` ${event.toolName ?? "?"}`}</Text>
<Text color="yellow" dimColor>
{" →"}
</Text>
</Box>
<Box flexDirection="column" paddingLeft={2} marginTop={1}>
<EditFileDiff text={event.text} />
</Box>
</Box>
);
}
// Compact one-line render for everything else. The summarizer
// produces a tool-aware one-liner (exit code for shell, line
// count for read_file, error tag for failures, ...). Full content
// remains accessible via `/tool N`, hinted as a dim suffix.
const summary = summarizeToolResult(event.toolName ?? "?", event.text);
const color = summary.isError ? "red" : "yellow";
const glyph = summary.isError ? ROLE_GLYPH.toolErr : ROLE_GLYPH.toolOk;
const marker = summary.isError ? "✗" : "→";
const durationLabel =
event.durationMs !== undefined && event.durationMs >= 100
? ` (${formatDuration(event.durationMs)})`
: "";
const indexHint = event.toolIndex !== undefined ? ` /tool ${event.toolIndex}` : "";
return (
<Box flexDirection="column" marginTop={1}>
<Text color="yellow">{`tool<${event.toolName ?? "?"}> →`}</Text>
<Text dimColor> {truncate(event.text, 400)}</Text>
<Box>
<RoleGlyph glyph={glyph} color={color} />
<Text color={color} bold>{` ${event.toolName ?? "?"}`}</Text>
{durationLabel ? <Text dimColor>{durationLabel}</Text> : null}
<Text color={color} dimColor>{` ${marker} `}</Text>
<Text color={summary.isError ? "red" : undefined} dimColor={!summary.isError}>
{summary.summary}
</Text>
{indexHint ? <Text dimColor>{indexHint}</Text> : null}
</Box>
);
}
if (event.role === "error") {
return (
<Box marginTop={1}>
<Text color="red" bold>
error{" "}
<RoleGlyph glyph={ROLE_GLYPH.error} color="red" />
<Text color="red">
{" "}
{indentContinuationLines(event.text)}
</Text>
<Text color="red">{event.text}</Text>
</Box>
);
}
@@ -77,6 +272,144 @@ export const EventRow = React.memo(function EventRow({ event }: { event: Display
</Box>
);
}
if (event.role === "plan") {
return (
<Box flexDirection="column" borderStyle="round" borderColor="cyan" paddingX={1} marginY={1}>
<Box>
<Text bold color="cyan">
{"📋 plan proposed — pick a choice below"}
</Text>
</Box>
<Box marginTop={1} flexDirection="column">
<Markdown text={event.text} projectRoot={projectRoot} />
</Box>
</Box>
);
}
if (event.role === "step-progress") {
const sp = event.stepProgress;
const counter = sp && sp.total > 0 ? ` (${sp.completed}/${sp.total})` : "";
const label = sp?.title ? `${sp.stepId} · ${sp.title}` : (sp?.stepId ?? "");
return (
<Box flexDirection="column" marginTop={1}>
<Box>
<Text color="green" bold>
✓
</Text>
<Text color="green">{` ${label}`}</Text>
<Text dimColor>{counter}</Text>
</Box>
{event.text ? (
<Box paddingLeft={2}>
<Text dimColor>{event.text}</Text>
</Box>
) : null}
{sp?.notes ? (
<Box paddingLeft={2}>
<Text color="yellow" dimColor>
{`note: ${sp.notes}`}
</Text>
</Box>
) : null}
</Box>
);
}
if (event.role === "plan-resumed") {
const rp = event.resumedPlan;
if (!rp || rp.steps.length === 0) return null;
const total = rp.steps.length;
const done = rp.completedStepIds.length;
const completedSet = new Set(rp.completedStepIds);
const statuses = new Map(
rp.steps.map((s) => [
s.id,
completedSet.has(s.id) ? ("done" as const) : ("pending" as const),
]),
);
// Focus the first pending step so the user immediately sees where
// execution will resume from. If the plan is fully done, no focus
// (the picker pattern uses › for "next up").
const nextStep = rp.steps.find((s) => !completedSet.has(s.id));
return (
<Box flexDirection="column" borderStyle="round" borderColor="cyan" paddingX={1} marginY={1}>
<Box flexDirection="column">
<Box>
<Text bold color="cyan">
▸ resumed plan
</Text>
<Text dimColor>{` ${done}/${total} done · last touched ${rp.relativeTime}`}</Text>
</Box>
{rp.summary ? (
<Box>
<Text color="cyan">{` ${rp.summary}`}</Text>
</Box>
) : null}
</Box>
<Box marginTop={1} flexDirection="column">
<PlanStepList steps={rp.steps} statuses={statuses} focusStepId={nextStep?.id} />
</Box>
</Box>
);
}
if (event.role === "plan-replay") {
const r = event.replayPlan;
if (!r || r.steps.length === 0) return null;
const total = r.steps.length;
const completedSet = new Set(r.completedStepIds);
const done = completedSet.size;
const statuses = new Map(
r.steps.map((s) => [s.id, completedSet.has(s.id) ? ("done" as const) : ("pending" as const)]),
);
const navHint = r.total > 1 ? ` · ${r.index}/${r.total}` : "";
return (
<Box flexDirection="column" borderStyle="round" borderColor="gray" paddingX={1} marginY={1}>
<Box flexDirection="column">
<Box>
<Text bold dimColor>
⏪ replay
</Text>
<Text
dimColor
>{` completed ${r.relativeTime} · ${done}/${total} done${navHint}`}</Text>
</Box>
{r.summary ? (
<Box>
<Text dimColor>{` ${r.summary}`}</Text>
</Box>
) : null}
<Box>
<Text dimColor>{` ${r.archiveBasename}`}</Text>
</Box>
</Box>
{r.body ? (
<Box marginTop={1} flexDirection="column">
<Markdown text={r.body} projectRoot={projectRoot} />
</Box>
) : null}
<Box marginTop={1} flexDirection="column">
<PlanStepList steps={r.steps} statuses={statuses} />
</Box>
<Box marginTop={1}>
<Text dimColor>
{r.total > 1
? `(read-only · /replay ${r.index === 1 ? 2 : 1} for the ${r.index === 1 ? "next" : "newest"} archive)`
: "(read-only · this is an archived plan)"}
</Text>
</Box>
</Box>
);
}
if (event.role === "warning") {
return (
<Box>
<RoleGlyph glyph={ROLE_GLYPH.warning} color="yellow" />
<Text color="yellow">
{" "}
{indentContinuationLines(event.text)}
</Text>
</Box>
);
}
return (
<Box>
<Text>{event.text}</Text>
@@ -84,6 +417,87 @@ export const EventRow = React.memo(function EventRow({ event }: { event: Display
);
});
/**
* Thin horizontal rule between turns with a cyan ◆ centered as the
* Reasonix mark. Past-turn separators live inside `<Static>` (Ink's
* render-once optimization), so animation here would freeze at
* tick=0 on every past turn — we keep it static by design. The
* animated heartbeat lives in PulsingAssistantGlyph (current turn)
* and the Wordmark (StatsPanel) where rerender is free.
*/
function TurnSeparator() {
const { stdout } = useStdout();
const cols = stdout?.columns ?? 80;
const width = Math.max(16, cols - 2);
const half = Math.floor((width - 3) / 2);
const left = "─".repeat(half);
const right = "─".repeat(width - half - 3);
return (
<Box marginTop={1} marginBottom={1}>
<Text dimColor>{left}</Text>
<Text color="cyan" bold>
{" ◆ "}
</Text>
<Text dimColor>{right}</Text>
</Box>
);
}
/**
* Render the payload of an `edit_file` tool result with proper
* diff coloring: first line is the header ("edited X (A→B chars)"),
* subsequent lines are prefixed with `-` (removed), `+` (added), or
* space (unchanged context). Unchanged lines render dim so the
* changed ones pop visually. No truncation — the whole diff is
* shown so the user can audit what landed before `/apply` or
* `git diff` review.
*/
function EditFileDiff({ text }: { text: string }) {
const lines = text.split(/\r?\n/);
// Line 0 is the status header ("edited X (A→B chars)"), Line 1 is
// the unified-diff hunk header ("@@ -N,M +N,M @@"), the rest is
// the colored diff body. We style the two headers distinctly so
// the hunk marker stands out the way git-diff's cyan `@@` does in
// most terminals.
const [statusHeader, hunkHeader, ...body] = lines;
return (
<Box flexDirection="column">
<Text dimColor>{` ${statusHeader ?? ""}`}</Text>
{hunkHeader !== undefined ? (
<Text color="cyan" bold>
{hunkHeader}
</Text>
) : null}
{body.map((line, i) => {
// Key includes the line content slice so React isn't forced
// to treat purely-positional identity; lines in the same
// diff don't reorder but could repeat (e.g. blank lines).
const key = `${i}-${line.slice(0, 32)}`;
if (line.startsWith("- ")) {
return (
<Text key={key} color="red">
{line}
</Text>
);
}
if (line.startsWith("+ ")) {
return (
<Text key={key} color="green">
{line}
</Text>
);
}
// Context line (starts with " ") or unknown — dim.
return (
<Text key={key} dimColor>
{line}
</Text>
);
})}
</Box>
);
}
function BranchBlock({ branch }: { branch: BranchSummary }) {
const per = branch.uncertainties
.map((u, i) => {
@@ -95,7 +509,7 @@ function BranchBlock({ branch }: { branch: BranchSummary }) {
return (
<Box>
<Text color="blue">
{"🔀 branched "}
{"⎇ branched "}
<Text bold>{branch.budget}</Text>
{` samples → picked #${branch.chosenIndex} `}
<Text dimColor>{per}</Text>
@@ -104,35 +518,25 @@ function BranchBlock({ branch }: { branch: BranchSummary }) {
);
}
function PlanStateBlock({ planState }: { planState: TypedPlanState }) {
const lines: Array<[string, string[]]> = [];
if (planState.subgoals.length) lines.push(["subgoals", planState.subgoals]);
if (planState.hypotheses.length) lines.push(["hypotheses", planState.hypotheses]);
if (planState.uncertainties.length) lines.push(["uncertainties", planState.uncertainties]);
if (planState.rejectedPaths.length) lines.push(["rejected", planState.rejectedPaths]);
return (
<Box flexDirection="column" marginBottom={1}>
{lines.map(([label, items]) => (
<Text key={label} color="magenta">
{"‹ "}
<Text bold>{label}</Text>
{` (${items.length}): ${items.join(" · ")}`}
</Text>
))}
</Box>
);
}
function ReasoningBlock({ reasoning }: { reasoning: string }) {
const max = 220;
const max = 260;
const flat = reasoning.replace(/\s+/g, " ").trim();
// Show the TAIL of the reasoning rather than the head. R1 opens
// with generic scaffolding ("let me look at the structure...") that
// repeats across turns and hides the part users actually want to
// see — the decision right before the model commits to an action.
// Users can dump the full reasoning with `/think` if needed.
const preview =
flat.length <= max ? flat : `${flat.slice(0, max)}… (+${flat.length - max} chars)`;
flat.length <= max ? flat : `… (+${flat.length - max} earlier chars) ${flat.slice(-max)}`;
// ▏ (LEFT ONE EIGHTH BLOCK) renders as a thin vertical rule at the
// cell edge — subtler than the role-level ▎ above, giving a
// visual hierarchy: thick bar = role, thin bar = nested detail
// under that role (thinking, stats, citations, etc).
return (
<Box marginBottom={1}>
<Text dimColor>▏ </Text>
<Text dimColor italic>
{"↳ thinking: "}
{preview}
thinking {preview}
</Text>
</Box>
);
@@ -144,17 +548,28 @@ function ReasoningBlock({ reasoning }: { reasoning: string }) {
* the terminal viewport and leaves artifacts in scrollback.
*/
function Elapsed() {
const [s, setS] = useState(0);
useEffect(() => {
const start = Date.now();
const id = setInterval(() => setS(Math.floor((Date.now() - start) / 1000)), 1000);
return () => clearInterval(id);
}, []);
const s = useElapsedSeconds();
const mm = String(Math.floor(s / 60)).padStart(2, "0");
const ss = String(s % 60).padStart(2, "0");
return <Text dimColor>{`${mm}:${ss}`}</Text>;
}
/**
* Animated role glyph for the actively-streaming assistant. Alternates
* ◆ ↔ ◇ every ~480ms so the user can see the model is alive even
* during R1's long pre-first-byte silence. Settles back to a static
* ◆ once the turn ends (StreamingAssistant is unmounted).
*/
function PulsingAssistantGlyph() {
const tick = useTick();
const on = Math.floor(tick / 4) % 2 === 0;
return (
<Text color="green" bold>
{on ? ROLE_GLYPH.assistant : ROLE_GLYPH.assistantPulse}
</Text>
);
}
function StreamingAssistant({ event }: { event: DisplayEvent }) {
if (event.branchProgress) {
const p = event.branchProgress;
@@ -163,15 +578,17 @@ function StreamingAssistant({ event }: { event: DisplayEvent }) {
return (
<Box flexDirection="column" marginTop={1}>
<Box>
<Text bold color="green">
assistant{" "}
</Text>
<PulsingAssistantGlyph />
<Text color="blue">
🔀 launching {p.total} parallel samples (R1 thinking in parallel)…{" "}
{" ⎇ launching "}
{p.total}
{" parallel samples (R1 thinking in parallel)… "}
</Text>
<Elapsed />
</Box>
<Text dimColor>{" "}spread across T=0.0/0.5/1.0 · typical wait 30-90s for reasoner</Text>
<Text color="yellow">
{" "}spread across T=0.0/0.5/1.0 · reasoner typically takes 30-90s — this is normal
</Text>
</Box>
);
}
@@ -179,11 +596,13 @@ function StreamingAssistant({ event }: { event: DisplayEvent }) {
return (
<Box flexDirection="column" marginTop={1}>
<Box>
<Text bold color="green">
assistant{" "}
</Text>
<PulsingAssistantGlyph />
<Text color="blue">
🔀 branching {p.completed}/{p.total} ({pct}%){" "}
{" ⎇ branching "}
{p.completed}/{p.total}
{" ("}
{pct}
{"%) "}
</Text>
<Elapsed />
</Box>
@@ -202,16 +621,50 @@ function StreamingAssistant({ event }: { event: DisplayEvent }) {
const tail = lastLine(event.text, 140);
const reasoningTail = event.reasoning ? lastLine(event.reasoning, 120) : "";
const toolCallBuild = event.toolCallBuild;
// Four distinct phases a turn can be in — label them plainly so
// the user doesn't have to decode "streaming · 391 + think 4506
// chars" to figure out what's happening:
// pre-first-byte: request in flight, no bytes back yet
// reasoning-only: R1 thinking, no visible content yet
// tool-call-only: tool_call arguments streaming, no content/reasoning bytes
// writing: content streaming (R1 has already produced its thought)
// both: rare — content present AND reasoning still growing
// We can't cheaply distinguish "reasoning still growing" from
// "reasoning finished but we already saw it", so when content is
// present we just say "writing response" and surface both counts.
const preFirstByte = !event.text && !event.reasoning && !toolCallBuild;
const reasoningOnly = !event.text && !!event.reasoning && !toolCallBuild;
const toolCallOnly = !event.text && !event.reasoning && !!toolCallBuild;
let label: string;
let labelColor: "yellow" | "cyan" | "green" | "magenta" | undefined;
if (preFirstByte) {
label = "request sent · waiting for server";
labelColor = "yellow";
} else if (reasoningOnly) {
label = `R1 reasoning · ${event.reasoning?.length ?? 0} chars of thought`;
labelColor = "cyan";
} else if (toolCallOnly) {
label = `assembling tool call${formatToolCallIndex(toolCallBuild)} <${toolCallBuild.name}> · ${toolCallBuild.chars} chars of arguments${formatReadyTail(toolCallBuild)}`;
labelColor = "magenta";
} else {
const parts: string[] = [`writing response · ${event.text.length} chars`];
if (event.reasoning) parts.push(`after ${event.reasoning.length} chars of reasoning`);
if (toolCallBuild) {
parts.push(
`building tool call${formatToolCallIndex(toolCallBuild)} <${toolCallBuild.name}> · ${toolCallBuild.chars} chars${formatReadyTail(toolCallBuild)}`,
);
}
label = parts.join(" · ");
labelColor = "green";
}
return (
<Box flexDirection="column" marginTop={1}>
<Box>
<Text bold color="green">
assistant{" "}
</Text>
<Text dimColor>
(streaming · {event.text.length}
{event.reasoning ? ` + think ${event.reasoning.length}` : ""} chars){" "}
</Text>
<PulsingAssistantGlyph />
<Text>{" "}</Text>
<Pulse />
<Text color={labelColor}>{` ${label} `}</Text>
<Elapsed />
</Box>
{reasoningTail ? (
@@ -221,15 +674,66 @@ function StreamingAssistant({ event }: { event: DisplayEvent }) {
) : null}
{tail ? (
<Text dimColor>▸ {tail}</Text>
) : (
<Text dimColor italic>
{" (waiting for first token…)"}
) : preFirstByte ? (
// Non-dim yellow: first-time users misread the dim version as
// "app frozen". The reassurance has to be VISIBLE to do its job.
<Text color="yellow" italic>
{" waiting for first byte — this is normal, typically 5-60s depending on model + load"}
</Text>
)}
) : reasoningOnly ? (
<Text color="yellow" italic>
{
" R1 is thinking before it speaks — body text arrives when reasoning finishes (typically 20-90s, this is normal)"
}
</Text>
) : toolCallOnly ? (
<Text color="magenta" italic>
{" tool-call arguments streaming — the model is about to dispatch a tool"}
</Text>
) : event.reasoning ? (
<Text color="yellow" italic>
{" R1 still reasoning — body text or tool call arrives when thinking finishes"}
</Text>
) : null}
</Box>
);
}
/**
* Blinking indicator so the user can tell the stream is alive even
* when the reasoner hasn't produced body text yet. Uses the shared
* tick (TICK_MS ≈ 120ms) scaled down 4× so the visible blink rate
* lands around 500ms — feels like a heartbeat, not a progress bar.
*/
function Pulse() {
const tick = useTick();
const frames = ["⠋", "⠙", "⠹", "⠸", "⠼", "⠴", "⠦", "⠧", "⠇", "⠏"];
return <Text color="cyan">{frames[Math.floor(tick / 4) % frames.length]}</Text>;
}
/**
* "(call 3)" suffix for the tool-call label when we have the index.
* Hides when the turn only has one call so the common case stays tidy.
*/
function formatToolCallIndex(tb: { index?: number; readyCount?: number } | undefined): string {
if (!tb || tb.index === undefined) return "";
// Only show the index when this isn't obviously the first + only call.
if (tb.index === 0 && (tb.readyCount ?? 0) === 0) return "";
return ` (call ${tb.index + 1})`;
}
/**
* "· 2 ready" tail that answers "how many tool calls have finished
* streaming so far this turn?" — user feedback for multi-file turns
* where the response takes 10–30s to stream. Hidden until readyCount
* > 0 so single-call turns aren't cluttered.
*/
function formatReadyTail(tb: { readyCount?: number } | undefined): string {
const n = tb?.readyCount ?? 0;
if (n <= 0) return "";
return ` · ${n} ready`;
}
function lastLine(s: string, maxChars: number): string {
const flat = s.replace(/\s+/g, " ").trim();
if (!flat) return "";
@@ -239,19 +743,18 @@ function lastLine(s: string, maxChars: number): string {
function StatsLine({ stats }: { stats: TurnStats }) {
const hit = (stats.cacheHitRatio * 100).toFixed(1);
return (
<Text dimColor>
{" ↳ cache "}
{hit}
{"% · tokens "}
{stats.usage.promptTokens}
{"→"}
{stats.usage.completionTokens}
{" · $"}
{stats.cost.toFixed(6)}
</Text>
<Box>
<Text dimColor>▏ </Text>
<Text dimColor>
{"cache "}
{hit}
{"% · tokens "}
{stats.usage.promptTokens}
{" → "}
{stats.usage.completionTokens}
{" · $"}
{stats.cost.toFixed(6)}
</Text>
</Box>
);
}
function truncate(s: string, max: number): string {
return s.length <= max ? s : `${s.slice(0, max)}… (+${s.length - max} chars)`;
}
+275
View File
@@ -0,0 +1,275 @@
import { Box, Text } from "ink";
import React from "react";
import type { ApplyResult } from "../../code/edit-blocks.js";
import type { EditMode } from "../../config.js";
import type { JobRegistry } from "../../tools/jobs.js";
import { useElapsedSeconds, useTick } from "./ticker.js";
export const SPINNER_FRAMES = ["⠋", "⠙", "⠹", "⠸", "⠼", "⠴", "⠦", "⠧", "⠇", "⠏"];
/**
* Transient "what's happening now" row shown during silent phases
* between the primary events — harvest round-trip, R1 thinking
* about a tool result before the next streaming delta, forced
* summary. Matches OngoingToolRow's visual language (braille
* spinner + elapsed seconds) so the user's eyes track the same
* spot regardless of which kind of wait it is.
*/
export function StatusRow({ text }: { text: string }) {
const tick = useTick();
const elapsed = useElapsedSeconds();
return (
<Box marginY={1}>
<Text color="magenta">{SPINNER_FRAMES[tick % SPINNER_FRAMES.length]}</Text>
<Text color="magenta">{` ${text}`}</Text>
<Text dimColor>{` ${elapsed}s`}</Text>
</Box>
);
}
/**
* One-line bottom status bar showing the current edit mode, pending
* queue size (review only), an undo hint (auto only / after /apply),
* and the Shift+Tab nudge. Rendered immediately above PromptInput so
* the mode is always in peripheral vision when the user's eyes are at
* the prompt. Flashes briefly on mode change so Shift+Tab gives a
* visible acknowledgment without the user having to scan the header.
*
* The plan-mode pill takes precedence — when plan mode is on, writes
* are bounced regardless of edit mode, so surfacing it is more useful
* than the review/auto toggle.
*/
export function ModeStatusBar({
editMode,
pendingCount,
flash,
planMode,
undoArmed,
jobs,
}: {
editMode: EditMode;
pendingCount: number;
flash: boolean;
planMode: boolean;
undoArmed: boolean;
jobs?: JobRegistry;
}) {
// Subscribe to tick so the jobs count stays live — the registry is
// mutated outside React, so we need a periodic repaint to catch it.
// No-op when there's no registry (chat mode / tests).
useTick();
const running = jobs?.runningCount() ?? 0;
const jobsTag =
running > 0 ? (
<Text color="yellow" bold>{` · ⏵ ${running} job${running === 1 ? "" : "s"}`}</Text>
) : null;
if (planMode) {
return (
<Box paddingX={1}>
<Text color="red" bold inverse={flash}>
{"▸ PLAN"}
</Text>
<Text dimColor>
{" writes gated — submit_plan + approval required · /plan off to leave"}
</Text>
{jobsTag}
</Box>
);
}
const label = editMode === "auto" ? "AUTO" : "review";
const color = editMode === "auto" ? "magenta" : "cyan";
const mid =
editMode === "auto"
? undoArmed
? "edits apply immediately · u = undo last batch"
: "edits apply immediately · 5s undo window after each batch"
: pendingCount > 0
? `${pendingCount} queued · y = /apply · n = /discard`
: "edits queue for review · y = /apply · n = /discard";
const flip = editMode === "auto" ? "Shift+Tab → review" : "Shift+Tab → AUTO";
return (
<Box paddingX={1}>
<Text color={color} bold inverse={flash}>
{`▸ ${label}`}
</Text>
<Text dimColor>{` ${mid} · ${flip}`}</Text>
{jobsTag}
</Box>
);
}
/**
* "Just auto-applied N edits — press u to undo" banner. Rendered below
* the live rows after an auto-mode edit batch lands, visible for 5s.
* `useTick` drives a crude live countdown so the user sees the window
* shrinking. State cleanup (the banner disappearing) happens in the
* parent's setTimeout — the component is purely display.
*/
export function UndoBanner({
banner,
}: {
banner: { results: ApplyResult[]; expiresAt: number };
}) {
useTick();
const remainingMs = Math.max(0, banner.expiresAt - Date.now());
const remainingSec = Math.ceil(remainingMs / 1000);
const ok = banner.results.filter((r) => r.status === "applied" || r.status === "created").length;
const total = banner.results.length;
return (
<Box marginY={1} borderStyle="round" borderColor="magenta" paddingX={1}>
<Text color="magenta" bold>
{"✓ auto-applied "}
</Text>
<Text color="magenta">{`${ok}/${total} edit${total === 1 ? "" : "s"}`}</Text>
<Text dimColor>{" · press "}</Text>
<Text color="magenta" bold>
{"u"}
</Text>
<Text dimColor>{" to undo ("}</Text>
<Text color={remainingSec <= 1 ? "red" : "magenta"}>{`${remainingSec}s`}</Text>
<Text dimColor>{")"}</Text>
</Box>
);
}
/**
* Live one-line indicator for a running subagent. Sits below the
* OngoingToolRow (the parent's tool dispatch row for `spawn_subagent`)
* so the user sees both layers at once: outer "spawn_subagent
* running…" + inner "⌬ subagent: <task> · iter N · 12.3s". Cleared
* when the subagent ends; a one-line summary lands in historical.
*/
export function SubagentRow({
activity,
}: {
activity: { task: string; iter: number; elapsedMs: number };
}) {
const tick = useTick();
const seconds = (activity.elapsedMs / 1000).toFixed(1);
return (
<Box paddingLeft={2}>
<Text color="magenta">{SPINNER_FRAMES[tick % SPINNER_FRAMES.length]}</Text>
<Text color="magenta">{` ⌬ subagent: ${activity.task}`}</Text>
<Text dimColor>{` · iter ${activity.iter} · ${seconds}s`}</Text>
</Box>
);
}
/**
* Live spinner row while a tool call is in flight. Without this the
* window between the model's `tool_calls` decision and the tool's
* result (often seconds for a multi-KB `filesystem_edit_file`) looks
* like the app has frozen — the streaming assistant display is
* already cleared and the input is disabled, so there's nothing to
* look at.
*
* Shows three signals: a braille spinner (liveness), an elapsed
* timer in seconds (so "long" has a number attached), and a
* per-tool summary of the most informative argument fields (path,
* edits count, pattern, etc.). As of 0.4.8, MCP progress frames
* (`notifications/progress`) land here too — bar + "n/N" when the
* server reports a total, free-form message when not.
*/
export function OngoingToolRow({
tool,
progress,
}: {
tool: { name: string; args?: string };
progress: { progress: number; total?: number; message?: string } | null;
}) {
const tick = useTick();
const elapsed = useElapsedSeconds();
const summary = summarizeToolArgs(tool.name, tool.args);
return (
<Box marginY={1} flexDirection="column">
<Box>
<Text color="cyan">{SPINNER_FRAMES[tick % SPINNER_FRAMES.length]}</Text>
<Text color="yellow">{` tool<${tool.name}> running…`}</Text>
<Text dimColor>{` ${elapsed}s`}</Text>
</Box>
{progress ? (
<Box paddingLeft={2}>
<Text color="cyan">{renderProgressLine(progress)}</Text>
</Box>
) : null}
{summary ? (
<Box paddingLeft={2}>
<Text dimColor>{summary}</Text>
</Box>
) : null}
</Box>
);
}
/**
* Render an MCP progress frame as a single line. When the server
* reports `total`, show an ASCII progress bar + "n/total pct%";
* otherwise just "progress" + optional message. Width is modest
* so the line fits even in a narrow terminal.
*/
function renderProgressLine(p: { progress: number; total?: number; message?: string }): string {
const msg = p.message ? ` ${p.message}` : "";
if (p.total && p.total > 0) {
const ratio = Math.max(0, Math.min(1, p.progress / p.total));
const width = 20;
const filled = Math.round(ratio * width);
const bar = "█".repeat(filled) + "░".repeat(width - filled);
const pct = (ratio * 100).toFixed(0);
return `[${bar}] ${p.progress}/${p.total} ${pct}%${msg}`;
}
return `progress: ${p.progress}${msg}`;
}
/**
* Turn raw JSON tool arguments into a one-line human summary. For
* common filesystem MCP tools we pull the actually-useful fields; for
* anything else we fall back to a truncated raw string so the user
* still sees *something* beyond the tool name.
*
* Match on suffix (e.g. `_read_file`) rather than exact name because
* `bridgeMcpTools({ namePrefix: "filesystem_" })` prepends the server
* namespace — tools arrive as `filesystem_read_file` in practice but
* callers might wire up anonymous too.
*/
function summarizeToolArgs(name: string, args?: string): string {
if (!args || args === "{}") return "";
let parsed: Record<string, unknown>;
try {
parsed = JSON.parse(args) as Record<string, unknown>;
} catch {
// Unparseable JSON — show a head slice so user at least sees
// what the model tried.
return args.length > 80 ? `${args.slice(0, 80)}…` : args;
}
const hasSuffix = (s: string) => name === s || name.endsWith(`_${s}`);
const path = typeof parsed.path === "string" ? parsed.path : undefined;
if (hasSuffix("read_file")) {
const head = typeof parsed.head === "number" ? `, head=${parsed.head}` : "";
const tail = typeof parsed.tail === "number" ? `, tail=${parsed.tail}` : "";
return `path: ${path ?? "?"}${head}${tail}`;
}
if (hasSuffix("write_file")) {
const content = typeof parsed.content === "string" ? parsed.content : "";
return `path: ${path ?? "?"} (${content.length} chars)`;
}
if (hasSuffix("edit_file")) {
const edits = Array.isArray(parsed.edits) ? parsed.edits.length : 0;
return `path: ${path ?? "?"} (${edits} edit${edits === 1 ? "" : "s"})`;
}
if (hasSuffix("list_directory") || hasSuffix("directory_tree")) {
return `path: ${path ?? "?"}`;
}
if (hasSuffix("search_files")) {
const pattern = typeof parsed.pattern === "string" ? parsed.pattern : "?";
return `path: ${path ?? "?"} · pattern: ${pattern}`;
}
if (hasSuffix("move_file")) {
const src = typeof parsed.source === "string" ? parsed.source : "?";
const dst = typeof parsed.destination === "string" ? parsed.destination : "?";
return `${src} → ${dst}`;
}
if (hasSuffix("get_file_info")) {
return `path: ${path ?? "?"}`;
}
return args.length > 80 ? `${args.slice(0, 80)}…` : args;
}
+124
View File
@@ -0,0 +1,124 @@
/**
* Modal-style picker shown when `mark_step_complete` pauses the loop
* via `PlanCheckpointError`. Three choices:
*
* 1. Continue — push "Step X done, proceed." so the model starts
* the next step on the next turn.
* 2. Revise — open a feedback input; whatever the user types
* becomes a synthetic "user feedback for remaining steps" message.
* The model can then adjust its approach without starting the
* whole plan over.
* 3. Stop — push "User stopped the plan. Summarize what was
* done." so the run ends cleanly rather than being abandoned.
*
* The ✓ step-progress scrollback row is pushed separately (by App.tsx
* at checkpoint detection time), so this modal stays a tight picker —
* no need to re-render the step body here.
*/
import { Box, Text } from "ink";
import React from "react";
import type { PlanStep } from "../../tools/plan.js";
import { PlanStepList, type StepStatus } from "./PlanStepList.js";
import { SingleSelect } from "./Select.js";
export type CheckpointChoice = "continue" | "revise" | "stop";
export interface PlanCheckpointConfirmProps {
stepId: string;
title?: string;
completed: number;
total: number;
/** Full step list from the approved plan, when available. */
steps?: PlanStep[];
/** Set of stepIds the model has marked complete so far. */
completedStepIds?: Set<string>;
onChoose: (choice: CheckpointChoice) => void;
}
function PlanCheckpointConfirmInner({
stepId,
title,
completed,
total,
steps,
completedStepIds,
onChoose,
}: PlanCheckpointConfirmProps) {
const label = title ? `${stepId} · ${title}` : stepId;
const counter = total > 0 ? ` (${completed}/${total})` : "";
const isLast = total > 0 && completed >= total;
const statuses = buildStatusMap(steps, completedStepIds, stepId, isLast);
return (
<Box flexDirection="column" borderStyle="round" borderColor="green" paddingX={1} marginY={1}>
<Box>
<Text bold color="green">
▸ checkpoint — step done
</Text>
<Text dimColor>{` ${label}${counter}`}</Text>
</Box>
{steps && steps.length > 0 ? (
<Box marginTop={1} flexDirection="column">
<PlanStepList steps={steps} statuses={statuses} focusStepId={stepId} />
</Box>
) : null}
<Box marginTop={1}>
<SingleSelect
initialValue={isLast ? "stop" : "continue"}
items={[
{
value: "continue",
label: "Continue — run the next step",
hint: "Model resumes with the next step. Use this when the result looks right and you don't need to tweak the remaining plan.",
},
{
value: "revise",
label: "Revise — give feedback before the next step",
hint: "Stay paused, type guidance (scope changes, skip steps, alternative approach). The model adjusts the remaining plan based on your message.",
},
{
value: "stop",
label: "Stop — end the plan here",
hint: "Model summarizes what was done and ends. Remaining steps are skipped.",
},
]}
onSubmit={(v) => onChoose(v as CheckpointChoice)}
onCancel={() => onChoose("stop")}
footer="[↑↓] navigate · [Enter] select · [Esc] stop"
/>
</Box>
</Box>
);
}
export const PlanCheckpointConfirm = React.memo(PlanCheckpointConfirmInner);
/**
* Derive a status map from the plan + completion set + current step.
* The currently-just-finished step always renders as "done" even if
* completedStepIds hasn't been flushed yet (it gets added in the
* same render cycle, order not guaranteed). Steps ahead of the
* cursor are "pending"; the next step after the current one isn't
* marked "running" because nothing is actually running while the
* picker is up — that belongs to the post-continue state.
*/
function buildStatusMap(
steps: PlanStep[] | undefined,
completedStepIds: Set<string> | undefined,
currentStepId: string,
isLast: boolean,
): Map<string, StepStatus> {
const map = new Map<string, StepStatus>();
if (!steps) return map;
for (const step of steps) {
if (completedStepIds?.has(step.id) || step.id === currentStepId) {
map.set(step.id, "done");
} else {
map.set(step.id, "pending");
}
}
if (isLast) {
// Every step is done; leave as "done" — no "running" overlay.
}
return map;
}
+108
View File
@@ -0,0 +1,108 @@
/**
* Modal-style approval for a `submit_plan` proposal.
*
* Three choices:
* 1. Approve + implement — exits plan mode, pushes a synthetic user
* message telling the model to implement the plan now.
* 2. Refine — stays in plan mode; tells the model to explore more
* and submit an improved plan.
* 3. Cancel — exits plan mode, drops the plan, tells the model the
* user didn't want any of it.
*
* The plan BODY is NOT rendered inside this modal — App.tsx pushes it
* into the Static scrollback as a `role: "plan"` display event the
* moment submit_plan fires. That's a one-time markdown render into
* permanent history, so the user reads the full proposal above and
* the modal below stays a tight picker. The previous design (body
* rendered inside the modal with an aggressive line clamp) left users
* staring at "(25 more lines truncated)" and unable to approve safely.
*/
import { Box, Text } from "ink";
import React from "react";
import type { PlanStep } from "../../tools/plan.js";
import { PlanStepList } from "./PlanStepList.js";
import { SingleSelect } from "./Select.js";
export type PlanConfirmChoice = "approve" | "refine" | "cancel";
export interface PlanConfirmProps {
plan: string;
steps?: PlanStep[];
/** Optional human-friendly title from the model — surfaced in the header. */
summary?: string;
onChoose: (choice: PlanConfirmChoice) => void;
projectRoot?: string;
}
function PlanConfirmInner({ plan, steps, summary, onChoose }: PlanConfirmProps) {
// Crude signal for "the model left questions or risks for me" — the
// typical section headings. Triggers an extra hint toward the Refine
// option so users know where to answer them.
const hasOpenQuestions =
/^#{1,6}\s*(open[-\s]?questions?|risks?|unknowns?|assumptions?|unclear)/im.test(plan) ||
/^#{1,6}\s*(待确认|开放问题|风险|未知|假设|不确定)/im.test(plan);
return (
<Box flexDirection="column" borderStyle="round" borderColor="cyan" paddingX={1} marginY={1}>
<Box flexDirection="column">
<Box>
<Text bold color="cyan">
▸ plan proposed (full text above) — approve / refine / cancel
</Text>
</Box>
{summary ? (
<Box>
<Text color="cyan">{` ${summary}`}</Text>
</Box>
) : null}
</Box>
{hasOpenQuestions ? (
<Box marginTop={1}>
<Text color="yellow">
▲ the plan flags open questions or risks — pick{" "}
<Text bold>Refine / answer questions</Text> to write concrete answers before the model
moves on.
</Text>
</Box>
) : null}
{steps && steps.length > 0 ? (
<Box marginTop={1} flexDirection="column">
<PlanStepList steps={steps} />
</Box>
) : null}
<Box marginTop={1}>
<SingleSelect
initialValue={hasOpenQuestions ? "refine" : "approve"}
items={[
{
value: "approve",
label: "Approve and implement",
hint: "Exit plan mode. The model starts executing. You'll get a text input to add any last instructions (or just press Enter to skip).",
},
{
value: "refine",
label: "Refine / answer questions",
hint: "Stay in plan mode. Write answers, modifications, or critiques; the model revises and re-submits.",
},
{
value: "cancel",
label: "Cancel",
hint: "Exit plan mode. Drop the plan; the model won't implement it.",
},
]}
onSubmit={(v) => onChoose(v as PlanConfirmChoice)}
onCancel={() => onChoose("cancel")}
footer="[↑↓] navigate · [Enter] select · [Esc] cancel"
/>
</Box>
</Box>
);
}
// React.memo: parent App re-renders every 120ms while the global ticker
// is running (even with the live status rows hidden — context changes
// propagate). Unless props change, skip re-rendering the heavy Markdown
// subtree. Default shallow prop compare is fine — `plan` + `onChoose`
// identity + `projectRoot` are the only fields that change.
export const PlanConfirm = React.memo(PlanConfirmInner);
+106
View File
@@ -0,0 +1,106 @@
/**
* Inline text input shown after the user picks Approve or Refine in
* PlanConfirm. Collects free-form feedback before the loop resumes.
*
* Why both paths: the plan may contain open questions or risks the
* model asked the user to weigh in on. If the user just picks Approve
* with no chance to answer, the model implements against its own
* guesses. This input lets the user answer questions, pass last-minute
* constraints, or (on Refine) request concrete changes. Empty input is
* fine for Approve (skip straight to implement) and triggers a
* "ask the user clarifying questions" path for Refine.
*
* Kept minimal: single-line prompt, Enter to submit, Esc to return to
* the picker without resuming.
*/
import { Box, Text, useInput } from "ink";
import React, { useState } from "react";
export interface PlanRefineInputProps {
/**
* Which path the user is on. approve = "implement with these last
* instructions"; refine = "revise the plan with this feedback";
* checkpoint-revise = mid-execution pause, user is tweaking the
* remaining plan after seeing a step's result; choice-custom = user
* typed an off-list answer to an ask_choice branch. Drives the
* header + hint text so users know what kind of message they're
* writing.
*/
mode: "approve" | "refine" | "checkpoint-revise" | "choice-custom";
/** Called with trimmed feedback. Empty string is allowed. */
onSubmit: (feedback: string) => void;
/** Called when the user presses Esc to return to the picker. */
onCancel: () => void;
}
export function PlanRefineInput({ mode, onSubmit, onCancel }: PlanRefineInputProps) {
const [value, setValue] = useState("");
useInput((input, key) => {
if (key.escape) {
onCancel();
return;
}
if (key.return) {
onSubmit(value.trim());
return;
}
if (key.backspace || key.delete) {
setValue((v) => v.slice(0, -1));
return;
}
// Filter out non-printable chars; accept ordinary text + CJK.
if (input && !key.ctrl && !key.meta) {
setValue((v) => v + input);
}
});
const title =
mode === "approve"
? "▸ approving — any last instructions or answers to open questions?"
: mode === "checkpoint-revise"
? "▸ revising — what should change before the next step?"
: mode === "choice-custom"
? "▸ custom answer — type whatever fits"
: "▸ refining — what should the model change?";
const hint =
mode === "approve"
? "Answer questions the plan raised, add constraints, or just press Enter to approve as-is."
: mode === "checkpoint-revise"
? "Scope change, skip steps, alternative approach — the model will adjust the remaining plan based on this."
: mode === "choice-custom"
? "Free-form reply. The model reads it verbatim and proceeds — no need to match the listed options."
: "Describe what's wrong or missing, or answer questions the plan raised.";
const blankHint =
mode === "approve"
? " (Enter with blank = approve without extra instructions.)"
: mode === "checkpoint-revise"
? " (Enter with blank = continue with the current plan.)"
: mode === "choice-custom"
? " (Enter with blank = ask the model what you actually want.)"
: " (Enter with blank = ask the model to list concrete questions.)";
return (
<Box flexDirection="column" borderStyle="round" borderColor="yellow" paddingX={1} marginY={1}>
<Box>
<Text bold color="yellow">
{title}
</Text>
</Box>
<Box marginTop={1}>
<Text dimColor>
{hint} Enter to send · Esc to return to the picker.
{value === "" ? blankHint : ""}
</Text>
</Box>
<Box marginTop={1}>
<Text>
<Text color="yellow">› </Text>
<Text>{value || " "}</Text>
<Text color="yellow">▍</Text>
</Text>
</Box>
</Box>
);
}
+146
View File
@@ -0,0 +1,146 @@
/**
* Modal shown when the model proposes a plan revision via
* `revise_plan`. Renders a step-level diff between the old remaining
* tail and the new proposed tail:
*
* ●● ✓ step-2 · Wire middleware (kept, dim)
* − ●●● ✗ step-3 · Migrate session cookies (removed, red)
* + ●● ▶ step-3 · Skip cookie migration (added, green)
* + ●● ▶ step-4 · Update cookie tests (added, green)
*
* Two buttons: Accept / Reject. Accept replaces the in-memory plan's
* remaining steps with the new ones; Reject leaves the original plan
* intact and lets the model continue. The picker's border is amber
* to distinguish from the green checkpoint picker — revisions are a
* different decision point, deserve a different visual lane.
*/
import { Box, Text } from "ink";
import React from "react";
import type { PlanStep } from "../../tools/plan.js";
import { SingleSelect } from "./Select.js";
export type ReviseChoice = "accept" | "reject";
export interface PlanReviseConfirmProps {
reason: string;
/** Remaining steps from the current plan (before this revision). */
oldRemaining: PlanStep[];
/** Remaining steps the model is proposing as a replacement. */
newRemaining: PlanStep[];
/** Optional updated plan summary. */
summary?: string;
onChoose: (choice: ReviseChoice) => void;
}
interface DiffRow {
kind: "kept" | "removed" | "added";
step: PlanStep;
}
function computeDiff(oldSteps: PlanStep[], newSteps: PlanStep[]): DiffRow[] {
const oldIds = new Set(oldSteps.map((s) => s.id));
const newIds = new Set(newSteps.map((s) => s.id));
const rows: DiffRow[] = [];
// Show removed (in old, not in new) first — preserve original order.
for (const s of oldSteps) {
if (!newIds.has(s.id)) rows.push({ kind: "removed", step: s });
}
// Then walk new list. Steps in both lists render as kept; new-only as added.
for (const s of newSteps) {
rows.push({ kind: oldIds.has(s.id) ? "kept" : "added", step: s });
}
return rows;
}
function riskDots(risk: PlanStep["risk"]): {
dots: string;
color: "green" | "yellow" | "red" | "gray";
} {
switch (risk) {
case "high":
return { dots: "●●●", color: "red" };
case "med":
return { dots: "●● ", color: "yellow" };
case "low":
return { dots: "● ", color: "green" };
default:
return { dots: " ", color: "gray" };
}
}
function PlanReviseConfirmInner({
reason,
oldRemaining,
newRemaining,
summary,
onChoose,
}: PlanReviseConfirmProps) {
const rows = computeDiff(oldRemaining, newRemaining);
const removedCount = rows.filter((r) => r.kind === "removed").length;
const addedCount = rows.filter((r) => r.kind === "added").length;
const keptCount = rows.filter((r) => r.kind === "kept").length;
return (
<Box flexDirection="column" borderStyle="round" borderColor="yellow" paddingX={1} marginY={1}>
<Box>
<Text bold color="yellow">
✏ plan revision proposed
</Text>
<Text dimColor>{` −${removedCount} +${addedCount} (${keptCount} kept)`}</Text>
</Box>
<Box marginTop={1}>
<Text>{reason}</Text>
</Box>
{summary ? (
<Box marginTop={1}>
<Text dimColor>{`updated summary: ${summary}`}</Text>
</Box>
) : null}
<Box marginTop={1} flexDirection="column">
{rows.map((row) => {
const risk = riskDots(row.step.risk);
const prefix = row.kind === "removed" ? "−" : row.kind === "added" ? "+" : " ";
const prefixColor =
row.kind === "removed" ? "red" : row.kind === "added" ? "green" : "gray";
const dim = row.kind === "kept";
const strike = row.kind === "removed";
return (
<Box key={`${row.kind}-${row.step.id}`}>
<Text color={prefixColor} bold>
{`${prefix} `}
</Text>
<Text color={risk.color} bold dimColor={dim}>
{risk.dots}
</Text>
<Text dimColor={dim} strikethrough={strike}>
{` ${row.step.id} · ${row.step.title}`}
</Text>
</Box>
);
})}
</Box>
<Box marginTop={1}>
<SingleSelect
initialValue="accept"
items={[
{
value: "accept",
label: "Accept revision — apply the new step list",
hint: "Replaces the remaining plan with the proposed steps. Done steps are untouched.",
},
{
value: "reject",
label: "Reject — keep the original plan",
hint: "Drops the proposal. Model continues with the original remaining steps.",
},
]}
onSubmit={(v) => onChoose(v as ReviseChoice)}
onCancel={() => onChoose("reject")}
footer="[↑↓] navigate · [Enter] select · [Esc] reject"
/>
</Box>
</Box>
);
}
export const PlanReviseConfirm = React.memo(PlanReviseConfirmInner);
+48
View File
@@ -0,0 +1,48 @@
/**
* Shared Ink block that renders a TypedPlanState. Used by the live chat
* EventLog AND by the RecordView in replay/diff TUIs, so harvest output
* looks identical live and on replay.
*
* Colors are semantic (not decorative):
* - subgoals: cyan — structure / plan
* - hypotheses: green — current beliefs (like assistant)
* - uncertainties: yellow — attention required (like tool)
* - rejected paths: red dim — ruled out (muted, like error-but-resolved)
*
* Only the label is colored + bold. The items themselves render in the
* terminal's default foreground, so they stay readable on any background —
* which is why the old single-magenta block was hard to see on dark themes.
*/
import { Box, Text } from "ink";
import React from "react";
import type { TypedPlanState } from "../../harvest.js";
type FieldColor = "cyan" | "green" | "yellow" | "red";
export function PlanStateBlock({ planState }: { planState: TypedPlanState }) {
const fields: Array<[string, string[], FieldColor, boolean]> = [];
if (planState.subgoals.length) fields.push(["subgoals", planState.subgoals, "cyan", false]);
if (planState.hypotheses.length)
fields.push(["hypotheses", planState.hypotheses, "green", false]);
if (planState.uncertainties.length)
fields.push(["uncertainties", planState.uncertainties, "yellow", false]);
if (planState.rejectedPaths.length)
fields.push(["rejected", planState.rejectedPaths, "red", true]);
if (fields.length === 0) return null;
return (
<Box flexDirection="column" marginBottom={1}>
{fields.map(([label, items, color, dim]) => (
<Text key={label}>
<Text color={color} bold dimColor={dim}>
{"‹ "}
{label}
</Text>
<Text dimColor>{` (${items.length})`}</Text>
<Text>{`: ${items.join(" · ")}`}</Text>
</Text>
))}
</Box>
);
}
+138
View File
@@ -0,0 +1,138 @@
/**
* Shared compact renderer for a plan's structured step list. Used by
* PlanConfirm (on approval) and PlanCheckpointConfirm (mid-execution)
* so the user always sees the same visual representation of the plan.
*
* Layout per step:
*
* ● ✓ step-1 · Extract tokens into a module
* ●●▶ step-2 · Migrate session cookies
* ●●● step-3 · Update tests
*
* The risk gutter (1–3 dots, green/yellow/red) is the signal the user
* learns to scan: high-risk steps are what deserves review before
* approve; low-risk is noise.
*/
import { Box, Text } from "ink";
import React from "react";
import type { PlanStep, PlanStepRisk } from "../../tools/plan.js";
export type StepStatus = "pending" | "running" | "done" | "skipped";
export interface PlanStepListProps {
steps: PlanStep[];
/**
* Map of stepId → status. Missing ids default to "pending" so a
* plan just submitted (no completions yet) renders cleanly.
*/
statuses?: Map<string, StepStatus> | Record<string, StepStatus>;
/**
* Optional current step — rendered with a `›` gutter mark so the
* user sees which one just completed / is about to run.
*/
focusStepId?: string;
}
function riskDots(risk: PlanStep["risk"]): {
dots: string;
color: "green" | "yellow" | "red" | "gray";
} {
switch (risk) {
case "high":
return { dots: "●●●", color: "red" };
case "med":
return { dots: "●● ", color: "yellow" };
case "low":
return { dots: "● ", color: "green" };
default:
return { dots: " ", color: "gray" };
}
}
function statusGlyph(status: StepStatus): {
glyph: string;
color: "green" | "cyan" | "gray" | "yellow";
} {
switch (status) {
case "done":
return { glyph: "✓", color: "green" };
case "running":
return { glyph: "▶", color: "cyan" };
case "skipped":
return { glyph: "—", color: "gray" };
default:
return { glyph: " ", color: "yellow" };
}
}
function getStatus(stepId: string, statuses: PlanStepListProps["statuses"]): StepStatus {
if (!statuses) return "pending";
if (statuses instanceof Map) {
return statuses.get(stepId) ?? "pending";
}
return statuses[stepId] ?? "pending";
}
function PlanStepListInner({ steps, statuses, focusStepId }: PlanStepListProps) {
if (steps.length === 0) return null;
const hasAnyRisk = steps.some((s) => s.risk !== undefined);
const doneCount = Array.from({ length: steps.length }, (_, i) =>
getStatus(steps[i]!.id, statuses),
).filter((s) => s === "done").length;
return (
<Box flexDirection="column">
<Box>
<Text dimColor>
{`${steps.length} step${steps.length === 1 ? "" : "s"}`}
{doneCount > 0 ? ` · ${doneCount} done` : ""}
{hasAnyRisk ? " · risk: " : ""}
</Text>
{hasAnyRisk ? <RiskLegend /> : null}
</Box>
<Box flexDirection="column" marginTop={1}>
{steps.map((step) => {
const status = getStatus(step.id, statuses);
const focus = focusStepId === step.id;
const risk = riskDots(step.risk);
const glyph = statusGlyph(status);
const titleDim = status === "done" || status === "skipped";
return (
<Box key={step.id}>
<Text color={focus ? "cyan" : "gray"} bold={focus}>
{focus ? "› " : " "}
</Text>
<Text color={risk.color} bold>
{risk.dots}
</Text>
<Text color={glyph.color} bold>
{` ${glyph.glyph} `}
</Text>
<Text dimColor={titleDim}>{`${step.id} · ${step.title}`}</Text>
</Box>
);
})}
</Box>
</Box>
);
}
function RiskLegend() {
return (
<Box>
<Text color="green">●</Text>
<Text dimColor> low </Text>
<Text color="yellow">●●</Text>
<Text dimColor> med </Text>
<Text color="red">●●●</Text>
<Text dimColor> high</Text>
</Box>
);
}
export const PlanStepList = React.memo(PlanStepListInner);
export function riskOf(step: PlanStep): PlanStepRisk | undefined {
return step.risk;
}
+500 -20
View File
@@ -1,6 +1,38 @@
import { Box, Text } from "ink";
import TextInput from "ink-text-input";
import React from "react";
import { Box, Text, useInput, useStdout } from "ink";
// biome-ignore lint/style/useImportType: tsconfig jsx=react needs React as a runtime value (classic transform compiles JSX to React.createElement)
import React, { useRef, useState } from "react";
import { type MultilineKey, lineAndColumn, processMultilineKey } from "./multiline-keys.js";
import {
PASTE_SENTINEL_RANGE,
type PasteEntry,
decodePasteSentinel,
encodePasteSentinel,
expandPasteSentinels,
formatBytesShort,
listPasteIdsInBuffer,
makePasteEntry,
} from "./paste-sentinels.js";
import { useTick } from "./ticker.js";
/**
* DECSET 2004 (bracketed paste) markers. The terminal sends these
* around every paste action when bracketed-paste mode is enabled
* (App.tsx writes the enable sequence at mount). Surface as exact
* literal byte strings so we can locate them in `input` regardless
* of how stdin chunks the surrounding bytes.
*/
const PASTE_START_MARKER = "\u001b[200~";
const PASTE_END_MARKER = "\u001b[201~";
/**
* Merge-fallback window for terminals that strip bracketed-paste
* markers (Windows PowerShell + ConPTY + Ink eats `\x1b[200~`).
* One Ctrl+V arrives as N chunks 1-5ms apart; we collapse them by
* checking arrival time + that the previous sentinel is still at
* cursor-1 (no typing happened). 30ms is well below the ~100ms
* minimum a human can release+repress Ctrl+V, so deliberate
* back-to-back pastes never falsely merge.
*/
const PASTE_MERGE_WINDOW_MS = 30;
export interface PromptInputProps {
value: string;
@@ -8,13 +40,27 @@ export interface PromptInputProps {
onSubmit: (v: string) => void;
disabled?: boolean;
placeholder?: string;
/**
* History recall. Fired when ↑/↓ hits a buffer boundary (empty
* buffer, or cursor already at the first/last line of a multi-line
* buffer). Parent walks its prompt history and swaps the value via
* `onChange`. Absent → keys are consumed silently.
*/
onHistoryPrev?: () => void;
onHistoryNext?: () => void;
}
/**
* Keep `<TextInput>` mounted at all times and use its `focus` prop to gate
* input. Conditionally rendering it (mount / unmount between turns) loses
* the stdin raw-mode claim on some terminals, which silently drops
* keystrokes after the first turn finishes.
* Input box with real cursor support. ←/→ move one column, ↑/↓ move
* across lines in multi-line buffers, Ctrl+A / Ctrl+E jump to
* start/end of the current line. Backspace deletes before cursor,
* Delete deletes under cursor. Multi-line composition via Ctrl+J,
* Shift+Enter, or bash-style `\<Enter>`.
*
* Cursor state lives locally. When the parent replaces `value` out
* of band (history recall, slash completion, setup wizard) the
* cursor jumps to end; the `lastLocalValueRef` guards distinguishes
* that case from our own edits.
*/
export function PromptInput({
value,
@@ -22,22 +68,456 @@ export function PromptInput({
onSubmit,
disabled,
placeholder,
onHistoryPrev,
onHistoryNext,
}: PromptInputProps) {
const [cursor, setCursor] = useState(value.length);
// Paste registry. Maps sentinel id → original paste content. Each
// entry is keyed by the codepoint stored in the buffer string.
// Lives in a ref because rendering doesn't depend on identity —
// mutating the map in-place is fine, the per-keystroke render
// reads the current state directly. `nextPasteIdRef` wraps modulo
// PASTE_SENTINEL_RANGE; collisions are rare in practice (256 slots,
// typical session has <10 pastes).
const pastesRef = useRef<Map<number, PasteEntry>>(new Map());
const nextPasteIdRef = useRef<number>(0);
// Bracketed-paste accumulator. When a paste begins, the terminal
// sends `\x1b[200~`; when it ends, `\x1b[201~`. We accumulate
// everything between markers into ONE entry. Works on terminals
// that pass markers through to Ink intact (iTerm, kitty, alacritty,
// most modern terminals on macOS/Linux). Doesn't work on Windows
// PowerShell+ConPTY where Ink's parse-keypress eats the markers
// before we see them — fallback below covers that case.
// null = not currently inside a paste; string = accumulating.
const pasteAccumRef = useRef<string | null>(null);
// Tight time-window merge fallback. When bracketed-paste markers
// don't reach us (Ink ate them, terminal didn't send them, etc.),
// a single user paste arrives as N stdin chunks 1-5ms apart, and
// each chunk on its own looks like a paste burst (multi-line
// content). Without merging the user gets four `[paste #N]`
// placeholders for one Ctrl+V. With a 30ms window + a guard that
// the previous sentinel is still right at cursor-1 (no typing
// happened in between), chunks of one paste collapse into one
// entry. The window is below human reaction time for double-
// pasting (Ctrl+V release → re-press takes 100ms+), so two
// deliberate pastes never falsely merge.
const lastPasteRef = useRef<{ id: number; at: number } | null>(null);
// Tracks the last `value` we ourselves produced via onChange. If the
// incoming `value` prop diverges from this, the parent (or some other
// source) replaced the buffer — we reset the cursor to end.
const lastLocalValueRef = useRef(value);
if (value !== lastLocalValueRef.current) {
lastLocalValueRef.current = value;
if (cursor !== value.length) {
// Conditional setState during render is the "derived state" pattern;
// React schedules the re-render and the else branch of the `if`
// prevents infinite loops.
setCursor(value.length);
}
}
// Synchronous mirror of `cursor` for the same reason. When two
// useInput firings happen in the same React tick (PowerShell+Ink
// emits useInput twice per stdin chunk), the second fire's
// closure still sees the stale `cursor` from before the first
// fire's setCursor took effect. Reading from a ref we update
// synchronously inside `registerPaste` lets the second fire's
// merge guard see the just-inserted sentinel at cursor-1.
const cursorRef = useRef(cursor);
cursorRef.current = cursor;
// Shared ticker drives the cursor blink. Dividing the tick by 4 lands
// the visible on/off cycle around 480ms — standard cursor cadence.
const tick = useTick();
const showCursor = disabled ? false : Math.floor(tick / 4) % 2 === 0;
// Helper: register an accumulated paste blob and insert its
// sentinel into the buffer at the current cursor. If the previous
// paste's sentinel is still at cursor-1 AND we're inside the
// sub-human-reaction merge window, append to that entry instead
// of creating a new sentinel — this collapses chunks of one
// user paste action that arrived as multiple stdin reads (the
// PowerShell+ConPTY+Ink case where bracketed-paste markers got
// eaten upstream).
const registerPaste = (content: string) => {
// Read from refs, NOT from closure variables. PowerShell+Ink
// fires useInput twice per stdin chunk; both fires close over
// the same stale `value` and `cursor` from React state. Refs
// get updated synchronously below, so the second fire sees the
// just-inserted sentinel at cursor-1 and the merge guard fires
// correctly. This was the core reason a single Ctrl+V kept
// producing four `[paste #N]` placeholders.
const v = lastLocalValueRef.current;
const c = cursorRef.current;
const now = Date.now();
const last = lastPasteRef.current;
const prevChar = c > 0 ? v[c - 1] : null;
const prevId = prevChar ? decodePasteSentinel(prevChar) : null;
const canMerge =
last !== null &&
prevId === last.id &&
now - last.at < PASTE_MERGE_WINDOW_MS &&
pastesRef.current.has(last.id);
if (canMerge && last) {
const existing = pastesRef.current.get(last.id);
if (existing) {
const merged = existing.content + content;
pastesRef.current.set(last.id, makePasteEntry(last.id, merged));
lastPasteRef.current = { id: last.id, at: now };
return;
}
}
const id = nextPasteIdRef.current % PASTE_SENTINEL_RANGE;
nextPasteIdRef.current = id + 1;
pastesRef.current.set(id, makePasteEntry(id, content));
const sentinel = encodePasteSentinel(id);
const next = v.slice(0, c) + sentinel + v.slice(c);
// Update refs synchronously so the SECOND useInput fire (same
// React tick) sees the new buffer + cursor. Then schedule the
// React state updates for re-render.
lastLocalValueRef.current = next;
cursorRef.current = c + 1;
onChange(next);
setCursor(c + 1);
lastPasteRef.current = { id, at: now };
};
useInput(
(input, key) => {
// Bracketed-paste accumulator. The terminal tells us EXACTLY
// when a paste begins / ends via `\x1b[200~` / `\x1b[201~`.
// Even when a 50KB paste arrives across many stdin reads,
// the markers bracket the entire paste once. We accumulate
// everything between them into a single sentinel — solving
// the "one user paste shows up as N adjacent placeholders"
// bug without resorting to time-based heuristics that would
// wrongly merge two quick deliberate pastes. On terminals
// that don't support DECSET 2004 (cmd.exe), markers never
// appear and we fall back to the per-chunk pasteRequest
// path below — chunks split visually but stay correct.
if (pasteAccumRef.current !== null) {
const endIdx = input.indexOf(PASTE_END_MARKER);
if (endIdx === -1) {
pasteAccumRef.current += input;
return;
}
const content = pasteAccumRef.current + input.slice(0, endIdx);
pasteAccumRef.current = null;
registerPaste(content);
return;
}
const startIdx = input.indexOf(PASTE_START_MARKER);
if (startIdx !== -1) {
const afterStart = input.slice(startIdx + PASTE_START_MARKER.length);
const endIdx = afterStart.indexOf(PASTE_END_MARKER);
if (endIdx !== -1) {
// Whole paste in one read — register and we're done.
registerPaste(afterStart.slice(0, endIdx));
} else {
// Open paste mode for subsequent useInput events.
pasteAccumRef.current = afterStart;
}
return;
}
const ke: MultilineKey = {
input,
return: key.return,
shift: key.shift,
ctrl: key.ctrl,
meta: key.meta,
backspace: key.backspace,
delete: key.delete,
tab: key.tab,
upArrow: key.upArrow,
downArrow: key.downArrow,
leftArrow: key.leftArrow,
rightArrow: key.rightArrow,
escape: key.escape,
pageUp: key.pageUp,
pageDown: key.pageDown,
};
const action = processMultilineKey(value, cursor, ke);
if (action.pasteRequest) {
// No bracketed-paste markers were seen — terminal doesn't
// support DECSET 2004, or Ink's key parser ate them. Fall
// back to per-chunk paste registration. Two chunks of the
// same big paste land as two placeholders; correctness
// preserved, only visual cohesion lost.
registerPaste(action.pasteRequest.content);
return;
}
if (action.next !== null) {
lastLocalValueRef.current = action.next;
onChange(action.next);
}
if (action.cursor !== null) {
setCursor(action.cursor);
}
if (action.submit) {
// Expand sentinels back to real paste content before handing
// the prompt up to the parent. The buffer carries placeholders
// for display; the model needs the full text.
const raw = action.submitValue ?? value;
const expanded = expandPasteSentinels(raw, pastesRef.current);
// GC unreachable paste entries — anything whose sentinel was
// backspace'd out of the buffer before submit. Keeps the
// registry from growing unbounded across many turns.
const reachable = new Set(listPasteIdsInBuffer(raw));
for (const id of pastesRef.current.keys()) {
if (!reachable.has(id)) pastesRef.current.delete(id);
}
onSubmit(expanded);
}
if (action.historyHandoff === "prev") onHistoryPrev?.();
if (action.historyHandoff === "next") onHistoryNext?.();
},
{ isActive: !disabled },
);
// Narrow-terminal mode: drop the `you ›` (6 col) prefix to a `›` (2
// col) marker so the writable area on 80-col terminals reclaims 4
// cols. Threshold of 90 keeps the friendly `you ›` on anything that
// resembles a normal terminal; modern laptops tend to default to
// 100+ cols, narrow ones (split panes, embedded shells) tend to be
// <=90. Continuation indent shrinks proportionally so wrapped lines
// still align under the prompt arrow.
const { stdout } = useStdout();
const cols = stdout?.columns ?? 80;
const narrow = cols <= 90;
const promptPrefix = narrow ? "› " : "you › ";
const continuationIndent = narrow ? " " : " ";
const placeholderActive = narrow
? "type a message, or /command"
: "type a message, or /command · [Shift+Enter] / [Ctrl+J] newline";
const effectivePlaceholder = disabled
? (placeholder ?? "…waiting for response…")
: (placeholder ?? "type a message, or /command");
: (placeholder ?? placeholderActive);
const lines = value.length > 0 ? value.split("\n") : [""];
const borderColor = disabled ? "gray" : "cyan";
const { line: cursorLine, col: cursorCol } = lineAndColumn(value, cursor);
// For large buffers (e.g. a big paste), rendering every line
// re-runs Ink's layout + terminal write on every keystroke. Each
// keystroke touching 500 rendered lines flickers visibly on most
// terminals. Collapse to HEAD + cursor-line + TAIL with a dim
// `[… N lines hidden …]` marker. Edit position is still anywhere;
// the visible cursor line follows the cursor into/out of the
// collapsed region so the user never loses sight of what they're
// typing. Submitted value is the FULL buffer — collapse is purely
// visual.
const renderItems = collapseLinesForDisplay(lines, cursorLine);
// When the buffer is large enough to be collapsed, surface a dim
// hint about the buffer-wide shortcuts. The user just pasted 500
// lines; without this they have no idea PageUp/Ctrl+U exist and
// ↑×500 is the only path back to the top.
const showHugeBufferHints = lines.length > 20;
return (
<Box borderStyle="round" borderColor={disabled ? "gray" : "cyan"} paddingX={1}>
<Text bold color={disabled ? "gray" : "cyan"}>
you ›{" "}
</Text>
<TextInput
value={value}
onChange={onChange}
onSubmit={onSubmit}
focus={!disabled}
placeholder={effectivePlaceholder}
/>
</Box>
<>
<Box borderStyle="round" borderColor={borderColor} paddingX={1} flexDirection="column">
{renderItems.map((item, renderIdx) => {
if (item.kind === "skip") {
return (
// biome-ignore lint/suspicious/noArrayIndexKey: stable — skip markers are derived from a fixed-size window over `lines`
<Box key={`skip-${renderIdx}`}>
<Text dimColor>{continuationIndent}</Text>
<Text
dimColor
>{`[… ${item.linesHidden} line${item.linesHidden === 1 ? "" : "s"} hidden — full content kept, submitted on Enter …]`}</Text>
</Box>
);
}
const line = item.line;
const i = item.originalIndex;
const isFirst = i === 0;
const showPlaceholder = isFirst && value.length === 0;
const isCursorLine = i === cursorLine;
return (
<Box key={`ln-${i}`}>
{isFirst ? (
<Text bold color={borderColor}>
{promptPrefix}
</Text>
) : (
<Text dimColor>{continuationIndent}</Text>
)}
{showPlaceholder ? (
<>
{isCursorLine && !disabled ? (
<Text color={borderColor}>{showCursor ? "▌" : " "}</Text>
) : null}
<Text dimColor>{effectivePlaceholder}</Text>
</>
) : isCursorLine && !disabled ? (
<LineWithCursor
line={line}
col={cursorCol}
showCursor={showCursor}
borderColor={borderColor}
pastes={pastesRef.current}
/>
) : (
<RenderLine line={line} pastes={pastesRef.current} />
)}
</Box>
);
})}
{showHugeBufferHints && !disabled ? (
<Box>
<Text dimColor>{continuationIndent}</Text>
<Text dimColor>
{`[${lines.length} lines · PageUp/PageDown jump to top/bottom · Ctrl+U clear · Ctrl+W del word]`}
</Text>
</Box>
) : null}
</Box>
{disabled ? (
<Box paddingX={1}>
<Text dimColor>[Esc] to stop</Text>
</Box>
) : null}
</>
);
}
/**
* One visual slot in the rendered prompt box. Either a real buffer
* line (with its original index so the cursor / first-line prefix
* still line up) or a "skip" marker summarizing hidden rows.
*/
type RenderItem =
| { kind: "line"; line: string; originalIndex: number }
| { kind: "skip"; linesHidden: number };
/**
* Above this line count we stop rendering every line on every
* keystroke — a 500-line paste would otherwise make Ink redraw
* hundreds of rows per character typed, which is visibly janky.
* Chosen empirically: under 20 lines the user is still visually
* scanning the buffer; above that they're almost always looking
* at a pasted blob that should be summarized.
*/
const COLLAPSE_THRESHOLD = 20;
const COLLAPSE_HEAD_LINES = 3;
const COLLAPSE_TAIL_LINES = 2;
export function collapseLinesForDisplay(lines: string[], cursorLine: number): RenderItem[] {
if (lines.length <= COLLAPSE_THRESHOLD) {
return lines.map((line, i) => ({ kind: "line" as const, line, originalIndex: i }));
}
// Always show the first HEAD lines, the last TAIL lines, and
// the cursor line if it falls in the collapsed middle. Union
// the indices so head/cursor/tail overlap collapses cleanly.
const keep = new Set<number>();
for (let i = 0; i < COLLAPSE_HEAD_LINES && i < lines.length; i++) keep.add(i);
for (let i = Math.max(0, lines.length - COLLAPSE_TAIL_LINES); i < lines.length; i++) keep.add(i);
if (cursorLine >= 0 && cursorLine < lines.length) keep.add(cursorLine);
const sorted = [...keep].sort((a, b) => a - b);
const out: RenderItem[] = [];
let prev = -1;
for (const idx of sorted) {
if (idx - prev > 1) {
out.push({ kind: "skip", linesHidden: idx - prev - 1 });
}
out.push({ kind: "line", line: lines[idx] ?? "", originalIndex: idx });
prev = idx;
}
return out;
}
/**
* Render a buffer line with paste sentinels expanded into magenta
* `[paste #N · …]` placeholder blocks. Used for non-cursor lines and
* for the prefix / suffix segments around the cursor on the cursor
* line.
*
* Each codepoint is emitted as either:
* - text: accumulated in `buf`, flushed when a sentinel or the end
* of the line is reached.
* - placeholder block: a styled `[paste #N · 3337l · 184KB]` Text.
*
* No layout magic — the emitted segments sit inline in the parent
* Box's row, just like plain text.
*/
function RenderLine({
line,
pastes,
inverse,
}: {
line: string;
pastes: ReadonlyMap<number, PasteEntry>;
inverse?: boolean;
}) {
const segments: React.ReactNode[] = [];
let buf = "";
let segIdx = 0;
const flushBuf = () => {
if (buf.length === 0) return;
segments.push(
<Text key={`t-${segIdx++}`} inverse={inverse}>
{buf}
</Text>,
);
buf = "";
};
for (let i = 0; i < line.length; i++) {
const ch = line[i]!;
const id = decodePasteSentinel(ch);
if (id === null) {
buf += ch;
continue;
}
flushBuf();
const entry = pastes.get(id);
const label = entry
? `[paste #${id + 1} · ${entry.lineCount}l · ${formatBytesShort(entry.charCount)}]`
: `[paste #${id + 1} · (missing)]`;
segments.push(
<Text key={`p-${segIdx++}`} color="magenta" bold inverse={inverse}>
{label}
</Text>,
);
}
flushBuf();
if (segments.length === 0) {
// Empty line — return a single empty Text so Ink still renders a
// row. Otherwise this Box collapses to zero height.
return <Text> </Text>;
}
return <>{segments}</>;
}
function LineWithCursor({
line,
col,
showCursor,
borderColor,
pastes,
}: {
line: string;
col: number;
showCursor: boolean;
borderColor: "cyan" | "gray";
pastes: ReadonlyMap<number, PasteEntry>;
}) {
const before = line.slice(0, col);
const atCursor = line.slice(col, col + 1);
const after = line.slice(col + 1);
if (atCursor.length === 0) {
// Cursor sits past the last char of this line (end-of-line). Render
// a trailing block so the user sees where they're typing next.
return (
<>
<RenderLine line={before} pastes={pastes} />
<Text color={borderColor}>{showCursor ? "▌" : " "}</Text>
</>
);
}
return (
<>
<RenderLine line={before} pastes={pastes} />
<RenderLine line={atCursor} pastes={pastes} inverse={showCursor} />
<RenderLine line={after} pastes={pastes} />
</>
);
}
+9 -1
View File
@@ -11,6 +11,7 @@
import { Box, Text } from "ink";
import React from "react";
import type { TranscriptRecord } from "../../transcript.js";
import { PlanStateBlock } from "./PlanStateBlock.js";
export interface RecordViewProps {
rec: TranscriptRecord;
@@ -27,12 +28,18 @@ export function RecordView({ rec, compact = false }: RecordViewProps) {
const toolContentMax = compact ? 200 : 400;
if (rec.role === "user") {
// Continuation indent of 6 spaces matches the `you › ` prefix width
// so wrapped multi-line user messages align under the body text
// instead of jumping to column 0.
const content = rec.content.includes("\n")
? rec.content.split("\n").join("\n ")
: rec.content;
return (
<Box marginTop={1}>
<Text bold color="cyan">
you ›{" "}
</Text>
<Text>{rec.content}</Text>
<Text>{content}</Text>
</Box>
);
}
@@ -51,6 +58,7 @@ export function RecordView({ rec, compact = false }: RecordViewProps) {
) : null}
{rec.usage ? <CacheBadge usage={rec.usage} /> : null}
</Box>
{rec.planState ? <PlanStateBlock planState={rec.planState} /> : null}
{rec.content ? (
<Text>{rec.content}</Text>
) : (
+5
View File
@@ -52,9 +52,14 @@ export function ReplayApp({ meta, pages }: ReplayAppProps) {
const summary = {
turns: cumStats.turns,
totalCostUsd: cumStats.totalCostUsd,
totalInputCostUsd: cumStats.totalInputCostUsd,
totalOutputCostUsd: cumStats.totalOutputCostUsd,
claudeEquivalentUsd: cumStats.claudeEquivalentUsd,
savingsVsClaudePct: cumStats.savingsVsClaudePct,
cacheHitRatio: cumStats.cacheHitRatio,
// Replay is read-only — no live last-turn prompt tokens to show.
lastPromptTokens: 0,
lastTurnCostUsd: 0,
};
const prefixHash =
+195
View File
@@ -0,0 +1,195 @@
/**
* Minimal arrow-key list components for Ink — single-select and
* multi-select. No external deps beyond Ink's `useInput`.
*
* Why hand-roll: `ink-select-input` exists, but it defaults to
* Enter-only interaction (no space-to-toggle for multi-select), doesn't
* expose the "hint / footer" slot we want under each item, and would be
* another dep for ~60 lines of UI code. Reasonix already has one React
* rendering quirk bundled (`ink-text-input`); adding more is low value.
*/
import { Box, Text, useInput } from "ink";
import React, { useState } from "react";
export interface SelectItem<V extends string = string> {
/** Stable identifier — returned to caller on submit. */
value: V;
/** First-row label. */
label: string;
/** Optional second row rendered dimmed. */
hint?: string;
/** If true, item is not selectable (rendered dimmed, skipped on nav). */
disabled?: boolean;
}
export interface SingleSelectProps<V extends string> {
items: SelectItem<V>[];
initialValue?: V;
onSubmit: (value: V) => void;
onCancel?: () => void;
/**
* Optional footer rendered dim beneath the list, e.g.
* `"[↑↓] navigate · [Enter] select · [Esc] cancel"`. Makes keyboard
* affordances discoverable — otherwise new users hit `y`/`n` and
* wonder why nothing happens.
*/
footer?: string;
}
export function SingleSelect<V extends string>({
items,
initialValue,
onSubmit,
onCancel,
footer,
}: SingleSelectProps<V>) {
const initialIndex = Math.max(
0,
items.findIndex((i) => i.value === initialValue && !i.disabled),
);
const [index, setIndex] = useState(initialIndex === -1 ? 0 : initialIndex);
useInput((_input, key) => {
if (key.upArrow) {
setIndex((i) => findNextEnabled(items, i, -1));
} else if (key.downArrow) {
setIndex((i) => findNextEnabled(items, i, +1));
} else if (key.return) {
const chosen = items[index];
if (chosen && !chosen.disabled) onSubmit(chosen.value);
} else if (key.escape && onCancel) {
onCancel();
}
});
return (
<Box flexDirection="column">
{items.map((item, i) => (
<SelectRow
key={item.value}
item={item}
active={i === index}
marker={i === index ? "▸" : " "}
/>
))}
{footer ? (
<Box marginTop={1}>
<Text dimColor>{footer}</Text>
</Box>
) : null}
</Box>
);
}
export interface MultiSelectProps<V extends string> {
items: SelectItem<V>[];
initialSelected?: V[];
onSubmit: (values: V[]) => void;
onCancel?: () => void;
/** Footer hint under the list — e.g. "[Space] toggle · [Enter] confirm". */
footer?: string;
}
export function MultiSelect<V extends string>({
items,
initialSelected = [],
onSubmit,
onCancel,
footer,
}: MultiSelectProps<V>) {
const [index, setIndex] = useState(() => {
const first = items.findIndex((i) => !i.disabled);
return first === -1 ? 0 : first;
});
const [selected, setSelected] = useState<Set<V>>(new Set(initialSelected));
useInput((input, key) => {
if (key.upArrow) {
setIndex((i) => findNextEnabled(items, i, -1));
} else if (key.downArrow) {
setIndex((i) => findNextEnabled(items, i, +1));
} else if (input === " ") {
const item = items[index];
if (!item || item.disabled) return;
setSelected((prev) => {
const next = new Set(prev);
if (next.has(item.value)) next.delete(item.value);
else next.add(item.value);
return next;
});
} else if (key.return) {
// Preserve catalog order rather than insertion order, so reruns
// produce the same spec list for the same checkbox set — makes the
// `config.json` diff trivially stable.
const ordered = items.filter((i) => selected.has(i.value)).map((i) => i.value);
onSubmit(ordered);
} else if (key.escape && onCancel) {
onCancel();
}
});
return (
<Box flexDirection="column">
{items.map((item, i) => {
const checked = selected.has(item.value);
const marker = checked ? "[x]" : "[ ]";
return (
<SelectRow
key={item.value}
item={item}
active={i === index}
marker={`${i === index ? "▸" : " "} ${marker}`}
/>
);
})}
{footer ? (
<Box marginTop={1}>
<Text dimColor>{footer}</Text>
</Box>
) : null}
</Box>
);
}
// ---------- internals ----------
function SelectRow<V extends string>({
item,
active,
marker,
}: {
item: SelectItem<V>;
active: boolean;
marker: string;
}) {
const color = item.disabled ? "gray" : active ? "cyan" : undefined;
return (
<Box flexDirection="column">
<Box>
<Text color={color}>
{marker} {item.label}
</Text>
</Box>
{item.hint ? (
<Box paddingLeft={marker.length + 1}>
<Text dimColor>{item.hint}</Text>
</Box>
) : null}
</Box>
);
}
function findNextEnabled<V extends string>(
items: SelectItem<V>[],
from: number,
step: -1 | 1,
): number {
if (items.length === 0) return 0;
let i = from;
for (let tries = 0; tries < items.length; tries++) {
i = (i + step + items.length) % items.length;
if (!items[i]?.disabled) return i;
}
return from;
}
+72
View File
@@ -0,0 +1,72 @@
import { Box, Text } from "ink";
import React from "react";
import { SingleSelect } from "./Select.js";
export type SessionChoice = "resume" | "new" | "delete";
export interface SessionPickerProps {
sessionName: string;
messageCount: number;
/** mtime of the session file; used to render "last active Nh ago". */
lastActive: Date;
onChoose: (choice: SessionChoice) => void;
}
export function SessionPicker({
sessionName,
messageCount,
lastActive,
onChoose,
}: SessionPickerProps) {
return (
<Box flexDirection="column" marginY={1}>
<Box marginBottom={1}>
<Text bold color="cyan">
{`Session "${sessionName}" has ${messageCount} prior message${messageCount === 1 ? "" : "s"}`}
</Text>
<Text dimColor>{` · last active ${relativeTime(lastActive)}`}</Text>
</Box>
<SingleSelect
initialValue="new"
items={[
{
value: "new",
label: "Start new conversation",
hint: "Previous messages kept on disk; your turn starts fresh.",
},
{
value: "resume",
label: "Resume",
hint: `Continue where you left off (${messageCount} messages in context).`,
},
{
value: "delete",
label: "Delete and start new",
hint: "Wipes the session file irreversibly. Other sessions untouched.",
},
]}
onSubmit={(v) => onChoose(v as SessionChoice)}
/>
<Box marginTop={1}>
<Text dimColor>[↑↓] navigate · [Enter] select</Text>
</Box>
</Box>
);
}
/**
* "Nh ago" / "Nm ago" / "yesterday" style relative time. Deliberately
* coarse — the picker just needs a sense of "how stale is this session".
*/
function relativeTime(date: Date): string {
const ms = Date.now() - date.getTime();
const mins = Math.floor(ms / 60_000);
if (mins < 1) return "just now";
if (mins < 60) return `${mins}m ago`;
const hours = Math.floor(mins / 60);
if (hours < 24) return `${hours}h ago`;
const days = Math.floor(hours / 24);
if (days === 1) return "yesterday";
if (days < 7) return `${days}d ago`;
return date.toISOString().slice(0, 10);
}
+129
View File
@@ -0,0 +1,129 @@
import { Box, Text } from "ink";
import React from "react";
import { SingleSelect } from "./Select.js";
export type ShellConfirmChoice = "run_once" | "always_allow" | "deny";
export interface ShellConfirmProps {
command: string;
/**
* The prefix that would be persisted if the user picks
* "always allow". Typically the first 1-2 tokens of `command`.
*/
allowPrefix: string;
/**
* Which tool is asking. `run_background` spawns via JobRegistry and
* returns early; `run_command` (default) blocks until the process
* exits. Shown as a hint in the modal so the user knows whether
* approving will block the TUI or not.
*/
kind?: "run_command" | "run_background";
onChoose: (choice: ShellConfirmChoice) => void;
}
/**
* Modal-style approval for a shell command the model wants to run.
* Three choices:
* 1. Run once — execute this invocation, prefix NOT remembered.
* 2. Always allow — persist the prefix to `~/.reasonix/config.json`
* under this project so every future invocation with that prefix
* auto-runs.
* 3. Deny — tell the model the user refused.
* Arrow keys + Enter. No y/n hotkey — too easy to trigger by accident
* when the user was mid-typing a response.
*/
export function ShellConfirm({ command, allowPrefix, kind, onChoose }: ShellConfirmProps) {
const isBackground = kind === "run_background";
return (
<Box flexDirection="column" borderStyle="round" borderColor="red" paddingX={1} marginY={1}>
<Box>
<Text bold color="red">
{isBackground
? "▸ model wants to start a BACKGROUND process"
: "▸ model wants to run a shell command"}
</Text>
</Box>
{isBackground ? (
<Box>
<Text dimColor>
{" (long-running: dev server / watcher; keeps running after approval, /kill to stop)"}
</Text>
</Box>
) : null}
<Box>
<Text color="red" dimColor>
{"──────────────────────────────────────────"}
</Text>
</Box>
<Box marginTop={1}>
<Text>
<Text dimColor>{"$ "}</Text>
<Text color="cyan">{command}</Text>
</Text>
</Box>
<Box marginTop={1}>
<SingleSelect
initialValue="run_once"
items={[
{
value: "run_once",
label: "Run once",
hint: "Execute this command, don't remember it.",
},
{
value: "always_allow",
label: `Always allow "${allowPrefix}" in this project`,
hint: "Save the prefix to ~/.reasonix/config.json; future matches auto-run.",
},
{
value: "deny",
label: "Deny",
hint: "Tell the model the user refused; it will continue without this command.",
},
]}
onSubmit={(v) => onChoose(v as ShellConfirmChoice)}
onCancel={() => onChoose("deny")}
footer="[↑↓] navigate · [Enter] select · [Esc] deny"
/>
</Box>
</Box>
);
}
/**
* Pick the "always allow" prefix from a full command. Heuristic:
* - one-token commands ("ls", "pytest") → the token itself
* - multi-token → first two tokens for well-known wrappers
* (`npm install`, `git commit`, `cargo add`, `docker run` …)
* otherwise just the first token (covers `node <script>` where the
* second token is usually a file path specific to this invocation).
* Exported so tests can pin the heuristic.
*/
export function derivePrefix(command: string): string {
const tokens = command.trim().split(/\s+/).filter(Boolean);
if (tokens.length === 0) return "";
if (tokens.length === 1) return tokens[0]!;
const first = tokens[0]!;
const TWO_TOKEN_WRAPPERS = new Set([
"npm",
"npx",
"pnpm",
"yarn",
"bun",
"git",
"cargo",
"go",
"docker",
"kubectl",
"python",
"python3",
"deno",
"pip",
"pip3",
"make",
"rake",
"bundle",
"gem",
]);
return TWO_TOKEN_WRAPPERS.has(first) ? `${first} ${tokens[1]}` : first;
}
+108
View File
@@ -0,0 +1,108 @@
import { Box, Text } from "ink";
// biome-ignore lint/style/useImportType: tsconfig.jsx = "react" needs React in value scope for JSX compilation
import React from "react";
import type { SlashCommandSpec } from "./slash.js";
export interface SlashArgPickerProps {
/**
* When set, render a picker with these matches (filter already
* applied upstream). Null → not in picker mode; check `hintSpec`
* for a usage hint instead.
*/
matches: readonly string[] | null;
/** Highlighted row within `matches`. */
selectedIndex: number;
/**
* Spec of the command the user is typing args for. Used to render
* the header label ("/edit <file>") even when matches is empty or
* the caller wants a hint instead of a picker.
*/
spec: SlashCommandSpec;
/** What kind of arg guidance to render. */
kind: "picker" | "hint";
/** The user's partial input — shown in the "no matches" hint. */
partial: string;
}
/**
* Argument-level picker for a slash command. Mirrors the visual
* layout of SlashSuggestions / AtMentionSuggestions so the UI stays
* consistent across all three picker surfaces.
*/
export function SlashArgPicker({
matches,
selectedIndex,
spec,
kind,
partial,
}: SlashArgPickerProps): React.ReactElement | null {
// Hint mode: a single dim row explaining the argsHint + summary.
if (kind === "hint") {
return (
<Box paddingX={1} marginTop={1}>
<Text dimColor>
{" "}
<Text bold>/{spec.cmd}</Text>
{spec.argsHint ? ` ${spec.argsHint}` : ""} — {spec.summary}
</Text>
</Box>
);
}
if (matches === null) return null;
if (matches.length === 0) {
return (
<Box flexDirection="column" paddingX={1} marginTop={1}>
<Text dimColor>
{" "}
<Text bold>/{spec.cmd}</Text>
{spec.argsHint ? ` ${spec.argsHint}` : ""} — {spec.summary}
</Text>
<Text color="yellow"> no match for "{partial}" — keep typing, or Backspace to edit</Text>
</Box>
);
}
const MAX = 8;
const total = matches.length;
const windowStart =
total <= MAX ? 0 : Math.max(0, Math.min(selectedIndex - Math.floor(MAX / 2), total - MAX));
const shown = matches.slice(windowStart, windowStart + MAX);
const hiddenAbove = windowStart;
const hiddenBelow = total - windowStart - shown.length;
return (
<Box flexDirection="column" paddingX={1} marginTop={1}>
<Text dimColor>
{" "}
<Text bold>/{spec.cmd}</Text>
{spec.argsHint ? ` ${spec.argsHint}` : ""} — {spec.summary}
</Text>
{hiddenAbove > 0 ? <Text dimColor> ↑ {hiddenAbove} more above</Text> : null}
{shown.map((value, i) => (
<ArgRow key={value} value={value} isSelected={windowStart + i === selectedIndex} />
))}
{hiddenBelow > 0 ? <Text dimColor> ↓ {hiddenBelow} more below</Text> : null}
<Text dimColor> [↑↓] navigate · [Tab]/[Enter] pick</Text>
</Box>
);
}
function ArgRow({ value, isSelected }: { value: string; isSelected: boolean }) {
const marker = isSelected ? "▸" : " ";
if (isSelected) {
return (
<Box>
<Text bold color="cyan">
{marker} {value}
</Text>
</Box>
);
}
return (
<Box>
<Text dimColor>
{marker} {value}
</Text>
</Box>
);
}
+85
View File
@@ -0,0 +1,85 @@
import { Box, Text } from "ink";
// biome-ignore lint/style/useImportType: tsconfig.jsx = "react" needs React in value scope for JSX compilation
import React from "react";
import type { SlashCommandSpec } from "./slash.js";
export interface SlashSuggestionsProps {
/**
* Current matching suggestions, computed by the parent. `null` means
* "not in slash-prefix mode" — render nothing. Empty array means "in
* slash mode but no matches" — render the "no matches" hint.
*/
matches: SlashCommandSpec[] | null;
/** Index (within `matches`) of the currently highlighted row. */
selectedIndex: number;
}
/**
* Floating slash-command panel. Rendered below the input box when
* the user is typing a `/…` prefix. Navigation state lives in the
* parent (App.tsx owns `slashSelected`) so ↑/↓/Tab/Enter stay
* consistent with the useInput handler. This component is pure
* display: `matches` and `selectedIndex` come in, rows go out.
*/
export function SlashSuggestions({
matches,
selectedIndex,
}: SlashSuggestionsProps): React.ReactElement | null {
if (matches === null) return null;
if (matches.length === 0) {
return (
<Box paddingX={1} marginTop={1}>
<Text color="yellow">no slash command matches that prefix</Text>
<Text dimColor> — Backspace to edit, or /help for the full list</Text>
</Box>
);
}
// Limit rows so the suggestion list never dwarfs the rest of the
// UI. Keep the currently-selected row in view by sliding the
// window when the selection is near either edge.
const MAX = 8;
const total = matches.length;
const windowStart =
total <= MAX ? 0 : Math.max(0, Math.min(selectedIndex - Math.floor(MAX / 2), total - MAX));
const shown = matches.slice(windowStart, windowStart + MAX);
const hiddenAbove = windowStart;
const hiddenBelow = total - windowStart - shown.length;
return (
<Box flexDirection="column" paddingX={1} marginTop={1}>
{hiddenAbove > 0 ? <Text dimColor> ↑ {hiddenAbove} more above</Text> : null}
{shown.map((spec, i) => (
<SuggestionRow key={spec.cmd} spec={spec} isSelected={windowStart + i === selectedIndex} />
))}
{hiddenBelow > 0 ? <Text dimColor> ↓ {hiddenBelow} more below</Text> : null}
<Text dimColor> [↑↓] navigate · [Tab]/[Enter] pick</Text>
</Box>
);
}
function SuggestionRow({ spec, isSelected }: { spec: SlashCommandSpec; isSelected: boolean }) {
const marker = isSelected ? "▸" : " ";
const name = `/${spec.cmd}`;
const argsSuffix = spec.argsHint ? ` ${spec.argsHint}` : "";
// Selected row gets full cyan coloring so it pops out against the
// dimmed others — mirrors the style GitHub Issues / Discord use
// for focused dropdown rows.
if (isSelected) {
return (
<Box>
<Text bold color="cyan">
{marker} {name.padEnd(12)}
{argsSuffix.padEnd(16)}
</Text>
<Text color="cyan"> {spec.summary}</Text>
</Box>
);
}
return (
<Box>
<Text dimColor>
{marker} {name.padEnd(12)}
{argsSuffix.padEnd(16)} {spec.summary}
</Text>
</Box>
);
}
+495 -41
View File
@@ -1,6 +1,55 @@
import { Box, Text } from "ink";
import { Box, Text, useStdout } from "ink";
import React from "react";
import type { EditMode } from "../../config.js";
import { DEEPSEEK_CONTEXT_TOKENS, DEFAULT_CONTEXT_TOKENS } from "../../telemetry.js";
import type { SessionSummary } from "../../telemetry.js";
import { VERSION } from "../../version.js";
import { useTick } from "./ticker.js";
/**
* Cyan → blue → purple truecolor gradient for the REASONIX wordmark.
* Each char gets its own hex color — terminals that support 24-bit
* color (nearly all since 2016) render this as a smooth fade. Older
* 256-color terminals snap to nearest; 8-color fall all the way back
* to plain cyan via Ink's color pipeline, so the worst case is still
* legible.
*/
const WORDMARK_STYLES: ReadonlyArray<{ ch: string; color: string; isLogo: boolean }> = [
{ ch: "◈", color: "#5eead4", isLogo: true }, // teal — brand mark
{ ch: " ", color: "#5eead4", isLogo: false },
{ ch: "R", color: "#67e8f9", isLogo: false }, // cyan
{ ch: "E", color: "#7dd3fc", isLogo: false }, // sky
{ ch: "A", color: "#93c5fd", isLogo: false }, // blue
{ ch: "S", color: "#a5b4fc", isLogo: false }, // indigo
{ ch: "O", color: "#c4b5fd", isLogo: false }, // violet
{ ch: "N", color: "#d8b4fe", isLogo: false }, // purple
{ ch: "I", color: "#f0abfc", isLogo: false }, // fuchsia
{ ch: "X", color: "#f0abfc", isLogo: false }, // fuchsia
];
/**
* Gradient-filled, animated app wordmark. The `◈` brand mark breathes
* (bold on/off) once every ~1.6s when idle, ~600ms when the model is
* working, so a glance at the top of the screen tells you immediately
* whether the app is doing something. Letters' keys use the char+color
* pair (not an index) so React state attaches to the glyph itself;
* fine because WORDMARK_STYLES never reorders.
*/
function Wordmark({ busy }: { busy: boolean }) {
const tick = useTick();
// Slow pulse = 12 ticks (~1.4s). Busy pulse = 5 ticks (~600ms).
const period = busy ? 5 : 12;
const bright = Math.floor(tick / period) % 2 === 0;
return (
<Text>
{WORDMARK_STYLES.map((c) => (
<Text key={`${c.ch}-${c.color}`} color={c.color} bold={c.isLogo ? bright : true}>
{c.ch}
</Text>
))}
</Text>
);
}
export interface StatsPanelProps {
summary: SessionSummary;
@@ -8,57 +57,462 @@ export interface StatsPanelProps {
prefixHash: string;
harvestOn?: boolean;
branchBudget?: number;
/**
* Current `reasoning_effort` cap. Shown as a green "· max" / yellow
* "· high" tag in the header so the user always sees which tier the
* next turn will use. Absent/undefined hides the tag (e.g. before
* the loop is constructed).
*/
reasoningEffort?: "high" | "max";
/**
* True when `reasonix code` is currently running in read-only Plan
* Mode. Surfaced as a red "PLAN" tag in the panel header so the user
* can tell at a glance that edits are gated behind submit_plan +
* approval.
*/
planMode?: boolean;
/**
* Edit-gate mode. Surfaced as a small pill in the header so the user
* can see at a glance whether edits will be queued for review or
* applied immediately. Omitted in chat (non-code) mode.
*/
editMode?: EditMode;
/**
* Account balance fetched once at launch (and optionally refreshed
* per-turn by the TUI). `null` or absent hides the balance cell
* entirely — /user/balance failed or the user ran with `--no-config`.
* The top-up warning fires below 1.0 unit of whatever currency
* the endpoint reports so a Chinese user with CNY and a U.S. user
* with USD both see "getting low."
*/
balance?: { currency: string; total: number } | null;
/**
* Published npm version newer than VERSION. Rendered as a yellow
* "· update: X" nudge in the panel header. `null` / `undefined`
* hides the nudge (offline launch, already up to date, or check
* still in flight).
*/
updateAvailable?: string | null;
/**
* True when the loop is currently mid-turn — drives the wordmark's
* "busy breathing" animation. Visual signal that the app is thinking,
* visible at a glance from anywhere on screen.
*/
busy?: boolean;
/**
* /pro is queued — the next turn will run on v4-pro regardless of
* `model`. Rendered as a yellow `⇧ pro armed` pill in the header so
* the user has a clear "this turn will be expensive" signal before
* submitting their message.
*/
proArmed?: boolean;
/**
* The CURRENT turn is running on v4-pro because the failure-
* escalation threshold fired mid-turn. Rendered as a red `⇧ pro
* escalated` pill. Clears at turn end.
*/
escalated?: boolean;
}
/**
* Terminal width under which we switch from one-line metrics to a
* stacked layout. Below 120 cols the wide version wraps mid-number
* and the parens ("in $X · out $Y") get split across lines — which
* looks broken. Stacking costs one row but stays readable on every
* SSH / split-pane case we've hit.
*/
const NARROW_BREAKPOINT = 120;
/**
* Cache-hit ratio is always zero on turn 1 (there's literally no cache
* to hit yet). Showing that as red "0.0%" is a false alarm — new users
* read it as "something is broken." We suppress the gradient until a
* few turns have landed; by turn 4 the cache has had time to warm up.
*/
const COLD_START_TURNS = 3;
export function StatsPanel({
summary,
model,
prefixHash,
harvestOn,
branchBudget,
reasoningEffort,
planMode,
editMode,
balance,
updateAvailable,
busy,
proArmed,
escalated,
}: StatsPanelProps) {
const hitPct = (summary.cacheHitRatio * 100).toFixed(1);
const hitColor =
summary.cacheHitRatio >= 0.7 ? "green" : summary.cacheHitRatio >= 0.4 ? "yellow" : "red";
const branchOn = (branchBudget ?? 1) > 1;
const ctxMax = DEEPSEEK_CONTEXT_TOKENS[model] ?? DEFAULT_CONTEXT_TOKENS;
const ctxRatio = summary.lastPromptTokens / ctxMax;
const { stdout } = useStdout();
const columns = stdout?.columns ?? 80;
const narrow = columns < NARROW_BREAKPOINT;
// Cold-start: first few turns render cache+cost muted so a 0.0% hit
// rate on turn 1 doesn't look like an error. Once the cache has
// actually had a chance to build, we flip to the live gradient.
const coldStart = summary.turns <= COLD_START_TURNS;
return (
<Box borderStyle="round" borderColor="cyan" flexDirection="column" paddingX={1}>
<Box justifyContent="space-between">
<Text>
<Text color="cyan" bold>
Reasonix
</Text>
<Text dimColor> · model </Text>
<Text color="yellow">{model}</Text>
<Text dimColor> · prefix </Text>
<Text dimColor>{prefixHash}</Text>
{harvestOn ? <Text color="magenta"> · harvest</Text> : null}
{branchOn ? <Text color="blue"> · branch{branchBudget}</Text> : null}
</Text>
<Text dimColor>turns {summary.turns} · type /help</Text>
</Box>
<Box marginTop={1} gap={3}>
<Text>
<Text dimColor>cache hit </Text>
<Text color={hitColor} bold>
{hitPct}%
</Text>
</Text>
<Text>
<Text dimColor>cost </Text>
<Text color="green">${summary.totalCostUsd.toFixed(6)}</Text>
</Text>
<Text>
<Text dimColor>vs Claude </Text>
<Text>${summary.claudeEquivalentUsd.toFixed(6)}</Text>
</Text>
<Text>
<Text dimColor>saving </Text>
<Text color="green" bold>
{summary.savingsVsClaudePct.toFixed(1)}%
</Text>
</Text>
</Box>
// Explicit `width={columns}` pins the border frame to the exact
// terminal width. Without this, Ink auto-flexes the Box to
// container width, and on terminal resize the prior frame's
// wrapped-overflow can leave tails in the scrollback (each
// redraw stacks a slightly-wider-or-narrower frame). Fixing
// width per-render doesn't eliminate the underlying Ink
// limitation (eraseLines counts logical rows, not post-wrap
// display rows) but makes each frame's dimensions exact so
// there's no residual uncertainty in the erase.
<Box borderStyle="round" borderColor="cyan" flexDirection="column" paddingX={1} width={columns}>
<Header
model={model}
prefixHash={prefixHash}
harvestOn={harvestOn}
branchOn={branchOn}
branchBudget={branchBudget ?? 1}
reasoningEffort={reasoningEffort}
planMode={planMode}
editMode={editMode}
turns={summary.turns}
updateAvailable={updateAvailable}
narrow={narrow}
busy={busy ?? false}
proArmed={proArmed ?? false}
escalated={escalated ?? false}
/>
{narrow ? (
<StackedMetrics
summary={summary}
ctxRatio={ctxRatio}
ctxMax={ctxMax}
balance={balance}
coldStart={coldStart}
/>
) : (
<InlineMetrics
summary={summary}
ctxRatio={ctxRatio}
ctxMax={ctxMax}
balance={balance}
coldStart={coldStart}
/>
)}
</Box>
);
}
function Header({
model,
prefixHash,
harvestOn,
branchOn,
branchBudget,
reasoningEffort,
planMode,
editMode,
turns,
updateAvailable,
narrow,
busy,
proArmed,
escalated,
}: {
model: string;
prefixHash: string;
harvestOn?: boolean;
branchOn: boolean;
branchBudget: number;
reasoningEffort?: "high" | "max";
planMode?: boolean;
editMode?: EditMode;
turns: number;
updateAvailable?: string | null;
narrow: boolean;
busy: boolean;
proArmed: boolean;
escalated: boolean;
}) {
return (
<Box justifyContent="space-between">
<Box>
<Wordmark busy={busy} />
<Text dimColor>{` v${VERSION}`}</Text>
<Text dimColor> · </Text>
<Text color="yellow">{model}</Text>
{narrow ? null : (
<>
<Text dimColor> · </Text>
<Text dimColor>{prefixHash}</Text>
</>
)}
{harvestOn ? <Text color="magenta"> · harvest</Text> : null}
{branchOn ? <Text color="blue"> · branch{branchBudget}</Text> : null}
{reasoningEffort === "max" ? <Text color="green"> · max</Text> : null}
{reasoningEffort === "high" ? <Text color="yellow"> · high</Text> : null}
{planMode ? (
<Text color="red" bold>
{" · PLAN"}
</Text>
) : null}
{editMode ? (
<Text color={editMode === "auto" ? "magenta" : "cyan"} bold>
{editMode === "auto" ? " · AUTO" : " · review"}
</Text>
) : null}
{escalated ? (
<Text color="red" bold>
{" · ⇧ pro escalated"}
</Text>
) : proArmed ? (
<Text color="yellow" bold>
{" · ⇧ pro armed"}
</Text>
) : null}
</Box>
<Text>
{updateAvailable ? (
<Text color="yellow" bold>{`update: ${updateAvailable} · `}</Text>
) : null}
<Text dimColor>{narrow ? `turn ${turns}` : `turn ${turns} · /help`}</Text>
</Text>
</Box>
);
}
/**
* Wide-terminal layout (≥120 cols): single metrics row. Matches the
* original panel, just with calmer spacing and the cold-start
* treatment folded in.
*/
function InlineMetrics({
summary,
ctxRatio,
ctxMax,
balance,
coldStart,
}: {
summary: SessionSummary;
ctxRatio: number;
ctxMax: number;
balance?: { currency: string; total: number } | null;
coldStart: boolean;
}) {
return (
<Box marginTop={1} gap={3}>
<ContextCell ratio={ctxRatio} promptTokens={summary.lastPromptTokens} ctxMax={ctxMax} />
<CacheCell hitRatio={summary.cacheHitRatio} coldStart={coldStart} turns={summary.turns} />
<CostCell summary={summary} coldStart={coldStart} />
{balance ? <BalanceCell balance={balance} /> : null}
</Box>
);
}
/**
* Narrow-terminal layout (<120 cols): one metric per line, in priority
* order (ctx → balance → cache → cost). Order matters because users
* scanning a cramped terminal want "am I about to hit a wall?" answered
* first; dollars spent comes later.
*/
function StackedMetrics({
summary,
ctxRatio,
ctxMax,
balance,
coldStart,
}: {
summary: SessionSummary;
ctxRatio: number;
ctxMax: number;
balance?: { currency: string; total: number } | null;
coldStart: boolean;
}) {
return (
<Box marginTop={1} flexDirection="column">
<ContextCell
ratio={ctxRatio}
promptTokens={summary.lastPromptTokens}
ctxMax={ctxMax}
showBar
/>
{balance ? <BalanceCell balance={balance} /> : null}
<CacheCell hitRatio={summary.cacheHitRatio} coldStart={coldStart} turns={summary.turns} />
<CostCell summary={summary} coldStart={coldStart} />
</Box>
);
}
function ContextCell({
ratio,
promptTokens,
ctxMax,
showBar,
}: {
ratio: number;
promptTokens: number;
ctxMax: number;
showBar?: boolean;
}) {
if (promptTokens === 0) {
return (
<Text>
<Text dimColor>ctx </Text>
<Text dimColor>— (no turns yet)</Text>
</Text>
);
}
const color = ratio >= 0.8 ? "red" : ratio >= 0.6 ? "yellow" : "green";
const pct = Math.round(ratio * 100);
return (
<Text>
<Text dimColor>ctx </Text>
{showBar ? <Bar ratio={ratio} color={color} /> : null}
{showBar ? <Text> </Text> : null}
<Text color={color} bold>
{formatTokens(promptTokens)}/{formatTokens(ctxMax)}
</Text>
<Text dimColor> ({pct}%)</Text>
{ratio >= 0.8 ? (
<Text color="red" bold>
{" · /compact"}
</Text>
) : null}
</Text>
);
}
function CacheCell({
hitRatio,
coldStart,
turns,
}: {
hitRatio: number;
coldStart: boolean;
turns: number;
}) {
const pct = (hitRatio * 100).toFixed(1);
if (turns === 0) {
return (
<Text>
<Text dimColor>cache </Text>
<Text dimColor>—</Text>
</Text>
);
}
if (coldStart) {
return (
<Text>
<Text dimColor>cache </Text>
<Text dimColor>{pct}% </Text>
<Text dimColor italic>
(cold start)
</Text>
</Text>
);
}
const color = hitRatio >= 0.7 ? "green" : hitRatio >= 0.4 ? "yellow" : "red";
return (
<Text>
<Text dimColor>cache </Text>
<Text color={color} bold>
{pct}%
</Text>
</Text>
);
}
/**
* Color thresholds. Per-turn and session cumulative scale roughly 10×
* apart — a $0.20 single turn should feel just as warn-worthy as a $2
* session total. Values are rough "notice this" points, not hard caps.
*/
function turnCostColor(cost: number): "green" | "yellow" | "red" | undefined {
if (cost <= 0) return undefined;
if (cost >= 0.2) return "red";
if (cost >= 0.05) return "yellow";
return "green";
}
function sessionCostColor(cost: number): "green" | "yellow" | "red" | undefined {
if (cost <= 0) return undefined;
if (cost >= 5) return "red";
if (cost >= 0.5) return "yellow";
return "green";
}
function CostCell({
summary,
coldStart,
}: {
summary: SessionSummary;
coldStart: boolean;
}) {
if (summary.turns === 0) {
return (
<Text>
<Text dimColor>cost </Text>
<Text dimColor>—</Text>
</Text>
);
}
// The first turn is unavoidably a cache-miss (nothing to hit),
// so the dollar figure is front-loaded. Muting it during the
// cold-start window keeps the "expensive first turn" from
// reading as "something is wrong."
const turnColor = coldStart ? undefined : turnCostColor(summary.lastTurnCostUsd);
const sessionColor = coldStart ? undefined : sessionCostColor(summary.totalCostUsd);
return (
<Text>
<Text dimColor>turn </Text>
<Text color={turnColor} bold={!coldStart} dimColor={coldStart}>
${summary.lastTurnCostUsd.toFixed(4)}
</Text>
<Text dimColor>{" · session "}</Text>
<Text color={sessionColor} bold={!coldStart} dimColor={coldStart}>
${summary.totalCostUsd.toFixed(4)}
</Text>
</Text>
);
}
function BalanceCell({ balance }: { balance: { currency: string; total: number } }) {
const color = balance.total < 1 ? "red" : balance.total < 5 ? "yellow" : "green";
return (
<Text>
<Text dimColor>balance </Text>
<Text color={color} bold>
{balance.currency === "USD" ? "$" : ""}
{balance.total.toFixed(2)}
{balance.currency !== "USD" ? ` ${balance.currency}` : ""}
</Text>
</Text>
);
}
/**
* Unicode progress bar for the narrow layout's context cell. 10 cells
* wide — narrow terminals are already cramped, and the bar is just a
* visual cue for the percentage next to it, not the primary readout.
*/
function Bar({ ratio, color }: { ratio: number; color: "green" | "yellow" | "red" }) {
const cells = 10;
const filled = Math.max(0, Math.min(cells, Math.round(ratio * cells)));
const bar = "█".repeat(filled) + "░".repeat(cells - filled);
return <Text color={color}>{bar}</Text>;
}
/**
* Compact token formatter using binary K (÷1024): 1234 → "1.2K",
* 131072 → "128K". Matches DeepSeek's marketing label of "128K context
* length" — showing "131k" confused users (the actual limit is
* 128×1024 = 131,072 tokens, but the doc consistently says "128K").
* Uppercase K signals binary-K to anyone who notices.
*/
function formatTokens(n: number): string {
if (n < 1024) return String(n);
const k = n / 1024;
return k >= 100 ? `${k.toFixed(0)}K` : `${k.toFixed(1)}K`;
}
+447
View File
@@ -0,0 +1,447 @@
/**
* First-run / re-configure wizard.
*
* Walks a new user through: API key → preset pick → MCP server pick →
* per-server args → save. Saved output lives in `~/.reasonix/config.json`
* so the next `reasonix chat` starts with everything already wired.
*
* The wizard is the antidote to "too many CLI flags" — a new user should
* never have to read `--help` to get MCP + a sensible model combo
* working. Everything a user could set via `--mcp`, `--harvest`,
* `--branch`, etc. can be picked here in a few arrow-key presses.
*/
import { Box, Text, useApp, useInput } from "ink";
import TextInput from "ink-text-input";
// biome-ignore lint/style/useImportType: JSX (jsx: "react") needs React as a value at runtime
import React, { useState } from "react";
import {
type PresetName,
type ReasonixConfig,
defaultConfigPath,
isPlausibleKey,
readConfig,
redactKey,
writeConfig,
} from "../../config.js";
import { type CatalogEntry, MCP_CATALOG } from "../../mcp/catalog.js";
import { MultiSelect, type SelectItem, SingleSelect } from "./Select.js";
import { PRESET_DESCRIPTIONS } from "./presets.js";
export interface WizardProps {
/** Called once the config has been saved. */
onComplete: (cfg: ReasonixConfig) => void;
/** Called if the user presses Esc to abort. */
onCancel?: () => void;
/** Skip the API-key step if a key already exists (env or config). */
existingApiKey?: string;
/** Pre-fill selections when re-running (reconfigure flow). */
initial?: {
preset?: PresetName;
mcp?: string[];
};
}
type Step = "apiKey" | "preset" | "mcp" | "mcpArgs" | "review" | "saved";
interface WizardData {
apiKey: string;
preset: PresetName;
selectedCatalog: string[]; // entries from MCP_CATALOG by `name`
/** Captured user inputs per catalog entry that has `userArgs` (e.g. fs dir). */
catalogArgs: Record<string, string>;
}
const CATALOG_BY_NAME = new Map(MCP_CATALOG.map((e) => [e.name, e]));
export function Wizard({ onComplete, onCancel, existingApiKey, initial }: WizardProps) {
const { exit } = useApp();
const [step, setStep] = useState<Step>(existingApiKey ? "preset" : "apiKey");
const [data, setData] = useState<WizardData>({
apiKey: existingApiKey ?? "",
preset: initial?.preset ?? "fast",
selectedCatalog: deriveInitialCatalog(initial?.mcp ?? []),
catalogArgs: {},
});
const [error, setError] = useState<string | null>(null);
// Global Esc → cancel. Disabled once we've started saving to avoid
// ejecting out of a half-written state.
useInput((_input, key) => {
if (key.escape && step !== "saved" && onCancel) onCancel();
});
if (step === "apiKey") {
return (
<ApiKeyStep
onSubmit={(key) => {
setData((d) => ({ ...d, apiKey: key }));
setError(null);
setStep("preset");
}}
error={error}
onError={setError}
/>
);
}
if (step === "preset") {
return (
<StepFrame title="Pick a preset" step={1} total={3}>
<SingleSelect<PresetName>
items={presetItems()}
initialValue={data.preset}
onSubmit={(preset) => {
setData((d) => ({ ...d, preset }));
setStep("mcp");
}}
/>
<Box marginTop={1}>
<Text dimColor>[↑↓] navigate · [Enter] confirm · [Esc] cancel</Text>
</Box>
</StepFrame>
);
}
if (step === "mcp") {
return (
<StepFrame title="Which MCP servers should Reasonix wire up for you?" step={2} total={3}>
<MultiSelect
items={mcpItems()}
initialSelected={data.selectedCatalog}
onSubmit={(selected) => {
setData((d) => ({ ...d, selectedCatalog: selected }));
// Only advance to the args step if any selected entry needs args.
const needsArgs = selected.some((name) => CATALOG_BY_NAME.get(name)?.userArgs);
setStep(needsArgs ? "mcpArgs" : "review");
}}
footer="[↑↓] navigate · [Space] toggle · [Enter] confirm · [Esc] cancel · empty = skip"
/>
</StepFrame>
);
}
if (step === "mcpArgs") {
const pending = data.selectedCatalog.filter((name) => {
const entry = CATALOG_BY_NAME.get(name);
return entry?.userArgs && !data.catalogArgs[name];
});
if (pending.length === 0) {
setStep("review");
return null;
}
const currentName = pending[0]!;
const entry = CATALOG_BY_NAME.get(currentName)!;
return (
<McpArgsStep
entry={entry}
error={error}
onSubmit={(value) => {
setData((d) => ({
...d,
catalogArgs: { ...d.catalogArgs, [currentName]: value },
}));
setError(null);
}}
onError={setError}
/>
);
}
if (step === "review") {
const specs = data.selectedCatalog.map((name) => buildSpec(name, data.catalogArgs));
return (
<StepFrame title="Ready to save" step={3} total={3}>
<Box flexDirection="column">
<SummaryLine label="API key" value={redactKey(data.apiKey)} />
<SummaryLine label="Preset" value={data.preset} />
<SummaryLine
label="MCP"
value={specs.length === 0 ? "(none)" : `${specs.length} server(s)`}
/>
{specs.map((spec, i) => (
// biome-ignore lint/suspicious/noArrayIndexKey: review-only render, order fixed
<Box key={i} paddingLeft={14}>
<Text dimColor>· {spec}</Text>
</Box>
))}
<Box marginTop={1}>
<Text>Saves to {defaultConfigPath()}</Text>
</Box>
{error ? (
<Box marginTop={1}>
<Text color="red">{error}</Text>
</Box>
) : null}
<Box marginTop={1}>
<Text dimColor>[Enter] save · [Esc] cancel</Text>
</Box>
</Box>
<ReviewConfirm
onConfirm={() => {
try {
const specsNow = data.selectedCatalog.map((name) =>
buildSpec(name, data.catalogArgs),
);
const prev = readConfig();
const next: ReasonixConfig = {
...prev,
apiKey: data.apiKey,
preset: data.preset,
mcp: specsNow,
setupCompleted: true,
};
writeConfig(next);
setStep("saved");
onComplete(next);
} catch (e) {
setError(`Could not save config: ${(e as Error).message}`);
}
}}
/>
</StepFrame>
);
}
// saved
return (
<Box flexDirection="column" borderStyle="round" borderColor="green" paddingX={1}>
<Text bold color="green">
▸ Saved.
</Text>
<Box marginTop={1}>
<Text>Run `reasonix` any time to start chatting — your settings are remembered.</Text>
</Box>
<Box marginTop={1}>
<Text dimColor>[Enter] to exit</Text>
</Box>
<ExitOnEnter onExit={exit} />
</Box>
);
}
// ---------- step components ----------
function ApiKeyStep({
onSubmit,
error,
onError,
}: {
onSubmit: (key: string) => void;
error: string | null;
onError: (e: string | null) => void;
}) {
const [value, setValue] = useState("");
return (
<Box flexDirection="column" borderStyle="round" borderColor="cyan" paddingX={1}>
<Text bold color="cyan">
Welcome to Reasonix.
</Text>
<Box marginTop={1}>
<Text>Paste your DeepSeek API key to get started.</Text>
</Box>
<Text dimColor>Get one (free credit on signup): https://platform.deepseek.com/api_keys</Text>
<Text dimColor>Saved locally to {defaultConfigPath()}</Text>
<Box marginTop={1}>
<Text bold color="cyan">
{"key › "}
</Text>
<TextInput
value={value}
onChange={setValue}
onSubmit={(raw) => {
const trimmed = raw.trim();
if (!isPlausibleKey(trimmed)) {
onError("Doesn't look like a DeepSeek key. They start with 'sk-' and are 30+ chars.");
setValue("");
return;
}
onSubmit(trimmed);
}}
mask="•"
placeholder="sk-..."
/>
</Box>
{error ? (
<Box marginTop={1}>
<Text color="red">{error}</Text>
</Box>
) : value ? (
<Box marginTop={1}>
<Text dimColor>preview: {redactKey(value)}</Text>
</Box>
) : null}
</Box>
);
}
function McpArgsStep({
entry,
error,
onSubmit,
onError,
}: {
entry: CatalogEntry;
error: string | null;
onSubmit: (value: string) => void;
onError: (e: string | null) => void;
}) {
const [value, setValue] = useState("");
return (
<StepFrame title={`Configure ${entry.name}`} step={2} total={3}>
<Box flexDirection="column">
<Text>{entry.summary}</Text>
{entry.note ? (
<Box marginTop={1}>
<Text dimColor>{entry.note}</Text>
</Box>
) : null}
<Box marginTop={1}>
<Text>Required parameter: </Text>
<Text bold>{entry.userArgs}</Text>
</Box>
<Box marginTop={1}>
<Text bold color="cyan">
{entry.userArgs}
{" › "}
</Text>
<TextInput
value={value}
onChange={setValue}
onSubmit={(raw) => {
const trimmed = raw.trim();
if (!trimmed) {
onError(`${entry.name} needs a value — got an empty string.`);
return;
}
onSubmit(trimmed);
setValue("");
}}
placeholder={placeholderFor(entry)}
/>
</Box>
{error ? (
<Box marginTop={1}>
<Text color="red">{error}</Text>
</Box>
) : null}
</Box>
</StepFrame>
);
}
function ReviewConfirm({ onConfirm }: { onConfirm: () => void }) {
useInput((_i, key) => {
if (key.return) onConfirm();
});
return null;
}
function ExitOnEnter({ onExit }: { onExit: () => void }) {
useInput((_i, key) => {
if (key.return) onExit();
});
return null;
}
// ---------- small bits ----------
function StepFrame({
title,
step,
total,
children,
}: {
title: string;
step: number;
total: number;
children: React.ReactNode;
}) {
return (
<Box flexDirection="column" borderStyle="round" borderColor="cyan" paddingX={1}>
<Box>
<Text dimColor>
Step {step}/{total} ·{" "}
</Text>
<Text bold color="cyan">
{title}
</Text>
</Box>
<Box marginTop={1} flexDirection="column">
{children}
</Box>
</Box>
);
}
function SummaryLine({ label, value }: { label: string; value: string }) {
return (
<Box>
<Text>{label.padEnd(12)}</Text>
<Text bold>{value}</Text>
</Box>
);
}
// ---------- data helpers ----------
function presetItems(): SelectItem<PresetName>[] {
return (["fast", "smart", "max"] as PresetName[]).map((name) => ({
value: name,
label: `${name} — ${PRESET_DESCRIPTIONS[name].headline}`,
hint: PRESET_DESCRIPTIONS[name].cost,
}));
}
function mcpItems(): SelectItem<string>[] {
return MCP_CATALOG.map((entry) => {
const hintParts: string[] = [entry.summary];
if (entry.userArgs) hintParts.push(`(you'll provide ${entry.userArgs})`);
if (entry.note) hintParts.push(entry.note);
return {
value: entry.name,
label: entry.name,
hint: hintParts.join(" · "),
};
});
}
function placeholderFor(entry: CatalogEntry): string {
if (entry.name === "filesystem") return "e.g. /tmp/reasonix-sandbox";
if (entry.name === "sqlite") return "e.g. ./notes.sqlite";
return entry.userArgs ?? "";
}
function deriveInitialCatalog(existingSpecs: string[]): string[] {
// Best-effort recovery: if the user previously picked catalog entries,
// the spec strings look like `name=npx -y <pkg> ...`. Match by package
// so reconfigure pre-checks the same boxes.
const packageToName = new Map(MCP_CATALOG.map((e) => [e.package, e.name]));
const out: string[] = [];
for (const spec of existingSpecs) {
for (const [pkg, name] of packageToName) {
if (spec.includes(pkg)) {
out.push(name);
break;
}
}
}
return out;
}
/**
* Build the `--mcp` spec string for a catalog entry. Same format
* `mcpCommandFor` produces for `reasonix mcp list`, minus the leading
* `--mcp "..."` wrapper — we store the inner spec directly.
*/
export function buildSpec(name: string, argsByName: Record<string, string>): string {
const entry = CATALOG_BY_NAME.get(name);
if (!entry) return name; // shouldn't happen; fall back gracefully
const userArg = entry.userArgs ? argsByName[name] : undefined;
const tail = userArg ? ` ${quoteIfNeeded(userArg)}` : "";
return `${entry.name}=npx -y ${entry.package}${tail}`;
}
function quoteIfNeeded(s: string): string {
return /\s|"/.test(s) ? `"${s.replace(/"/g, '\\"')}"` : s;
}
+39
View File
@@ -0,0 +1,39 @@
/**
* Bash-mode (`!cmd`) prefix parsing.
*
* A `!` at the start of the user's input means "run this as a shell
* command in the sandbox root, and put both the command and its output
* into the conversation so the model sees it next turn." Same idea as
* Claude Code's `!` prefix — faster than round-tripping through the
* model just to cat a file or check git status.
*
* Design choice: user-typed `!` commands skip the allowlist. The
* allowlist exists to bound what the MODEL can do with run_command;
* the user typing `!git push` by hand is explicit consent. If a user
* wants stricter gating they can set `REASONIX_BANG_CONFIRM=1` in a
* future iteration.
*/
/**
* Return the command portion of a `!`-prefixed input, or `null` if
* the text isn't a bang invocation. Trims leading/trailing whitespace
* from the command body. `!` alone (or `!` followed by only whitespace)
* returns `null` — no command to run.
*/
export function detectBangCommand(text: string): string | null {
if (!text.startsWith("!")) return null;
const body = text.slice(1).trim();
if (!body) return null;
return body;
}
/**
* Format a bang command + its output into a single user-role message
* body that the model will see on the next turn. The `[!cmd]` header
* marks the run explicitly so the model can distinguish
* user-typed shell output from its own `run_command` tool results
* (which are `role: tool`, different message shape entirely).
*/
export function formatBangUserMessage(cmd: string, output: string): string {
return `[!${cmd}]\n${output}`;
}
+109
View File
@@ -0,0 +1,109 @@
import { formatAllBlockDiffs } from "../../code/diff-preview.js";
import type { ApplyResult, EditBlock, EditSnapshot } from "../../code/edit-blocks.js";
/**
* One batch of edits that actually landed on disk — durable enough for
* `/undo`, `/history`, and `/show` within a session. Not persisted
* across restarts: restoring pre-apply content from a process that
* crashed last week is git's job, not ours.
*/
export interface EditHistoryEntry {
/** Sequence number within the session, stable for `/show <id>`. */
id: number;
/** Epoch ms when the entry was opened (first edit landed). */
at: number;
/**
* Short tag for what produced the batch — "auto" (auto-mode tool
* call), "auto-text" (auto-mode text SEARCH/REPLACE at turn end),
* "review-apply" (user-approved modal edit or /apply flush).
*/
source: string;
/** Edit blocks included in this batch, in arrival order. */
blocks: EditBlock[];
/** Per-block outcome — some may be "not-found" if SEARCH drifted. */
results: ApplyResult[];
/**
* First-snapshot-per-path wins: this is what `/undo` restores to.
* Deduped so multi-edit turns still roll back to pre-turn state.
*/
snapshots: EditSnapshot[];
/**
* Paths within this entry that have already been reverted (via
* `/undo <id>`, `/undo <id> <path>`, or the newest-non-undone /undo
* shortcut). Per-path instead of entry-level so a batch can be
* partially undone — user reverts src/foo.ts out of a 3-file batch
* without rolling back the other two.
*/
undoneFiles: Set<string>;
}
/** True when every path in the entry has been undone. */
export function isEntryFullyUndone(e: EditHistoryEntry): boolean {
return e.snapshots.length > 0 && e.snapshots.every((s) => e.undoneFiles.has(s.path));
}
/** Per-entry three-state status label for display. */
export function entryStatus(e: EditHistoryEntry): "applied" | "UNDONE" | "PARTIAL" {
if (e.undoneFiles.size === 0) return "applied";
if (isEntryFullyUndone(e)) return "UNDONE";
return "PARTIAL";
}
/**
* Render a batch of SEARCH/REPLACE application results as one
* human-scannable info line per edit. Prefixes denote status so the
* line reads well even without color (e.g. when piped to a log file
* or stripped for screenshots):
* ✓ applied src/foo.ts
* ✓ created src/new.ts
* ✗ not-found src/bar.ts (SEARCH text does not match…)
*/
export function formatEditResults(results: ApplyResult[]): string {
const lines = results.map((r) => {
const mark = r.status === "applied" || r.status === "created" ? "✓" : "✗";
const detail = r.message ? ` (${r.message})` : "";
return ` ${mark} ${r.status.padEnd(11)} ${r.path}${detail}`;
});
const ok = results.filter((r) => r.status === "applied" || r.status === "created").length;
const total = results.length;
const header = `▸ edit blocks: ${ok}/${total} applied — /undo to roll back, or \`git diff\` to review`;
return [header, ...lines].join("\n");
}
/**
* Pending-edits preview shown after each assistant turn that proposed
* changes. Per-block path header + ±line-count, then a unified-diff-
* style preview (context trimmed to 2 lines each side, total capped
* at 20 lines per block). Users can eyeball what's about to land
* BEFORE pressing `y` — the old summary-only view was a common
* mistake surface.
*/
export function formatPendingPreview(blocks: EditBlock[]): string {
const header = `▸ ${blocks.length} pending edit block(s) — /apply (or y) to commit · /discard (or n) to drop`;
const diffLines = formatAllBlockDiffs(blocks);
return [header, ...diffLines].join("\n");
}
/**
* Per-file rows for the multi-level `/undo` output, without the
* single-batch header (the caller prepends its own).
*/
export function formatUndoRows(results: ApplyResult[]): string[] {
return results.map((r) => {
const mark = r.status === "applied" ? "✓" : "✗";
const detail = r.message ? ` (${r.message})` : "";
return ` ${mark} ${r.path}${detail}`;
});
}
export function describeRepair(repair: {
scavenged: number;
truncationsFixed: number;
stormsBroken: number;
}): string {
const parts: string[] = [];
if (repair.scavenged) parts.push(`scavenged ${repair.scavenged}`);
if (repair.truncationsFixed) parts.push(`repaired ${repair.truncationsFixed} truncation`);
if (repair.stormsBroken) parts.push(`broke ${repair.stormsBroken} storm`);
return parts.length ? `[repair] ${parts.join(", ")}` : "";
}
+1126 -62
View File
File diff suppressed because it is too large. Load diff
+242
View File
@@ -0,0 +1,242 @@
/**
* `/resource` and `/prompt` slash handlers for the chat/code TUI.
*
* The slash-command registry (slash.ts) advertises both commands so the
* argument-level picker and /help surface them, but the actual read/fetch
* work is async — McpClient.readResource and getPrompt both round-trip to
* the server — so it doesn't fit the synchronous `handleSlash` shape used
* by every other slash command. App.tsx intercepts the commands directly
* and calls into the helpers below.
*
* Split by effect boundary:
* - formatters (resource list, contents, prompt list, messages) are
* pure over already-fetched data and unit-tested
* - find-server helpers are pure lookups against inspection reports
* - `handleMcpBrowseSlash` is the async orchestrator App.tsx calls
*
* v1 intentionally does NOT inject the fetched resource/prompt into the
* next model turn. It's a display-only browser so users can see what
* their MCP servers expose. A future version may add a Tab-to-inject
* hotkey once the UX is settled.
*/
import type { McpClient } from "../../mcp/client.js";
import type {
GetPromptResult,
McpPromptMessage,
McpResourceContents,
ReadResourceResult,
} from "../../mcp/types.js";
import type { DisplayEvent } from "./EventLog.js";
import type { McpServerSummary } from "./slash.js";
/**
* React setState for Historical — typed loose because the App state
* shape is App-internal. We only ever append, so `(prev) => prev.concat(row)`
* works against any array-of-DisplayEvent state.
*/
export type HistoricalSetter = (updater: (prev: DisplayEvent[]) => DisplayEvent[]) => void;
export function formatResourceList(servers: readonly McpServerSummary[]): string {
const lines: string[] = [];
let total = 0;
for (const s of servers) {
if (!s.report.resources.supported) continue;
const items = s.report.resources.items;
if (items.length === 0) continue;
lines.push(`[${s.label}] ${items.length} resource(s):`);
for (const r of items.slice(0, 20)) {
const name = r.name && r.name !== r.uri ? ` ${r.name}` : "";
const mime = r.mimeType ? ` · ${r.mimeType}` : "";
lines.push(` · ${r.uri}${name}${mime}`);
total++;
}
if (items.length > 20) lines.push(` (+${items.length - 20} more)`);
lines.push("");
}
if (total === 0) {
return "No resources on any connected MCP server (or no servers connected). `/mcp` shows the current set.";
}
lines.push("Read one: `/resource <uri>` — or use Tab in the picker.");
return lines.join("\n");
}
export function formatPromptList(servers: readonly McpServerSummary[]): string {
const lines: string[] = [];
let total = 0;
for (const s of servers) {
if (!s.report.prompts.supported) continue;
const items = s.report.prompts.items;
if (items.length === 0) continue;
lines.push(`[${s.label}] ${items.length} prompt(s):`);
for (const p of items.slice(0, 20)) {
const desc = p.description ? ` — ${p.description}` : "";
const argHint =
p.arguments && p.arguments.length > 0
? ` (args: ${p.arguments.map((a) => a.name + (a.required ? "*" : "?")).join(", ")})`
: "";
lines.push(` · ${p.name}${argHint}${desc}`);
total++;
}
if (items.length > 20) lines.push(` (+${items.length - 20} more)`);
lines.push("");
}
if (total === 0) {
return "No prompts on any connected MCP server (or no servers connected). `/mcp` shows the current set.";
}
lines.push(
"Fetch one: `/prompt <name>` — args are not supported yet; prompts with required args will surface an error from the server.",
);
return lines.join("\n");
}
export function findServerForResource(
servers: readonly McpServerSummary[],
uri: string,
): McpServerSummary | null {
for (const s of servers) {
if (!s.report.resources.supported) continue;
if (s.report.resources.items.some((r) => r.uri === uri)) return s;
}
return null;
}
export function findServerForPrompt(
servers: readonly McpServerSummary[],
name: string,
): McpServerSummary | null {
for (const s of servers) {
if (!s.report.prompts.supported) continue;
if (s.report.prompts.items.some((p) => p.name === name)) return s;
}
return null;
}
export function formatResourceContents(uri: string, result: ReadResourceResult): string {
const lines: string[] = [`Resource ${uri} (${result.contents.length} content block(s)):`, ""];
for (let i = 0; i < result.contents.length; i++) {
const c = result.contents[i]!;
const header = `— block ${i + 1}${c.mimeType ? ` · ${c.mimeType}` : ""}`;
lines.push(header);
lines.push(formatOneResourceContent(c));
lines.push("");
}
return lines.join("\n").trimEnd();
}
function formatOneResourceContent(c: McpResourceContents): string {
if ("text" in c) {
const MAX = 8_000;
if (c.text.length > MAX) {
return `${c.text.slice(0, MAX)}\n\n[…truncated ${c.text.length - MAX} chars; full contents available via McpClient.readResource in library mode.]`;
}
return c.text;
}
// blob — we can't render arbitrary binary in the TUI; give the size.
const bytes = typeof c.blob === "string" ? approximateBase64ByteSize(c.blob) : 0;
return `[binary · ~${bytes.toLocaleString()} bytes · base64]`;
}
function approximateBase64ByteSize(b64: string): number {
// 4 base64 chars encode 3 bytes; padding `=` trims the output.
const padding = b64.endsWith("==") ? 2 : b64.endsWith("=") ? 1 : 0;
return Math.floor((b64.length * 3) / 4) - padding;
}
export function formatPromptMessages(name: string, result: GetPromptResult): string {
const lines: string[] = [
`Prompt ${name}${result.description ? ` — ${result.description}` : ""}`,
`(${result.messages.length} message(s))`,
"",
];
for (let i = 0; i < result.messages.length; i++) {
const m = result.messages[i]!;
lines.push(`— ${i + 1}. ${m.role}`);
lines.push(formatOnePromptMessage(m));
lines.push("");
}
return lines.join("\n").trimEnd();
}
function formatOnePromptMessage(m: McpPromptMessage): string {
const block = m.content as { type?: string; text?: string; resource?: McpResourceContents };
if (block.type === "text" && typeof block.text === "string") return block.text;
if (block.type === "resource" && block.resource) {
return `[resource: ${block.resource.uri}]\n${formatOneResourceContent(block.resource)}`;
}
return `[non-text content: ${block.type ?? "unknown"}]`;
}
/**
* Orchestrator. Looks up the right server, calls readResource/getPrompt
* via its `client`, and pushes one info row into `Historical`. Errors
* (server missing, -32601, network) surface as a warning row; the user
* can always fall back to `reasonix mcp inspect <spec>` for diagnostics.
*/
export async function handleMcpBrowseSlash(
kind: "resource" | "prompt",
arg: string,
servers: readonly McpServerSummary[],
setHistorical: HistoricalSetter,
): Promise<void> {
const ts = Date.now();
const push = (role: DisplayEvent["role"], text: string) => {
setHistorical((prev) => [...prev, { id: `mcp-${role}-${ts}-${prev.length}`, role, text }]);
};
// No arg → list mode.
if (!arg) {
push("info", kind === "resource" ? formatResourceList(servers) : formatPromptList(servers));
return;
}
if (kind === "resource") {
const server = findServerForResource(servers, arg);
if (!server) {
push(
"warning",
`no server exposes resource "${arg}". \`/resource\` with no arg lists what's available.`,
);
return;
}
const client: McpClient | undefined = server.client;
if (!client) {
push(
"warning",
`server [${server.label}] is not connected (display-only). Resource read requires a live MCP client.`,
);
return;
}
try {
const result = await client.readResource(arg);
push("info", formatResourceContents(arg, result));
} catch (err) {
push("warning", `readResource failed: ${(err as Error).message}`);
}
return;
}
// prompt
const server = findServerForPrompt(servers, arg);
if (!server) {
push(
"warning",
`no server exposes prompt "${arg}". \`/prompt\` with no arg lists what's available.`,
);
return;
}
const client: McpClient | undefined = server.client;
if (!client) {
push(
"warning",
`server [${server.label}] is not connected (display-only). Prompt fetch requires a live MCP client.`,
);
return;
}
try {
const result = await client.getPrompt(arg);
push("info", formatPromptMessages(arg, result));
} catch (err) {
push("warning", `getPrompt failed: ${(err as Error).message}`);
}
}
+314
View File
@@ -0,0 +1,314 @@
/**
* Pure keystroke → action reducer for PromptInput.
*
* Kept separate from the React component so the keyboard semantics
* are easy to unit-test. The component threads `useInput` through
* this function and applies the returned action.
*
* Edit model:
* - Full cursor support. ←/→ move one column. ↑/↓ move across
* lines in a multi-line buffer (column preserved when possible).
* Ctrl+A / Ctrl+E jump to start / end of the current line.
* - Backspace deletes the char before the cursor; Delete deletes
* the char under the cursor.
* - Printable chars (including multi-char paste bursts) insert
* at the cursor.
* - Enter submits unless Shift is held (newline), the line ends
* with '\' and cursor is at end (bash-style continuation), or
* the input is Ctrl+J (LF, terminal-universal newline).
* - Parent owns Tab, Esc, PageUp/Down (slash-complete, abort,
* unused). Arrow keys are split: empty buffer → parent (history
* recall); non-empty → child (cursor movement).
*/
export interface MultilineKey {
input: string;
return?: boolean;
shift?: boolean;
ctrl?: boolean;
meta?: boolean;
backspace?: boolean;
delete?: boolean;
tab?: boolean;
upArrow?: boolean;
downArrow?: boolean;
leftArrow?: boolean;
rightArrow?: boolean;
escape?: boolean;
pageUp?: boolean;
pageDown?: boolean;
}
export interface MultilineAction {
/** New buffer value. `null` = unchanged. */
next: string | null;
/** New cursor position (0..value.length). `null` = unchanged. */
cursor: number | null;
/** When `true`, fire `onSubmit(submitValue ?? value)`. */
submit: boolean;
submitValue?: string;
/**
* When set, the key was ↑/↓ at a buffer boundary (empty buffer, or
* cursor already at first/last line) and the component should hand
* off to the parent's history-recall handler. The child's cursor
* didn't move; the parent decides whether to swap in a prior
* prompt. Lets users escape out of a multi-line buffer into
* history without first emptying it — previously NOOP felt stuck.
*/
historyHandoff?: "prev" | "next";
/**
* Multi-char paste detected. The reducer is pure so it can't
* allocate a sentinel id or write to the registry — it hands the
* raw normalized payload up to PromptInput, which registers the
* paste, picks a sentinel codepoint, and inserts THAT (one char)
* into the buffer. Result: the user sees a `[paste #N · M lines]`
* placeholder instead of the full content drowning the typed text.
*/
pasteRequest?: { content: string };
}
const BACKSLASH_SUFFIX = /\\$/;
const NOOP: MultilineAction = { next: null, cursor: null, submit: false };
function rewriteRawArrowEscape(key: MultilineKey): MultilineKey {
if (key.upArrow || key.downArrow || key.leftArrow || key.rightArrow) return key;
if (key.input === "\x1b[A") return { ...key, upArrow: true, input: "" };
if (key.input === "\x1b[B") return { ...key, downArrow: true, input: "" };
if (key.input === "\x1b[C") return { ...key, rightArrow: true, input: "" };
if (key.input === "\x1b[D") return { ...key, leftArrow: true, input: "" };
return key;
}
export function processMultilineKey(
value: string,
cursor: number,
keyIn: MultilineKey,
): MultilineAction {
// Raw-escape fallback for terminals (some Windows configurations —
// cmd.exe, older winpty) that don't set `key.upArrow` / etc. on
// arrow-key press and instead leak the raw ANSI CSI sequence into
// `input`. Without this, `\x1b[A` lands on the "printable" branch
// below and the user sees literal escape bytes inserted into their
// buffer. Rewrite the event into the structured key here.
const key: MultilineKey = rewriteRawArrowEscape(keyIn);
// Parent-owned keys: Tab (slash-complete), Esc (abort).
if (key.tab || key.escape) {
return NOOP;
}
// Buffer-wide navigation. Per-line motion (↑/↓ / Ctrl+A / Ctrl+E)
// is already covered; PageUp/PageDown are the missing "jump to
// top / bottom of the WHOLE buffer" pair, useful after pasting a
// 500-line blob where ↑×500 is absurd. Repurposed from the
// previous NOOP behavior (PageUp/Down had no binding).
if (key.pageUp) {
return cursor === 0 ? NOOP : { next: null, cursor: 0, submit: false };
}
if (key.pageDown) {
return cursor === value.length ? NOOP : { next: null, cursor: value.length, submit: false };
}
// Empty buffer + ↑/↓ → parent handles history recall.
if (value.length === 0 && (key.upArrow || key.downArrow)) {
return { ...NOOP, historyHandoff: key.upArrow ? "prev" : "next" };
}
// Cursor motion.
if (key.leftArrow) {
return { next: null, cursor: Math.max(0, cursor - 1), submit: false };
}
if (key.rightArrow) {
return { next: null, cursor: Math.min(value.length, cursor + 1), submit: false };
}
if (key.upArrow) {
const moved = moveCursorUp(value, cursor);
// Cursor already on the first line — hand off to history recall
// instead of sitting stuck. Users can now escape into history
// from the middle of a multi-line draft.
if (moved === cursor) return { ...NOOP, historyHandoff: "prev" };
return { next: null, cursor: moved, submit: false };
}
if (key.downArrow) {
const moved = moveCursorDown(value, cursor);
if (moved === cursor) return { ...NOOP, historyHandoff: "next" };
return { next: null, cursor: moved, submit: false };
}
// Emacs-style line jumps (universal across terminals; Home/End aren't
// reliably reported by Ink so we don't depend on them).
if (key.ctrl && key.input === "a") {
return { next: null, cursor: startOfLine(value, cursor), submit: false };
}
if (key.ctrl && key.input === "e") {
return { next: null, cursor: endOfLine(value, cursor), submit: false };
}
// Bash / readline conventions:
// Ctrl+U — clear the whole buffer (readline treats this as
// "clear from cursor to start"; for our text-area we treat it
// as "clear all" because there's no ergonomic way to clear a
// huge paste otherwise).
// Ctrl+W — delete the word before the cursor.
if (key.ctrl && key.input === "u") {
return value.length === 0 ? NOOP : { next: "", cursor: 0, submit: false };
}
if (key.ctrl && key.input === "w") {
if (cursor === 0) return NOOP;
const wordStart = previousWordStart(value, cursor);
return {
next: value.slice(0, wordStart) + value.slice(cursor),
cursor: wordStart,
submit: false,
};
}
// Paste-burst detection. If `input` contains a newline (or
// bracketed-paste markers from a terminal that supports them),
// this is a paste — surface it as a `pasteRequest` so the parent
// can register the blob and insert ONE sentinel codepoint instead
// of the full content. The buffer stays small + readable; the
// user sees `[paste #N · M lines]` where the paste lives.
//
// Always overrides `key.return` for pastes: Ink occasionally sets
// key.return when a paste's trailing \n looks like Enter, which
// would submit the partial buffer mid-paste and silently truncate
// the content. Pastes always insert; Enter only submits typed
// content. We normalize \r\n and bare \r to \n so mixed-line-
// ending pastes (Windows clipboard, web copy) land cleanly.
const stripped = key.input.replaceAll("\u001b[200~", "").replaceAll("\u001b[201~", "");
// Paste = newline-containing input with MORE than just the newline
// itself. A bare "\n" is Ctrl+J / one-keystroke newline (handled
// below); only multi-char input wrapped around a newline is a real
// paste burst that warrants a sentinel.
const looksLikePaste =
stripped.length > 1 && (stripped.includes("\n") || stripped.includes("\r"));
if (looksLikePaste) {
const normalized = stripped.replace(/\r\n?/g, "\n");
return {
next: null,
cursor: null,
submit: false,
pasteRequest: { content: normalized },
};
}
// Single-char Ctrl+J / LF: insert one newline.
if (key.input === "\n" || (key.ctrl && key.input === "j")) {
return insertAt(value, cursor, "\n");
}
if (key.return) {
if (key.shift) return insertAt(value, cursor, "\n");
// Bash-style line continuation: trailing '\' + Enter (only when the
// cursor sits at end-of-buffer, so a stray '\' mid-line doesn't
// trigger it).
if (cursor === value.length && BACKSLASH_SUFFIX.test(value)) {
const replaced = `${value.slice(0, -1)}\n`;
return { next: replaced, cursor: replaced.length, submit: false };
}
return { next: null, cursor: null, submit: true, submitValue: value };
}
// Backspace = delete the char BEFORE the cursor. We also accept
// `key.delete` and the raw DEL (0x7f) / BS (0x08) bytes as backspace
// for the same purpose — some Windows terminals (cmd.exe, certain
// winpty configs) report plain Backspace without setting
// `key.backspace`, which used to leave the user typing into a prompt
// where the Backspace key did nothing. Reasonix doesn't offer a
// separate forward-delete operation, so collapsing them is safe.
if (key.backspace || key.delete || key.input === "\x7f" || key.input === "\b") {
if (cursor === 0) return NOOP;
return {
next: value.slice(0, cursor - 1) + value.slice(cursor),
cursor: cursor - 1,
submit: false,
};
}
// Bare modifier events (Ctrl/Meta with no printable) and unhandled
// Ctrl-<letter> chords are dropped so a stray Ctrl+L doesn't insert "l".
if ((key.ctrl || key.meta) && key.input.length === 0) return NOOP;
if (key.ctrl || key.meta) return NOOP;
// Printable input (may be a multi-char paste; pasted newlines land
// inside the buffer rather than triggering submit on the first line).
if (key.input.length > 0) {
return insertAt(value, cursor, key.input);
}
return NOOP;
}
function insertAt(value: string, cursor: number, insert: string): MultilineAction {
return {
next: value.slice(0, cursor) + insert + value.slice(cursor),
cursor: cursor + insert.length,
submit: false,
};
}
/**
* Line + column of a cursor inside a buffer. Exported because the
* renderer needs the same mapping for drawing the cursor block on the
* right line.
*/
export function lineAndColumn(value: string, cursor: number): { line: number; col: number } {
let line = 0;
let col = 0;
const n = Math.min(cursor, value.length);
for (let i = 0; i < n; i++) {
if (value[i] === "\n") {
line++;
col = 0;
} else {
col++;
}
}
return { line, col };
}
function startOfLine(value: string, cursor: number): number {
return value.lastIndexOf("\n", cursor - 1) + 1;
}
/**
* Find the start of the word immediately to the left of the cursor.
* Skips trailing whitespace first (so Ctrl+W after typing space
* still removes the previous word, not just the space), then walks
* back over the word characters until a whitespace boundary or
* start-of-buffer. Newlines count as whitespace, so Ctrl+W at the
* start of a line deletes the preceding line's last word — same
* behavior as bash/readline.
*/
function previousWordStart(value: string, cursor: number): number {
let i = cursor;
while (i > 0 && /\s/.test(value[i - 1] ?? "")) i--;
while (i > 0 && !/\s/.test(value[i - 1] ?? "")) i--;
return i;
}
function endOfLine(value: string, cursor: number): number {
const nl = value.indexOf("\n", cursor);
return nl === -1 ? value.length : nl;
}
function moveCursorUp(value: string, cursor: number): number {
const curStart = startOfLine(value, cursor);
if (curStart === 0) return cursor; // already on the first line
const col = cursor - curStart;
const prevEnd = curStart - 1; // the '\n' between the two lines
const prevStart = value.lastIndexOf("\n", prevEnd - 1) + 1;
const prevLen = prevEnd - prevStart;
return prevStart + Math.min(col, prevLen);
}
function moveCursorDown(value: string, cursor: number): number {
const nextNl = value.indexOf("\n", cursor);
if (nextNl === -1) return cursor; // already on the last line
const curStart = startOfLine(value, cursor);
const col = cursor - curStart;
const nextStart = nextNl + 1;
const followingNl = value.indexOf("\n", nextStart);
const nextLen = (followingNl === -1 ? value.length : followingNl) - nextStart;
return nextStart + Math.min(col, nextLen);
}
+81
View File
@@ -0,0 +1,81 @@
/**
* Collapse long user-typed input for display purposes.
*
* Problem: pasting a stack trace, log dump, or sample file into the
* prompt box floods the Historical scrollback with a huge block — the
* user can't see their previous turns, the assistant's replies, or
* where the cursor is. Terminal UIs have shipped this shape for
* years (iTerm's "pasted text" notation, Claude Code's preview).
*
* Split of concerns: the MODEL still gets the full text. This helper
* only rewrites what we render in the Historical row. `@` expansions
* and `!` bang outputs have their own display paths (unaffected).
*/
/** Defaults tuned to typical prose vs. typical code-paste shapes. */
export const DEFAULT_PASTE_LINE_THRESHOLD = 40;
export const DEFAULT_PASTE_CHAR_THRESHOLD = 2000;
/** Lines kept visible at the head of a collapsed paste. */
export const DEFAULT_PASTE_HEAD_LINES = 10;
export interface PasteCollapseOptions {
lineThreshold?: number;
charThreshold?: number;
headLines?: number;
}
export interface PasteCollapseResult {
/** Text to render in the Historical row (possibly collapsed). */
displayText: string;
/** True when collapsing happened. False = input passed through verbatim. */
collapsed: boolean;
/** Original char length — exposed so callers can log/annotate. */
originalChars: number;
/** Original line count. */
originalLines: number;
}
/**
* Collapse `input` when it exceeds either the line OR char threshold.
* Display shape:
*
* ▸ pasted 2.3 KB (84 lines) — first 10 shown, full text sent to model
* line 1
* line 2
* …
* line 10
* … (74 more lines)
*
* Short input passes through unchanged — collapsed = false.
*/
export function formatLongPaste(
input: string,
opts: PasteCollapseOptions = {},
): PasteCollapseResult {
const lineCap = opts.lineThreshold ?? DEFAULT_PASTE_LINE_THRESHOLD;
const charCap = opts.charThreshold ?? DEFAULT_PASTE_CHAR_THRESHOLD;
const headN = Math.max(1, opts.headLines ?? DEFAULT_PASTE_HEAD_LINES);
const originalChars = input.length;
const lines = input.split("\n");
const originalLines = lines.length;
if (originalChars <= charCap && originalLines <= lineCap) {
return { displayText: input, collapsed: false, originalChars, originalLines };
}
const header = `▸ pasted ${formatBytes(originalChars)} (${originalLines} lines) — first ${Math.min(headN, originalLines)} shown, full text sent to model`;
const head = lines.slice(0, headN).join("\n");
const remaining = originalLines - headN;
const footer = remaining > 0 ? `… (${remaining} more line${remaining === 1 ? "" : "s"})` : "";
const displayText = footer ? `${header}\n${head}\n${footer}` : `${header}\n${head}`;
return { displayText, collapsed: true, originalChars, originalLines };
}
function formatBytes(n: number): string {
if (n < 1024) return `${n} B`;
const kb = n / 1024;
if (kb < 1024) return `${kb.toFixed(kb >= 10 ? 0 : 1)} KB`;
const mb = kb / 1024;
return `${mb.toFixed(mb >= 10 ? 0 : 1)} MB`;
}
+133
View File
@@ -0,0 +1,133 @@
/**
* Paste sentinels — represent a pasted blob as a single codepoint in
* the input buffer instead of inlining its full contents.
*
* Why: a 3000-line paste shoved verbatim into the buffer drowns the
* surrounding typed text, costs a lot to render per keystroke, and
* makes navigation/clear awkward. Replace it with one PUA char (a
* "sentinel") and store the real content in a side registry. The
* buffer string stays small, the user types around the sentinel as
* if it were a single character, and a Backspace at the sentinel
* deletes the whole paste in one stroke. On submit we expand the
* sentinels back to real content.
*
* Encoding:
* - One codepoint per paste, in PUA range U+E100..U+E1FF (256 slots).
* - The codepoint's offset within that range is the paste id.
* - That gives us 256 distinct paste blobs per session before ids
* wrap. In practice users paste a handful per session — wrap is
* a non-issue, but if it happens, the new paste overwrites the
* oldest registry entry; any stale sentinels still in the buffer
* will render with a "(missing)" badge so the user can clean up.
*
* Range chosen from the Supplementary PUA-A region's neighbor (BMP
* PUA) so a single `String.fromCharCode` works — no surrogate pairs,
* no `length === 2` weirdness for cursor arithmetic.
*/
export const PASTE_SENTINEL_BASE = 0xe100;
export const PASTE_SENTINEL_RANGE = 256;
export const PASTE_SENTINEL_END = PASTE_SENTINEL_BASE + PASTE_SENTINEL_RANGE;
export interface PasteEntry {
id: number;
content: string;
lineCount: number;
charCount: number;
}
export function encodePasteSentinel(id: number): string {
if (id < 0 || id >= PASTE_SENTINEL_RANGE) {
throw new Error(`paste sentinel id ${id} out of range [0, ${PASTE_SENTINEL_RANGE})`);
}
return String.fromCharCode(PASTE_SENTINEL_BASE + id);
}
/** Returns the paste id, or `null` if `ch` is not a sentinel codepoint. */
export function decodePasteSentinel(ch: string): number | null {
if (ch.length === 0) return null;
const cp = ch.charCodeAt(0);
if (cp < PASTE_SENTINEL_BASE || cp >= PASTE_SENTINEL_END) return null;
return cp - PASTE_SENTINEL_BASE;
}
export function isPasteSentinel(ch: string): boolean {
return decodePasteSentinel(ch) !== null;
}
/**
* Build a PasteEntry from raw paste content. Computes line + char
* counts once at registration time so the renderer doesn't re-count
* on every keystroke.
*/
export function makePasteEntry(id: number, content: string): PasteEntry {
return {
id,
content,
lineCount: content.split("\n").length,
charCount: content.length,
};
}
/**
* Expand every sentinel in `text` back to its registered paste
* content. Unknown sentinels (entry missing — registry was wiped, or
* id wrap collision) drop to empty string so the resulting prompt
* doesn't carry a literal PUA codepoint to the model.
*
* Used at submit time to recover the full prompt the user composed.
*/
export function expandPasteSentinels(
text: string,
pastes: ReadonlyMap<number, PasteEntry>,
): string {
let out = "";
for (let i = 0; i < text.length; i++) {
const ch = text[i]!;
const id = decodePasteSentinel(ch);
if (id === null) {
out += ch;
continue;
}
const entry = pastes.get(id);
out += entry?.content ?? "";
}
return out;
}
/**
* Quick check: does the buffer contain ANY sentinel? Used to gate
* UI hints (the "paste #N" listing in the prompt-box footer) without
* walking the whole buffer twice.
*/
export function bufferHasPaste(text: string): boolean {
for (let i = 0; i < text.length; i++) {
if (decodePasteSentinel(text[i]!) !== null) return true;
}
return false;
}
/**
* Walk the buffer and return the ids of every sentinel still
* present, in source order. Used by the registry's GC pass at
* submit time so unreachable paste entries don't accumulate.
* (No-op when the buffer is sentinel-free.)
*/
export function listPasteIdsInBuffer(text: string): number[] {
const ids: number[] = [];
for (let i = 0; i < text.length; i++) {
const id = decodePasteSentinel(text[i]!);
if (id !== null) ids.push(id);
}
return ids;
}
/**
* Format `1234` chars as `1.2KB` etc. Tiny helper used in placeholder
* labels — kept here so paste-related display logic is co-located.
*/
export function formatBytesShort(n: number): string {
if (n < 1024) return `${n}B`;
if (n < 1024 * 1024) return `${(n / 1024).toFixed(n < 1024 * 10 ? 1 : 0)}KB`;
return `${(n / (1024 * 1024)).toFixed(1)}MB`;
}
+79
View File
@@ -0,0 +1,79 @@
/**
* One place that defines what each preset means. Both `slash.ts`
* (in-chat `/preset`) and the wizard (first-run setup) read from here.
*
* Presets are the single vocabulary we teach new users: they don't need
* to know model IDs, reasoning effort, or thinking mode independently
* — they pick "fast / smart / max" and we translate.
*
* Design rules (v0.6+):
* - Branching (`branch >= 2`) is NEVER in a preset. Self-consistency
* sampling is `N×` cost; auto-enabling it would ambush users into
* multi-dollar turns without asking. Opt-in only via `/branch N`.
* - Harvest (Pillar-2 plan-state extraction) is NEVER in a preset.
* In practice it's display sugar — the typed plan state hasn't
* fed back into orchestration decisions (branch trigger) often
* enough to pay for the extra round-trip. Opt-in only via
* `/harvest on`.
* - The three tiers differ on only TWO knobs: model (flash/pro) and
* reasoning effort (high/max). Same on-the-wire billing axis,
* easy to reason about, easy to budget.
*/
import type { PresetName } from "../../config.js";
export interface PresetSettings {
model: string;
/**
* Reasoning-effort cap sent per turn. `high` = shorter chain of
* thought (cheaper, faster); `max` = agent-class default (deeper,
* more output tokens). DeepSeek ignores this field on non-thinking
* calls, so it's safe to pin across models.
*/
reasoningEffort: "high" | "max";
/**
* Pillar-2 plan-state extraction. Every preset ships `false` (see
* module header); kept in the shape so a user who later flips it on
* at runtime still round-trips cleanly. `/harvest on` toggles it.
*/
harvest: boolean;
/**
* Branch budget. Every preset ships `1` (off). `/branch N` with
* N>=2 is the only way to enable self-consistency sampling.
*/
branch: number;
}
export const PRESETS: Record<PresetName, PresetSettings> = {
// fast — flash + effort=high. Quick Q&A, one-line tweaks, anything
// where shallow reasoning is enough. Cheapest turn possible.
fast: { model: "deepseek-v4-flash", reasoningEffort: "high", harvest: false, branch: 1 },
// smart — flash + effort=max. Full thinking budget on the cheap
// model. The default: handles 90%+ of coding work at a fraction
// of pro's cost.
smart: { model: "deepseek-v4-flash", reasoningEffort: "max", harvest: false, branch: 1 },
// max — pro + effort=max. Frontier model for hard tasks: cross-
// file architecture, subtle bug hunts, anything where flash's
// reasoning has measurably failed. ~12× per-token vs flash; save
// for when you need it, or use `/pro` to escalate a single turn.
max: { model: "deepseek-v4-pro", reasoningEffort: "max", harvest: false, branch: 1 },
};
export const PRESET_DESCRIPTIONS: Record<PresetName, { headline: string; cost: string }> = {
fast: {
headline: "v4-flash · effort=high",
cost: "cheapest · quick Q&A, one-line edits",
},
smart: {
headline: "v4-flash · effort=max",
cost: "~1.5× fast · default · day-to-day coding",
},
max: {
headline: "v4-pro · effort=max",
cost: "~12× fast · hard single-shots · use /pro for a single-turn bump",
},
};
export function resolvePreset(name: PresetName | undefined): PresetSettings {
return PRESETS[name ?? "smart"];
}
+20 -157
View File
@@ -1,157 +1,20 @@
import type { CacheFirstLoop } from "../../loop.js";
import { deleteSession, listSessions } from "../../session.js";
export interface SlashResult {
/** Text to display back to the user as a system/info line. */
info?: string;
/** Exit the app. */
exit?: boolean;
/** Clear the visible history. */
clear?: boolean;
/** Unknown command — display usage hint. */
unknown?: boolean;
}
export function parseSlash(text: string): { cmd: string; args: string[] } | null {
if (!text.startsWith("/")) return null;
const parts = text.slice(1).trim().split(/\s+/);
const cmd = parts[0]?.toLowerCase() ?? "";
if (!cmd) return null;
return { cmd, args: parts.slice(1) };
}
export function handleSlash(cmd: string, args: string[], loop: CacheFirstLoop): SlashResult {
switch (cmd) {
case "exit":
case "quit":
return { exit: true };
case "clear":
return { clear: true };
case "help":
case "?":
return {
info: [
"Commands:",
" /help this message",
" /status show current settings",
" /preset <fast|smart|max> one-tap presets — see below",
" /model <id> deepseek-chat or deepseek-reasoner",
" /harvest [on|off] Pillar 2: structured plan-state extraction",
" /branch <N|off> run N parallel samples (N>=2), pick most confident",
" /sessions list saved sessions (current is marked with ▸)",
" /forget delete the current session from disk",
" /clear clear displayed history (log + session kept)",
" /exit quit",
"",
"Presets:",
" fast deepseek-chat no harvest no branch ~1¢/100turns ← default",
" smart reasoner harvest ~10x cost, slower",
" max reasoner harvest branch 3 ~30x cost, slowest",
"",
"Sessions (auto-enabled by default, named 'default'):",
" reasonix chat --session <name> use a different named session",
" reasonix chat --no-session disable persistence for this run",
].join("\n"),
};
case "sessions": {
const items = listSessions();
if (items.length === 0) {
return {
info: "no saved sessions yet — chat normally and your messages will be saved automatically",
};
}
const lines = ["Saved sessions:"];
for (const s of items) {
const sizeKb = (s.size / 1024).toFixed(1);
const when = s.mtime.toISOString().replace("T", " ").slice(0, 16);
const marker = s.name === loop.sessionName ? "▸" : " ";
lines.push(
` ${marker} ${s.name.padEnd(22)} ${String(s.messageCount).padStart(5)} msgs ${sizeKb.padStart(7)} KB ${when}`,
);
}
lines.push("");
lines.push("Resume with: reasonix chat --session <name>");
return { info: lines.join("\n") };
}
case "forget": {
if (!loop.sessionName) {
return { info: "not in a session — nothing to forget" };
}
const name = loop.sessionName;
const ok = deleteSession(name);
return {
info: ok
? `▸ deleted session "${name}" — current screen still shows the conversation, but next launch starts fresh`
: `could not delete session "${name}" (already gone?)`,
};
}
case "status": {
const branchBudget = loop.branchOptions.budget ?? 1;
return {
info:
`model=${loop.model} ` +
`harvest=${loop.harvestEnabled ? "on" : "off"} ` +
`branch=${branchBudget > 1 ? branchBudget : "off"} ` +
`stream=${loop.stream ? "on" : "off"}`,
};
}
case "model": {
const id = args[0];
if (!id) return { info: "usage: /model <id> (try deepseek-chat or deepseek-reasoner)" };
loop.configure({ model: id });
return { info: `model → ${id}` };
}
case "harvest": {
const arg = (args[0] ?? "").toLowerCase();
const on = arg === "" ? !loop.harvestEnabled : arg === "on" || arg === "true" || arg === "1";
loop.configure({ harvest: on });
return { info: `harvest → ${loop.harvestEnabled ? "on" : "off"}` };
}
case "preset": {
const name = (args[0] ?? "").toLowerCase();
if (name === "fast" || name === "default") {
loop.configure({ model: "deepseek-chat", harvest: false, branch: 1 });
return { info: "preset → fast (deepseek-chat, no harvest, no branch)" };
}
if (name === "smart") {
loop.configure({ model: "deepseek-reasoner", harvest: true, branch: 1 });
return { info: "preset → smart (reasoner + harvest, ~10x cost vs fast)" };
}
if (name === "max" || name === "best") {
loop.configure({ model: "deepseek-reasoner", harvest: true, branch: 3 });
return {
info: "preset → max (reasoner + harvest + branch3, ~30x cost vs fast, slowest)",
};
}
return { info: "usage: /preset <fast|smart|max>" };
}
case "branch": {
const raw = (args[0] ?? "").toLowerCase();
if (raw === "" || raw === "off" || raw === "0" || raw === "1") {
loop.configure({ branch: 1 });
return { info: "branch → off" };
}
const n = Number.parseInt(raw, 10);
if (!Number.isFinite(n) || n < 2) {
return { info: "usage: /branch <N> (N>=2, or 'off')" };
}
if (n > 8) {
return { info: "branch budget capped at 8 to prevent runaway cost" };
}
loop.configure({ branch: n });
return { info: `branch → ${n} (harvest auto-enabled; streaming disabled)` };
}
default:
return { unknown: true, info: `unknown command: /${cmd} (try /help)` };
}
}
// Slash-command barrel. Public surface is stable across the slash/
// split — App.tsx, tests, and sibling components continue to import
// { handleSlash, parseSlash, suggestSlashCommands, SLASH_COMMANDS, ... }
// from "./slash.js". Everything below is re-exported from the per-topic
// modules under ./slash/.
export {
SLASH_COMMANDS,
detectSlashArgContext,
parseSlash,
suggestSlashCommands,
} from "./slash/commands.js";
export { handleSlash } from "./slash/dispatch.js";
export type { SlashHandler } from "./slash/dispatch.js";
export type {
McpServerSummary,
SlashArgContext,
SlashCommandSpec,
SlashContext,
SlashResult,
} from "./slash/types.js";
+219
View File
@@ -0,0 +1,219 @@
import type { SlashArgContext, SlashCommandSpec } from "./types.js";
export const SLASH_COMMANDS: readonly SlashCommandSpec[] = [
{ cmd: "help", summary: "show the full command reference" },
{ cmd: "status", summary: "current model, flags, context, session" },
{
cmd: "preset",
argsHint: "<fast|smart|max>",
summary: "one-tap model + harvest + branch bundle",
argCompleter: ["fast", "smart", "max"],
},
{
cmd: "model",
argsHint: "<id>",
summary: "switch DeepSeek model id",
argCompleter: "models",
},
{ cmd: "models", summary: "list available models fetched from DeepSeek /models" },
{
cmd: "harvest",
argsHint: "[on|off]",
summary: "toggle Pillar-2 plan-state extraction",
argCompleter: ["on", "off"],
},
{
cmd: "branch",
argsHint: "<N|off>",
summary: "run N parallel samples per turn (N>=2)",
argCompleter: ["off", "2", "3", "4", "5"],
},
{
cmd: "effort",
argsHint: "<high|max>",
summary: "reasoning_effort cap — max is default (agent-class), high is cheaper/faster",
argCompleter: ["max", "high"],
},
{
cmd: "pro",
argsHint: "[off]",
summary: "arm v4-pro for the NEXT turn only (one-shot · auto-disarms after turn)",
argCompleter: ["off"],
},
{ cmd: "mcp", summary: "list MCP servers + tools attached to this session" },
{
cmd: "resource",
argsHint: "[uri]",
summary: "browse + read MCP resources (no arg → list URIs; <uri> → fetch contents)",
argCompleter: "mcp-resources",
},
{
cmd: "prompt",
argsHint: "[name]",
summary: "browse + fetch MCP prompts (no arg → list names; <name> → render prompt)",
argCompleter: "mcp-prompts",
},
{ cmd: "tool", argsHint: "[N]", summary: "dump full output of the Nth tool call (1=latest)" },
{
cmd: "memory",
argsHint: "[list|show <name>|forget <name>|clear <scope> confirm]",
summary: "show / manage pinned memory (REASONIX.md + ~/.reasonix/memory)",
},
{
cmd: "skill",
argsHint: "[list|show <name>|<name> [args]]",
summary: "list / run user skills (<project>/.reasonix/skills + ~/.reasonix/skills)",
},
{
cmd: "hooks",
argsHint: "[reload]",
summary: "list active hooks (settings.json under .reasonix/) · reload re-reads from disk",
},
{
cmd: "update",
summary: "show current vs latest version + the shell command to upgrade",
},
{
cmd: "stats",
summary:
"cross-session cost dashboard (today / week / month / all-time · cache hit · vs Claude)",
},
{ cmd: "think", summary: "dump the last turn's full R1 reasoning (reasoner only)" },
{
cmd: "context",
summary: "break down where context tokens are going: system / tools / per-turn log",
},
{ cmd: "retry", summary: "truncate & resend your last message (fresh sample)" },
{
cmd: "compact",
argsHint: "[tokens]",
summary:
"shrink oversized tool results AND tool-call args (edit_file search/replace) in the log; cap in tokens, default 4000",
},
{ cmd: "keys", summary: "show all keyboard shortcuts and prompt prefixes" },
{ cmd: "plans", summary: "list this session's active + archived plans, newest first" },
{
cmd: "replay",
summary: "load an archived plan as a read-only Time Travel snapshot (default: newest)",
argsHint: "[N]",
},
{ cmd: "sessions", summary: "list saved sessions (current marked with ▸)" },
{ cmd: "forget", summary: "delete the current session from disk" },
{ cmd: "setup", summary: "reminds you to exit and run `reasonix setup`" },
{ cmd: "clear", summary: "clear visible scrollback only (log/context kept)" },
{ cmd: "new", summary: "start a fresh conversation (clear context + scrollback)" },
{ cmd: "exit", summary: "quit the TUI" },
// Code-mode only
{ cmd: "apply", summary: "commit pending edit blocks to disk", contextual: "code" },
{ cmd: "discard", summary: "drop pending edit blocks without writing", contextual: "code" },
{ cmd: "undo", summary: "roll back the last applied edit batch", contextual: "code" },
{
cmd: "history",
summary: "list every edit batch this session (ids for /show, undone markers)",
contextual: "code",
},
{
cmd: "show",
argsHint: "[id]",
summary: "dump a stored edit diff (omit id for newest non-undone)",
contextual: "code",
},
{
cmd: "commit",
argsHint: '"msg"',
summary: "git add -A && git commit -m ...",
contextual: "code",
},
{
cmd: "plan",
argsHint: "[on|off]",
summary: "toggle read-only plan mode (writes bounced until submit_plan + approval)",
contextual: "code",
argCompleter: ["on", "off"],
},
{
cmd: "apply-plan",
summary: "force-approve a pending / in-text plan (fallback if picker was missed)",
contextual: "code",
},
{
cmd: "mode",
argsHint: "[review|auto]",
summary: "edit-gate: review (queue for /apply) or auto (apply+undo banner). Shift+Tab cycles.",
contextual: "code",
argCompleter: ["review", "auto"],
},
{ cmd: "jobs", summary: "list background jobs started by run_background", contextual: "code" },
{
cmd: "kill",
argsHint: "<id>",
summary: "stop a background job by id (SIGTERM → SIGKILL after grace)",
contextual: "code",
},
{
cmd: "logs",
argsHint: "<id> [lines]",
summary: "tail a background job's output (default last 80 lines)",
contextual: "code",
},
];
/**
* Filter the registry by a prefix string (without the leading `/`).
* Empty prefix returns the full non-contextual list (plus code-mode
* entries when `codeMode` is true). Case-insensitive.
*/
export function suggestSlashCommands(prefix: string, codeMode = false): SlashCommandSpec[] {
const p = prefix.toLowerCase();
return SLASH_COMMANDS.filter((c) => {
if (c.contextual === "code" && !codeMode) return false;
return c.cmd.startsWith(p);
});
}
/**
* Classify the prompt buffer for argument completion. Returns `null`
* when the buffer isn't in a slash-with-args state.
*
* Firing shape: input must start with `/<cmd> ` (space after a known
* command). The character right after the space through end-of-buffer
* is the "arg tail"; if the tail has NO internal whitespace the
* picker is live (tail is the partial). If the tail has whitespace,
* the user has moved past the first argument position and we surface
* the usage hint only.
*/
export function detectSlashArgContext(input: string, codeMode = false): SlashArgContext | null {
// `/cmd <rest>` — one space, rest captured up to end-of-buffer.
const m = /^\/(\S+) ([\s\S]*)$/.exec(input);
if (!m) return null;
const cmdName = m[1]!.toLowerCase();
const tail = m[2] ?? "";
const spec = SLASH_COMMANDS.find(
(s) => s.cmd === cmdName && (s.contextual !== "code" || codeMode),
);
if (!spec) return null;
const hasInternalSpace = /\s/.test(tail);
const partialOffset = input.length - tail.length;
if (hasInternalSpace) {
// Past the first arg position (typing the second arg for e.g.
// `/edit <file> <instruction>`, or mid-sentence for free-form).
return { spec, partial: tail, partialOffset, kind: "hint" };
}
// No internal whitespace — we're still typing the first arg. Picker
// is live if the spec declares a completer; otherwise show a hint
// ("what goes here?") since the user's guessing.
return {
spec,
partial: tail,
partialOffset,
kind: spec.argCompleter ? "picker" : "hint",
};
}
export function parseSlash(text: string): { cmd: string; args: string[] } | null {
if (!text.startsWith("/")) return null;
const parts = text.slice(1).trim().split(/\s+/);
const cmd = parts[0]?.toLowerCase() ?? "";
if (!cmd) return null;
return { cmd, args: parts.slice(1) };
}
+54
View File
@@ -0,0 +1,54 @@
import type { CacheFirstLoop } from "../../../loop.js";
import { handlers as adminHandlers } from "./handlers/admin.js";
import { handlers as basicHandlers } from "./handlers/basic.js";
import { handlers as editsHandlers } from "./handlers/edits.js";
import { handlers as jobsHandlers } from "./handlers/jobs.js";
import { handlers as mcpHandlers } from "./handlers/mcp.js";
import { handlers as memoryHandlers } from "./handlers/memory.js";
import { handlers as modelHandlers } from "./handlers/model.js";
import { handlers as observabilityHandlers } from "./handlers/observability.js";
import { handlers as plansHandlers } from "./handlers/plans.js";
import { handlers as sessionsHandlers } from "./handlers/sessions.js";
import { handlers as skillHandlers } from "./handlers/skill.js";
import type { SlashContext, SlashResult } from "./types.js";
/**
* A slash handler receives the command's args + the loop + shared
* runtime context, and returns a synchronous SlashResult. Async work
* (balance fetches, stop_job) fires-and-forgets via `ctx.postInfo`
* instead — keeps the TUI input non-blocking.
*/
export type SlashHandler = (args: string[], loop: CacheFirstLoop, ctx: SlashContext) => SlashResult;
/**
* Flat map of cmd → handler. Composed from per-topic modules so each
* feature's logic stays local; aliases (e.g. `exit` / `quit`) are just
* extra keys in the per-module handlers bag pointing at the same fn.
*
* Ordering of the spread matters only for duplicate keys; there are
* none. Keep alphabetical for diff sanity when adding modules.
*/
const HANDLERS: Record<string, SlashHandler> = {
...adminHandlers,
...basicHandlers,
...editsHandlers,
...jobsHandlers,
...mcpHandlers,
...memoryHandlers,
...modelHandlers,
...observabilityHandlers,
...plansHandlers,
...sessionsHandlers,
...skillHandlers,
};
export function handleSlash(
cmd: string,
args: string[],
loop: CacheFirstLoop,
ctx: SlashContext = {},
): SlashResult {
const h = HANDLERS[cmd];
if (h) return h(args, loop, ctx);
return { unknown: true, info: `unknown command: /${cmd} (try /help)` };
}
+158
View File
@@ -0,0 +1,158 @@
import {
HOOK_EVENTS,
type HookEvent,
type ResolvedHook,
globalSettingsPath,
projectSettingsPath,
} from "../../../../hooks.js";
import { aggregateUsage, defaultUsageLogPath, readUsageLog } from "../../../../usage.js";
import { VERSION, compareVersions, isNpxInstall } from "../../../../version.js";
import { renderDashboard } from "../../../commands/stats.js";
import type { SlashHandler } from "../dispatch.js";
const hooks: SlashHandler = (args, loop, ctx) => {
const sub = (args[0] ?? "").toLowerCase();
if (sub === "reload") {
if (!ctx.reloadHooks) {
return {
info: "/hooks reload is not available in this context (no reload callback wired).",
};
}
const count = ctx.reloadHooks();
return { info: `▸ reloaded hooks · ${count} active` };
}
if (sub !== "" && sub !== "list" && sub !== "ls") {
return {
info: "usage: /hooks list active hooks\n /hooks reload re-read settings.json files",
};
}
const all = loop.hooks;
const projPath = ctx.codeRoot ? projectSettingsPath(ctx.codeRoot) : undefined;
const globPath = globalSettingsPath();
if (all.length === 0) {
const lines = [
"no hooks configured.",
"",
"drop a settings.json with a `hooks` key into either of:",
ctx.codeRoot
? ` · ${projPath} (project)`
: " · <project>/.reasonix/settings.json (project)",
` · ${globPath} (global)`,
"",
"events: PreToolUse, PostToolUse, UserPromptSubmit, Stop",
"exit 0 = pass · exit 2 = block (Pre*) · other = warn",
];
return { info: lines.join("\n") };
}
const grouped = new Map<HookEvent, ResolvedHook[]>();
for (const event of HOOK_EVENTS) grouped.set(event, []);
for (const h of all) grouped.get(h.event)?.push(h);
const lines: string[] = [`▸ ${all.length} hook(s) loaded`];
for (const event of HOOK_EVENTS) {
const list = grouped.get(event) ?? [];
if (list.length === 0) continue;
lines.push("", `${event}:`);
for (const h of list) {
const match = h.match && h.match !== "*" ? ` match=${h.match}` : "";
const desc = h.description ? ` — ${h.description}` : "";
lines.push(` [${h.scope}]${match} ${h.command}${desc}`);
}
}
lines.push("", `sources: project=${projPath ?? "(none — chat mode)"} · global=${globPath}`);
return { info: lines.join("\n") };
};
/**
* `/update` — inside the TUI we deliberately do NOT spawn `npm install`.
* stdio:inherit into a running Ink renderer corrupts the display, and
* the process being upgraded is the same process that's still reading
* its own binaries (messy on Windows). Instead we surface what we
* already know from the App's background registry check and print the
* exact shell command the user should run after exiting.
*
* The `latestVersion` ctx field is populated by App.tsx's mount-time
* `getLatestVersion()` effect. When it's `null` we report the check
* as pending/offline — still a useful output (current version + how
* to force a fresh check from another terminal).
*/
const update: SlashHandler = (_args, _loop, ctx) => {
const latest = ctx.latestVersion ?? null;
const lines: string[] = [`current: reasonix ${VERSION}`];
if (latest === null) {
// Kick off a fresh fetch so a follow-up /update a few seconds
// later has a real answer instead of the same pending message.
ctx.refreshLatestVersion?.();
lines.push(
"latest: (not yet resolved — background check in flight or offline)",
"",
"triggered a fresh registry fetch — retry `/update` in a few seconds,",
"or run `reasonix update` in another terminal to force it synchronously.",
);
return { info: lines.join("\n") };
}
lines.push(`latest: reasonix ${latest}`);
const diff = compareVersions(VERSION, latest);
if (diff >= 0) {
lines.push("", "you're on the latest. nothing to do.");
return { info: lines.join("\n") };
}
if (isNpxInstall()) {
lines.push(
"",
"you're running via npx — the next `npx reasonix ...` launch will auto-fetch.",
"to force a refresh sooner: `npm cache clean --force`.",
);
} else {
lines.push(
"",
"to upgrade, exit this session and run:",
" reasonix update (interactive, dry-run supported via --dry-run)",
" npm install -g reasonix@latest (direct)",
"",
"in-session install is deliberately disabled — the npm spawn would",
"corrupt this TUI's rendering and Windows can lock the running binary.",
);
}
return { info: lines.join("\n") };
};
/**
* `/stats` — dashboard view of `~/.reasonix/usage.jsonl`, the same
* roll-up `reasonix stats` (no arg) prints at the shell. Synchronous
* disk read; cheap enough that we don't bother caching between slash
* invocations.
*
* No transcript-path variant in-TUI: the per-file summary is scripty
* and rarely wanted mid-session. If someone needs it they have the
* CLI form (`reasonix stats <path>`).
*/
const stats: SlashHandler = () => {
const path = defaultUsageLogPath();
const records = readUsageLog(path);
if (records.length === 0) {
return {
info: [
"no usage data yet.",
"",
` ${path}`,
"",
"every turn you run here appends one record — this session's turns",
"will show up in the dashboard once you send a message.",
].join("\n"),
};
}
const agg = aggregateUsage(records);
return { info: renderDashboard(agg, path) };
};
export const handlers: Record<string, SlashHandler> = {
hook: hooks,
hooks,
update,
stats,
};
+160
View File
@@ -0,0 +1,160 @@
import type { SlashHandler } from "../dispatch.js";
const exit: SlashHandler = () => ({ exit: true });
const clear: SlashHandler = () => ({
clear: true,
info: "▸ terminal cleared (viewport + scrollback). Context (message log) is intact — next turn still sees everything. Use /new to start fresh, or /forget to delete the session entirely.",
});
const resetLog: SlashHandler = (_args, loop) => {
// Actually drop the in-memory log + rewrite the session file so the
// NEXT call has no prior context. Keeps session name, model, and
// other config — just the conversation is reset.
const { dropped } = loop.clearLog();
return {
clear: true,
info: `▸ new conversation — dropped ${dropped} message(s) from context. Same session, fresh slate.`,
};
};
const keys: SlashHandler = () => ({
info: [
"Keyboard & prompt shortcuts:",
"",
" Enter submit the current prompt",
" Shift+Enter / Ctrl+J insert a newline (multi-line prompt)",
" \\<Enter> bash-style line continuation",
" ← → ↑ ↓ move cursor / recall history at buffer boundary",
" PageUp / PageDown jump to top / bottom of the WHOLE buffer (handy after a big paste)",
" Ctrl+A / Ctrl+E jump to start / end of the CURRENT line",
" Ctrl+U clear the entire input buffer",
" Ctrl+W delete the word before the cursor",
" Backspace delete left; Delete delete under cursor",
" Esc abort the in-flight turn",
" y / n accept / reject pending edits (code mode)",
" Shift+Tab cycle edit gate: review ↔ AUTO (code mode, persists to config)",
" u undo the latest non-undone edit batch (session-wide, not just banner)",
"",
"Prompt prefixes:",
" /<name> slash command; Tab/Enter picks from the suggestion list",
" @<path> inline a file under [Referenced files] (code mode).",
" Trailing `@…` opens a file picker; ↑/↓ navigate, Tab/Enter pick.",
" !<cmd> run <cmd> as shell in the sandbox root; output goes into context",
" so the model sees it next turn. No allowlist gate.",
"",
"Pickers (slash + @-mention):",
" ↑ / ↓ navigate the suggestion list",
" Tab insert the highlighted item without submitting",
" Enter insert and (slash) run it, (@) keep editing",
"",
"MCP exploration:",
" /mcp servers + tool/resource/prompt counts",
" /resource [uri] browse & read resources exposed by your MCP servers",
" /prompt [name] browse & fetch prompts exposed by your MCP servers",
"",
"Useful slashes: /help · /context · /stats · /compact · /new · /exit",
].join("\n"),
});
const help: SlashHandler = () => ({
info: [
"Commands:",
" /help this message",
" /keys keyboard shortcuts + prompt prefixes (!, @, /)",
" /status show current settings",
" /preset <fast|smart|max> one-tap presets — see below",
" /model <id> deepseek-v4-flash or deepseek-v4-pro",
" /pro [off] arm v4-pro for NEXT turn only (one-shot, auto-disarms)",
" /harvest [on|off] Pillar 2: structured plan-state extraction (OPT-IN — costs extra)",
" /branch <N|off> run N parallel samples (N>=2) — MANUAL ONLY, N× cost",
" /effort <high|max> reasoning_effort cap (max=full thinking, high=cheaper/faster)",
" /mcp list MCP servers + tools attached to this session",
" /resource [uri] browse + read MCP resources (no arg → list URIs; <uri> → fetch)",
" /prompt [name] browse + fetch MCP prompts (no arg → list names; <name> → render)",
" /setup (exit + reconfigure) → run `reasonix setup`",
" /compact [tokens] shrink large tool results in history (default 4000 tokens/result)",
" /think dump the most recent turn's full R1 reasoning (reasoner only)",
" /tool [N] list tool calls (or dump full output of #N, 1=most recent)",
" /memory [sub] show pinned memory (REASONIX.md + ~/.reasonix/memory).",
" subs: list | show <name> | forget <name> | clear <scope> confirm",
" /skill [sub] list / run user skills (project/.reasonix/skills + ~/.reasonix/skills).",
" subs: list | show <name> | <name> [args] (injects skill body as user turn)",
" /retry truncate & resend your last message (fresh sample from the model)",
" /apply (code mode) commit the pending edit blocks to disk",
" /discard (code mode) drop pending edits without writing",
" /undo (code mode) roll back the latest non-undone edit batch",
" /history (code mode) list every edit batch this session",
" /show [id] (code mode) dump a stored edit diff (newest when id omitted)",
' /commit "msg" (code mode) git add -A && git commit -m "msg"',
" /plan [on|off] (code mode) toggle read-only plan mode; writes gated behind submit_plan + your approval",
" /apply-plan (code mode) force-approve pending/in-text plan (fallback)",
" /mode [review|auto] (code mode) edit-gate: queue edits for /apply or apply instantly (Shift+Tab cycles, u undoes within 5s)",
" /jobs (code mode) list background processes (run_background) — running and exited",
" /kill <id> (code mode) stop a background job by id (SIGTERM → SIGKILL)",
" /logs <id> [lines] (code mode) tail a background job's output (default 80 lines)",
" /sessions list saved sessions (current is marked with ▸)",
" /forget delete the current session from disk",
" /new start fresh: drop all context + clear scrollback",
" /clear clear displayed scrollback only (context kept — model still sees it)",
" /exit quit",
"",
"Shell shortcut:",
" !<cmd> run <cmd> in the sandbox root; output goes into",
" the conversation so the model sees it next turn.",
" No allowlist gate — user-typed = explicit consent.",
" Example: !git status !ls src/ !npm test",
"",
"File references (code mode):",
" @path/to/file inline file content under [Referenced files] on send.",
" Type `@` to open the picker (↑↓ navigate, Tab/Enter pick).",
"",
"Presets (branch + harvest are NEVER auto-enabled — opt-in only):",
" fast v4-flash · effort=high cheapest · quick Q&A, one-line edits",
" smart v4-flash · effort=max ← default · day-to-day coding",
" max v4-pro · effort=max ~12× fast · hard single-shots",
"",
"Sessions (auto-enabled by default, named 'default'):",
" reasonix chat --session <name> use a different named session",
" reasonix chat --no-session disable persistence for this run",
"",
"Known limitation:",
" Resizing the terminal mid-session may stack ghost header frames in",
" scrollback (Ink library's live-region clear doesn't account for line",
" re-wrapping at the new width). Scroll-up history is unaffected; the",
" artifact is purely visual and clears the next time you /clear.",
].join("\n"),
});
const setup: SlashHandler = () => ({
info:
"To reconfigure (preset, MCP servers, API key), exit this chat and run " +
"`reasonix setup`. Changes take effect on next launch.",
});
const retry: SlashHandler = (_args, loop) => {
const prev = loop.retryLastUser();
if (!prev) {
return {
info: "nothing to retry — no prior user message in this session's log.",
};
}
const preview = prev.length > 80 ? `${prev.slice(0, 80)}…` : prev;
return {
info: `▸ retrying: "${preview}"`,
resubmit: prev,
};
};
export const handlers: Record<string, SlashHandler> = {
exit,
quit: exit,
clear,
new: resetLog,
reset: resetLog,
keys,
help,
"?": help,
setup,
retry,
};
+142
View File
@@ -0,0 +1,142 @@
import type { EditMode } from "../../../../config.js";
import type { SlashHandler } from "../dispatch.js";
import { runGitCommit, stripOuterQuotes } from "../helpers.js";
const undo: SlashHandler = (args, _loop, ctx) => {
if (!ctx.codeUndo) {
return {
info: "/undo is only available inside `reasonix code` — chat mode doesn't apply edits.",
};
}
return { info: ctx.codeUndo(args) };
};
const history: SlashHandler = (_args, _loop, ctx) => {
if (!ctx.codeHistory) {
return { info: "/history is only available inside `reasonix code`." };
}
return { info: ctx.codeHistory() };
};
const show: SlashHandler = (args, _loop, ctx) => {
if (!ctx.codeShowEdit) {
return { info: "/show is only available inside `reasonix code`." };
}
return { info: ctx.codeShowEdit(args) };
};
const apply: SlashHandler = (_args, _loop, ctx) => {
if (!ctx.codeApply) {
return {
info: "/apply is only available inside `reasonix code` (nothing to apply here).",
};
}
return { info: ctx.codeApply() };
};
const discard: SlashHandler = (_args, _loop, ctx) => {
if (!ctx.codeDiscard) {
return {
info: "/discard is only available inside `reasonix code`.",
};
}
return { info: ctx.codeDiscard() };
};
const plan: SlashHandler = (args, _loop, ctx) => {
if (!ctx.setPlanMode) {
return {
info: "/plan is only available inside `reasonix code` — chat mode doesn't gate tool writes.",
};
}
const currentOn = Boolean(ctx.planMode);
const raw = (args[0] ?? "").toLowerCase();
let target: boolean;
if (raw === "on" || raw === "true" || raw === "1") target = true;
else if (raw === "off" || raw === "false" || raw === "0") target = false;
else target = !currentOn;
ctx.setPlanMode(target);
if (target) {
return {
info: "▸ plan mode ON — write tools are gated; the model MUST call `submit_plan` before anything executes. (The model can also call submit_plan on its own for big tasks even when plan mode is off — this toggle is the stronger, explicit constraint.) Type /plan off to leave.",
};
}
return {
info: "▸ plan mode OFF — write tools are live again. Model can still propose plans autonomously for large tasks.",
};
};
const applyPlan: SlashHandler = (_args, _loop, ctx) => {
if (!ctx.setPlanMode) {
return {
info: "/apply-plan is only available inside `reasonix code`.",
};
}
ctx.setPlanMode(false);
ctx.clearPendingPlan?.();
return {
info: "▸ plan approved — implementing",
resubmit:
"The plan above has been approved. Implement it now. You are out of plan mode — use edit_file / write_file / run_command as needed. Stick to the plan unless you discover a concrete reason to deviate; if you do, tell me and wait for a response before making that deviation.",
};
};
const mode: SlashHandler = (args, _loop, ctx) => {
if (!ctx.setEditMode) {
return {
info: "/mode is only available inside `reasonix code`.",
};
}
const raw = (args[0] ?? "").toLowerCase();
const current = ctx.editMode ?? "review";
let target: EditMode;
if (raw === "review") target = "review";
else if (raw === "auto") target = "auto";
else if (raw === "") {
// Bare /mode toggles, mirroring Shift+Tab. Users who just want to
// see current mode without flipping can read /status.
target = current === "auto" ? "review" : "auto";
} else {
return { info: "usage: /mode <review|auto> (Shift+Tab also cycles)" };
}
ctx.setEditMode(target);
return {
info:
target === "auto"
? "▸ edit mode: AUTO — edits apply immediately; press u within 5s to undo, or /undo later"
: "▸ edit mode: review — edits queue for /apply (or y) / /discard (or n)",
};
};
const commit: SlashHandler = (args, _loop, ctx) => {
if (!ctx.codeRoot) {
return {
info: "/commit is only available inside `reasonix code` (needs a rooted git repo).",
};
}
// Reassemble the original argv. The parser lowercases cmd but leaves
// args alone, and the TUI splits on whitespace which mangles quoted
// messages — rejoin with spaces and strip a surrounding pair of
// double quotes if the user wrote them.
const raw = args.join(" ").trim();
const message = stripOuterQuotes(raw);
if (!message) {
return {
info: `usage: /commit "your commit message" — runs \`git add -A && git commit -m "…"\` in ${ctx.codeRoot}`,
};
}
return runGitCommit(ctx.codeRoot, message);
};
export const handlers: Record<string, SlashHandler> = {
undo,
history,
show,
apply,
discard,
plan,
"apply-plan": applyPlan,
applyplan: applyPlan,
mode,
commit,
};
+84
View File
@@ -0,0 +1,84 @@
import type { SlashHandler } from "../dispatch.js";
const jobs: SlashHandler = (_args, _loop, ctx) => {
if (!ctx.jobs) {
return { info: "/jobs is only available inside `reasonix code`." };
}
const rows = ctx.jobs.list();
if (rows.length === 0) {
return { info: "no background jobs yet — use run_background to start one" };
}
const lines = ["Background jobs:"];
for (const r of rows) {
const age = ((Date.now() - r.startedAt) / 1000).toFixed(1);
const state = r.running
? `running · pid ${r.pid ?? "?"}`
: r.exitCode !== null
? `exit ${r.exitCode}`
: r.spawnError
? "failed"
: "stopped";
lines.push(
` ${String(r.id).padStart(3)} ${state.padEnd(20)} ${age.padStart(6)}s ago $ ${r.command}`,
);
}
lines.push("");
lines.push("/kill <id> to stop one · /logs <id> [lines] to tail output");
return { info: lines.join("\n") };
};
const kill: SlashHandler = (args, _loop, ctx) => {
if (!ctx.jobs) return { info: "/kill is only available inside `reasonix code`." };
const id = Number.parseInt(args[0] ?? "", 10);
if (!Number.isFinite(id)) return { info: "usage: /kill <id> (see /jobs for ids)" };
const rec = ctx.jobs.list().find((r) => r.id === id);
if (!rec) return { info: `job ${id}: not found` };
if (!rec.running) return { info: `job ${id} already exited (${rec.exitCode ?? "?"})` };
// Fire-and-forget: the registry waits for grace + SIGKILL internally;
// returning immediately keeps the slash synchronous so the user's
// prompt doesn't lock up for 2s on every /kill. The postInfo
// callback lands a follow-up row in historical when the kill
// actually completes, so the user sees "job N stopped" without
// polling /jobs.
const jobsRef = ctx.jobs;
void (async () => {
const final = await jobsRef.stop(id);
if (!final) return;
const status = final.running
? "still alive after SIGKILL (!) — report this as a bug"
: final.exitCode !== null
? `exit ${final.exitCode}`
: "stopped";
ctx.postInfo?.(`▸ job ${id} ${status}`);
})();
return {
info: `▸ stopping job ${id} (tree kill: SIGTERM → SIGKILL after 2s grace; Windows: taskkill /T /F)`,
};
};
const logs: SlashHandler = (args, _loop, ctx) => {
if (!ctx.jobs) return { info: "/logs is only available inside `reasonix code`." };
const id = Number.parseInt(args[0] ?? "", 10);
if (!Number.isFinite(id)) {
return { info: "usage: /logs <id> [lines] (default last 80 lines)" };
}
const requested = Number.parseInt(args[1] ?? "", 10);
const tail = Number.isFinite(requested) && requested > 0 ? requested : 80;
const out = ctx.jobs.read(id, { tailLines: tail });
if (!out) return { info: `job ${id}: not found` };
const status = out.running
? `running · pid ${out.pid ?? "?"}`
: out.exitCode !== null
? `exited ${out.exitCode}`
: out.spawnError
? `failed (${out.spawnError})`
: "stopped";
const header = `[job ${id} · ${status}]\n$ ${out.command}`;
return { info: out.output ? `${header}\n${out.output}` : header };
};
export const handlers: Record<string, SlashHandler> = {
jobs,
kill,
logs,
};
+64
View File
@@ -0,0 +1,64 @@
import type { SlashHandler } from "../dispatch.js";
import { appendSection } from "../helpers.js";
const mcp: SlashHandler = (_args, loop, ctx) => {
const servers = ctx.mcpServers ?? [];
const specs = ctx.mcpSpecs ?? [];
const toolSpecs = loop.prefix.toolSpecs ?? [];
if (servers.length === 0 && specs.length === 0 && toolSpecs.length === 0) {
return {
info:
"no MCP servers attached. Run `reasonix setup` to pick some, " +
'or launch with --mcp "<spec>". `reasonix mcp list` shows the catalog.',
};
}
// Rich path — we have full inspection reports, so show each server
// with its tools / resources / prompts grouped together.
if (servers.length > 0) {
const lines: string[] = [];
let anyResources = false;
let anyPrompts = false;
for (const s of servers) {
const { report } = s;
const serverName = report.serverInfo.name || "(unknown)";
const serverVer = report.serverInfo.version ? ` v${report.serverInfo.version}` : "";
lines.push(`[${s.label}] ${serverName}${serverVer} — ${s.spec}`);
lines.push(` tools ${s.toolCount}`);
appendSection(lines, "resources", report.resources);
appendSection(lines, "prompts ", report.prompts);
if (report.resources.supported && report.resources.items.length > 0) anyResources = true;
if (report.prompts.supported && report.prompts.items.length > 0) anyPrompts = true;
lines.push("");
}
if (anyResources || anyPrompts) {
const hints: string[] = [];
if (anyResources) hints.push("`/resource` to browse+read");
if (anyPrompts) hints.push("`/prompt` to browse+fetch");
lines.push(hints.join(" · "));
} else {
lines.push(
"Chat mode consumes tools today; resources+prompts are surfaced here for awareness.",
);
}
lines.push(
"Full catalog: `reasonix mcp list` · deeper diagnosis: `reasonix mcp inspect <spec>`.",
);
return { info: lines.join("\n") };
}
// Fallback — older path when the TUI hasn't populated `mcpServers`.
const lines: string[] = [];
if (specs.length > 0) {
lines.push(`MCP servers (${specs.length}):`);
for (const spec of specs) lines.push(` · ${spec}`);
lines.push("");
}
if (toolSpecs.length > 0) {
lines.push(`Tools in registry (${toolSpecs.length}):`);
for (const t of toolSpecs) lines.push(` · ${t.function.name}`);
}
lines.push("");
lines.push("To change this set, exit and run `reasonix setup`.");
return { info: lines.join("\n") };
};
export const handlers: Record<string, SlashHandler> = { mcp };
+169
View File
@@ -0,0 +1,169 @@
import {
PROJECT_MEMORY_FILE,
memoryEnabled,
readProjectMemory,
} from "../../../../project-memory.js";
import { type MemoryScope, MemoryStore } from "../../../../user-memory.js";
import type { SlashHandler } from "../dispatch.js";
import { resolveMemoryTarget } from "../helpers.js";
/**
* `/memory` family. Bare `/memory` shows what's pinned (REASONIX.md +
* both MEMORY.md blocks). Subcommands manage the user-memory store:
* list — every memory file, both scopes
* show <name> — dump one file's body
* show <scope>/<name> — disambiguate when name exists in both scopes
* forget <name> — delete (same scope resolution as show)
* clear <scope> confirm — wipe a scope (typed literal "confirm" required)
*/
const memory: SlashHandler = (args, _loop, ctx) => {
if (!memoryEnabled()) {
return {
info: "memory is disabled (REASONIX_MEMORY=off in env). Unset the var to re-enable — no REASONIX.md or ~/.reasonix/memory content will be pinned in the meantime.",
};
}
if (!ctx.memoryRoot) {
return {
info: "no working directory on this session — `/memory` needs a root to resolve REASONIX.md from. (Running in a test harness?)",
};
}
// `codeRoot` is set only when running `reasonix code`. Chat mode has
// `memoryRoot` = cwd (for REASONIX.md), but we don't treat cwd as a
// sandbox — project-scope user memory requires a real code-mode root.
const store = new MemoryStore({ projectRoot: ctx.codeRoot });
const sub = (args[0] ?? "").toLowerCase();
if (sub === "list" || sub === "ls") {
const entries = store.list();
if (entries.length === 0) {
return {
info: "no user memories yet. The model can call `remember` to save one, or you can create files by hand in ~/.reasonix/memory/global/ or the per-project subdir.",
};
}
const lines = [`User memories (${entries.length}):`];
for (const e of entries) {
const tag = `${e.scope}/${e.type}`.padEnd(18);
const name = e.name.padEnd(28);
const desc = e.description.length > 70 ? `${e.description.slice(0, 69)}…` : e.description;
lines.push(` ${tag} ${name} ${desc}`);
}
lines.push("");
lines.push("View body: /memory show <name> Delete: /memory forget <name>");
return { info: lines.join("\n") };
}
if (sub === "show" || sub === "cat") {
const target = args[1];
if (!target) return { info: "usage: /memory show <name> or /memory show <scope>/<name>" };
const resolved = resolveMemoryTarget(store, target);
if (!resolved) return { info: `no memory found: ${target}` };
try {
const entry = store.read(resolved.scope, resolved.name);
return {
info: [
`▸ ${entry.scope}/${entry.name} (${entry.type}, created ${entry.createdAt || "?"})`,
entry.description ? ` ${entry.description}` : "",
"",
entry.body,
]
.filter((l) => l !== "")
.concat("")
.join("\n"),
};
} catch (err) {
return { info: `show failed: ${(err as Error).message}` };
}
}
if (sub === "forget" || sub === "rm" || sub === "delete") {
const target = args[1];
if (!target) return { info: "usage: /memory forget <name> or /memory forget <scope>/<name>" };
const resolved = resolveMemoryTarget(store, target);
if (!resolved) return { info: `no memory found: ${target}` };
try {
const ok = store.delete(resolved.scope, resolved.name);
return {
info: ok
? `▸ forgot ${resolved.scope}/${resolved.name}. Next /new or launch won't see it.`
: `could not forget ${resolved.scope}/${resolved.name} (already gone?)`,
};
} catch (err) {
return { info: `forget failed: ${(err as Error).message}` };
}
}
if (sub === "clear") {
const rawScope = (args[1] ?? "").toLowerCase();
if (rawScope !== "global" && rawScope !== "project") {
return { info: "usage: /memory clear <global|project> confirm" };
}
if ((args[2] ?? "").toLowerCase() !== "confirm") {
return {
info: `about to delete every memory in scope=${rawScope}. Re-run with the word 'confirm' to proceed: /memory clear ${rawScope} confirm`,
};
}
const scope = rawScope as MemoryScope;
const entries = store.list().filter((e) => e.scope === scope);
let deleted = 0;
for (const e of entries) {
try {
if (store.delete(scope, e.name)) deleted++;
} catch {
/* skip */
}
}
return { info: `▸ cleared scope=${scope} — deleted ${deleted} memory file(s).` };
}
// Bare `/memory` — show REASONIX.md + both MEMORY.md blocks.
const parts: string[] = [];
const projMem = readProjectMemory(ctx.memoryRoot);
if (projMem) {
const hdr = projMem.truncated
? `▸ ${PROJECT_MEMORY_FILE}: ${projMem.path} (${projMem.originalChars.toLocaleString()} chars, truncated)`
: `▸ ${PROJECT_MEMORY_FILE}: ${projMem.path} (${projMem.originalChars.toLocaleString()} chars)`;
parts.push(hdr, "", projMem.content);
}
const globalIdx = store.loadIndex("global");
if (globalIdx) {
parts.push(
"",
`▸ global memory (${globalIdx.originalChars.toLocaleString()} chars${globalIdx.truncated ? ", truncated" : ""})`,
"",
globalIdx.content,
);
}
const projectIdx = store.loadIndex("project");
if (projectIdx) {
parts.push(
"",
`▸ project memory (${projectIdx.originalChars.toLocaleString()} chars${projectIdx.truncated ? ", truncated" : ""})`,
"",
projectIdx.content,
);
}
if (parts.length === 0) {
return {
info: [
`no memory pinned in ${ctx.memoryRoot}.`,
"",
"Three layers are available:",
` 1. ${PROJECT_MEMORY_FILE} — committable team memory (in the repo).`,
" 2. ~/.reasonix/memory/global/ — your cross-project private memory.",
` 3. ~/.reasonix/memory/<project-hash>/ — this project's private memory.`,
"",
"Ask the model to `remember` something, or hand-edit files directly.",
"Changes take effect on next /new or launch — the system prompt is hashed once per session to keep the prefix cache warm.",
"",
"Subcommands: /memory list | /memory show <name> | /memory forget <name> | /memory clear <scope> confirm",
].join("\n"),
};
}
parts.push(
"",
"Changes take effect on next /new or launch. Subcommands: /memory list | show | forget | clear",
);
return { info: parts.join("\n") };
};
export const handlers: Record<string, SlashHandler> = { memory };
+187
View File
@@ -0,0 +1,187 @@
import { saveReasoningEffort } from "../../../../config.js";
import type { SlashHandler } from "../dispatch.js";
const model: SlashHandler = (args, loop, ctx) => {
const id = args[0];
const known = ctx.models ?? null;
if (!id) {
const hint =
known && known.length > 0
? known.join(" | ")
: "try deepseek-v4-flash or deepseek-v4-pro — run /models to fetch the live list";
return { info: `usage: /model <id> (${hint})` };
}
loop.configure({ model: id });
// Soft validation: if we have the live list and the id isn't in
// it, flag a warning but still switch — DeepSeek may have just
// released something we haven't indexed yet, and refusing would
// be worse than a bad API error on the next call.
if (known && known.length > 0 && !known.includes(id)) {
return {
info: `model → ${id} (⚠ not in the fetched catalog: ${known.join(", ")}. If this is wrong the next call will 400 — run /models to refresh.)`,
};
}
return { info: `model → ${id}` };
};
const models: SlashHandler = (_args, loop, ctx) => {
const list = ctx.models ?? null;
if (list === null) {
ctx.refreshModels?.();
return {
info: "fetching /models from DeepSeek… run /models again in a moment. If it stays empty, your API key may lack permission or the network is blocked.",
};
}
if (list.length === 0) {
return {
info: "DeepSeek /models returned an empty list. Try /models again, or check your account status at api-docs.deepseek.com.",
};
}
const current = loop.model;
const lines = list.map((id) => (id === current ? `▸ ${id} (current)` : ` ${id}`));
return {
info: [
`Available models (DeepSeek /models · ${list.length} total):`,
"",
...lines,
"",
"Switch with: /model <id>",
].join("\n"),
};
};
const harvest: SlashHandler = (args, loop) => {
const arg = (args[0] ?? "").toLowerCase();
const on = arg === "" ? !loop.harvestEnabled : arg === "on" || arg === "true" || arg === "1";
loop.configure({ harvest: on });
if (loop.harvestEnabled) {
return {
info: "harvest → on (Pillar-2 plan-state extraction · +1 cheap flash call per turn · opt-in only; no preset turns it on)",
};
}
return { info: "harvest → off" };
};
const preset: SlashHandler = (args, loop) => {
const name = (args[0] ?? "").toLowerCase();
// Persist the effort along with the preset change so a relaunch
// doesn't revert to the previously-saved /effort value.
const applyAndPersist = (effort: "high" | "max") => {
try {
saveReasoningEffort(effort);
} catch {
/* disk full / perms — runtime change still took effect */
}
};
if (name === "fast" || name === "default") {
loop.configure({
model: "deepseek-v4-flash",
reasoningEffort: "high",
harvest: false,
branch: 1,
});
applyAndPersist("high");
return { info: "preset → fast (v4-flash · effort=high · cheapest)" };
}
if (name === "smart") {
loop.configure({
model: "deepseek-v4-flash",
reasoningEffort: "max",
harvest: false,
branch: 1,
});
applyAndPersist("max");
return { info: "preset → smart (v4-flash · effort=max · default · ~1.5× fast)" };
}
if (name === "max" || name === "best") {
loop.configure({
model: "deepseek-v4-pro",
reasoningEffort: "max",
harvest: false,
branch: 1,
});
applyAndPersist("max");
return {
info: "preset → max (v4-pro · effort=max · ~12× fast · save for hard tasks, or use /pro for a single-turn bump)",
};
}
return { info: "usage: /preset <fast|smart|max>" };
};
const branch: SlashHandler = (args, loop) => {
const raw = (args[0] ?? "").toLowerCase();
if (raw === "" || raw === "off" || raw === "0" || raw === "1") {
loop.configure({ branch: 1 });
return { info: "branch → off" };
}
const n = Number.parseInt(raw, 10);
if (!Number.isFinite(n) || n < 2) {
return { info: "usage: /branch <N> (N>=2, or 'off')" };
}
if (n > 8) {
return { info: "branch budget capped at 8 to prevent runaway cost" };
}
loop.configure({ branch: n });
return {
info: `branch → ${n} (runs ${n} parallel samples per turn · ${n}× per-turn cost · streaming disabled · manual only, no preset enables branching)`,
};
};
const effort: SlashHandler = (args, loop) => {
const raw = (args[0] ?? "").toLowerCase();
if (raw === "") {
return {
info: `reasoning_effort → ${loop.reasoningEffort} (use /effort high for cheaper/faster, /effort max for the agent-class default · persisted across relaunches)`,
};
}
if (raw !== "high" && raw !== "max") {
return { info: "usage: /effort <high|max>" };
}
loop.configure({ reasoningEffort: raw });
// Persist so the next launch starts with this value instead of
// reverting to the constructor default.
try {
saveReasoningEffort(raw);
} catch {
/* disk full / perms — runtime change still took effect */
}
return { info: `reasoning_effort → ${raw} (persisted)` };
};
const pro: SlashHandler = (args, loop, ctx) => {
const arg = (args[0] ?? "").toLowerCase();
if (arg === "off" || arg === "cancel" || arg === "disarm") {
if (!loop.proArmed) {
return { info: "nothing armed — /pro with no args will arm pro for your next turn" };
}
if (ctx.disarmPro) ctx.disarmPro();
else loop.disarmPro();
return { info: "▸ /pro disarmed — next turn falls back to the current preset" };
}
if (arg && arg !== "on" && arg !== "arm") {
return {
info: "usage: /pro arm pro for the next turn (one-shot, auto-disarms after)\n /pro off cancel armed state before the next turn",
};
}
if (ctx.armPro) ctx.armPro();
else loop.armProForNextTurn();
return {
info: `▸ /pro armed — your NEXT message runs on ${ESCALATION_MODEL_ID} regardless of preset. Auto-disarms after one turn. Use /preset max for a persistent switch.`,
};
};
// Kept in sync with loop.ts ESCALATION_MODEL — hard-coding rather than
// importing it because loop.ts already exports enough surface, and this
// string is user-facing (description strings stay verbatim even if the
// internal constant renames).
const ESCALATION_MODEL_ID = "deepseek-v4-pro";
export const handlers: Record<string, SlashHandler> = {
model,
models,
harvest,
preset,
branch,
effort,
pro,
};
+192
View File
@@ -0,0 +1,192 @@
import { DEEPSEEK_CONTEXT_TOKENS, DEFAULT_CONTEXT_TOKENS } from "../../../../telemetry.js";
import { countTokens } from "../../../../tokenizer.js";
import type { SlashHandler } from "../dispatch.js";
import { compactNum, formatToolList } from "../helpers.js";
const think: SlashHandler = (_args, loop) => {
const raw = loop.scratch.reasoning;
if (!raw || !raw.trim()) {
return {
info:
"no reasoning cached. `/think` shows the full thinking-mode thought for the most recent " +
"turn — only thinking-mode models (deepseek-v4-flash / -v4-pro / -reasoner) produce it, " +
"and only once the turn completes.",
};
}
return { info: `↳ full thinking (${raw.length} chars):\n\n${raw.trim()}` };
};
const tool: SlashHandler = (args, _loop, ctx) => {
// EventLog renders tool results as a one-line summary for display.
// When the user wants to check what the model actually read (e.g.
// to verify it isn't hallucinating a file's contents), they need
// the full text. `/tool` is the escape hatch.
const history = ctx.toolHistory?.() ?? [];
if (history.length === 0) {
return {
info:
"no tool calls yet in this session. `/tool` lists them once the model has actually " +
"used a tool; `/tool N` dumps the full (untruncated) output of the Nth-most-recent.",
};
}
const raw = (args[0] ?? "").toLowerCase();
if (raw === "" || raw === "list" || raw === "ls") {
return { info: formatToolList(history) };
}
const n = Number.parseInt(raw, 10);
if (!Number.isFinite(n) || n < 1) {
return {
info: "usage: /tool [N] (no arg → list; N=1 → most recent result in full, N=2 → previous, …)",
};
}
if (n > history.length) {
return {
info: `only ${history.length} tool call(s) in history — asked for #${n}. Try /tool with no arg to see the list.`,
};
}
const entry = history[history.length - n];
if (!entry) {
return { info: `could not read tool call #${n}` };
}
return {
info: `↳ tool<${entry.toolName}> #${n} (${entry.text.length} chars):\n\n${entry.text}`,
};
};
const context: SlashHandler = (_args, loop) => {
// Measure each slice of the next request locally so the user can see
// *where* context is being spent — a much more useful number than
// the "last turn's total" the gauge shows. Tokenization is lazy so
// the first /context call carries the data-file load cost (~100ms);
// subsequent calls are pure compute.
const systemTokens = countTokens(loop.prefix.system);
const toolsTokens = countTokens(JSON.stringify(loop.prefix.toolSpecs));
const entries = loop.log.toMessages();
let userTokens = 0;
let assistantTokens = 0;
let toolResultTokens = 0;
let toolCallTokens = 0;
const toolBreakdown: Array<{ name: string; tokens: number; turn: number }> = [];
let logTurn = 0;
for (const e of entries) {
const content = typeof e.content === "string" ? e.content : "";
if (e.role === "user") {
userTokens += countTokens(content);
logTurn += 1;
} else if (e.role === "assistant") {
assistantTokens += countTokens(content);
if (Array.isArray(e.tool_calls) && e.tool_calls.length > 0) {
toolCallTokens += countTokens(JSON.stringify(e.tool_calls));
}
} else if (e.role === "tool") {
const n = countTokens(content);
toolResultTokens += n;
toolBreakdown.push({ name: e.name ?? "?", tokens: n, turn: logTurn });
}
}
const logTokens = userTokens + assistantTokens + toolResultTokens + toolCallTokens;
const total = systemTokens + toolsTokens + logTokens;
const ctxMax = DEEPSEEK_CONTEXT_TOKENS[loop.model] ?? DEFAULT_CONTEXT_TOKENS;
const pct = (n: number) => (total > 0 ? `${Math.round((n / total) * 100)}%`.padStart(4) : " 0%");
const row = (label: string, n: number, note = "") =>
` ${label.padEnd(20)}${compactNum(n).padStart(8)} tokens ${pct(n)}${note ? ` ${note}` : ""}`;
const lines = [
`Next-request estimate: ~${compactNum(total)} tokens of ${compactNum(ctxMax)} (${Math.round(
(total / ctxMax) * 100,
)}% of window)`,
"",
row("system prompt", systemTokens),
row("tool specs", toolsTokens, `(${loop.prefix.toolSpecs.length} tools)`),
row("log (all turns)", logTokens, `(${entries.length} messages)`),
` user ${compactNum(userTokens).padStart(8)} tokens`,
` assistant ${compactNum(assistantTokens).padStart(8)} tokens`,
` tool-call args ${compactNum(toolCallTokens).padStart(8)} tokens`,
` tool results ${compactNum(toolResultTokens).padStart(8)} tokens`,
];
// Top 5 heaviest tool results — usually where unexpected bloat
// lives (a big read_file, an unfiltered search_content).
if (toolBreakdown.length > 0) {
const top = [...toolBreakdown].sort((a, b) => b.tokens - a.tokens).slice(0, 5);
lines.push("");
lines.push(`Top tool results by cost (of ${toolBreakdown.length} total):`);
for (const t of top) {
lines.push(
` turn ${String(t.turn).padStart(3)} ${t.name.padEnd(22)} ${compactNum(t.tokens).padStart(8)} tokens`,
);
}
}
lines.push("");
lines.push(
"Count is a local estimate (DeepSeek V3 tokenizer, pure-TS port); server prompt_tokens may add ~3-6% for chat-template role markers.",
);
return { info: lines.join("\n") };
};
const status: SlashHandler = (_args, loop, ctx) => {
const branchBudget = loop.branchOptions.budget ?? 1;
const ctxMax = DEEPSEEK_CONTEXT_TOKENS[loop.model] ?? DEFAULT_CONTEXT_TOKENS;
const lastPromptTokens = loop.stats.summary().lastPromptTokens;
const ctxPct = ctxMax > 0 ? Math.round((lastPromptTokens / ctxMax) * 100) : 0;
const ctxLine =
lastPromptTokens > 0
? ` ctx ${compactNum(lastPromptTokens)}/${compactNum(ctxMax)} (${ctxPct}%)`
: " ctx no turns yet";
const pending = ctx.pendingEditCount ?? 0;
const sessionLine = loop.sessionName
? ` session "${loop.sessionName}" · ${loop.log.length} messages in log (resumed ${loop.resumedMessageCount})`
: " session (ephemeral — no persistence)";
const mcpCount = ctx.mcpSpecs?.length ?? 0;
const toolCount = loop.prefix.toolSpecs.length;
const mcpLine = ` mcp ${mcpCount} server(s), ${toolCount} tool(s) in registry`;
const pendingLine =
pending > 0 ? ` edits ${pending} pending (/apply to commit, /discard to drop)` : "";
const planLine = ctx.planMode ? " plan ON — writes gated (submit_plan + approval)" : "";
const modeLine =
ctx.editMode === "auto"
? " mode AUTO — edits apply immediately (u to undo within 5s · Shift+Tab to flip)"
: ctx.editMode === "review"
? " mode review — edits queue for /apply or y (Shift+Tab to flip)"
: "";
const lines = [
` model ${loop.model}`,
` flags harvest=${loop.harvestEnabled ? "on" : "off"} · branch=${branchBudget > 1 ? branchBudget : "off"} · stream=${loop.stream ? "on" : "off"} · effort=${loop.reasoningEffort}`,
ctxLine,
mcpLine,
sessionLine,
];
if (pendingLine) lines.push(pendingLine);
if (planLine) lines.push(planLine);
if (modeLine) lines.push(modeLine);
return { info: lines.join("\n") };
};
const compact: SlashHandler = (args, loop) => {
// Manual companion to the automatic 60%/80% auto-compact. Re-applies
// token-aware truncation with a tighter cap (default 4000 tokens per
// tool result) and rewrites the session file so the shrink persists.
// Useful when the ctx gauge in StatsPanel goes yellow/red mid-session
// and the user wants to keep chatting without /forget'ing everything.
const tight = Number.parseInt(args[0] ?? "", 10);
const cap = Number.isFinite(tight) && tight >= 100 ? tight : 4000;
const { healedCount, tokensSaved, charsSaved } = loop.compact(cap);
if (healedCount === 0) {
return {
info: `▸ nothing to compact — no tool result or tool-call args in history exceed ${cap.toLocaleString()} tokens.`,
};
}
return {
info: `▸ compacted ${healedCount} payload(s) to ${cap.toLocaleString()} tokens each (tool results + tool-call args), saved ${tokensSaved.toLocaleString()} tokens (${charsSaved.toLocaleString()} chars). Session file rewritten.`,
};
};
export const handlers: Record<string, SlashHandler> = {
think,
reasoning: think,
tool,
context,
status,
compact,
};
+111
View File
@@ -0,0 +1,111 @@
/**
* `/plans` — show this session's plan history. Both the live in-flight
* plan (if any) and the archive of completed `.done.json` files. Local
* to the current session by design — a plan lives with its project,
* and resuming one just means cd'ing back to that project directory.
*/
import { basename } from "node:path";
import { listPlanArchives, loadPlanState, relativeTime } from "../../../../code/plan-store.js";
import type { SlashHandler } from "../dispatch.js";
const plans: SlashHandler = (_args, loop) => {
const sessionName = loop.sessionName;
if (!sessionName) {
return {
info: "no session attached — `/plans` is per-session. Run `reasonix code` in a project to get a session.",
};
}
const lines: string[] = [];
// Active (in-flight) plan summary first — it's the one the user is
// most likely asking about.
const active = loadPlanState(sessionName);
if (active && active.steps.length > 0) {
const total = active.steps.length;
const done = active.completedStepIds.length;
const when = relativeTime(active.updatedAt);
const label = active.summary ? `: ${active.summary}` : "";
lines.push(
`▸ active plan${label} — ${done}/${total} step${total === 1 ? "" : "s"} done · last touched ${when}`,
);
} else {
lines.push("▸ active plan: (none)");
}
// Archives (completed plans) — newest first.
const archives = listPlanArchives(sessionName);
if (archives.length === 0) {
lines.push("");
lines.push(
"no archived plans yet for this session — they auto-archive when every step is done",
);
return { info: lines.join("\n") };
}
lines.push("");
lines.push(`Archived (${archives.length}):`);
for (const a of archives) {
const when = relativeTime(a.completedAt);
const total = a.steps.length;
const done = a.completedStepIds.length;
const completion = done >= total ? "complete" : `${done}/${total}`;
// Prefer the model-supplied summary as the label; fall back to
// the bare filename so legacy archives without a summary still
// show something identifying.
const label = a.summary ?? a.path.split(/[\\/]/).pop() ?? a.path;
lines.push(
` ✓ ${when.padEnd(10)} ${total} step${total === 1 ? "" : "s"} · ${completion} ${label}`,
);
}
return { info: lines.join("\n") };
};
/**
* `/replay [N]` — Time Travel. Loads archive #N (1-based, newest
* first; defaults to 1) and asks the TUI to render it as a read-only
* snapshot. Pure display — no execution, no plan state changes.
*
* The structured payload (steps + completedStepIds + body + summary)
* goes back through SlashResult.replayPlan so EventLog can apply the
* same step-list rendering used elsewhere, complete with risk gutter
* and ✓ status.
*/
const replay: SlashHandler = (args, loop) => {
const sessionName = loop.sessionName;
if (!sessionName) {
return {
info: "no session attached — `/replay` is per-session. Run `reasonix code` in a project to get a session.",
};
}
const archives = listPlanArchives(sessionName);
if (archives.length === 0) {
return {
info: "no archived plans yet for this session — `/replay` lights up once a plan completes (auto-archives when every step is done).",
};
}
const arg = args[0]?.trim() ?? "";
const index = arg ? Number.parseInt(arg, 10) : 1;
if (!Number.isFinite(index) || index < 1 || index > archives.length) {
return {
info: `invalid index — \`/replay\` takes 1..${archives.length} (newest = 1). Use \`/plans\` to see the list.`,
};
}
const a = archives[index - 1]!;
return {
replayPlan: {
summary: a.summary,
body: a.body,
steps: a.steps,
completedStepIds: a.completedStepIds,
completedAt: a.completedAt,
relativeTime: relativeTime(a.completedAt),
archiveBasename: basename(a.path),
index,
total: archives.length,
},
};
};
export const handlers: Record<string, SlashHandler> = {
plans,
replay,
};
+41
View File
@@ -0,0 +1,41 @@
import { deleteSession, listSessions } from "../../../../session.js";
import type { SlashHandler } from "../dispatch.js";
const sessions: SlashHandler = (_args, loop) => {
const items = listSessions();
if (items.length === 0) {
return {
info: "no saved sessions yet — chat normally and your messages will be saved automatically",
};
}
const lines = ["Saved sessions:"];
for (const s of items) {
const sizeKb = (s.size / 1024).toFixed(1);
const when = s.mtime.toISOString().replace("T", " ").slice(0, 16);
const marker = s.name === loop.sessionName ? "▸" : " ";
lines.push(
` ${marker} ${s.name.padEnd(22)} ${String(s.messageCount).padStart(5)} msgs ${sizeKb.padStart(7)} KB ${when}`,
);
}
lines.push("");
lines.push("Resume with: reasonix chat --session <name>");
return { info: lines.join("\n") };
};
const forget: SlashHandler = (_args, loop) => {
if (!loop.sessionName) {
return { info: "not in a session — nothing to forget" };
}
const name = loop.sessionName;
const ok = deleteSession(name);
return {
info: ok
? `▸ deleted session "${name}" — current screen still shows the conversation, but next launch starts fresh`
: `could not delete session "${name}" (already gone?)`,
};
};
export const handlers: Record<string, SlashHandler> = {
sessions,
forget,
};
+94
View File
@@ -0,0 +1,94 @@
import { SkillStore } from "../../../../skills.js";
import type { SlashHandler } from "../dispatch.js";
/**
* `/skill` family. Bare `/skill` (or `/skill list`) prints the
* discovered skills from `<projectRoot>/.reasonix/skills` (code mode
* only) + `~/.reasonix/skills`. `/skill show <name>` dumps one body
* inline for reading. `/skill <name> [args...]` injects the skill body
* as a user turn via `resubmit` — the same mechanism `/apply-plan`
* uses — so the next model turn runs with the skill's instructions
* fresh in the log.
*
* Project scope is only populated when the session has a `codeRoot`
* (set by `reasonix code`). In plain chat mode the store reads the
* global scope only, matching how user-memory behaves.
*/
const skill: SlashHandler = (args, _loop, ctx) => {
const store = new SkillStore({ projectRoot: ctx.codeRoot });
const sub = (args[0] ?? "").toLowerCase();
if (sub === "" || sub === "list" || sub === "ls") {
const skills = store.list();
if (skills.length === 0) {
const lines = ["no skills found. Reasonix reads skills from:"];
if (store.hasProjectScope()) {
lines.push(
" · <project>/.reasonix/skills/<name>/SKILL.md (or <name>.md) — project scope",
);
}
lines.push(" · ~/.reasonix/skills/<name>/SKILL.md (or <name>.md) — global scope");
if (!store.hasProjectScope()) {
lines.push(" (project scope is only active in `reasonix code`)");
}
lines.push(
"",
"Each file's frontmatter needs at least `name` and `description`.",
"Invoke a skill with `/skill <name> [args]` or by asking the model to call `run_skill`.",
);
return { info: lines.join("\n") };
}
const lines = [`User skills (${skills.length}):`];
for (const s of skills) {
const scope = `(${s.scope})`.padEnd(11);
const name = s.name.padEnd(24);
const desc = s.description.length > 70 ? `${s.description.slice(0, 69)}…` : s.description;
lines.push(` ${scope} ${name} ${desc}`);
}
lines.push("");
lines.push("View body: /skill show <name> Run: /skill <name> [args]");
return { info: lines.join("\n") };
}
if (sub === "show" || sub === "cat") {
const target = args[1];
if (!target) return { info: "usage: /skill show <name>" };
const found = store.read(target);
if (!found) return { info: `no skill found: ${target}` };
return {
info: [
`▸ ${found.name} (${found.scope})`,
found.description ? ` ${found.description}` : "",
` ${found.path}`,
"",
found.body,
]
.filter((l) => l !== "")
.join("\n"),
};
}
// Bare `/skill <name> [args...]` — inject the body as a user turn.
// The first arg is the skill name; remaining args are forwarded
// verbatim as the skill's "Arguments:" line.
const name = args[0] ?? "";
const found = store.read(name);
if (!found) {
return {
info: `no skill found: ${name} (try /skill list)`,
};
}
const extra = args.slice(1).join(" ").trim();
const header = `# Skill: ${found.name}${found.description ? `\n> ${found.description}` : ""}`;
const argsLine = extra ? `\n\nArguments: ${extra}` : "";
const payload = `${header}\n\n${found.body}${argsLine}`;
return {
info: `▸ running skill: ${found.name}${extra ? ` — ${extra}` : ""}`,
resubmit: payload,
};
};
export const handlers: Record<string, SlashHandler> = {
skill,
skills: skill,
};
+145
View File
@@ -0,0 +1,145 @@
import { spawnSync } from "node:child_process";
import type { MemoryScope, MemoryStore } from "../../../user-memory.js";
import type { SlashResult } from "./types.js";
/**
* Parse a `/memory show|forget` argument. Accepts bare `<name>` or
* `<scope>/<name>`. For bare names, tries project scope first (more
* specific, usually what the user means) then falls back to global.
*/
export function resolveMemoryTarget(
store: MemoryStore,
raw: string,
): { scope: MemoryScope; name: string } | null {
const slash = raw.indexOf("/");
if (slash > 0) {
const scopeRaw = raw.slice(0, slash).toLowerCase();
const name = raw.slice(slash + 1);
if (scopeRaw !== "global" && scopeRaw !== "project") return null;
const scope = scopeRaw as MemoryScope;
if (scope === "project" && !store.hasProjectScope()) return null;
return { scope, name };
}
for (const scope of ["project", "global"] as MemoryScope[]) {
if (scope === "project" && !store.hasProjectScope()) continue;
try {
store.read(scope, raw);
return { scope, name: raw };
} catch {
/* next scope */
}
}
return null;
}
/**
* Render a section (resources / prompts) of an MCP inspection into a
* compact "name count items" form, collapsing when unsupported.
* Names-only — descriptions and full metadata live in
* `reasonix mcp inspect`, which is purpose-built for the deep view.
*/
export function appendSection(
lines: string[],
label: string,
section:
| { supported: true; items: Array<{ name: string }> }
| { supported: false; reason: string }
| undefined,
): void {
if (!section || !section.supported) {
lines.push(
` ${label.trim()} ${section?.supported === false ? "(not supported)" : "(none)"}`,
);
return;
}
const names = section.items.map((i) => i.name);
if (names.length === 0) {
lines.push(` ${label.trim()} (none)`);
return;
}
const head = names.slice(0, 5).join(", ");
const more = names.length > 5 ? ` +${names.length - 5} more` : "";
lines.push(` ${label.trim()} ${names.length} [${head}${more}]`);
}
export function formatToolList(history: Array<{ toolName: string; text: string }>): string {
const total = history.length;
const header = `Tool calls in this session (${total}, most recent first):`;
// Show the 10 most recent. Older ones are rarely what the user
// wants — and the help footer tells them how to reach any entry
// by index if they do.
const shown = Math.min(total, 10);
const lines: string[] = [header];
for (let i = 0; i < shown; i++) {
const entry = history[total - 1 - i];
if (!entry) continue;
const idx = i + 1; // 1-based from most recent
const flat = entry.text.replace(/\s+/g, " ").trim();
const preview = flat.length > 80 ? `${flat.slice(0, 80)}…` : flat;
const name = entry.toolName.length > 24 ? `${entry.toolName.slice(0, 23)}…` : entry.toolName;
lines.push(
` #${String(idx).padStart(2)} ${name.padEnd(24)} ${String(entry.text.length).padStart(6)} chars ${preview}`,
);
}
if (total > shown) {
lines.push(` … (${total - shown} earlier, reach with /tool N)`);
}
lines.push("");
lines.push("View full output: /tool N (N=1 → most recent)");
return lines.join("\n");
}
/**
* Binary-K token formatter: 1234 → "1.2K", 131072 → "128K". Matches
* DeepSeek's doc ("128K context"). Every call site here is rendering
* token counts — if a future caller wants decimal-K for dollars or
* similar, add a separate formatter rather than reusing this one.
*/
export function compactNum(n: number): string {
if (n < 1024) return String(n);
const k = n / 1024;
return k >= 100 ? `${Math.round(k)}K` : `${k.toFixed(1)}K`;
}
export function stripOuterQuotes(s: string): string {
if (s.length >= 2 && s.startsWith('"') && s.endsWith('"')) {
return s.slice(1, -1);
}
return s;
}
/**
* Run `git add -A` then `git commit -m <message>` in `rootDir`. Returns
* a SlashResult with a human-scannable info line. We surface stderr on
* failure so the user sees exactly what git complained about (bad
* config, pre-commit hook rejection, nothing staged, etc.).
*/
export function runGitCommit(rootDir: string, message: string): SlashResult {
const add = spawnSync("git", ["add", "-A"], { cwd: rootDir, encoding: "utf8" });
if (add.error || add.status !== 0) {
return { info: `git add failed (${add.status ?? "?"}):\n${gitTail(add)}` };
}
const commit = spawnSync("git", ["commit", "-m", message], {
cwd: rootDir,
encoding: "utf8",
});
if (commit.error || commit.status !== 0) {
return { info: `git commit failed (${commit.status ?? "?"}):\n${gitTail(commit)}` };
}
const firstLine = (commit.stdout || "").split(/\r?\n/)[0] ?? "";
return { info: `▸ committed: ${message}${firstLine ? `\n ${firstLine}` : ""}` };
}
/**
* Safely extract whatever diagnostic text is available from a spawnSync
* result — on Windows or when cwd doesn't exist, `stderr`/`stdout` can
* be `undefined` and the caller has only `error.message` to go on.
*/
export function gitTail(res: ReturnType<typeof spawnSync>): string {
const stderr = (res.stderr as string | undefined) ?? "";
const stdout = (res.stdout as string | undefined) ?? "";
const body = stderr.trim() || stdout.trim();
if (body) return body;
if (res.error) return (res.error as Error).message;
return "(no output from git)";
}
+294
View File
@@ -0,0 +1,294 @@
import type { EditMode } from "../../../config.js";
import type { McpClient } from "../../../mcp/client.js";
import type { InspectionReport } from "../../../mcp/inspect.js";
import type { JobRegistry } from "../../../tools/jobs.js";
import type { PlanStep } from "../../../tools/plan.js";
export interface SlashResult {
/** Text to display back to the user as a system/info line. */
info?: string;
/** Exit the app. */
exit?: boolean;
/** Clear the visible history. */
clear?: boolean;
/** Unknown command — display usage hint. */
unknown?: boolean;
/**
* Re-submit this text as a user message after displaying `info`.
* Used by `/retry` — the slash command truncates the log, then
* asks the TUI to push the original text back through the normal
* submit flow so a fresh turn runs.
*/
resubmit?: string;
/**
* Render an archived plan as a read-only "Time Travel" block in
* scrollback. Populated by `/replay [N]`. The TUI mounts it as a
* `plan-replay` DisplayEvent so the same step-list / risk gutter
* styling gets reused. Strictly a display payload — no execution.
*/
replayPlan?: {
summary?: string;
body?: string;
steps: PlanStep[];
completedStepIds: string[];
completedAt: string;
relativeTime: string;
archiveBasename: string;
/** 1-based index in `/plans` listing — surfaced in the header. */
index: number;
/** Total archives at the time of the lookup; helps the user navigate. */
total: number;
};
}
/**
* Extra runtime context a slash handler may care about but that isn't
* already on the loop. Kept as an optional object so tests that only
* need loop-scoped commands can skip it, and callers only populate the
* slots that apply to their session.
*/
export interface SlashContext {
/**
* The exact `--mcp` / config-derived spec strings that were bridged
* into this session (one entry per server). Used by `/mcp`. Empty or
* omitted → no MCP servers attached.
*/
mcpSpecs?: string[];
/**
* Callback for `/undo` — provided by the TUI when it's running in
* code mode. Returns a human-readable report of what was restored.
* Absent outside code mode → `/undo` replies "not available here".
* Accepts slash args: `[id]`, `[id, path]`.
*/
codeUndo?: (args: readonly string[]) => string;
/**
* Callback for `/apply` — commits pending edit blocks to disk. Returns
* a report of what landed. Absent → `/apply` replies "nothing pending"
* or "not available outside code mode".
*/
codeApply?: () => string;
/**
* Callback for `/discard` — drops the pending edit blocks without
* touching disk.
*/
codeDiscard?: () => string;
/**
* Callback for `/history` — returns a human-readable list of every
* edit batch this session, newest last. Includes entry ids (for
* `/show`) and undone status.
*/
codeHistory?: () => string;
/**
* Callback for `/show [id] [path]` — with no args, shows a per-file
* summary of the newest non-undone entry. With id only, the entry's
* per-file summary. With id + path, the full diff of that single
* file in that entry.
*/
codeShowEdit?: (args: readonly string[]) => string;
/**
* Root directory passed by `reasonix code`. Enables `/commit`, which
* runs `git add -A && git commit` in this directory. Missing → `/commit`
* replies "only available in code mode".
*/
codeRoot?: string;
/**
* How many edit blocks are currently pending `/apply` or `/discard`.
* Surfaced by `/status`. TUI populates it live from its pending ref;
* omitted → treat as 0 (chat-only session).
*/
pendingEditCount?: number;
/**
* Callback returning every tool result seen this session in
* chronological order (oldest first). Powers `/tool [N]` for
* inspecting the full untruncated output that `EventLog` clips at
* 400 chars for display. Absent → `/tool` replies "not available".
*/
toolHistory?: () => Array<{ toolName: string; text: string }>;
/**
* Pre-captured inspection reports for each connected MCP server.
* Populated once at chat startup (chat.tsx) so `/mcp` can render
* tools + resources + prompts synchronously without needing async
* handler support.
*/
mcpServers?: McpServerSummary[];
/**
* Directory `/memory` should resolve `REASONIX.md` from. In code
* mode this is the rootDir the filesystem tools are pinned to; in
* plain chat this is `process.cwd()` at launch time. Absent → the
* TUI is running in some non-cwd context (tests) and `/memory`
* replies "root unknown" instead of silently reading a different dir.
*/
memoryRoot?: string;
/**
* Current plan-mode state, surfaced in `/status` and toggled by
* `/plan`. Present iff the session is a `reasonix code` run — chat
* mode doesn't have plan mode.
*/
planMode?: boolean;
/**
* Current edit-gate mode (`review` or `auto`). Surfaced in `/status`,
* toggled by `/mode`, also flipped by the Shift+Tab keybind in the
* TUI. Absent → not in `reasonix code`.
*/
editMode?: EditMode;
/**
* Set the edit-gate mode. Callback rather than raw state so App can
* also persist the choice to config and echo the change in historical.
*/
setEditMode?: (mode: EditMode) => void;
/**
* Background-process registry backing /jobs / /kill / /logs. Present
* iff the session is a `reasonix code` run. Slash handlers expect
* synchronous info strings, but stop_job is async — we return a
* "stopping, watch /jobs" info and let the registry do its thing.
*/
jobs?: JobRegistry;
/**
* Async-late append to the historical log. /kill uses this to
* surface "job N stopped" the moment stop() actually resolves,
* rather than leaving the user to poll /jobs themselves.
*/
postInfo?: (text: string) => void;
/**
* Callback the `/plan` slash uses to flip plan mode on/off. Also
* mirrors the state to the underlying ToolRegistry so dispatch
* enforcement follows. Absent → `/plan` replies "only available in
* code mode".
*/
setPlanMode?: (on: boolean) => void;
/**
* Callback that clears a pending-plan picker state. Called by
* `/apply-plan` so that when the user force-approves, the picker
* dismisses without also firing its own approval synthetic (the
* slash returns its own `resubmit` instead). Safe to call with no
* pending plan.
*/
clearPendingPlan?: () => void;
/**
* Re-load `~/.reasonix/settings.json` + `<project>/.reasonix/settings.json`
* and update both the App's hook state and the loop's mutable hook
* list. Returns the new hook count so the slash can echo a sane
* confirmation. Absent → `/hooks reload` replies "not available".
*/
reloadHooks?: () => number;
/**
* Latest published version if App's background registry check
* has completed, `null` otherwise (still in flight OR offline).
* Drives `/update` — the slash shows whatever the async check
* already resolved, so the command is fully synchronous.
*/
latestVersion?: string | null;
/**
* Fire-and-forget: kick off a fresh registry fetch. `/update`
* calls this whenever it encounters `latestVersion === null`
* so the user can rerun the slash a few seconds later and see
* a concrete answer. Absent → the slash just reports "pending"
* with no retry path.
*/
refreshLatestVersion?: () => void;
/**
* Model catalog fetched from DeepSeek's `/models` endpoint at App
* mount. `null` → still in flight or the call failed (auth / offline);
* `[]` → the API answered with zero entries. `/models` uses this to
* render the list, and `/model <id>` uses it for soft validation
* (warn-only — we still switch even on unknown ids since the list
* can lag a newly-released model).
*/
models?: string[] | null;
/**
* Fire-and-forget refresh for the models list. Lets `/models` retry
* after a flaky first fetch without needing async slash support.
*/
refreshModels?: () => void;
/**
* Arm pro for the next turn. Called by `/pro`. The TUI wires this
* to both `loop.armProForNextTurn()` and its React mirror state so
* the StatsPanel badge flips immediately. Absent → the handler
* calls `loop.armProForNextTurn()` directly and the badge updates
* on the next render tick (slightly laggy but still correct).
*/
armPro?: () => void;
/** Cancel a pending /pro arming. Mirrors `armPro` semantics. */
disarmPro?: () => void;
}
export interface McpServerSummary {
/** Short label shown in the `/mcp` output (server namespace or "anon"). */
label: string;
/** Original --mcp spec string. */
spec: string;
/** Count of tools bridged into the Reasonix registry from this server. */
toolCount: number;
/** Full inspection snapshot — used for the resources + prompts sections. */
report: InspectionReport;
/**
* Live MCP client, kept so `/resource` and `/prompt` can call
* `readResource` / `getPrompt` against this server. Omitted by
* callers that only build the summary for display; those slashes
* fall back to "not available" when the client is missing.
*/
client?: McpClient;
}
/**
* Slash command registry. Drives `/help`, the on-type suggestion
* popup (`SlashSuggestions`), and auto-complete. Kept as data rather
* than derived from the `handleSlash` switch so summaries can be
* user-facing rather than code comments.
*
* `contextual` gates commands that only make sense in certain modes:
* - `"code"` — only show when the TUI is running `reasonix code`
* - absent → always shown
*/
export interface SlashCommandSpec {
cmd: string;
summary: string;
contextual?: "code";
/** If the command takes args, hint text shown after the name. */
argsHint?: string;
/**
* How the first argument position should autocomplete. Shapes the
* picker that appears below the prompt once the user types `/<cmd>`
* + space:
* - `"models"` → DeepSeek model-id list fetched at startup.
* - `"mcp-resources"` → live URIs aggregated across connected MCP servers.
* - `"mcp-prompts"` → live prompt names aggregated across MCP servers.
* - `string[]` → small enum of literal values (e.g. `["on", "off"]`).
* - omitted → no picker; a persistent usage hint shows the
* argsHint + summary so the user knows what to type.
*
* File-path completion is deliberately NOT offered here. Users who
* want to reference a file in a prompt use `@path/to/file` (0.5.5);
* the `@` picker already surfaces files with mtime + recently-used
* ranking. Adding a second file-picker surface for slash commands
* would split the UX without adding leverage.
*/
argCompleter?: "models" | "mcp-resources" | "mcp-prompts" | readonly string[];
}
/**
* Shape describing what the prompt buffer is asking for AFTER the
* user has committed to a slash command (`/<cmd>`) and started
* typing its first argument. Consumed by the TUI to drive an
* argument-level picker.
*/
export interface SlashArgContext {
/** The command spec (looked up by name from SLASH_COMMANDS). */
spec: SlashCommandSpec;
/** The partial first-argument text, possibly empty. */
partial: string;
/**
* Buffer offset where `partial` begins. Used by the TUI to splice
* a picked completion back in at the right position.
*/
partialOffset: number;
/**
* Classification of what the caller should show:
* - `"picker"` → an interactive picker (file / enum / models). The
* caller uses `spec.argCompleter` to pick the data source and
* filters against `partial`.
* - `"hint"` → past the completable position (additional args or
* no completer declared). Caller shows a dim usage hint only.
*/
kind: "picker" | "hint";
}
+55
View File
@@ -0,0 +1,55 @@
import React, { type ReactNode, createContext, useContext, useEffect, useState } from "react";
/**
* Global heartbeat for every animated component (braille spinners,
* elapsed-seconds counters, cursor blink). A single setInterval feeds
* all of them instead of each component owning one. Consolidating the
* 5-6 independent timers that used to exist in App.tsx + EventLog.tsx +
* PromptInput.tsx into one source dramatically cuts the number of
* React re-renders per second on heavy turns and stops Ink from
* patching the terminal 30+ times/sec — the main amplifier of redraw
* artifacts on winpty/MINTTY-class Windows terminals.
*
* Resolution: `TICK_MS` (default 120). Components that want 500ms or
* 1s cadence just modulo the tick counter.
*/
export const TICK_MS = 120;
const TickContext = createContext(0);
export interface TickerProviderProps {
children: ReactNode;
/**
* When true, the provider skips the setInterval entirely — tick stays at
* 0, all consumers render once and never re-render from the timer. Used
* by PLAIN_UI mode so the cursor and any surviving spinners don't drive
* repaints on fragile Windows terminals.
*/
disabled?: boolean;
}
export function TickerProvider({ children, disabled }: TickerProviderProps) {
const [tick, setTick] = useState(0);
useEffect(() => {
if (disabled) return;
const id = setInterval(() => setTick((t) => t + 1), TICK_MS);
return () => clearInterval(id);
}, [disabled]);
return <TickContext.Provider value={tick}>{children}</TickContext.Provider>;
}
/** Current global tick. Re-renders the calling component every `TICK_MS`. */
export function useTick(): number {
return useContext(TickContext);
}
/**
* Seconds elapsed since the calling component mounted. Derived from
* the shared tick + a fresh Date.now() read, so no dedicated timer
* is needed.
*/
export function useElapsedSeconds(): number {
const [start] = useState(() => Date.now());
useTick(); // subscribe to the tick so we re-render
return Math.floor((Date.now() - start) / 1000);
}
+200
View File
@@ -0,0 +1,200 @@
/**
* One-line tool-result summarizer for the compact scrollback row.
*
* Old rendering: glyph + arrow + blank line + 400-char body block.
* Cost ~6–8 vertical lines per tool call. Long sessions drown in
* noise; the actually-interesting tool result (an edit diff, a
* checkpoint signal) gets buried.
*
* New rendering: glyph + tool name + arrow + a SINGLE-LINE summary
* tailored to the tool family. Full content stays in the tool history
* and can be expanded via `/tool N`. edit_file keeps its multi-line
* diff renderer (the diff IS the value).
*
* Pure function — lives outside EventLog.tsx so it's testable without
* Ink and can be reused if other surfaces (replay, transcript export)
* want the same one-liner.
*/
const MAX_SUMMARY_CHARS = 80;
const TRAILING_ELLIPSIS = "…";
export interface ToolSummary {
/** Single-line summary text. Empty string if the result was empty. */
summary: string;
/** True when the tool result represents a failure the renderer should color red. */
isError: boolean;
}
function clip(s: string, max: number): string {
if (s.length <= max) return s;
return s.slice(0, Math.max(1, max - TRAILING_ELLIPSIS.length)) + TRAILING_ELLIPSIS;
}
function firstNonEmptyLine(text: string): string {
for (const line of text.split(/\r?\n/)) {
const trimmed = line.trim();
if (trimmed) return trimmed;
}
return "";
}
/**
* Render a duration in milliseconds as a tight human label for the
* compact tool row. Picks a representation that fits in ~5 chars so
* the surrounding row stays readable on narrow terminals.
*
* < 100ms → "47ms"
* < 1000ms → "0.4s"
* < 60s → "12s" (or "1.2s" for sub-10-second times)
* >= 60s → "1m30s"
*/
export function formatDuration(ms: number): string {
if (!Number.isFinite(ms) || ms < 0) return "";
if (ms < 100) return `${Math.round(ms)}ms`;
if (ms < 1000) return `${(ms / 1000).toFixed(1)}s`;
if (ms < 10_000) return `${(ms / 1000).toFixed(1)}s`;
if (ms < 60_000) return `${Math.round(ms / 1000)}s`;
const totalSec = Math.round(ms / 1000);
const m = Math.floor(totalSec / 60);
const s = totalSec % 60;
return s === 0 ? `${m}m` : `${m}m${s}s`;
}
function formatBytes(n: number): string {
if (n < 1000) return `${n}B`;
if (n < 1_000_000) return `${(n / 1000).toFixed(1)}KB`;
return `${(n / 1_000_000).toFixed(1)}MB`;
}
function formatLineCount(text: string): string {
// Cheap line count — the +1 covers files without a trailing newline.
const lines = text.split(/\r?\n/).length;
return `${lines} line${lines === 1 ? "" : "s"}`;
}
/**
* Try to recognize a structured error envelope. Reasonix tools emit
* `{ "error": "..." }` JSON for failures and structured payloads
* (PlanProposedError carries `{error, plan, ...}`) for special
* signals. We surface the error name as the summary so the user
* sees what kind of failure happened at a glance.
*/
function summarizeStructured(content: string): ToolSummary | null {
const trimmed = content.trim();
if (!trimmed.startsWith("{")) return null;
try {
const parsed = JSON.parse(trimmed);
if (!parsed || typeof parsed !== "object") return null;
const obj = parsed as Record<string, unknown>;
// Plan / choice signals come through as errors carrying structured
// payloads — the App-level handlers extract the structured part.
// For the tool row here we just want the tag.
if (typeof obj.error === "string") {
const tag = obj.error.split(":", 1)[0]?.trim() ?? "error";
const detail = obj.error.slice(tag.length + 1).trim();
// The tag-only case (no colon body) — show the bare tag.
const summary = detail ? `${tag} — ${detail}` : tag;
// Plan / Choice errors are control-flow signals, not real errors.
const isControlSignal =
tag === "PlanProposedError" ||
tag === "PlanCheckpointError" ||
tag === "PlanRevisionProposedError" ||
tag === "ChoiceRequestedError" ||
tag === "NeedsConfirmationError";
return { summary: clip(summary, MAX_SUMMARY_CHARS), isError: !isControlSignal };
}
// step_completed payload (when used outside the error path, kept
// for forward-compat with non-throwing variants).
if (obj.kind === "step_completed" && typeof obj.stepId === "string") {
const result = typeof obj.result === "string" ? obj.result : "";
return {
summary: clip(`✓ ${obj.stepId}: ${result}`, MAX_SUMMARY_CHARS),
isError: false,
};
}
return null;
} catch {
return null;
}
}
/**
* Per-tool-name overrides for cases where a smarter summary is cheap
* to compute. Returning null means "fall through to the generic
* summary path."
*
* Suffix-match is on purpose: MCP-bridged tools come in prefixed
* (`filesystem_read_file`, `git_search_files`) and we want them to
* pick up the same specialized summary as the bare local name.
*/
function summarizeKnownTool(toolName: string, content: string): ToolSummary | null {
const hasSuffix = (s: string) => toolName === s || toolName.endsWith(`_${s}`);
if (hasSuffix("read_file")) {
const lines = formatLineCount(content);
const bytes = formatBytes(content.length);
const head = clip(
firstNonEmptyLine(content),
MAX_SUMMARY_CHARS - lines.length - bytes.length - 8,
);
return {
summary: head ? `${head} · ${lines} · ${bytes}` : `${lines} · ${bytes}`,
isError: false,
};
}
if (hasSuffix("list_directory") || hasSuffix("directory_tree")) {
const entries = content.split(/\r?\n/).filter((l) => l.trim()).length;
return { summary: `${entries} entr${entries === 1 ? "y" : "ies"}`, isError: false };
}
if (hasSuffix("search_files") || hasSuffix("search_content")) {
const matches = content.split(/\r?\n/).filter((l) => l.trim()).length;
if (matches === 0) return { summary: "no matches", isError: false };
const first = firstNonEmptyLine(content);
return {
summary: clip(`${matches} match${matches === 1 ? "" : "es"} · ${first}`, MAX_SUMMARY_CHARS),
isError: false,
};
}
if (hasSuffix("write_file")) {
const lines = formatLineCount(content);
const bytes = formatBytes(content.length);
return { summary: `wrote ${lines} · ${bytes}`, isError: false };
}
if (hasSuffix("run_command") || hasSuffix("run_background")) {
// Native shell tools prepend "exit 0:" / "exit N:" or the result
// already mentions exit code. Try to surface it.
const exitMatch = content.match(/exit (?:code )?(-?\d+)/i);
const first = firstNonEmptyLine(content);
if (exitMatch) {
const code = exitMatch[1];
const isError = code !== "0";
return {
summary: clip(`exit ${code} · ${first}`, MAX_SUMMARY_CHARS),
isError,
};
}
return { summary: clip(first || "(no output)", MAX_SUMMARY_CHARS), isError: false };
}
return null;
}
export function summarizeToolResult(toolName: string, content: string): ToolSummary {
const isExplicitError = content.startsWith("ERROR:");
if (isExplicitError) {
const stripped = content.slice("ERROR:".length).trim();
return { summary: clip(stripped || "(unknown error)", MAX_SUMMARY_CHARS), isError: true };
}
const structured = summarizeStructured(content);
if (structured) return structured;
const known = summarizeKnownTool(toolName, content);
if (known) return known;
// Generic: first line + size hint.
const first = firstNonEmptyLine(content);
if (!content.trim()) return { summary: "(empty)", isError: false };
if (content.length <= MAX_SUMMARY_CHARS) {
return { summary: clip(first, MAX_SUMMARY_CHARS), isError: false };
}
const sizeHint = formatBytes(content.length);
const head = clip(first, MAX_SUMMARY_CHARS - sizeHint.length - 3);
return { summary: `${head} · ${sizeHint}`, isError: false };
}
+218
View File
@@ -0,0 +1,218 @@
import { useCallback, useEffect, useMemo, useRef, useState } from "react";
import {
type FileWithStats,
detectAtPicker,
listFilesWithStatsSync,
rankPickerCandidates,
} from "../../at-mentions.js";
import {
type McpServerSummary,
type SlashArgContext,
type SlashCommandSpec,
detectSlashArgContext,
suggestSlashCommands,
} from "./slash.js";
export interface UseCompletionPickersParams {
input: string;
setInput: (v: string) => void;
codeMode: { rootDir: string } | undefined;
models: string[] | null;
mcpServers: McpServerSummary[] | undefined;
}
export interface UseCompletionPickersResult {
// ── slash-name picker ──
slashMatches: SlashCommandSpec[] | null;
slashSelected: number;
setSlashSelected: React.Dispatch<React.SetStateAction<number>>;
// ── @-mention picker ──
atPicker: ReturnType<typeof detectAtPicker>;
atMatches: readonly string[] | null;
atSelected: number;
setAtSelected: React.Dispatch<React.SetStateAction<number>>;
pickAtMention: (chosenPath: string) => void;
recordRecentFile: (path: string) => void;
// ── slash-arg picker ──
slashArgContext: SlashArgContext | null;
slashArgMatches: readonly string[] | null;
slashArgSelected: number;
setSlashArgSelected: React.Dispatch<React.SetStateAction<number>>;
pickSlashArg: (chosen: string) => void;
}
/**
* The three mutually-exclusive input-prefix pickers share enough
* structure (matches list + highlighted index + reset-on-shrink effect
* + commit-back-into-buffer callback) that they live together here.
* Priority in the parent useInput handler:
* atMatches > slashArgMatches > slashMatches > prompt history
* detection already disambiguates by construction — the slash-name
* picker fires only when the buffer has no space; the slash-arg picker
* only after a space; the @-picker only outside slash mode.
*/
export function useCompletionPickers({
input,
setInput,
codeMode,
models,
mcpServers,
}: UseCompletionPickersParams): UseCompletionPickersResult {
// ── slash-name picker ──
const [slashSelected, setSlashSelected] = useState(0);
const slashMatches = useMemo(() => {
if (!input.startsWith("/") || input.includes(" ")) return null;
return suggestSlashCommands(input.slice(1), !!codeMode);
}, [input, codeMode]);
useEffect(() => {
setSlashSelected((prev) => {
if (!slashMatches || slashMatches.length === 0) return 0;
if (prev >= slashMatches.length) return slashMatches.length - 1;
return prev;
});
}, [slashMatches]);
// ── @-mention picker ──
const [atSelected, setAtSelected] = useState(0);
// Walk the code root ONCE on mount, collecting mtime alongside path
// so the picker can surface recently-edited files first. Files
// created mid-session via tool edits won't appear until restart —
// rare, and the user can always type the full path.
const atFiles = useMemo<readonly FileWithStats[]>(() => {
if (!codeMode?.rootDir) return [];
try {
return listFilesWithStatsSync(codeMode.rootDir, { maxResults: 500 });
} catch {
return [];
}
}, [codeMode?.rootDir]);
// LRU of files touched by recent tool calls. Seeds the picker with
// "stuff I just looked at" at the top, so a user typing `@` in the
// same file they were just discussing gets it instantly.
const recentFilesRef = useRef<string[]>([]);
const recordRecentFile = useCallback((p: string) => {
const list = recentFilesRef.current;
const i = list.indexOf(p);
if (i >= 0) list.splice(i, 1);
list.unshift(p);
if (list.length > 20) list.length = 20;
}, []);
const atPicker = useMemo(() => {
if (!codeMode?.rootDir) return null;
// Slash prefix wins — avoids the picker confusingly surfacing on
// `/@wat`-style edge inputs.
if (slashMatches !== null) return null;
return detectAtPicker(input);
}, [codeMode?.rootDir, input, slashMatches]);
const atMatches = useMemo<readonly string[] | null>(() => {
if (!atPicker) return null;
return rankPickerCandidates(atFiles, atPicker.query, {
limit: 40,
recentlyUsed: recentFilesRef.current,
});
}, [atPicker, atFiles]);
useEffect(() => {
setAtSelected((prev) => {
if (!atMatches || atMatches.length === 0) return 0;
if (prev >= atMatches.length) return atMatches.length - 1;
return prev;
});
}, [atMatches]);
const pickAtMention = useCallback(
(chosenPath: string) => {
if (!atPicker) return;
const before = input.slice(0, atPicker.atOffset);
setInput(`${before}@${chosenPath} `);
},
[atPicker, input, setInput],
);
// ── slash-arg picker ──
const [slashArgSelected, setSlashArgSelected] = useState(0);
const slashArgContext = useMemo<SlashArgContext | null>(() => {
if (!input.startsWith("/")) return null;
if (slashMatches !== null) return null;
return detectSlashArgContext(input, !!codeMode);
}, [input, slashMatches, codeMode]);
const slashArgMatches = useMemo<readonly string[] | null>(() => {
if (!slashArgContext || slashArgContext.kind !== "picker") return null;
const completer = slashArgContext.spec.argCompleter;
const partial = slashArgContext.partial;
const needle = partial.toLowerCase();
// Once the partial is an EXACT match for a valid completion, hide
// the picker so Enter submits the command instead of re-picking
// the same value in an infinite loop. Case-insensitive — users
// may type `/preset FAST` and still mean the same thing.
if (Array.isArray(completer)) {
if (partial && completer.some((v) => v.toLowerCase() === needle)) return null;
if (!partial) return completer.slice();
return completer.filter((v) => v.toLowerCase().startsWith(needle));
}
if (completer === "models") {
const all = models ?? [];
if (partial && all.some((m) => m.toLowerCase() === needle)) return null;
if (!partial) return all.slice(0, 40);
return all.filter((m) => m.toLowerCase().includes(needle)).slice(0, 40);
}
if (completer === "mcp-resources") {
// Aggregate URIs across every server's cached inspection.
const uris: string[] = [];
const servers = mcpServers ?? [];
for (const s of servers) {
if (!s.report.resources.supported) continue;
for (const r of s.report.resources.items) uris.push(r.uri);
}
if (partial && uris.some((u) => u.toLowerCase() === needle)) return null;
if (!partial) return uris.slice(0, 40);
return uris.filter((u) => u.toLowerCase().includes(needle)).slice(0, 40);
}
if (completer === "mcp-prompts") {
const names: string[] = [];
const servers = mcpServers ?? [];
for (const s of servers) {
if (!s.report.prompts.supported) continue;
for (const p of s.report.prompts.items) names.push(p.name);
}
if (partial && names.some((n) => n.toLowerCase() === needle)) return null;
if (!partial) return names.slice(0, 40);
return names.filter((n) => n.toLowerCase().includes(needle)).slice(0, 40);
}
return null;
}, [slashArgContext, models, mcpServers]);
useEffect(() => {
setSlashArgSelected((prev) => {
if (!slashArgMatches || slashArgMatches.length === 0) return 0;
if (prev >= slashArgMatches.length) return slashArgMatches.length - 1;
return prev;
});
}, [slashArgMatches]);
const pickSlashArg = useCallback(
(chosen: string) => {
if (!slashArgContext) return;
const before = input.slice(0, slashArgContext.partialOffset);
// No trailing space — enum picks take no further args, so the
// user presses Enter once more to run the command.
setInput(`${before}${chosen}`);
},
[slashArgContext, input, setInput],
);
return {
slashMatches,
slashSelected,
setSlashSelected,
atPicker,
atMatches,
atSelected,
setAtSelected,
pickAtMention,
recordRecentFile,
slashArgContext,
slashArgMatches,
slashArgSelected,
setSlashArgSelected,
pickSlashArg,
};
}
+309
View File
@@ -0,0 +1,309 @@
import { useCallback, useRef, useState } from "react";
import { formatAllBlockDiffs } from "../../code/diff-preview.js";
import {
type ApplyResult,
type EditBlock,
type EditSnapshot,
restoreSnapshots,
} from "../../code/edit-blocks.js";
import {
type EditHistoryEntry,
entryStatus,
formatUndoRows,
isEntryFullyUndone,
} from "./edit-history.js";
export interface UndoBannerState {
results: ApplyResult[];
expiresAt: number;
}
export interface UseEditHistoryResult {
/** Post-auto-apply banner state — rendered at the bottom for 5s. */
undoBanner: UndoBannerState | null;
/**
* Append a batch of successfully-applied edits into the session's
* edit history. If the current turn already has an open entry,
* append into it (first-wins-per-path so `/undo` restores the
* pre-turn state, not an intermediate half-edit). Otherwise open a
* new entry.
*/
recordEdit: (
source: string,
blocks: readonly EditBlock[],
results: readonly ApplyResult[],
snaps: readonly EditSnapshot[],
) => void;
/**
* Show the post-auto-apply undo banner for 5 seconds. Overwrites any
* prior banner and replaces the auto-dismiss timer so multiple
* edits inside a single turn don't prematurely expire the window.
*/
armUndoBanner: (results: ApplyResult[]) => void;
/**
* `/undo` — revert applied edits.
* `/undo` → newest non-fully-undone entry, all its
* remaining (non-undone) files.
* `/undo <id>` → that specific entry's remaining files.
* `/undo <id> <path>` → just that one file in that entry.
* Works as long as the session is alive; no 5-second banner limit.
*/
codeUndo: (args?: readonly string[]) => string;
/**
* `/history` — list every edit batch this session. Each entry's id
* is the token for `/show <id>` and the target of per-batch undo.
*/
codeHistory: () => string;
/**
* `/show` — inspect a stored edit batch.
* `/show` → newest non-fully-undone entry, per-file summary.
* `/show <id>` → that entry's per-file summary.
* `/show <id> <path>` → full diff of one file in that entry.
*/
codeShowEdit: (args?: readonly string[]) => string;
/**
* Seal the in-progress entry so the next edit opens a fresh one.
* Called at handleSubmit start — prior turns stay intact for
* `/history` and `/undo` to walk through independently.
*/
sealCurrentEntry: () => void;
/**
* True when there's at least one history entry that isn't fully
* undone yet. Used by the `u` keybind and the bottom ModeStatusBar.
* Reads the ref fresh — callers must re-read each time.
*/
hasUndoable: () => boolean;
}
/**
* Session-scoped edit history and undo machinery for `reasonix code`.
* Keeps the history ref + snapshot bookkeeping out of App.tsx so the
* parent only sees a small API: append, banner, three slash handlers,
* a turn sealer, and an undoable probe.
*
* `codeMode` is optional because the hook is always mounted but its
* handlers turn into no-ops when code mode isn't active.
*/
export function useEditHistory(codeMode: { rootDir: string } | undefined): UseEditHistoryResult {
const editHistory = useRef<EditHistoryEntry[]>([]);
const nextHistoryId = useRef(1);
const currentTurnEntry = useRef<EditHistoryEntry | null>(null);
const [undoBanner, setUndoBanner] = useState<UndoBannerState | null>(null);
const undoTimeoutRef = useRef<ReturnType<typeof setTimeout> | null>(null);
const recordEdit = useCallback<UseEditHistoryResult["recordEdit"]>(
(source, blocks, results, snaps) => {
if (snaps.length === 0) return;
let entry = currentTurnEntry.current;
if (!entry) {
entry = {
id: nextHistoryId.current++,
at: Date.now(),
source,
blocks: [],
results: [],
snapshots: [],
undoneFiles: new Set<string>(),
};
currentTurnEntry.current = entry;
editHistory.current.push(entry);
}
entry.blocks.push(...blocks);
entry.results.push(...results);
const seen = new Set(entry.snapshots.map((s) => s.path));
for (const s of snaps) {
if (!seen.has(s.path)) entry.snapshots.push(s);
}
},
[],
);
const armUndoBanner = useCallback<UseEditHistoryResult["armUndoBanner"]>((results) => {
setUndoBanner({ results, expiresAt: Date.now() + 5000 });
if (undoTimeoutRef.current) clearTimeout(undoTimeoutRef.current);
undoTimeoutRef.current = setTimeout(() => {
setUndoBanner(null);
undoTimeoutRef.current = null;
}, 5000);
}, []);
const codeUndo = useCallback<UseEditHistoryResult["codeUndo"]>(
(args = []) => {
if (!codeMode) return "not in code mode";
const root = codeMode.rootDir;
const revert = (entry: EditHistoryEntry, paths: readonly string[]): string => {
const subset = entry.snapshots.filter((s) => paths.includes(s.path));
if (subset.length === 0) {
return `batch #${entry.id}: nothing to undo (already restored or path not in batch)`;
}
const results = restoreSnapshots(subset, root);
for (const s of subset) entry.undoneFiles.add(s.path);
if (currentTurnEntry.current === entry && isEntryFullyUndone(entry)) {
currentTurnEntry.current = null;
}
if (undoTimeoutRef.current) {
clearTimeout(undoTimeoutRef.current);
undoTimeoutRef.current = null;
}
setUndoBanner(null);
const when = new Date(entry.at).toISOString().replace("T", " ").slice(11, 19);
const scope = subset.length === 1 ? subset[0]!.path : `${subset.length} file(s)`;
const header = `▸ undo: reverted ${scope} from batch #${entry.id} (${when})`;
return [header, ...formatUndoRows(results)].join("\n");
};
const idArg = args[0];
const pathArg = args[1];
if (!idArg) {
for (let i = editHistory.current.length - 1; i >= 0; i--) {
const e = editHistory.current[i]!;
if (isEntryFullyUndone(e)) continue;
const remaining = e.snapshots.map((s) => s.path).filter((p) => !e.undoneFiles.has(p));
return revert(e, remaining);
}
return "nothing to undo — every batch in the session history is already undone";
}
const id = Number.parseInt(idArg, 10);
if (!Number.isFinite(id)) {
return "usage: /undo [id] [path] (omit id for newest; id from /history; path from /show <id>)";
}
const entry = editHistory.current.find((e) => e.id === id);
if (!entry) return `no edit #${id} — run /history to see valid ids`;
if (!pathArg) {
const remaining = entry.snapshots
.map((s) => s.path)
.filter((p) => !entry.undoneFiles.has(p));
if (remaining.length === 0) return `batch #${id} is already fully undone`;
return revert(entry, remaining);
}
const snap = entry.snapshots.find((s) => s.path === pathArg);
if (!snap) {
const files = [...new Set(entry.blocks.map((b) => b.path))];
return `batch #${id} doesn't include "${pathArg}" — files in this batch: ${files.join(", ")}`;
}
if (entry.undoneFiles.has(pathArg)) {
return `${pathArg} in batch #${id} is already undone`;
}
return revert(entry, [pathArg]);
},
[codeMode],
);
const codeHistory = useCallback<UseEditHistoryResult["codeHistory"]>(() => {
if (!codeMode) return "not in code mode";
const entries = editHistory.current;
if (entries.length === 0) return "no edits recorded this session yet";
const lines = ["Edit history (oldest first):"];
for (const e of entries) {
const when = new Date(e.at).toISOString().replace("T", " ").slice(11, 19);
const files = new Set(e.blocks.map((b) => b.path));
const fileList = [...files].join(", ");
const fileSummary = fileList.length > 60 ? `${fileList.slice(0, 60)}…` : fileList;
const status = entryStatus(e);
const statusText =
status === "applied" ? "applied" : status === "PARTIAL" ? "PARTIAL" : "UNDONE ";
lines.push(
` #${String(e.id).padStart(3)} ${when} ${statusText} ${e.source.padEnd(12)} ${files.size} file · ${e.blocks.length} block ${fileSummary}`,
);
}
lines.push("");
lines.push(
"/show <id> → per-file summary · /show <id> <path> → full diff of one file",
);
lines.push(
"/undo → newest non-undone · /undo <id> [path] → target a specific batch or file",
);
return lines.join("\n");
}, [codeMode]);
const codeShowEdit = useCallback<UseEditHistoryResult["codeShowEdit"]>(
(args = []) => {
if (!codeMode) return "not in code mode";
const entries = editHistory.current;
if (entries.length === 0) return "no edits recorded this session — /history is empty";
const idArg = args[0];
const pathArg = args[1];
let entry: EditHistoryEntry | undefined;
if (!idArg) {
entry =
[...entries].reverse().find((e) => !isEntryFullyUndone(e)) ?? entries[entries.length - 1];
} else {
const id = Number.parseInt(idArg, 10);
if (!Number.isFinite(id)) {
return "usage: /show [id] [path] (omit id for newest; path from the per-file summary)";
}
entry = entries.find((e) => e.id === id);
if (!entry) return `no edit #${id} — run /history to see valid ids`;
}
if (!entry) return "unexpected: history lookup failed";
if (pathArg) {
const fileBlocks = entry.blocks.filter((b) => b.path === pathArg);
if (fileBlocks.length === 0) {
const files = [...new Set(entry.blocks.map((b) => b.path))];
return `batch #${entry.id} doesn't include "${pathArg}" — files in this batch: ${files.join(", ")}`;
}
const when = new Date(entry.at).toISOString().replace("T", " ").slice(11, 19);
const state = entry.undoneFiles.has(pathArg) ? "UNDONE" : "applied";
const header = `▸ edit #${entry.id} · ${when} · ${pathArg} · ${state} · ${fileBlocks.length} block(s)`;
const diff = formatAllBlockDiffs(fileBlocks, { maxLines: 60, contextLines: 2 });
const footer = entry.undoneFiles.has(pathArg)
? "(already reverted — /history shows the batch-level status)"
: `/undo ${entry.id} ${pathArg} → revert just this file`;
return [header, ...diff, "", footer].join("\n");
}
const when = new Date(entry.at).toISOString().replace("T", " ").slice(11, 19);
const files = [...new Set(entry.blocks.map((b) => b.path))];
const status = entryStatus(entry);
const header = `▸ edit #${entry.id} · ${when} · ${entry.source} · ${status} · ${files.length} file(s)`;
const countLines = (s: string) => (s.length === 0 ? 0 : (s.match(/\n/g)?.length ?? 0) + 1);
const fileLines = files.map((path) => {
const fileBlocks = entry!.blocks.filter((b) => b.path === path);
let removed = 0;
let added = 0;
for (const b of fileBlocks) {
removed += countLines(b.search);
added += countLines(b.replace);
}
const state = entry!.undoneFiles.has(path) ? "UNDONE" : "applied";
return ` ${state.padEnd(7)} -${String(removed).padStart(3)}/+${String(added).padStart(3)} ${path} (${fileBlocks.length} block${fileBlocks.length === 1 ? "" : "s"})`;
});
return [
header,
...fileLines,
"",
`/show ${entry.id} <path> → full diff of one file`,
`/undo ${entry.id} <path> → revert just that file · /undo ${entry.id} → revert whole batch`,
].join("\n");
},
[codeMode],
);
const sealCurrentEntry = useCallback(() => {
currentTurnEntry.current = null;
}, []);
const hasUndoable = useCallback(
() => editHistory.current.some((e) => !isEntryFullyUndone(e)),
[],
);
return {
undoBanner,
recordEdit,
armUndoBanner,
codeUndo,
codeHistory,
codeShowEdit,
sealCurrentEntry,
hasUndoable,
};
}
+119
View File
@@ -0,0 +1,119 @@
import { useCallback, useEffect, useState } from "react";
import type { CacheFirstLoop } from "../../loop.js";
import { VERSION, compareVersions, getLatestVersion } from "../../version.js";
export interface Balance {
currency: string;
total: number;
}
export interface UseSessionInfoResult {
balance: Balance | null;
models: string[] | null;
latestVersion: string | null;
/** Strictly-newer version string (for the header badge) — else `null`. */
updateAvailable: string | null;
refreshBalance: () => void;
refreshModels: () => void;
refreshLatestVersion: () => void;
}
/**
* Ambient session-level data fetched from DeepSeek + the npm registry
* at mount, refreshed either implicitly (balance after each turn) or
* on demand (`/update`, `/models`).
*
* All three are best-effort — a `null` value means "not loaded yet or
* the endpoint failed." The StatsPanel hides the cell in that case.
*/
export function useSessionInfo(loop: CacheFirstLoop): UseSessionInfoResult {
const [balance, setBalance] = useState<Balance | null>(null);
const [models, setModels] = useState<string[] | null>(null);
const [latestVersion, setLatestVersion] = useState<string | null>(null);
// Fetch balance on mount. Non-blocking — the session works without
// it; `null` hides the cell. handleSubmit calls refreshBalance in
// its finally so the number tracks actual spend rather than
// freezing at mount-time.
useEffect(() => {
let cancelled = false;
void (async () => {
const bal = await loop.client.getBalance().catch(() => null);
if (cancelled || !bal || !bal.balance_infos.length) return;
const primary = bal.balance_infos[0]!;
setBalance({ currency: primary.currency, total: Number(primary.total_balance) });
})();
return () => {
cancelled = true;
};
}, [loop]);
// Fetch the model catalog from DeepSeek once. Silent degrade on
// failure (stays null), so `/models` can tell "still loading /
// offline" apart from "loaded, here's the list."
useEffect(() => {
let cancelled = false;
void (async () => {
const list = await loop.client.listModels().catch(() => null);
if (cancelled || !list) return;
setModels(list.data.map((m) => m.id));
})();
return () => {
cancelled = true;
};
}, [loop]);
// Background registry check — 24h disk cache absorbs repeated
// launches, timeout bounded so a flaky network doesn't delay the
// notification. `null` on failure (silent). We store the raw version
// regardless of whether it's newer; the header badge's newer-only
// check happens at the `updateAvailable` derivation below.
useEffect(() => {
let cancelled = false;
void (async () => {
const latest = await getLatestVersion();
if (cancelled || !latest) return;
setLatestVersion(latest);
})();
return () => {
cancelled = true;
};
}, []);
const updateAvailable =
latestVersion && compareVersions(VERSION, latestVersion) < 0 ? latestVersion : null;
const refreshBalance = useCallback(() => {
void (async () => {
const bal = await loop.client.getBalance().catch(() => null);
if (bal?.balance_infos.length) {
const p = bal.balance_infos[0]!;
setBalance({ currency: p.currency, total: Number(p.total_balance) });
}
})();
}, [loop]);
const refreshModels = useCallback(() => {
void (async () => {
const list = await loop.client.listModels().catch(() => null);
if (list) setModels(list.data.map((m) => m.id));
})();
}, [loop]);
const refreshLatestVersion = useCallback(() => {
void (async () => {
const fresh = await getLatestVersion({ force: true });
if (fresh) setLatestVersion(fresh);
})();
}, []);
return {
balance,
models,
latestVersion,
updateAvailable,
refreshBalance,
refreshModels,
refreshLatestVersion,
};
}
+99
View File
@@ -0,0 +1,99 @@
import { useEffect, useRef, useState } from "react";
import type { SubagentEvent, SubagentSink } from "../../tools/subagent.js";
import { appendUsage } from "../../usage.js";
import type { DisplayEvent } from "./EventLog.js";
export interface SubagentActivity {
task: string;
iter: number;
elapsedMs: number;
}
export interface UseSubagentParams {
session: string | undefined;
setHistorical: React.Dispatch<React.SetStateAction<DisplayEvent[]>>;
}
export interface UseSubagentResult {
/** Live state for an in-flight subagent, null when none is running. */
activity: SubagentActivity | null;
/**
* Ref captured by the loop's `subagentRunner` closure so even
* late-spawned subagents find the current handler. Consumers pass
* this to `spawnSubagent({ sink })`.
*/
sinkRef: React.MutableRefObject<SubagentSink>;
}
/**
* Subagent UI wiring. `start` opens the activity row; each `progress`
* updates iter + elapsed in place; `end` clears the row and posts a
* one-line summary (with inline cost) into Historical. Only one
* subagent is active at a time in the MVP — overlapping events just
* replace the prior activity.
*/
export function useSubagent({ session, setHistorical }: UseSubagentParams): UseSubagentResult {
const [activity, setActivity] = useState<SubagentActivity | null>(null);
const sinkRef = useRef<SubagentSink>({ current: null });
useEffect(() => {
sinkRef.current.current = (ev: SubagentEvent) => {
if (ev.kind === "start") {
setActivity({
task: ev.task,
iter: ev.iter ?? 0,
elapsedMs: ev.elapsedMs ?? 0,
});
return;
}
if (ev.kind === "progress") {
setActivity({
task: ev.task,
iter: ev.iter ?? 0,
elapsedMs: ev.elapsedMs ?? 0,
});
return;
}
// end
setActivity(null);
const seconds = ((ev.elapsedMs ?? 0) / 1000).toFixed(1);
// Inline cost: the one number most users look at. Shown in the
// Historical row so they don't have to run `/stats` to see it.
const costTail =
ev.costUsd !== undefined && ev.costUsd > 0 ? ` · $${ev.costUsd.toFixed(4)}` : "";
const summary = ev.error
? `⌬ subagent "${ev.task}" failed after ${seconds}s · ${ev.iter ?? 0} tool call(s) — ${ev.error}`
: `⌬ subagent "${ev.task}" done in ${seconds}s · ${ev.iter ?? 0} tool call(s) · ${ev.turns ?? 0} turn(s)${costTail}`;
setHistorical((prev) => [
...prev,
{
id: `subagent-end-${Date.now()}`,
role: "info",
text: summary,
},
]);
// Persist a subagent summary row to ~/.reasonix/usage.jsonl so
// `/stats` and `reasonix stats` surface it. Skipped on error —
// we only record what actually cost money and did work.
if (!ev.error && ev.usage && ev.model) {
appendUsage({
session: session ?? null,
model: ev.model,
usage: ev.usage,
kind: "subagent",
subagent: {
skillName: ev.skillName,
taskPreview: ev.task.slice(0, 60),
toolIters: ev.iter ?? 0,
durationMs: ev.elapsedMs ?? 0,
},
});
}
};
return () => {
sinkRef.current.current = null;
};
}, [session, setHistorical]);
return { activity, sinkRef };
}
+104 -1
View File
@@ -45,6 +45,42 @@ export interface StreamChunk {
raw: any;
}
/**
* Response shape for DeepSeek's `/user/balance` endpoint. One entry
* per currency the account is funded in (typically CNY, sometimes
* USD). `total_balance` is the spendable figure; `granted_balance`
* counts promotional credits that expire, `topped_up_balance` is
* what the user paid for and keeps.
*/
export interface BalanceInfo {
currency: string;
total_balance: string;
granted_balance?: string;
topped_up_balance?: string;
}
export interface UserBalance {
is_available: boolean;
balance_infos: BalanceInfo[];
}
/**
* Response shape for DeepSeek's `/models` endpoint. Mirrors the OpenAI
* models list shape DeepSeek copied — `id` is the model name to pass to
* `/chat/completions`, `owned_by` is the provider string (always
* `"deepseek"` today).
*/
export interface ModelInfo {
id: string;
object: "model";
owned_by: string;
}
export interface ModelList {
object: "list";
data: ModelInfo[];
}
export interface DeepSeekClientOptions {
apiKey?: string;
baseUrl?: string;
@@ -74,7 +110,17 @@ export class DeepSeekClient {
process.env.DEEPSEEK_BASE_URL ??
"https://api.deepseek.com"
).replace(/\/+$/, "");
this.timeoutMs = opts.timeoutMs ?? 120_000;
// 11 min. DeepSeek's load-balancer may keep a connection open for
// up to 10 minutes while the request waits in queue (non-streaming
// sends empty lines, streaming sends `:` SSE keep-alive comments —
// both are invisible to our parsers, so neither surfaces until the
// real response starts). Timing out at the legacy 2-min default
// killed queued requests prematurely, burned the queue slot on
// retry, and could loop through the whole queue repeatedly.
// Setting 11 min lets the server's own 10-min cap close the
// connection first (clean EOF → natural retry), and our timer
// is a safety net for genuinely hung sockets.
this.timeoutMs = opts.timeoutMs ?? 660_000;
this._fetch = opts.fetch ?? globalThis.fetch.bind(globalThis);
this.retry = opts.retry ?? {};
}
@@ -89,9 +135,66 @@ export class DeepSeekClient {
if (opts.temperature !== undefined) payload.temperature = opts.temperature;
if (opts.maxTokens !== undefined) payload.max_tokens = opts.maxTokens;
if (opts.responseFormat) payload.response_format = opts.responseFormat;
// V4 thinking-mode toggle: lives under `extra_body.thinking.type` per
// DeepSeek's docs. Docs also note that in thinking mode `temperature`,
// `top_p`, `presence_penalty`, `frequency_penalty` are silently
// ignored — we don't strip them here because the server's explicit
// "setting won't report an error" contract means leaving them in is
// safe and keeps the request payload diffable against OpenAI tooling.
if (opts.thinking) {
payload.extra_body = { thinking: { type: opts.thinking } };
}
if (opts.reasoningEffort) {
payload.reasoning_effort = opts.reasoningEffort;
}
return payload;
}
/**
* Fetch the current DeepSeek account balance. Separate endpoint
* from chat completions, no billing impact. Returns null on any
* network/auth failure so callers can gate the balance display
* without a hard error — the rest of the session works regardless.
*/
async getBalance(opts: { signal?: AbortSignal } = {}): Promise<UserBalance | null> {
try {
const resp = await this._fetch(`${this.baseUrl}/user/balance`, {
method: "GET",
headers: { Authorization: `Bearer ${this.apiKey}` },
signal: opts.signal,
});
if (!resp.ok) return null;
const data = (await resp.json()) as UserBalance;
if (!data || !Array.isArray(data.balance_infos)) return null;
return data;
} catch {
return null;
}
}
/**
* Fetch the model catalog DeepSeek currently exposes. Today this is
* `deepseek-chat` (V3) and `deepseek-reasoner` (R1), but querying is
* the only way to learn about new ones without a Reasonix release.
* Returns null on any network/auth failure so callers can degrade
* gracefully — e.g. `/models` falls back to the hardcoded hint.
*/
async listModels(opts: { signal?: AbortSignal } = {}): Promise<ModelList | null> {
try {
const resp = await this._fetch(`${this.baseUrl}/models`, {
method: "GET",
headers: { Authorization: `Bearer ${this.apiKey}` },
signal: opts.signal,
});
if (!resp.ok) return null;
const data = (await resp.json()) as ModelList;
if (!data || !Array.isArray(data.data)) return null;
return data;
} catch {
return null;
}
}
async chat(opts: ChatRequestOptions): Promise<ChatResponse> {
const ctrl = new AbortController();
const timer = setTimeout(() => ctrl.abort(), this.timeoutMs);
+124
View File
@@ -0,0 +1,124 @@
/**
* Render a SEARCH/REPLACE edit block as a compact unified-diff-style
* preview for the code-mode confirm gate. Shows the user what's about
* to land on disk BEFORE they press `y` — catches "wrong file" and
* "wrong replacement" mistakes that the old path + line-count summary
* couldn't.
*
* Not a full Myers diff: we trim shared leading/trailing lines as
* context and render the middle divergence as `-old` / `+new`. That's
* enough for the common SEARCH/REPLACE shape (small change inside a
* function body, wrapped with a few lines of surrounding code for
* uniqueness) and avoids pulling in a diff library.
*/
import type { EditBlock } from "./edit-blocks.js";
export interface DiffPreviewOptions {
/** How many lines of unchanged context to show at each end. Default 2. */
contextLines?: number;
/** Hard cap on total rendered lines. Default 20 — beyond this the preview collapses. */
maxLines?: number;
/** Indent applied to every output line. Default 8 spaces — matches the pending-preview nesting. */
indent?: string;
}
/** Render one edit block's diff. Returns an array of formatted lines. */
export function formatEditBlockDiff(block: EditBlock, opts: DiffPreviewOptions = {}): string[] {
const contextLines = Math.max(0, opts.contextLines ?? 2);
const maxLines = Math.max(4, opts.maxLines ?? 20);
const indent = opts.indent ?? " ";
const search = block.search === "" ? [] : block.search.split("\n");
const replace = block.replace.split("\n");
// New-file case: no search to compare, show the full new content
// (capped). Mark every line `+` so the user knows it's all additions.
if (search.length === 0) {
return renderAllPlus(replace, indent, maxLines);
}
// Common leading / trailing lines — shared context we can collapse.
let leading = 0;
while (
leading < search.length &&
leading < replace.length &&
search[leading] === replace[leading]
) {
leading++;
}
let trailing = 0;
while (
trailing < search.length - leading &&
trailing < replace.length - leading &&
search[search.length - 1 - trailing] === replace[replace.length - 1 - trailing]
) {
trailing++;
}
const searchMiddle = search.slice(leading, search.length - trailing);
const replaceMiddle = replace.slice(leading, replace.length - trailing);
// Trim context to `contextLines` on each side.
const leadShown = search.slice(Math.max(0, leading - contextLines), leading);
const leadHidden = leading - leadShown.length;
const trailShown = search.slice(
search.length - trailing,
search.length - trailing + contextLines,
);
const trailHidden = trailing - trailShown.length;
const out: string[] = [];
if (leadHidden > 0) {
out.push(`${indent} … ${leadHidden} unchanged line${leadHidden === 1 ? "" : "s"} above`);
}
for (const l of leadShown) out.push(`${indent} ${l}`);
for (const l of searchMiddle) out.push(`${indent}- ${l}`);
for (const l of replaceMiddle) out.push(`${indent}+ ${l}`);
for (const l of trailShown) out.push(`${indent} ${l}`);
if (trailHidden > 0) {
out.push(`${indent} … ${trailHidden} unchanged line${trailHidden === 1 ? "" : "s"} below`);
}
return capLines(out, maxLines, indent);
}
/**
* Render the full set of blocks back-to-back, each preceded by a
* path-and-size header so the user can tell which file owns each
* diff chunk. Blocks are separated by a blank line for breathing room.
*/
export function formatAllBlockDiffs(
blocks: readonly EditBlock[],
opts: DiffPreviewOptions = {},
): string[] {
const out: string[] = [];
for (let i = 0; i < blocks.length; i++) {
const b = blocks[i]!;
const removed = b.search === "" ? 0 : countLines(b.search);
const added = countLines(b.replace);
const tag = b.search === "" ? "NEW " : " ";
if (i > 0) out.push("");
out.push(` ${tag}${b.path} (-${removed} +${added} lines)`);
out.push(...formatEditBlockDiff(b, opts));
}
return out;
}
function countLines(s: string): number {
if (s.length === 0) return 0;
return (s.match(/\n/g)?.length ?? 0) + 1;
}
function renderAllPlus(lines: string[], indent: string, maxLines: number): string[] {
const out = lines.map((l) => `${indent}+ ${l}`);
return capLines(out, maxLines, indent);
}
function capLines(lines: string[], maxLines: number, indent: string): string[] {
if (lines.length <= maxLines) return lines;
const head = lines.slice(0, maxLines - 1);
const hidden = lines.length - head.length;
head.push(`${indent}… (${hidden} more diff lines — full content applies on /apply)`);
return head;
}
+262
View File
@@ -0,0 +1,262 @@
/**
* Aider-style SEARCH/REPLACE edit blocks.
*
* The model emits blocks in this exact shape, one or more per response:
*
* path/to/file.ts
* <<<<<<< SEARCH
* exact existing lines (whitespace-sensitive)
* =======
* replacement lines
* >>>>>>> REPLACE
*
* We chose this over unified diffs because:
* - Models produce it reliably — no line-number drift.
* - It tolerates multi-edit responses without ambiguity over which
* hunk belongs to which file.
* - Aider has years of evidence that this format works even against
* weaker models than DeepSeek R1, so it's a conservative pick.
*
* The SEARCH text must match the file byte-for-byte. Empty SEARCH is a
* sentinel for "create new file" — the REPLACE becomes the whole file.
* If SEARCH doesn't match we refuse the edit and surface the failure;
* we do NOT guess or fuzzy-match. A wrong silent edit is worse than a
* missing one — the user can re-ask with the exact current content.
*/
import { existsSync, mkdirSync, readFileSync, unlinkSync, writeFileSync } from "node:fs";
import { dirname, resolve } from "node:path";
export interface EditBlock {
/** Path as written by the model — relative to rootDir, or absolute. */
path: string;
/** Literal text to match in the target file. Empty → create new file. */
search: string;
/** Replacement text to write in place of `search`. */
replace: string;
/** Char offset in the source message where this block started. */
offset: number;
}
export type ApplyStatus =
/** Edit landed on disk. */
| "applied"
/** New file created (SEARCH was empty and file didn't exist). */
| "created"
/** File exists but SEARCH block wasn't found in its content. */
| "not-found"
/** File doesn't exist and SEARCH was non-empty (can't create without content). */
| "file-missing"
/** Path escapes rootDir — refused on safety grounds. */
| "path-escape"
/** fs write / read threw. */
| "error";
export interface ApplyResult {
path: string;
status: ApplyStatus;
/** Extra detail (e.g. error message) for logs. */
message?: string;
}
/**
* One edit block per match. The regex is anchored to the 7-char marker
* lines because those are visually distinct and unlikely to appear in
* normal code.
*
* Anchored with `^` + `m` flag so the filename has to live on its own
* line. Keeps us from matching e.g. a JS-import string that happens to
* contain `<<<<<<< SEARCH` in inner text.
*/
// `\n?` before the =======/REPLACE separators makes the body optional:
// empty SEARCH (new-file sentinel) works without requiring a gratuitous
// empty line, and the same holds for empty REPLACE (file-deletion
// semantics, not yet supported but cheaply representable).
const BLOCK_RE = /^(\S[^\n]*)\n<{7} SEARCH\n([\s\S]*?)\n?={7}\n([\s\S]*?)\n?>{7} REPLACE/gm;
export function parseEditBlocks(text: string): EditBlock[] {
const out: EditBlock[] = [];
BLOCK_RE.lastIndex = 0;
let m: RegExpExecArray | null = BLOCK_RE.exec(text);
while (m !== null) {
out.push({
path: m[1]!.trim(),
search: m[2]!,
replace: m[3]!,
offset: m.index,
});
m = BLOCK_RE.exec(text);
}
return out;
}
export function applyEditBlock(block: EditBlock, rootDir: string): ApplyResult {
const absRoot = resolve(rootDir);
const absTarget = resolve(absRoot, block.path);
// Refuse paths that escape rootDir. `resolve` normalizes `..`, so
// startsWith on the normalized pair is enough.
if (absTarget !== absRoot && !absTarget.startsWith(`${absRoot}${sep()}`)) {
return {
path: block.path,
status: "path-escape",
message: `resolved path ${absTarget} is outside rootDir ${absRoot}`,
};
}
const searchEmpty = block.search.length === 0;
const exists = existsSync(absTarget);
try {
if (!exists) {
if (!searchEmpty) {
return {
path: block.path,
status: "file-missing",
message: "file does not exist; to create it, use an empty SEARCH block",
};
}
mkdirSync(dirname(absTarget), { recursive: true });
writeFileSync(absTarget, block.replace, "utf8");
return { path: block.path, status: "created" };
}
const content = readFileSync(absTarget, "utf8");
if (searchEmpty) {
return {
path: block.path,
status: "not-found",
message: "empty SEARCH only creates new files — this file already exists",
};
}
const idx = content.indexOf(block.search);
if (idx === -1) {
return {
path: block.path,
status: "not-found",
message: "SEARCH text does not match the current file content exactly",
};
}
// Replace only the first occurrence — if the model needs multiple
// identical edits it should emit multiple blocks (each anchored by
// more surrounding context). Auto-expanding to replace-all is a
// footgun when the same string legitimately appears in several
// unrelated places.
const replaced = `${content.slice(0, idx)}${block.replace}${content.slice(idx + block.search.length)}`;
writeFileSync(absTarget, replaced, "utf8");
return { path: block.path, status: "applied" };
} catch (err) {
return { path: block.path, status: "error", message: (err as Error).message };
}
}
export function applyEditBlocks(blocks: EditBlock[], rootDir: string): ApplyResult[] {
return blocks.map((b) => applyEditBlock(b, rootDir));
}
/**
* Build an EditBlock that represents a whole-file overwrite. If the
* target exists, SEARCH = current content so applyEditBlock replaces
* the whole thing when committed; if it doesn't, SEARCH is empty (the
* create-new sentinel). Used by the edit-mode gate when routing a
* `write_file` tool call through the review queue without executing
* the write inline.
*/
export function toWholeFileEditBlock(path: string, content: string, rootDir: string): EditBlock {
const abs = resolve(rootDir, path);
let search = "";
if (existsSync(abs)) {
try {
search = readFileSync(abs, "utf8");
} catch {
search = "";
}
}
return { path, search, replace: content, offset: 0 };
}
// ---------- snapshot / restore (for /undo) ----------
export interface EditSnapshot {
/** Path relative to rootDir, as the block named it. */
path: string;
/**
* File content before the edit batch was applied. `null` means the
* file didn't exist yet — restoring that means deleting whatever the
* edit created.
*/
prevContent: string | null;
}
/**
* Capture the current state of every file an edit batch is about to
* touch, so `/undo` can roll back if the user doesn't like the result.
* De-duplicates by path because one batch can contain multiple blocks
* for the same file, and we only want one "before" snapshot per file.
*/
export function snapshotBeforeEdits(blocks: EditBlock[], rootDir: string): EditSnapshot[] {
const absRoot = resolve(rootDir);
const seen = new Set<string>();
const snapshots: EditSnapshot[] = [];
for (const b of blocks) {
if (seen.has(b.path)) continue;
seen.add(b.path);
const abs = resolve(absRoot, b.path);
if (!existsSync(abs)) {
snapshots.push({ path: b.path, prevContent: null });
continue;
}
try {
snapshots.push({ path: b.path, prevContent: readFileSync(abs, "utf8") });
} catch {
// Unreadable (permission / binary) — record null so we at least
// don't pretend the snapshot is authoritative. The restore path
// will treat null as "delete on undo", which is wrong in that
// case but the file wasn't ours to begin with.
snapshots.push({ path: b.path, prevContent: null });
}
}
return snapshots;
}
/**
* Restore files to their snapshotted state. Snapshots with
* `prevContent === null` were created by the edit, so undo = delete.
* Otherwise the prior content is written back, replacing whatever the
* edit left behind.
*/
export function restoreSnapshots(snapshots: EditSnapshot[], rootDir: string): ApplyResult[] {
const absRoot = resolve(rootDir);
return snapshots.map((snap) => {
const abs = resolve(absRoot, snap.path);
if (abs !== absRoot && !abs.startsWith(`${absRoot}${sep()}`)) {
return {
path: snap.path,
status: "path-escape",
message: "snapshot path escapes rootDir — refusing to restore",
};
}
try {
if (snap.prevContent === null) {
if (existsSync(abs)) unlinkSync(abs);
return {
path: snap.path,
status: "applied",
message: "removed (the edit had created it)",
};
}
writeFileSync(abs, snap.prevContent, "utf8");
return {
path: snap.path,
status: "applied",
message: "restored to pre-edit content",
};
} catch (err) {
return { path: snap.path, status: "error", message: (err as Error).message };
}
});
}
/** Platform separator — `\` on Windows, `/` elsewhere. */
function sep(): string {
return process.platform === "win32" ? "\\" : "/";
}
+111
View File
@@ -0,0 +1,111 @@
/**
* Durable checkpoint for the pending-edits queue.
*
* Code mode holds parsed SEARCH/REPLACE blocks in an in-memory
* `useRef<EditBlock[]>` until the user runs `/apply` or `/discard`.
* Pre-0.5.14 that was ephemeral: a crash or accidental Ctrl+C after
* the model proposed seven edits discarded all seven — the session
* log had the assistant text, but the "please review this batch"
* state was gone.
*
* This module checkpoints the queue to
* `~/.reasonix/sessions/<name>.pending.json`
* after every mutation (parse → set / apply → clear / discard →
* clear). On session resume the App reads the file and re-populates
* the queue. If the file doesn't exist the session resumes as before.
*
* Format choices:
* - JSON (not JSONL) — the queue is a single array written at once,
* not a stream of records.
* - Overwrite-on-write — the queue is small (kilobytes) and atomicity
* is "last write wins"; partial-write on crash is fine since we'd
* rather lose the checkpoint than have a torn file block resume.
* - Best-effort I/O — disk full or permission denied must not break
* the session. Silent skip matches the rest of the durable logs
* (session.ts, usage.ts).
*
* Ephemeral sessions (sessionName === null) skip persistence entirely:
* there's no stable name to key the checkpoint to.
*/
import { existsSync, mkdirSync, readFileSync, unlinkSync, writeFileSync } from "node:fs";
import { dirname, join } from "node:path";
import { sanitizeName, sessionsDir } from "../session.js";
import type { EditBlock } from "./edit-blocks.js";
/** Absolute path for the checkpoint file that belongs to this session. */
export function pendingEditsPath(sessionName: string): string {
return join(sessionsDir(), `${sanitizeName(sessionName)}.pending.json`);
}
/**
* Write the queue to disk, or delete the checkpoint file when `blocks`
* is empty. Callers pass the full current queue every time; we don't
* attempt append-style deltas because the queue is tiny.
*
* No-op when `sessionName` is null (ephemeral session has nowhere to
* write), so call sites can pass the session name directly without a
* null guard.
*/
export function savePendingEdits(sessionName: string | null, blocks: EditBlock[]): void {
if (!sessionName) return;
const path = pendingEditsPath(sessionName);
try {
if (blocks.length === 0) {
if (existsSync(path)) unlinkSync(path);
return;
}
mkdirSync(dirname(path), { recursive: true });
writeFileSync(path, JSON.stringify(blocks, null, 2), "utf8");
} catch {
/* best-effort — disk full / perms should not break the session */
}
}
/**
* Load the queue from disk, returns `null` when there's no checkpoint.
* A malformed file (power-loss torn write, user hand-edit) also returns
* null — silent recovery beats failing to open the session.
*/
export function loadPendingEdits(sessionName: string | null): EditBlock[] | null {
if (!sessionName) return null;
const path = pendingEditsPath(sessionName);
if (!existsSync(path)) return null;
let raw: string;
try {
raw = readFileSync(path, "utf8");
} catch {
return null;
}
try {
const parsed = JSON.parse(raw);
if (!Array.isArray(parsed)) return null;
const out: EditBlock[] = [];
for (const item of parsed) {
if (
item &&
typeof item === "object" &&
typeof item.path === "string" &&
typeof item.search === "string" &&
typeof item.replace === "string" &&
typeof item.offset === "number"
) {
out.push(item as EditBlock);
}
}
return out;
} catch {
return null;
}
}
/** Delete the checkpoint file unconditionally — called by /apply and /discard. */
export function clearPendingEdits(sessionName: string | null): void {
if (!sessionName) return;
const path = pendingEditsPath(sessionName);
try {
if (existsSync(path)) unlinkSync(path);
} catch {
/* best-effort */
}
}
+292
View File
@@ -0,0 +1,292 @@
/**
* Per-session plan persistence.
*
* The structured plan that the model submits via `submit_plan` (and
* subsequently mutates via `mark_step_complete` / `revise_plan`) is a
* meaningful artifact of the user's work. Without persistence it
* evaporates the moment the terminal closes — which means the user
* loses context every time they take a coffee break, and the rich
* checkpoint / revise / progress UX has nothing to attach to in
* resumed sessions.
*
* This module ships the smallest useful piece: read/write a plan
* state JSON next to the session's JSONL log. App.tsx loads on
* mount and saves after every state change. Storage path mirrors
* the JSONL convention: `~/.reasonix/sessions/<sanitized>.plan.json`.
*
* What's persisted: the structured `steps[]` (with risk levels), the
* set of completedStepIds, and an updatedAt timestamp. The plan's
* markdown body is NOT persisted here — it lives in the JSONL log
* (it was a tool result), so resuming the session replays it
* naturally if the user wants to re-read it. We only carry forward
* the live state needed to keep mark_step_complete and revise_plan
* meaningful.
*/
import {
existsSync,
mkdirSync,
readFileSync,
readdirSync,
renameSync,
statSync,
unlinkSync,
writeFileSync,
} from "node:fs";
import { dirname, join } from "node:path";
import { sanitizeName, sessionsDir } from "../session.js";
import type { PlanStep } from "../tools/plan.js";
export interface PlanStateOnDisk {
/** File format version — bump when shape changes. */
version: 1;
steps: PlanStep[];
completedStepIds: string[];
/** ISO8601 timestamp of the last write. */
updatedAt: string;
/**
* Markdown body the model submitted via submit_plan. Persisted so
* Time Travel replay can show the full proposal without going back
* to the JSONL log. Optional — older / minimal plans may lack it.
*/
body?: string;
/**
* Optional one-sentence human-friendly title. Surfaces in the
* PlanConfirm header, the resume banner, and /plans listings so
* the user identifies plans by intent rather than file path.
*/
summary?: string;
}
export function planStatePath(sessionName: string): string {
return join(sessionsDir(), `${sanitizeName(sessionName)}.plan.json`);
}
/**
* Read the persisted plan for this session, if any. Returns `null`
* for missing / unreadable / malformed files — callers should treat
* the absence of a stored plan as "no plan yet", not a hard error.
*/
export function loadPlanState(sessionName: string): PlanStateOnDisk | null {
const path = planStatePath(sessionName);
if (!existsSync(path)) return null;
try {
const raw = readFileSync(path, "utf8");
const parsed = JSON.parse(raw) as Partial<PlanStateOnDisk>;
if (!parsed || typeof parsed !== "object") return null;
if (parsed.version !== 1) return null;
if (!Array.isArray(parsed.steps)) return null;
if (!Array.isArray(parsed.completedStepIds)) return null;
if (typeof parsed.updatedAt !== "string") return null;
// Defensive: filter out any malformed step entries so a partially
// corrupted file still yields a usable subset.
const steps: PlanStep[] = [];
for (const s of parsed.steps) {
if (!s || typeof s !== "object") continue;
const e = s as unknown as Record<string, unknown>;
if (typeof e.id !== "string" || !e.id) continue;
if (typeof e.title !== "string" || !e.title) continue;
if (typeof e.action !== "string" || !e.action) continue;
const step: PlanStep = { id: e.id, title: e.title, action: e.action };
if (e.risk === "low" || e.risk === "med" || e.risk === "high") step.risk = e.risk;
steps.push(step);
}
if (steps.length === 0) return null;
const completedStepIds = parsed.completedStepIds.filter(
(id): id is string => typeof id === "string" && id.length > 0,
);
const out: PlanStateOnDisk = {
version: 1,
steps,
completedStepIds,
updatedAt: parsed.updatedAt,
};
if (typeof parsed.body === "string" && parsed.body) out.body = parsed.body;
if (typeof parsed.summary === "string" && parsed.summary) out.summary = parsed.summary;
return out;
} catch {
return null;
}
}
/**
* Persist the current plan state. Called whenever the in-memory plan
* meaningfully changes (submit, complete, revise). Best-effort: a
* write failure logs to stderr but doesn't propagate — losing the
* persisted copy is annoying but shouldn't crash the TUI.
*/
export function savePlanState(
sessionName: string,
steps: PlanStep[],
completedStepIds: Iterable<string>,
extras?: { body?: string; summary?: string },
): void {
const path = planStatePath(sessionName);
try {
mkdirSync(dirname(path), { recursive: true });
const state: PlanStateOnDisk = {
version: 1,
steps,
completedStepIds: [...completedStepIds],
updatedAt: new Date().toISOString(),
};
if (extras?.body) state.body = extras.body;
if (extras?.summary) state.summary = extras.summary;
writeFileSync(path, `${JSON.stringify(state, null, 2)}\n`, "utf8");
} catch (err) {
process.stderr.write(
`▸ plan-store: failed to save plan for "${sessionName}": ${(err as Error).message}\n`,
);
}
}
/** Remove the persisted plan, if any. Used on cancel / clean reset. */
export function clearPlanState(sessionName: string): void {
const path = planStatePath(sessionName);
try {
if (existsSync(path)) unlinkSync(path);
} catch {
/* nothing to do — leftover file is harmless, will be overwritten next save */
}
}
/**
* Move the active plan to a timestamped .done.json archive when the
* model has marked every step complete. Future Time-Travel replay
* will load these archives; for now the archive just exists as a
* historical artifact and frees the active plan.json so the next
* session starts fresh.
*
* Returns the archive path on success, or null if there was nothing
* to archive (no active plan) / the rename failed (logged to stderr,
* not propagated — losing the archive is annoying but shouldn't
* crash the TUI).
*
* The timestamp uses ISO 8601 with a millisecond suffix and `:` and
* `.` swapped for `-` so the filename is filesystem-safe on Windows.
* Two archives created within the same millisecond would collide;
* we append a short random suffix to dodge that.
*/
export function archivePlanState(sessionName: string): string | null {
const active = planStatePath(sessionName);
if (!existsSync(active)) return null;
const stamp = new Date().toISOString().replace(/[:.]/g, "-");
const suffix = Math.random().toString(36).slice(2, 6);
const archive = join(
sessionsDir(),
`${sanitizeName(sessionName)}.plan.${stamp}-${suffix}.done.json`,
);
try {
renameSync(active, archive);
return archive;
} catch (err) {
process.stderr.write(
`▸ plan-store: failed to archive plan for "${sessionName}": ${(err as Error).message}\n`,
);
return null;
}
}
/**
* Summary of one archived (completed) plan, as returned by
* `listPlanArchives`. The `completedAt` ISO string comes from the
* archive file's stored `updatedAt` (or its mtime as fallback) so it
* survives across machines / clock skew. `path` is absolute and ready
* for a future `/replay` to read directly.
*/
export interface PlanArchiveSummary {
path: string;
completedAt: string;
steps: PlanStep[];
completedStepIds: string[];
/** Markdown body, when the archive carried it. */
body?: string;
/** One-line human-friendly title, when supplied. */
summary?: string;
}
/**
* List all archived `.done.json` files for this session, newest
* first. Used by `/plans` to give the user a project-local history.
* Cross-project listing is intentionally NOT supported here — a plan
* lives next to its session, and resuming it just means switching
* back to that project's directory.
*
* Robust to missing dir / unreadable entries: a corrupt archive is
* skipped, not propagated. Worst case the user sees a shorter list
* than reality.
*/
export function listPlanArchives(sessionName: string): PlanArchiveSummary[] {
const dir = sessionsDir();
if (!existsSync(dir)) return [];
const prefix = `${sanitizeName(sessionName)}.plan.`;
const suffix = ".done.json";
let entries: string[];
try {
entries = readdirSync(dir);
} catch {
return [];
}
const summaries: PlanArchiveSummary[] = [];
for (const name of entries) {
if (!name.startsWith(prefix) || !name.endsWith(suffix)) continue;
const full = join(dir, name);
try {
const raw = readFileSync(full, "utf8");
const parsed = JSON.parse(raw) as Partial<PlanStateOnDisk>;
if (parsed.version !== 1) continue;
if (!Array.isArray(parsed.steps) || parsed.steps.length === 0) continue;
const steps = parsed.steps.filter(
(s): s is PlanStep =>
!!s &&
typeof s === "object" &&
typeof (s as PlanStep).id === "string" &&
typeof (s as PlanStep).title === "string" &&
typeof (s as PlanStep).action === "string",
);
if (steps.length === 0) continue;
const completedStepIds = Array.isArray(parsed.completedStepIds)
? parsed.completedStepIds.filter((id): id is string => typeof id === "string" && !!id)
: [];
// Prefer the file's own updatedAt; fall back to mtime if missing
// or unparseable so a hand-edited archive still sorts sensibly.
let completedAt = typeof parsed.updatedAt === "string" ? parsed.updatedAt : "";
if (!completedAt || Number.isNaN(Date.parse(completedAt))) {
try {
completedAt = statSync(full).mtime.toISOString();
} catch {
completedAt = new Date(0).toISOString();
}
}
const entry: PlanArchiveSummary = { path: full, completedAt, steps, completedStepIds };
if (typeof parsed.body === "string" && parsed.body) entry.body = parsed.body;
if (typeof parsed.summary === "string" && parsed.summary) entry.summary = parsed.summary;
summaries.push(entry);
} catch {
// Skip the corrupt archive entirely.
}
}
summaries.sort((a, b) => b.completedAt.localeCompare(a.completedAt));
return summaries;
}
/**
* Render `updatedAt` as a short relative-time string for the resume
* notice ("2h ago", "3 days ago"). Falls back to the raw ISO string
* for anything beyond a week so users don't see misleading
* "47 days ago" approximations.
*/
export function relativeTime(updatedAt: string, now: number = Date.now()): string {
const t = Date.parse(updatedAt);
if (Number.isNaN(t)) return updatedAt;
const diffMs = Math.max(0, now - t);
const sec = Math.floor(diffMs / 1000);
if (sec < 60) return `${sec}s ago`;
const min = Math.floor(sec / 60);
if (min < 60) return `${min}m ago`;
const hr = Math.floor(min / 60);
if (hr < 24) return `${hr}h ago`;
const day = Math.floor(hr / 24);
if (day < 7) return `${day}d ago`;
return updatedAt.slice(0, 10);
}
+238
View File
@@ -0,0 +1,238 @@
/**
* System prompt used by `reasonix code`. Teaches the model:
*
* 1. It has a filesystem MCP bridge rooted at the user's CWD.
* 2. To modify files it emits SEARCH/REPLACE blocks (not
* `write_file` — that would whole-file rewrite and kill diff
* reviewability).
* 3. Read first, edit second — SEARCH must match byte-for-byte.
* 4. Be concise. The user can read a diff faster than prose.
*
* Kept short on purpose. Long system prompts eat context budget that
* the Cache-First Loop is trying to conserve. The SEARCH/REPLACE spec
* is the one unavoidable bloat; we trim everything else.
*/
import { existsSync, readFileSync } from "node:fs";
import { join } from "node:path";
import { ESCALATION_CONTRACT, TUI_FORMATTING_RULES } from "../prompt-fragments.js";
import { applyMemoryStack } from "../user-memory.js";
export const CODE_SYSTEM_PROMPT = `You are Reasonix Code, a coding assistant. You have filesystem tools (read_file, write_file, edit_file, list_directory, directory_tree, search_files, search_content, get_file_info) rooted at the user's working directory, plus run_command / run_background for shell.
# Cite or shut up — non-negotiable
Every factual claim you make about THIS codebase must be backed by evidence. Reasonix VALIDATES the citations you write — broken paths or out-of-range lines render in **red strikethrough with ❌** in front of the user.
**Positive claims** (a file exists, a function does X, a feature IS implemented) — append a markdown link to the source:
- ✅ Correct: \`The MCP client supports listResources [listResources](src/mcp/client.ts:142).\`
- ❌ Wrong: \`The MCP client supports listResources.\` ← no citation, looks authoritative but unverifiable.
**Negative claims** (X is missing, Y is not implemented, lacks Z, doesn't have W) are the **most common hallucination shape**. They feel safe to write because no citation seems possible — but that's exactly why you must NOT write them on instinct.
If you are about to write "X is missing" or "Y is not implemented" — **STOP**. Call \`search_content\` for the relevant symbol or term FIRST. Only then:
- If the search returns matches → you were wrong; correct yourself and cite the matches.
- If the search returns nothing → state the absence with the search query as your evidence: \`No callers of \\\`foo()\\\` found (search_content "foo").\`
Asserting absence without a search is the #1 way evaluative answers go wrong. Treat the urge to write "missing" as a red flag in your own reasoning.
# When to propose a plan (submit_plan)
You have a \`submit_plan\` tool that shows the user a markdown plan and lets them Approve / Refine / Cancel before you execute. Use it proactively when the task is large enough to deserve a review gate:
- Multi-file refactors or renames.
- Architecture changes (moving modules, splitting / merging files, new abstractions).
- Anything where "undo" after the fact would be expensive — migrations, destructive cleanups, API shape changes.
- When the user's request is ambiguous and multiple reasonable interpretations exist — propose your reading as a plan and let them confirm.
Skip submit_plan for small, obvious changes: one-line typo, clear bug with a clear fix, adding a missing import, renaming a local variable. Just do those.
Plan body: one-sentence summary, then a file-by-file breakdown of what you'll change and why, and any risks or open questions. If some decisions are genuinely up to the user (naming, tradeoffs, out-of-scope possibilities), list them in an "Open questions" section — the user sees the plan in a picker and has a text input to answer your questions before approving. Don't pretend certainty you don't have; flagged questions are how the user tells you what they care about. After calling submit_plan, STOP — don't call any more tools, wait for the user's verdict.
**Do NOT use submit_plan to present A/B/C route menus.** The approve/refine/cancel picker has no branch selector — a menu plan strands the user. For branching decisions, use \`ask_choice\` (see below); only call submit_plan once the user has picked a direction and you have ONE actionable plan.
# When to ask the user to pick (ask_choice)
You have an \`ask_choice\` tool. **If the user is supposed to pick between alternatives, the tool picks — you don't enumerate the choices as prose.** Prose menus have no picker in this TUI: the user gets a wall of text and has to type a letter back. The tool fires an arrow-key picker that's strictly better.
Call it when:
- The user has asked for options / doesn't want a recommendation / wants to decide.
- You've analyzed multiple approaches and the final call is theirs.
- It's a preference fork you can't resolve without them (deployment target, team convention, taste).
Skip it when one option is clearly correct (just do it, or submit_plan) or a free-form text answer fits (ask in prose).
Each option: short stable id (A/B/C), one-line title, optional summary. \`allowCustom: true\` when their real answer might not fit. Max 6. A ~1-sentence lead-in before the call is fine ("I see three directions — letting you pick"); don't repeat the options in it. After the call, STOP.
# Plan mode (/plan)
The user can ALSO enter "plan mode" via /plan, which is a stronger, explicit constraint:
- Write tools (edit_file, write_file, create_directory, move_file) and non-allowlisted run_command calls are BOUNCED at dispatch — you'll get a tool result like "unavailable in plan mode". Don't retry them.
- Read tools (read_file, list_directory, search_files, directory_tree, get_file_info) and allowlisted read-only / test shell commands still work — use them to investigate.
- You MUST call submit_plan before anything will execute. Approve exits plan mode; Refine stays in; Cancel exits without implementing.
# Delegating to subagents via Skills
The pinned Skills index below lists playbooks you can invoke with \`run_skill\`. Entries tagged \`[🧬 subagent]\` spawn an **isolated subagent** — a fresh child loop that runs the playbook in its own context and returns only the final answer. The subagent's tool calls and reasoning never enter your context, so subagent skills are how you keep the main session lean.
**When you call \`run_skill\`, the \`name\` is ONLY the identifier before the tag** — e.g. \`run_skill({ name: "explore", arguments: "..." })\`, NOT \`"[🧬 subagent] explore"\` and NOT \`"explore [🧬 subagent]"\`. The tag is display sugar; the name argument is just the bare identifier.
Two built-ins ship by default:
- **explore** \`[🧬 subagent]\` — read-only investigation across the codebase. Use when the user says things like "find all places that...", "how does X work across the project", "survey the code for Y". Pass \`arguments\` describing the concrete question.
- **research** \`[🧬 subagent]\` — combines web search + code reading. Use for "is X supported by lib Y", "what's the canonical way to Z", "compare our impl to the spec".
When to delegate (call \`run_skill\` with a subagent skill):
- The task would otherwise need >5 file reads or searches.
- You only need the conclusion, not the exploration trail.
- The work is self-contained (you can describe it in one paragraph).
When NOT to delegate:
- Direct, narrow questions answerable in 1-2 tool calls — just do them.
- Anything where you need to track intermediate results yourself (planning, multi-step edits).
- Anything that requires user interaction (subagents can't submit plans or ask you for clarification).
Always pass a clear, self-contained \`arguments\` — that text is the **only** context the subagent gets.
# When to edit vs. when to explore
Only propose edits when the user explicitly asks you to change, fix, add, remove, refactor, or write something. Do NOT propose edits when the user asks you to:
- analyze, read, explore, describe, or summarize a project
- explain how something works
- answer a question about the code
In those cases, use tools to gather what you need, then reply in prose. No SEARCH/REPLACE blocks, no file changes. If you're unsure what the user wants, ask.
When you do propose edits, the user will review them and decide whether to \`/apply\` or \`/discard\`. Don't assume they'll accept — write as if each edit will be audited, because it will.
Reasonix runs an **edit gate**. The user's current mode (\`review\` or \`auto\`) decides what happens to your writes; you DO NOT see which mode is active, and you SHOULD NOT ask. Write the same way in both cases.
- In \`auto\` mode \`edit_file\` / \`write_file\` calls land on disk immediately with an undo window — you'll get the normal "edit blocks: 1/1 applied" style response.
- In \`review\` mode EACH \`edit_file\` / \`write_file\` call pauses tool dispatch while the user decides. You'll get one of these responses:
- \`"edit blocks: 1/1 applied"\` — user approved it. Continue as normal.
- \`"User rejected this edit to <path>. Don't retry the same SEARCH/REPLACE…"\` — user said no to THIS specific edit. Do NOT re-emit the same block, do NOT switch tools to sneak it past the gate (write_file → edit_file, or text-form SEARCH/REPLACE). Either take a clearly different approach or stop and ask the user what they want instead.
- Text-form SEARCH/REPLACE blocks in your assistant reply queue for end-of-turn /apply — same "don't retry on rejection" rule.
- If the user presses Esc mid-prompt the whole turn is aborted; you won't get another tool response. Don't keep spamming tool calls after an abort.
# Editing files
When you've been asked to change a file, output one or more SEARCH/REPLACE blocks in this exact format:
path/to/file.ext
<<<<<<< SEARCH
exact existing lines from the file, including whitespace
=======
the new lines
>>>>>>> REPLACE
Rules:
- Always read_file first so your SEARCH matches byte-for-byte. If it doesn't match, the edit is rejected and you'll have to retry with the exact current content.
- One edit per block. Multiple blocks in one response are fine.
- To create a new file, leave SEARCH empty:
path/to/new.ts
<<<<<<< SEARCH
=======
(whole file content here)
>>>>>>> REPLACE
- Do NOT use write_file to change existing files — the user reviews your edits as SEARCH/REPLACE. write_file is only for files you explicitly want to overwrite wholesale (rare).
- Paths are relative to the working directory. Don't use absolute paths.
# Trust what you already know
Before exploring the filesystem to answer a factual question, check whether the answer is already in context: the user's current message, earlier turns in this conversation (including prior tool results from \`remember\`), and the pinned memory blocks at the top of this prompt. When the user has stated a fact or you have remembered one, it outranks what the files say — don't re-derive from code what the user already told you. Explore when you genuinely don't know.
# Exploration
- Skip dependency, build, and VCS directories unless the user explicitly asks. The pinned .gitignore block (if any, below) is your authoritative denylist.
- Prefer \`search_files\` over \`list_directory\` when you know roughly what you're looking for — it saves context and avoids enumerating huge trees. Note: \`search_files\` matches file NAMES; for searching file CONTENTS use \`search_content\`.
- Available exploration tools: \`read_file\`, \`list_directory\`, \`directory_tree\`, \`search_files\` (filename match), \`search_content\` (content grep — use for "where is X called", "find all references to Y"), \`get_file_info\`. Don't call \`grep\` or other tools that aren't in this list — they don't exist as functions.
# Path conventions
Two different rules depending on which tool:
- **Filesystem tools** (\`read_file\`, \`list_directory\`, \`search_files\`, \`edit_file\`, etc.): paths are sandbox-relative. \`/\` means the project root, \`/src/foo.ts\` means \`<project>/src/foo.ts\`. Both relative (\`src/foo.ts\`) and POSIX-absolute (\`/src/foo.ts\`) forms work.
- **\`run_command\`**: the command runs in a real OS shell with cwd pinned to the project root. Paths inside the shell command are interpreted by THAT shell, not by us. **Never use leading \`/\` in run_command arguments** — Windows treats \`/tests\` as drive-root \`F:\\tests\` (non-existent), POSIX shells treat it as filesystem root. Use plain relative paths (\`tests\`, \`./tests\`, \`src/loop.ts\`) instead.
# Foreground vs. background commands
You have TWO tools for running shell commands, and picking the right one is non-negotiable:
- \`run_command\` — blocks until the process exits. Use for: **tests, builds, lints, typechecks, git operations, one-shot scripts**. Anything that naturally returns in under a minute.
- \`run_background\` — spawns and detaches after a brief startup window. Use for: **dev servers, watchers, any command with "dev" / "serve" / "watch" / "start" in the name**. Examples: \`npm run dev\`, \`pnpm dev\`, \`yarn start\`, \`vite\`, \`next dev\`, \`uvicorn app:app --reload\`, \`flask run\`, \`python -m http.server\`, \`cargo watch\`, \`tsc --watch\`, \`webpack serve\`.
**Never use run_command for a dev server.** It will block for 60s, time out, and the user will see a frozen tool call while the server was actually running fine. Always \`run_background\`, then \`job_output\` to peek at the logs when you need to verify something.
After \`run_background\`, tools available to you:
- \`job_output(jobId, tailLines?)\` — read recent logs to verify startup / debug errors.
- \`list_jobs\` — see every job this session (running + exited).
- \`stop_job(jobId)\` — SIGTERM → SIGKILL after grace. Stop before switching port / config.
Don't re-start an already-running dev server — call \`list_jobs\` first when in doubt.
# Scope discipline on "run it" / "start it" requests
When the user's request is to **run / start / launch / serve / boot up** something, your job is ONLY:
1. Start it (\`run_background\` for dev servers, \`run_command\` for one-shots).
2. Verify it came up (read a ready signal via \`job_output\`, or fetch the URL with \`web_fetch\` if they want you to confirm).
3. Report what's running, where (URL / port / pid), and STOP.
Do NOT, in the same turn:
- Run \`tsc\` / type-checkers / linters unless the user asked for it.
- Scan for bugs to "proactively" fix. The page rendering is success.
- Clean up unused imports, dead code, or refactor "while you're here."
- Edit files to improve anything the user didn't mention.
If you notice an obvious issue, MENTION it in one sentence and wait for the user to say "fix it." The cost of over-eagerness is real: you burn tokens, make surprise edits the user didn't want, and chain into cascading "fix the new error I just introduced" loops. The storm-breaker will cut you off, but the user still sees the mess.
"It works" is the end state. Resist the urge to polish.
# Style
- Show edits; don't narrate them in prose. "Here's the fix:" is enough.
- One short paragraph explaining *why*, then the blocks.
- If you need to explore first (list / read / search), do it with tool calls before writing any prose — silence while exploring is fine.
${ESCALATION_CONTRACT}
${TUI_FORMATTING_RULES}
`;
/**
* Inject the project's `.gitignore` content into the system prompt as a
* "respect this on top of the built-in denylist" hint. We don't parse
* the file — we hand it to the model as-is. Truncate long ones so we
* don't eat context budget on huge generated ignore lists.
*
* Stacking order (stable for cache prefix):
* base prompt → REASONIX.md → global MEMORY.md → project MEMORY.md → .gitignore
*/
export function codeSystemPrompt(rootDir: string): string {
const withMemory = applyMemoryStack(CODE_SYSTEM_PROMPT, rootDir);
const gitignorePath = join(rootDir, ".gitignore");
if (!existsSync(gitignorePath)) return withMemory;
let content: string;
try {
content = readFileSync(gitignorePath, "utf8");
} catch {
return withMemory;
}
const MAX = 2000;
const truncated =
content.length > MAX
? `${content.slice(0, MAX)}\n… (truncated ${content.length - MAX} chars)`
: content;
return `${withMemory}
# Project .gitignore
The user's repo ships this .gitignore — treat every pattern as "don't traverse or edit inside these paths unless explicitly asked":
\`\`\`
${truncated}
\`\`\`
`;
}
+173
View File
@@ -8,15 +8,92 @@
* The library itself never touches the config file — it only reads
* `DEEPSEEK_API_KEY` from the environment. The CLI is responsible for
* pulling from the config file and exposing it via env var to the loop.
*
* Beyond the API key, the config also remembers the user's *defaults*
* from `reasonix setup`: preset, MCP servers, session. This is what
* makes `reasonix chat` with no flags "just work" after first-run.
*/
import { chmodSync, mkdirSync, readFileSync, writeFileSync } from "node:fs";
import { homedir } from "node:os";
import { dirname, join } from "node:path";
/** One of the preset bundles (model + harvest + branch combo). */
export type PresetName = "fast" | "smart" | "max";
/**
* How `reasonix code` handles model-issued edits:
* - "review" — queue the edit into pendingEdits; user /apply or `y` commits.
* - "auto" — apply immediately, snapshot for /undo, show a short undo
* banner so the user can roll back with one keystroke.
* Persisted so `/mode auto` survives a relaunch. Missing → "review".
*/
export type EditMode = "review" | "auto";
/**
* reasoning_effort cap for the model. "max" is the agent-class default;
* "high" is cheaper / faster. Persisted so `/effort high` survives a
* relaunch — earlier versions silently reverted to "max" on every new
* session, which burned budget unexpectedly.
*/
export type ReasoningEffort = "high" | "max";
export interface ReasonixConfig {
apiKey?: string;
baseUrl?: string;
/**
* Default preset for `reasonix chat` / `reasonix run` when no flags override.
* Maps to model + harvest + branch combos (see presets.ts). Missing → "fast".
*/
preset?: PresetName;
/**
* Edit-gate mode for `reasonix code`. See EditMode doc. Absent → "review".
*/
editMode?: EditMode;
/**
* Set to `true` the first time we've shown the "Shift+Tab cycles
* review/AUTO" onboarding tip in `reasonix code`. Once seen, we stop
* posting the tip — the bottom status bar carries the knowledge
* forward without further nagging.
*/
editModeHintShown?: boolean;
/**
* Last reasoning_effort chosen via `/effort`. Loaded on launch so
* "high" stays "high" — default is "max" when unset.
*/
reasoningEffort?: ReasoningEffort;
/**
* Default MCP server specs to bridge on every `reasonix chat`, in the
* same `"name=cmd args..."` format that `--mcp` takes. Stored as strings
* so `reasonix setup` stays symmetrical with the flag — one parser, one
* format in the config file, grep-friendly.
*/
mcp?: string[];
/**
* Default session name (null/missing → "default", which is what the
* CLI has been doing anyway). `reasonix setup` lets users pick a name
* or opt into ephemeral.
*/
session?: string | null;
/** Marks that `reasonix setup` has completed at least once. */
setupCompleted?: boolean;
/**
* Whether `web_search` + `web_fetch` tools are registered. Default:
* enabled (no key required — backed by DuckDuckGo's public HTML
* endpoint). Set to `false` to keep the session offline.
*/
search?: boolean;
/**
* Per-project state keyed by absolute directory path. Written by the
* "always allow" choice on a shell confirmation prompt; merged into
* `registerShellTools({ extraAllowed })` when `reasonix code` runs
* against that directory again.
*/
projects?: {
[absoluteRootDir: string]: {
shellAllowed?: string[];
};
};
}
export function defaultConfigPath(): string {
@@ -51,12 +128,108 @@ export function loadApiKey(path: string = defaultConfigPath()): string | undefin
return readConfig(path).apiKey;
}
/**
* Resolve whether web-search tools should be registered. Default: on.
* Env `REASONIX_SEARCH=off` or config `search: false` turns it off.
* Any other value falls through to enabled.
*/
export function searchEnabled(path: string = defaultConfigPath()): boolean {
const env = process.env.REASONIX_SEARCH;
if (env === "off" || env === "false" || env === "0") return false;
const cfg = readConfig(path).search;
if (cfg === false) return false;
return true;
}
export function saveApiKey(key: string, path: string = defaultConfigPath()): void {
const cfg = readConfig(path);
cfg.apiKey = key.trim();
writeConfig(cfg, path);
}
/**
* Read the persisted "always allow" shell-command prefixes for a
* given project root. Returns an empty array when nothing's stored.
*/
export function loadProjectShellAllowed(
rootDir: string,
path: string = defaultConfigPath(),
): string[] {
const cfg = readConfig(path);
return cfg.projects?.[rootDir]?.shellAllowed ?? [];
}
/**
* Append a prefix to the project's shell-allowed list, dedup and
* persist. No-op if the prefix is empty/whitespace or already stored.
*/
export function addProjectShellAllowed(
rootDir: string,
prefix: string,
path: string = defaultConfigPath(),
): void {
const trimmed = prefix.trim();
if (!trimmed) return;
const cfg = readConfig(path);
if (!cfg.projects) cfg.projects = {};
if (!cfg.projects[rootDir]) cfg.projects[rootDir] = {};
const existing = cfg.projects[rootDir].shellAllowed ?? [];
if (existing.includes(trimmed)) return;
cfg.projects[rootDir].shellAllowed = [...existing, trimmed];
writeConfig(cfg, path);
}
/**
* Read the persisted edit-mode. Unknown values fall back to "review" so
* a user who hand-edits the file into an invalid state still gets the
* safe default. `reasonix code` calls this at launch and the App lets
* `/mode` / Shift+Tab flip it.
*/
export function loadEditMode(path: string = defaultConfigPath()): EditMode {
const v = readConfig(path).editMode;
return v === "auto" ? "auto" : "review";
}
/** Persist the edit mode so `/mode auto` survives a relaunch. */
export function saveEditMode(mode: EditMode, path: string = defaultConfigPath()): void {
const cfg = readConfig(path);
cfg.editMode = mode;
writeConfig(cfg, path);
}
/** True when the onboarding tip for the review/AUTO gate has been shown. */
export function editModeHintShown(path: string = defaultConfigPath()): boolean {
return readConfig(path).editModeHintShown === true;
}
/**
* Read the persisted reasoning_effort. Unknown / missing values fall
* back to "max" so the agent-class default is never silently overridden
* by a hand-edited bad value in config.json.
*/
export function loadReasoningEffort(path: string = defaultConfigPath()): ReasoningEffort {
const v = readConfig(path).reasoningEffort;
return v === "high" ? "high" : "max";
}
/** Persist the reasoning_effort cap so `/effort high` survives a relaunch. */
export function saveReasoningEffort(
effort: ReasoningEffort,
path: string = defaultConfigPath(),
): void {
const cfg = readConfig(path);
cfg.reasoningEffort = effort;
writeConfig(cfg, path);
}
/** Mark the onboarding tip as shown so subsequent launches skip it. */
export function markEditModeHintShown(path: string = defaultConfigPath()): void {
const cfg = readConfig(path);
if (cfg.editModeHintShown === true) return;
cfg.editModeHintShown = true;
writeConfig(cfg, path);
}
export function isPlausibleKey(key: string): boolean {
const trimmed = key.trim();
return /^sk-[A-Za-z0-9_-]{16,}$/.test(trimmed);
+48
View File
@@ -271,6 +271,43 @@ export function renderSummaryTable(report: DiffReport, _opts: RenderOptions = {}
),
);
lines.push(statRow("prefix hashes", a.stats.prefixHashes.length, b.stats.prefixHashes.length));
// Harvest signal row — only surface when at least one side carries plan
// state. Keeps no-harvest diffs visually identical to pre-v0.3 output.
if (a.stats.harvestedTurns > 0 || b.stats.harvestedTurns > 0) {
lines.push(
row(
[
"harvest turns",
`${a.stats.harvestedTurns}`,
`${b.stats.harvestedTurns}`,
signed(b.stats.harvestedTurns - a.stats.harvestedTurns),
],
[20, 14, 14, 14],
),
);
lines.push(
row(
[
" subgoals",
`${a.stats.totalSubgoals}`,
`${b.stats.totalSubgoals}`,
signed(b.stats.totalSubgoals - a.stats.totalSubgoals),
],
[20, 14, 14, 14],
),
);
lines.push(
row(
[
" uncertainties",
`${a.stats.totalUncertainties}`,
`${b.stats.totalUncertainties}`,
signed(b.stats.totalUncertainties - a.stats.totalUncertainties),
],
[20, 14, 14, 14],
),
);
}
lines.push("");
// Prefix stability story — the headline finding when comparing bench modes.
@@ -348,6 +385,17 @@ export function renderMarkdown(report: DiffReport): string {
out.push(
`| prefix hashes | ${a.stats.prefixHashes.length} | ${b.stats.prefixHashes.length} | — |`,
);
if (a.stats.harvestedTurns > 0 || b.stats.harvestedTurns > 0) {
out.push(
`| harvest turns | ${a.stats.harvestedTurns} | ${b.stats.harvestedTurns} | ${signed(b.stats.harvestedTurns - a.stats.harvestedTurns)} |`,
);
out.push(
`| harvest subgoals | ${a.stats.totalSubgoals} | ${b.stats.totalSubgoals} | ${signed(b.stats.totalSubgoals - a.stats.totalSubgoals)} |`,
);
out.push(
`| harvest uncertainties | ${a.stats.totalUncertainties} | ${b.stats.totalUncertainties} | ${signed(b.stats.totalUncertainties - a.stats.totalUncertainties)} |`,
);
}
out.push("");
out.push("## Turn-by-turn");
+20 -1
View File
@@ -68,13 +68,24 @@ export async function harvest(
reasoningContent: string | null | undefined,
client?: DeepSeekClient,
options: HarvestOptions = {},
signal?: AbortSignal,
): Promise<TypedPlanState> {
if (!client || !reasoningContent) return emptyPlanState();
// Fast-path the already-aborted case so we don't burn a network
// round-trip for a result the caller no longer wants.
if (signal?.aborted) return emptyPlanState();
const minLen = options.minReasoningLen ?? 40;
const trimmed = reasoningContent.trim();
if (trimmed.length < minLen) return emptyPlanState();
const model = options.model ?? "deepseek-chat";
// Harvest is schema-constrained JSON extraction, not agent reasoning.
// Default to v4-flash with `thinking: "disabled"` below — a few
// hundred output tokens fit easily in the non-thinking budget, the
// reply comes back ~10× faster than thinking mode, and the per-turn
// cost stays an asterisk next to the main loop's spend rather than a
// visible slice of it. (`deepseek-chat` was the compat alias for this
// same route; we now name the real model.)
const model = options.model ?? "deepseek-v4-flash";
const maxItems = options.maxItems ?? 5;
const maxItemLen = options.maxItemLen ?? 80;
const system = SYSTEM_PROMPT.replace("{maxItems}", String(maxItems)).replace(
@@ -92,6 +103,14 @@ export async function harvest(
responseFormat: { type: "json_object" },
temperature: 0,
maxTokens: 600,
// Pin mode + effort so a future default-model swap (e.g. someone
// sets `options.model = "deepseek-v4-pro"`) can't accidentally
// turn this micro-extraction into a multi-thousand-reasoning-
// token call. DeepSeek ignores these on non-thinking models, so
// the request stays valid regardless of the chosen model.
thinking: "disabled",
reasoningEffort: "high",
signal,
});
return parsePlanState(resp.content, maxItems, maxItemLen);
} catch {
+404
View File
@@ -0,0 +1,404 @@
/**
* Hooks — user-defined automation that fires at well-known points in
* the agent loop. Mirrors the two-scope layout we use for memory and
* skills:
*
* - `<project>/.reasonix/settings.json` — committable per-project
* - `~/.reasonix/settings.json` — every session
*
* A hook is a shell command. We invoke it with stdin = a JSON
* payload describing the event, and interpret the exit code:
*
* - `0` — pass; loop continues normally
* - `2` — block; for `PreToolUse` / `UserPromptSubmit` the
* loop refuses to continue with that step and surfaces the
* hook's stderr as the reason. For `PostToolUse` / `Stop` block
* is meaningless (the action already happened) — treat as warn.
* - anything else — warn; loop continues but stderr is rendered
* to the user as an inline notice.
*
* stdin JSON shape (one envelope per event):
*
* {
* "event": "PreToolUse" | "PostToolUse" | "UserPromptSubmit" | "Stop",
* "cwd": "<absolute project root or process.cwd()>",
* "toolName": "<string>", // tool events only
* "toolArgs": <unknown>, // tool events only — already JSON-decoded
* "toolResult": "<string>", // PostToolUse only — same body the model sees
* "prompt": "<string>", // UserPromptSubmit only
* "lastAssistantText": "<string>", // Stop only
* "turn": <number>, // Stop only
* }
*
* Hooks are executed in order: project scope first, then global.
* `Pre*` events stop dispatching at the first block; non-block
* outcomes accumulate into a single report so the UI can render
* each warning inline.
*/
import { spawn } from "node:child_process";
import { existsSync, readFileSync } from "node:fs";
import { homedir } from "node:os";
import { join } from "node:path";
export type HookEvent = "PreToolUse" | "PostToolUse" | "UserPromptSubmit" | "Stop";
/** All four events as a const array — drives slash listing + validation. */
export const HOOK_EVENTS: readonly HookEvent[] = [
"PreToolUse",
"PostToolUse",
"UserPromptSubmit",
"Stop",
] as const;
/** Only the gating events can block the loop. */
const BLOCKING_EVENTS: ReadonlySet<HookEvent> = new Set(["PreToolUse", "UserPromptSubmit"]);
/** Per-event default timeout. Tool/prompt hooks gate progress, so they're tight. */
const DEFAULT_TIMEOUTS_MS: Record<HookEvent, number> = {
PreToolUse: 5_000,
UserPromptSubmit: 5_000,
PostToolUse: 30_000,
Stop: 30_000,
};
export type HookScope = "project" | "global";
export interface HookConfig {
/**
* Tool-name pattern (PreToolUse / PostToolUse only). Anchored regex.
* Omitted or `"*"` matches every tool. Ignored for prompt / Stop
* events (they have no tool name to match against).
*/
match?: string;
/** Shell command to run. Spawned through the platform shell. */
command: string;
/** Optional human description — surfaced in `/hooks`. */
description?: string;
/** Per-hook timeout override in ms. */
timeout?: number;
/**
* Working directory for the spawned process. Defaults to:
* - project scope → the project root
* - global scope → process.cwd()
*/
cwd?: string;
}
/** Shape of `<scope>/.reasonix/settings.json` — only `hooks` for now. */
export interface HookSettings {
hooks?: Partial<Record<HookEvent, HookConfig[]>>;
}
/** A loaded hook with its origin scope baked in (used for ordering and `/hooks`). */
export interface ResolvedHook extends HookConfig {
event: HookEvent;
scope: HookScope;
/** Absolute path to the settings.json the hook came from. */
source: string;
}
/** Outcome of a single hook invocation. */
export interface HookOutcome {
/** Which hook fired. */
hook: ResolvedHook;
/**
* Decision:
* - `pass` — exit 0
* - `block` — exit 2 on a blocking event (otherwise downgraded to `warn`)
* - `warn` — non-zero exit that is not a successful block
* - `timeout` — the spawn was killed past `timeout`
* - `error` — could not spawn at all (missing command, etc.)
*/
decision: "pass" | "block" | "warn" | "timeout" | "error";
exitCode: number | null;
/** Captured stdout (trimmed). May be empty. */
stdout: string;
/** Captured stderr (trimmed). The block / warn message comes from here. */
stderr: string;
durationMs: number;
}
/** Aggregate report for `runHooks`. */
export interface HookReport {
event: HookEvent;
outcomes: HookOutcome[];
/** True iff at least one outcome was a `block` — only meaningful for blocking events. */
blocked: boolean;
}
export const HOOK_SETTINGS_FILENAME = "settings.json";
export const HOOK_SETTINGS_DIRNAME = ".reasonix";
/** Where the global settings.json lives. Equivalent to `~/.reasonix/settings.json`. */
export function globalSettingsPath(homeDirOverride?: string): string {
return join(homeDirOverride ?? homedir(), HOOK_SETTINGS_DIRNAME, HOOK_SETTINGS_FILENAME);
}
/** Where the project settings.json lives for a given root. */
export function projectSettingsPath(projectRoot: string): string {
return join(projectRoot, HOOK_SETTINGS_DIRNAME, HOOK_SETTINGS_FILENAME);
}
function readSettingsFile(path: string): HookSettings | null {
if (!existsSync(path)) return null;
try {
const raw = readFileSync(path, "utf8");
const parsed = JSON.parse(raw);
if (parsed && typeof parsed === "object") return parsed as HookSettings;
} catch {
/* malformed JSON → treat as no hooks; do NOT throw, the user
* shouldn't lose the whole CLI to a typo in their settings */
}
return null;
}
/**
* Pull every configured hook out of the project + global settings
* files, in the order they should fire (project first, global second,
* within each scope: array order from the file).
*
* Returns a flat list — the dispatcher filters by event + match
* pattern at run time. Loading is cheap (one or two JSON files), so
* we don't memoize across processes; re-load is allowed via
* `/hooks reload` and on every fresh App mount.
*/
export interface LoadHookSettingsOptions {
/** Absolute project root, if any. Without it, only global hooks load. */
projectRoot?: string;
/** Override `~` for tests. */
homeDir?: string;
}
export function loadHooks(opts: LoadHookSettingsOptions = {}): ResolvedHook[] {
const out: ResolvedHook[] = [];
if (opts.projectRoot) {
const projPath = projectSettingsPath(opts.projectRoot);
const settings = readSettingsFile(projPath);
if (settings) appendResolved(out, settings, "project", projPath);
}
const globalPath = globalSettingsPath(opts.homeDir);
const settings = readSettingsFile(globalPath);
if (settings) appendResolved(out, settings, "global", globalPath);
return out;
}
function appendResolved(
out: ResolvedHook[],
settings: HookSettings,
scope: HookScope,
source: string,
): void {
if (!settings.hooks) return;
for (const event of HOOK_EVENTS) {
const list = settings.hooks[event];
if (!Array.isArray(list)) continue;
for (const cfg of list) {
if (!cfg || typeof cfg.command !== "string" || cfg.command.trim() === "") continue;
out.push({ ...cfg, event, scope, source });
}
}
}
/**
* True if `toolName` matches the hook's `match` field. `"*"` and
* undefined match everything. Otherwise we anchor the field as a
* regex — partial-name matches don't fire, so `"file"` would not
* trigger on `read_file` (use `".*file"` for that).
*/
export function matchesTool(hook: ResolvedHook, toolName: string): boolean {
if (hook.event !== "PreToolUse" && hook.event !== "PostToolUse") return true;
const m = hook.match;
if (!m || m === "*") return true;
try {
const re = new RegExp(`^(?:${m})$`);
return re.test(toolName);
} catch {
/* malformed regex → don't fire (safer than firing on every tool) */
return false;
}
}
/** Payload envelope passed to hook stdin. */
export interface HookPayload {
event: HookEvent;
cwd: string;
toolName?: string;
toolArgs?: unknown;
toolResult?: string;
prompt?: string;
lastAssistantText?: string;
turn?: number;
}
/** Test seam — same shape as Node's spawn but returns a Promise of the raw outcome bits. */
export interface HookSpawnInput {
command: string;
cwd: string;
stdin: string;
timeoutMs: number;
}
export interface HookSpawnResult {
exitCode: number | null;
stdout: string;
stderr: string;
timedOut: boolean;
/** True iff spawn() itself failed (ENOENT, EACCES, …). */
spawnError?: Error;
}
export type HookSpawner = (input: HookSpawnInput) => Promise<HookSpawnResult>;
/**
* Default spawner — runs `command` through the platform shell so
* `&&`, pipes, env-var expansion all work without a tokenizer.
* Stdin is the JSON payload, stdout / stderr are buffered.
*
* Why `shell: true`? A hook is intentionally a shell command — that's
* the contract. Treating it like an argv array would surprise users
* who write `bun run check && eslint .` and expect it to behave the
* way it does in their terminal.
*/
function defaultSpawner(input: HookSpawnInput): Promise<HookSpawnResult> {
return new Promise<HookSpawnResult>((resolve) => {
const child = spawn(input.command, {
cwd: input.cwd,
shell: true,
stdio: ["pipe", "pipe", "pipe"],
});
let stdout = "";
let stderr = "";
let timedOut = false;
const timer = setTimeout(() => {
timedOut = true;
child.kill("SIGTERM");
// SIGTERM may not land on Windows for shell children — followed
// by a hard kill a moment later if the process is still around.
setTimeout(() => {
try {
child.kill("SIGKILL");
} catch {
/* already gone */
}
}, 500);
}, input.timeoutMs);
child.stdout.on("data", (chunk: Buffer) => {
stdout += chunk.toString("utf8");
});
child.stderr.on("data", (chunk: Buffer) => {
stderr += chunk.toString("utf8");
});
child.once("error", (err) => {
clearTimeout(timer);
resolve({
exitCode: null,
stdout,
stderr,
timedOut: false,
spawnError: err,
});
});
child.once("close", (code) => {
clearTimeout(timer);
resolve({
exitCode: code,
stdout: stdout.trim(),
stderr: stderr.trim(),
timedOut,
});
});
try {
child.stdin.write(input.stdin);
child.stdin.end();
} catch {
/* stdin write can race with spawn errors; the close handler
* still fires with exit 0/null */
}
});
}
/**
* Format a hook outcome as a single-line UI string. Used by both the
* loop (for `warning` events) and the App (for UserPromptSubmit /
* Stop outcomes). Centralizing keeps the language consistent across
* scopes.
*/
export function formatHookOutcomeMessage(outcome: HookOutcome): string {
if (outcome.decision === "pass") return "";
const detail = (outcome.stderr || outcome.stdout || "").trim();
const tag = `${outcome.hook.scope}/${outcome.hook.event}`;
const cmd =
outcome.hook.command.length > 60
? `${outcome.hook.command.slice(0, 60)}…`
: outcome.hook.command;
const head = `hook ${tag} \`${cmd}\` ${outcome.decision}`;
return detail ? `${head}: ${detail}` : head;
}
/**
* Decide the hook's outcome decision from raw spawn results.
* Pulled out as a pure function so tests can pin the matrix.
*/
export function decideOutcome(
event: HookEvent,
raw: HookSpawnResult,
): "pass" | "block" | "warn" | "timeout" | "error" {
if (raw.spawnError) return "error";
if (raw.timedOut) return BLOCKING_EVENTS.has(event) ? "block" : "warn";
if (raw.exitCode === 0) return "pass";
if (raw.exitCode === 2 && BLOCKING_EVENTS.has(event)) return "block";
return "warn";
}
export interface RunHooksOptions {
payload: HookPayload;
hooks: ResolvedHook[];
/** Test seam — defaults to a real `spawn`. */
spawner?: HookSpawner;
}
/**
* Filter hooks down to the ones that match `payload.event` (and
* `payload.toolName`, for tool events), then run them in order.
* Stops at the first `block` outcome on a blocking event so a
* gating hook can prevent later hooks from incorrectly seeing a
* success that wasn't going to happen.
*/
export async function runHooks(opts: RunHooksOptions): Promise<HookReport> {
const spawner = opts.spawner ?? defaultSpawner;
const event = opts.payload.event;
const toolName = opts.payload.toolName ?? "";
const matching = opts.hooks.filter((h) => h.event === event && matchesTool(h, toolName));
const outcomes: HookOutcome[] = [];
let blocked = false;
const stdin = `${JSON.stringify(opts.payload)}\n`;
for (const hook of matching) {
const start = Date.now();
const timeoutMs = hook.timeout ?? DEFAULT_TIMEOUTS_MS[event];
const cwd = hook.cwd ?? opts.payload.cwd;
const raw = await spawner({ command: hook.command, cwd, stdin, timeoutMs });
const decision = decideOutcome(event, raw);
outcomes.push({
hook,
decision,
exitCode: raw.exitCode,
stdout: raw.stdout,
stderr:
raw.stderr ||
(raw.spawnError ? raw.spawnError.message : "") ||
(raw.timedOut ? `hook timed out after ${timeoutMs}ms` : ""),
durationMs: Date.now() - start,
});
if (decision === "block") {
blocked = true;
break;
}
}
return { event, outcomes, blocked };
}
+232 -5
View File
@@ -3,7 +3,33 @@
export { DeepSeekClient, Usage } from "./client.js";
export type { ChatResponse, StreamChunk, DeepSeekClientOptions } from "./client.js";
export { CacheFirstLoop } from "./loop.js";
export {
CacheFirstLoop,
formatLoopError,
fixToolCallPairing,
healLoadedMessages,
healLoadedMessagesByTokens,
stripHallucinatedToolMarkup,
} from "./loop.js";
export {
AT_MENTION_PATTERN,
AT_PICKER_PREFIX,
DEFAULT_AT_MENTION_MAX_BYTES,
DEFAULT_PICKER_IGNORE_DIRS,
detectAtPicker,
expandAtMentions,
listFilesSync,
listFilesWithStatsSync,
rankPickerCandidates,
} from "./at-mentions.js";
export type {
AtMentionExpansion,
AtMentionOptions,
FileWithStats,
ListFilesOptions,
PickerCandidate,
RankPickerOptions,
} from "./at-mentions.js";
export type {
CacheFirstLoopOptions,
LoopEvent,
@@ -24,10 +50,92 @@ export type {
export { ImmutablePrefix, AppendOnlyLog, VolatileScratch } from "./memory.js";
export type { ImmutablePrefixOptions } from "./memory.js";
export { ToolRegistry } from "./tools.js";
export type { ToolDefinition } from "./tools.js";
export {
PROJECT_MEMORY_FILE,
PROJECT_MEMORY_MAX_CHARS,
applyProjectMemory,
memoryEnabled,
readProjectMemory,
} from "./project-memory.js";
export type { ProjectMemory } from "./project-memory.js";
export { SessionStats, costUsd, claudeEquivalentCost } from "./telemetry.js";
export {
MEMORY_INDEX_FILE,
MEMORY_INDEX_MAX_CHARS,
MemoryStore,
USER_MEMORY_DIR,
applyMemoryStack,
applyUserMemory,
projectHash,
sanitizeMemoryName,
} from "./user-memory.js";
export type {
MemoryEntry,
MemoryScope,
MemoryStoreOptions,
MemoryType,
WriteInput as MemoryWriteInput,
} from "./user-memory.js";
export { ToolRegistry } from "./tools.js";
export type { ToolDefinition, ToolCallContext } from "./tools.js";
export { registerFilesystemTools } from "./tools/filesystem.js";
export type { FilesystemToolsOptions } from "./tools/filesystem.js";
export { registerMemoryTools } from "./tools/memory.js";
export type { MemoryToolsOptions } from "./tools/memory.js";
export { ChoiceRequestedError, registerChoiceTool } from "./tools/choice.js";
export type { ChoiceOption, ChoiceToolOptions } from "./tools/choice.js";
export {
PlanCheckpointError,
PlanProposedError,
PlanRevisionProposedError,
registerPlanTool,
} from "./tools/plan.js";
export type { PlanStep, PlanStepRisk, PlanToolOptions, StepCompletion } from "./tools/plan.js";
export { forkRegistryExcluding, registerSubagentTool } from "./tools/subagent.js";
export type {
SubagentEvent,
SubagentSink,
SubagentToolOptions,
} from "./tools/subagent.js";
export {
NeedsConfirmationError,
detectShellOperator,
formatCommandResult,
injectPowerShellUtf8,
isAllowed,
prepareSpawn,
quoteForCmdExe,
registerShellTools,
resolveExecutable,
runCommand,
tokenizeCommand,
withUtf8Codepage,
} from "./tools/shell.js";
export type { RunCommandResult, ShellToolsOptions } from "./tools/shell.js";
export {
formatSearchResults,
htmlToText,
parseMojeekResults,
registerWebTools,
webFetch,
webSearch,
} from "./tools/web.js";
export type {
PageContent,
SearchResult,
WebFetchOptions,
WebSearchOptions,
WebToolsOptions,
} from "./tools/web.js";
export {
SessionStats,
costUsd,
inputCostUsd,
outputCostUsd,
claudeEquivalentCost,
} from "./telemetry.js";
export type { TurnStats, SessionSummary } from "./telemetry.js";
export {
@@ -85,6 +193,73 @@ export {
} from "./diff.js";
export type { DiffReport, DiffSide, TurnPair, RenderOptions as DiffRenderOptions } from "./diff.js";
// ---------- MCP (v0.3 foundation) ----------
export { McpClient } from "./mcp/client.js";
export type { McpClientOptions } from "./mcp/client.js";
export { StdioTransport } from "./mcp/stdio.js";
export type { McpTransport, StdioTransportOptions } from "./mcp/stdio.js";
export { SseTransport } from "./mcp/sse.js";
export type { SseTransportOptions } from "./mcp/sse.js";
export {
DEFAULT_MAX_RESULT_CHARS,
DEFAULT_MAX_RESULT_TOKENS,
bridgeMcpTools,
flattenMcpResult,
truncateForModel,
truncateForModelByTokens,
} from "./mcp/registry.js";
export type { BridgeOptions, BridgeResult, FlattenOptions } from "./mcp/registry.js";
export { parseMcpSpec } from "./mcp/spec.js";
export type { McpSpec, StdioMcpSpec, SseMcpSpec } from "./mcp/spec.js";
export { inspectMcpServer } from "./mcp/inspect.js";
export type { InspectionReport, SectionResult } from "./mcp/inspect.js";
// ---------- code mode (v0.3 — `reasonix code`) ----------
export {
parseEditBlocks,
applyEditBlock,
applyEditBlocks,
snapshotBeforeEdits,
restoreSnapshots,
} from "./code/edit-blocks.js";
export type {
EditBlock,
ApplyResult,
ApplyStatus,
EditSnapshot,
} from "./code/edit-blocks.js";
export { CODE_SYSTEM_PROMPT, codeSystemPrompt } from "./code/prompt.js";
export {
MCP_PROTOCOL_VERSION,
isJsonRpcError,
} from "./mcp/types.js";
export type {
McpTool,
McpToolSchema,
CallToolResult,
ListToolsResult,
McpContentBlock,
InitializeResult,
JsonRpcRequest,
JsonRpcResponse,
JsonRpcMessage,
McpResource,
McpResourceContents,
McpResourceContentsText,
McpResourceContentsBlob,
ListResourcesResult,
ReadResourceResult,
McpPrompt,
McpPromptArgument,
McpPromptMessage,
McpPromptResourceBlock,
ListPromptsResult,
GetPromptResult,
McpProgressHandler,
McpProgressInfo,
ProgressNotificationParams,
} from "./mcp/types.js";
export { fetchWithRetry } from "./retry.js";
export type { RetryOptions, RetryInfo } from "./retry.js";
@@ -108,4 +283,56 @@ export type {
JSONSchema,
} from "./types.js";
export const VERSION = "0.2.2";
export {
LATEST_CACHE_TTL_MS,
LATEST_FETCH_TIMEOUT_MS,
VERSION,
compareVersions,
getLatestVersion,
isNpxInstall,
} from "./version.js";
export type { GetLatestVersionOptions } from "./version.js";
export {
HOOK_EVENTS,
HOOK_SETTINGS_DIRNAME,
HOOK_SETTINGS_FILENAME,
decideOutcome,
formatHookOutcomeMessage,
globalSettingsPath,
loadHooks,
matchesTool,
projectSettingsPath,
runHooks,
} from "./hooks.js";
export {
aggregateUsage,
appendUsage,
bucketCacheHitRatio,
bucketSavingsFraction,
defaultUsageLogPath,
formatLogSize,
readUsageLog,
} from "./usage.js";
export type {
AggregateOptions,
AppendUsageInput,
UsageAggregate,
UsageBucket,
UsageRecord,
} from "./usage.js";
export type {
HookConfig,
HookEvent,
HookOutcome,
HookPayload,
HookReport,
HookScope,
HookSettings,
HookSpawner,
HookSpawnInput,
HookSpawnResult,
LoadHookSettingsOptions,
ResolvedHook,
RunHooksOptions,
} from "./hooks.js";
Loaded 100 of 199 files, more files were not shown because too many files have changed in this diff. Show more