The CI sync step failed on v0.43.0 because the release commit had
already bumped Cargo.toml to the target version. The old guard fired
on `nextCargo === cargoToml` — true both when the regex didn't match
AND when the value was already correct. Switch to checking whether
the version line exists at all; re-syncing to the same value is
legitimate.
Co-authored-by: test <[email protected]>
Today a skill_run dispatches via the palette and the user sees nothing
until the assistant response streams — no signal that "a skill kicked
this off" vs "a regular long turn." Closes#882.
Add two surfaces, both driven by client-side state (no protocol
churn):
1. Live status row — `InterruptBar` now reads `state.activeSkill` and
labels itself `Skill · <name>` instead of `Reasoning` for the
duration of the turn, with the same elapsed timer + esc-to-stop
affordance.
2. User-message card chip — the synthetic user card injected by
`start_skill` carries a `skill: { name, runAs }` field. `UserMsg`
renders a warning-toned `/name` chip in the header (plus a
subagent micro-badge when `runAs === "subagent"`).
State:
- `activeSkill: SkillOrigin | null` on `State`; set by `start_skill`,
cleared on `$turn_complete`, `clear`, `$session_loaded`, `error`,
and `rpc_exit`.
- `start_skill` action also pushes a user-card row tagged with the
skill, so the thread now shows `/skillname` instead of being silent
until the assistant replies.
No backend changes — `$turn_complete` is the natural cleanup signal,
no new event types needed.
Co-authored-by: test <[email protected]>
The sidebar's per-workspace session filter compared paths via strict
`===` against `meta.workspace`. On Windows that's fragile — drive
letter case, separator style (`\` vs `/`), and trailing slashes drift
between session writes and reads, so yesterday's sessions silently
disappeared from today's sidebar even though the .jsonl files were
still on disk.
Add `normalizeWorkspace` that resolves and canonicalizes the path
before comparison (forward-slash separators, lowercase drive letter
on win32). Apply on both sides of the filter so sessions whose meta
was written before this fix recover automatically — no migration
needed.
Sessions with no `meta.workspace` stay hidden, same as before;
resume by name still works.
Closes#878
Co-authored-by: test <[email protected]>
The slash command popup hard-coded 9 built-in actions and never
folded in the user's `~/.reasonix/skills` and `.reasonix/skills`
entries — typing `/myskill` produced "no matches" even though the
skill loaded fine and showed up in the Skills tab. Skills also had
no execution path on the desktop side at all: `user_input` ships
text straight to the model loop, so a typed `/skill_name` reached
the model as plain text rather than triggering the skill.
- Add a `skill_run` RPC to the desktop protocol.
- Bridge handler resolves the skill via `SkillStore`, builds the
same `# Skill: <name>\n> <desc>\n\n<body>` payload the CLI uses,
and feeds it through `runTurn` so the skill enters the
conversation as user-authored content.
- `App.tsx` merges `state.skills` into `slashCommands` so each
user-authored skill shows up in the popup with its description
and an invocation handler that fires `skill_run`.
Issue #854 also asked for a "skill is running" indicator. That's a
separate UX surface (status row / live row) and lands separately.
Closes#854 (autocomplete half) — follow-up issue for the indicator.
`/api/plans` walked every session via `listSessions()` (which calls
`countLines()` on every `.jsonl`) and then `listPlanArchives(name)`
per session (which re-scanned the same directory each time). On a
real developer machine with hundreds of sessions and large JSONL
files the handler ran past the 5s test timeout and got flagged in
CI as flaky.
Replace the per-session loop with a single dir-scan helper —
`listAllPlanArchives()` in `plan-store.ts` — that derives the
session name from the archive filename. The dashboard plans
handler now does O(N) work over plan-archive files instead of
O(sessions × archives) over the full session corpus.
Confirmed locally: full test suite drops from intermittent timeouts
to consistently green.
Co-authored-by: test <[email protected]>
Two follow-ups to #877 plus a long-standing typecheck cleanup:
Font family — sans / system / serif segmented control under appearance.
Driven by a new `--font-sans` CSS variable on the root element;
styles.css and the inline `IBM Plex Sans` reference in App.tsx now
read through `var(--font-sans, ...)`. Mono is left hardcoded so code
blocks and transcripts stay monospace either way.
Language — promote the existing `/lang` palette command into a 中文 /
English segmented control in the same section. Reads `useLang()` and
writes through `setLang()`; the slash command keeps working.
i18n cleanup — add the long-missing `contextPanel`, `extraCards`,
and `thread` namespaces (en + zh-CN). These keys were referenced in
code but absent from the dictionaries, surfacing as 8 TKey errors in
every `tsc --noEmit` run.
All settings persist in localStorage like theme and font-scale.
Co-authored-by: test <[email protected]>
The API key + base URL inputs in settings were gated behind
`settings.baseUrl !== undefined` — so first-time users with no base
URL set never saw the inputs and couldn't change them from the UI.
Drop the guard; show the section whenever general is the active page.
Add a font-scale setting (small / medium / large) next to the theme
toggle. Persists in localStorage like theme, applies via
`document.documentElement.style.zoom` so every px-based size scales
without a CSS rewrite. Three presets — 0.875× / 1.0× / 1.125× —
cover the common high-DPI / cramped-display asks without a free-form
slider.
* fix(slash): /help hanging-indent wrap + fill btw/search-engine zh-CN keys
`/help` rendered broken on zh-CN: CJK summaries are double-wide so
long descriptions overflowed the terminal width and the continuation
landed at column 0, breaking the visual column alignment of the
command list. Two zh-CN entries (`btw`, `search-engine`) were also
missing, falling back to the hardcoded English summary even under
the Chinese locale.
- renderRow now wraps the description with `wrapToCells` (grapheme-
safe, accounts for visual width) and hangs continuation lines at
column 32 (2 indent + 28 name + 2 gap). Width budget matches the
info card's BODY_LEFT_CELLS=7 chrome.
- Add zh-CN + EN entries for `slash.btw.description` and
`slash.search-engine.description`.
- New regression test asserts every SLASH_COMMANDS entry has both an
EN and a zh-CN `slash.<cmd>.description` key.
Closes#865
* fix(tui): strip bidi + zero-width controls from pasted text
A clipboard payload from a browser (e.g. copying a Bilibili tab title)
can carry bidi overrides (RLE/PDF/isolates), zero-width spaces, BOMs,
and soft hyphens. These render as 0 cells but still occupy buffer
offsets, so the composer's cursor and line-split math drift —
characters appear hidden, overlaid, or "lost" after submit.
Add `sanitizePasteText` and apply it at the paste dispatch in
`StdinReader.handleChunk`. The strip set covers bidi controls (LRE
through RLO, LRM/RLM, FSI/PDI), ZWSP, WJ, soft hyphen, BOM. ZWJ /
ZWNJ / variation selectors / combining marks are deliberately
preserved so emoji sequences and accented letters keep their semantics.
Closes#849
`/help` rendered broken on zh-CN: CJK summaries are double-wide so
long descriptions overflowed the terminal width and the continuation
landed at column 0, breaking the visual column alignment of the
command list. Two zh-CN entries (`btw`, `search-engine`) were also
missing, falling back to the hardcoded English summary even under
the Chinese locale.
- renderRow now wraps the description with `wrapToCells` (grapheme-
safe, accounts for visual width) and hangs continuation lines at
column 32 (2 indent + 28 name + 2 gap). Width budget matches the
info card's BODY_LEFT_CELLS=7 chrome.
- Add zh-CN + EN entries for `slash.btw.description` and
`slash.search-engine.description`.
- New regression test asserts every SLASH_COMMANDS entry has both an
EN and a zh-CN `slash.<cmd>.description` key.
Closes#865
Every TabRuntime stays mounted (display:none on the inactive ones) and
each registers its own window-level keydown listener. Without an
`active` gate Cmd+N fires `newChat()` in every tab — both clear their
state, so the inactive tab's sidebar suddenly shows no active session
and any in-flight turn is aborted. The same path catches Cmd+L, Cmd+O,
Cmd+, and Escape-while-busy.
`useCommandPalette` had the same shape, so Cmd+K toggled every tab's
palette in parallel.
Add `active` to both listeners; only attach on the visible tab.
The pauseGate listener's if-chain in desktop.ts had no default
branch. Any new PauseKind added to pause-gate.ts without a matching
handler here would be silently dropped — the gate request stays
pending forever and the agent loop hangs waiting on a response that
never arrives, with no visible signal to the user.
Add a `never` cast at the end of the chain so a new kind without a
handler is a compile error, plus a runtime stderr warning + auto-
cancel via `pauseGate.cancel()` as the last-mile defense if a build
ever slips past the typecheck.
ConPTY occasionally strips the leading ESC off CSI sequences. Mouse
reports — `\x1b[<btn;col;rowM/m` — then arrive in the byte stream as
`[<btn;col;rowM/m`, slip past the escapeless-CSI lookahead (which only
knows arrow / page tails), and fall into the printable accumulator. The
composer receives the literal SGR text and the user has to backspace
through every wheel nudge.
Add `tryEscapelessSgrMouse` alongside the existing escapeless-paste and
escapeless-arrow guards. Recognised reports dispatch the same
mouseScroll/Click/Drag/Release events the with-ESC path already emits;
unmapped buttons are consumed and dropped. Share `decodeSgrMouseBody`
with `dispatchCsi` so both paths surface the same shape.
Closes#867
Without this, the fold summarizer paraphrased inline skill bodies into
prose. Past the fold threshold the model lost the explicit step-by-step
paradigm and drifted back to generic tool-thrashing mid-skill — visible
as the activity row flickering between error and thinking glyphs.
run_skill wraps its inline result in a <skill-pin name="..."> sentinel.
ContextManager.fold extracts every pinned block from the head before
summarizing, stubs the original tool message so the summarizer doesn't
paraphrase it, and re-attaches the bodies verbatim to the synthesized
assistant message. Repeat invocations dedupe by name; last one wins.
Remove the feature that auto-escalated flash→pro after 8 consecutive
read-only tool calls without a write. Deleted:
- src/loop/read-only-loop-tracker.ts (entire file)
- All references in src/loop.ts (import, field, init, method, call site)
- 3 related test cases in tests/loop.test.ts
- i18n keys readOnlyLoopEscalation in EN.ts, zh-CN.ts, types.ts
Reported in #855 (v0.42.0-3 on Windows): with both side and context
panels open at moderate window widths, the composer footer (commands /
mention / Review-Auto-YOLO / model pill / send) extends past the
textarea's right edge and gets clipped by the right panel.
Root cause was the responsive rules collapsing labels and shrinking the
model pill keyed off viewport `max-width`, so a wide window with both
panels open never tripped them even though the actual composer column
was narrower than the no-panel case.
Switch to container queries against `.composer-inner` (now an
`inline-size` container named `composer`) so the same thresholds fire
on the column's own width regardless of which panels are open.
#848 added docs/architecture.html and docs/cli-reference.html but
left configuration.html's two "Architecture deep dive" / "CLI
reference" CTAs aimed at GitHub blob URLs — so the bouncing-out
behavior issue #623 was filed against still happens from that page.
Swap the two hrefs to the local pages and drop the now-irrelevant
target/rel attributes.
* fix(cli): await profile stop inside the action so the .cpuprofile actually lands
beforeExit async handlers aren't awaited by Node, and while the
inspector Session is connected the loop never empties anyway — on
Ctrl+C the process tore down before V8 flushed the profile, and the
writeFileSync never ran. Reproducer: --profile a TUI session, exit,
no file appears.
Moves stop+save into the commander action's try/finally so it runs
inside the explicit await chain. Ink's exitOnCtrlC resolves
waitUntilExit(), then finally awaits stopAndSaveCpuProfile() before
the action returns — Node then exits naturally with the inspector
session already disconnected.
While here: gzip the output and print drop-into-GitHub instructions
on save. Real .cpuprofiles are 5-20 MB raw, gzipped they fit inside
GitHub's 10 MB comment-attachment limit.
* fix(cli): flush profile before useQuit's process.exit so --profile actually writes
PR #846 set up --profile but no file landed on Ctrl+C from `reasonix
code`. Root cause was deeper than the commander-action try/finally:
the TUI's useQuit calls `process.exit(0)` directly (intentionally —
the singleton stdin reader would otherwise hang the terminal), which
skips the whole await chain. waitUntilExit() never resolves, the
action's finally never runs, V8 buffer drops on the floor.
Hooks the stop+save into the two TUI quit paths that call
process.exit:
- src/cli/ui/hooks/useQuit.ts (Ctrl+C / SIGINT) — awaits
stopAndSaveCpuProfile() before process.exit(0).
- src/cli/commands/chat.tsx:187 (session-picker quit) — same.
stopAndSaveCpuProfile is a no-op when --profile isn't active so the
TUI's normal quit path adds nothing.
Refs #843.
Adds `--profile [path]` to `reasonix code` and `reasonix chat`. Starts a
V8 CPU profile on launch via node:inspector/promises, saves the
.cpuprofile to the given path (or cwd with a timestamped default) when
the process exits. Stops on SIGINT/SIGTERM/SIGHUP and on natural exit
via `beforeExit`.
Reason: #843-style perf reports come in vague ("卡了"). A real .cpuprofile
from the user's actual terminal + workload is the only way to tell
CPU-bound from terminal-emulator-bound. Profiling synthetic harnesses
on my box keeps showing 98%+ idle, so the bottleneck is elsewhere; this
flag lets users send back the actual evidence.
Bundles two reusable harnesses + an analyzer under scripts/perf/:
profile-tui-streaming.tsx (throttled, mimics real streaming),
profile-tui-sync.tsx (synchronous, measures raw reducer+commit), and
analyze-cpu-prof.mjs (top-N self/total with idle excluded).
Long conversations on the desktop got laggy because every streaming
chunk re-rendered the whole `state.messages.map(...)` tree. Each
historical `<AssistantMsg>` re-ran `<Markdown>` → `<ReactMarkdown>` +
`remark-gfm` on text that hadn't changed. At 50+ turns the per-chunk
cost stacked into thousands of redundant markdown parses per second.
- `UserMsg`, `AssistantMsg` (`desktop/src/ui/thread.tsx`) — wrapped
in `React.memo`.
- `AssistantText` (`desktop/src/ui/cards.tsx`), `Markdown`
(`desktop/src/Markdown.tsx`) — same.
- The three approval callbacks (`onApproveConfirm`, `onRejectConfirm`,
`onAlwaysAllowConfirm`) were minted inline at the `<AssistantMsg>`
call site on every render, defeating the memo's shallow compare.
Hoisted them to stable `useCallback` refs.
The TUI and dashboard already have this memo discipline
(`src/cli/ui/cards/CardRenderer.tsx:26` and
`dashboard/src/components/chat-internals.ts:308`), so no changes
there.
Closes#844
Refs #843
The desktop already had the full i18n machinery (en.ts / zh-CN.ts /
t() / useLang() / localStorage + browser autodetect) and most chrome
went through it, but three holes made the panel unusable for English
users:
- Settings UI was entirely hardcoded Chinese — side nav, page bodies,
API-key section, shortcuts list — none of it touched t().
- The Language / langEn / langZhCn keys existed in both dictionaries
but were never referenced; switching language required knowing the
/lang slash command.
- index.html shipped a static `<html lang="zh-CN">`, so screen
readers and `:lang()` CSS selectors saw Chinese regardless of UI
language.
Adds a Language section to PageGeneral with en / zh-CN buttons,
routes every visible string in settings.tsx through t(), and pushes
`document.documentElement.lang` from the i18n module on load + on
setLang. index.html ships `lang="en"` as a neutral fallback; the
runtime overrides it from getLang() before paint.
Each Page* component pulls useLang() so language changes re-render
immediately without closing/reopening the modal.
Closes#841
The agent emits a `plan_checkpoint` pause request after each completed
step. The TUI handled it by setting `pendingCheckpoint` and rendering
the local Continue / Revise / Stop card, but the dashboard side was
silent — the broadcast effect that mirrors plan / edit-review /
revision modals over SSE had no checkpoint case. From the user's
perspective the web UI just froze: the model was waiting on a button
the page never rendered.
Also adds the missing branch to `getActiveModal` so a dashboard that
connects mid-checkpoint replays the modal instead of starting blank.
The dashboard modal component (`CheckpointModal`), the resolve route
(`/api/modal/resolve` with `kind: "checkpoint"`), and the App-side
`resolveCheckpointConfirm` resolver were already in place — only the
broadcast was missing.
Closes#832
When a subagent yielded `paused`, the parent agent had no signal about
what was actually done — only the resume token and an iter count. That
forced the orchestrator to either resume blindly or accept partial
work blindly, defeating the point of pause-as-checkpoint.
Adds one no-tools call (`summarizePartialProgress`, pinned to flash
+ effort=high) before yielding `paused`. The call returns 3-6
sentences of progress / remaining / blockers, attached to the paused
event as `partialSummary`. Subagent JSON now surfaces it as
`partial_summary`.
The summary is NOT persisted to session messages — the resumed child
picks up clean state. Failure is non-fatal: pause still works, the
parent just gets the old opaque shape back.
Closes#838
Adds a context-fill indicator to the bottom status row so the user can
tell at a glance how close the current prompt is to the model's
context window — same role claude-dashboard plays for Claude Code.
Rendered as `ctx 72%` by default, `ctx 72% · 144K/1M` at ≥90 cols,
and `ctx ████░░░░ 72% · 144K/1M` at ≥110 cols. Tier-colored: green
under 50%, amber 50–80%, red ≥80%.
Plumbed via the existing `turn.end` event (already carries
`usage.prompt` + optional `promptCap`); cap falls back to the model's
entry in DEEPSEEK_CONTEXT_TOKENS, then to DEFAULT_CONTEXT_TOKENS.
Opt-out lives next to the other status-row toggles
(`statusBar.showCtxUsage` in user config).
Closes#828
`desktopCommand` awaited `buildCodeToolset` inside `createTab` before
emitting ANY event. That bundled semantic bootstrap, MCP probes,
tokenizer cold-load, and runtime construction into 1.5–3s of dead
time during which the Tauri window had nothing to render — feels
much slower than the web dashboard (which piggybacks on an already-
warm CLI process).
Split into a synchronous skeleton + async toolset init:
- `createTabSkeleton(dir)` — sets `toolset: null`, `runtime: null`,
`system: ""`. Returns instantly.
- `initTabToolset(tab)` — awaits `buildCodeToolset`, fills in
`tab.toolset` / `tab.system`, builds the runtime if an API key is
present, bridges MCP in the background.
Boot path fires `$tab_opened`, `$sessions`, `$settings`, `$mcp_specs`,
`$skills`, `$memory`, `$needs_setup?`, `$balance` IMMEDIATELY (all
disk-only or fire-and-forget). `initTabToolset` runs concurrently
and emits `$ready` + `$ctx_breakdown` on completion. UI's
`disabled={!state.ready}` keeps the composer locked until then —
existing safety, no new gate needed.
Subtler bits:
- `Tab.toolset` is now `Toolset | null`; the few hot paths that
touch it (`buildRuntimeFor`, `bridgeTabMcp`, `closeTab`,
`switchWorkspace`, settings-save preset change) gain a null guard.
`buildRuntimeFor` keeps an explicit "called before init" throw —
callers that need a runtime were already gated on `tab.runtime`.
- `setup_save_key` now tolerates a still-bootstrapping tab: skip
the `buildRuntimeFor` branch, `initTabToolset`'s tail reads
`loadApiKey()` after the new key was persisted and constructs the
runtime there.
- `tab_open` (multi-tab) follows the same skeleton + lazy-init shape.
P0 from the desktop perf analysis; P1 (semantic / MCP lazy-load
inside `buildCodeToolset`) and P2 (Tauri-side splash before Node
spawn) stay separate.
The default 1024×720 logical-px window doesn't fit on a Windows
laptop at 200% scaling (1920×1080 panel → 960×540 effective logical
space): the window opens partially off-screen, the user has to drag
or resize to see the right edge / bottom rows. The minWidth=640 /
minHeight=400 floor also locked out 1366×768 @ 200% setups entirely
(683×384 effective).
Fix:
- main.rs setup hook: query the current monitor's logical size,
clamp the window to 90% of available when 1024/720 overflows,
then recenter.
- tauri.conf.json: drop minWidth → 480, minHeight → 320 (still
comfortable on a normal display, lets the window actually meet
its minimum on tight HiDPI setups). Add `center: true` so the
window is centered on first launch.
The normal-DPI case (no overflow) is unchanged: the clamp branch
only fires when the configured size doesn't fit the monitor.
Refs #827.
The three coloured dots (red / yellow / green) in the top-left of
the titlebar were pure decoration — no onClick handlers, no Tauri
window-API wiring, just `<span>`s styled to look like macOS
traffic-light buttons. Users (rightly) clicked them expecting
close / minimize / maximize and got nothing. Remove the markup, the
matching `.traffic` / `.dot` CSS, and the now-redundant `margin-left`
on `.brand` that compensated for the removed block.
Native window chrome handles min / max / close on every OS we ship to.
The three coloured dots (red / yellow / green) in the top-left of
the titlebar were pure decoration — no onClick handlers, no Tauri
window-API wiring, just `<span>`s styled to look like macOS
traffic-light buttons. Users (rightly) clicked them expecting
close / minimize / maximize and got nothing. Remove the markup, the
matching `.traffic` / `.dot` CSS, and the now-redundant `margin-left`
on `.brand` that compensated for the removed block.
Native window chrome handles min / max / close on every OS we ship to.
The right-hand memory panel only got an `\$memory` event on tab open
— so when the agent called `remember` (or `forget`) mid-turn the
file was written to disk but the panel stayed on the prior list
until the user reopened the tab.
Re-emit `\$memory` from the turn loop whenever a `remember` /
`forget` tool event flows past. Same shape as how we re-emit
sessions / balance on turn complete; just on the tool boundary
instead so the UI sees the new entry the moment it's written.
* fix(desktop): expire the @-mention file index after 10s
The file index cached at tab construction lived for the lifetime of
the tab — files deleted, renamed, or added inside the workspace never
showed up (or refused to disappear) in the @ picker. #816 reported
this on the desktop client.
Add a 10s TTL: the next @ query past that window triggers a rebuild.
Balances "fresh enough for edit-then-mention flows" against scanning
5000 files on every keystroke.
* feat(desktop): tree-style @ picker — bare @ shows workspace top level
Bare @ in the desktop composer used to flood the popup with a flat
fuzzy match across all 5000 files in the workspace. Mirrors the TUI's
@+Tab pattern: empty query lists the workspace root's top-level
entries, and Tab on a directory item enters it (replaces `@src` with
`@src/` and re-queries to show that directory's children). Enter on
a directory still picks the directory itself.
Backend side (mention_query treeWalk branch) landed in the previous
commit on this branch as part of the desktop.ts change set.
Part of #816.
* feat(desktop): drag-and-drop files / folders → @-mention
Files dragged onto the Reasonix desktop window now append as
@-mentions in the draft. Paths inside `workspaceDir` are normalised
to relative; everything else passes through as absolute. While the
drag is over the window, an overlay shows "Drop to attach as
@-mention" so the user knows we'll accept it.
Tauri 2's webview `onDragDropEvent` provides the path list — uses
the standard {enter, over, drop, leave} state machine, no native
plugin needed.
Part of #816.
The dashboard installs `window.addEventListener("error", ...)` and
`unhandledrejection` to surface app crashes through the error overlay.
Both handlers forwarded unconditionally — so when a user's browser ran
an ad-blocker userscript that threw `require is not defined`, the
overlay caught it and prompted the user to file an issue against
*us*. #818 is exactly that: a `ReferenceError` from
`chrome-extension://…/userscript.html?name=屏蔽广告…`, nothing to do
with the dashboard.
Filter by origin: if the error's stack or the ErrorEvent's filename
contains `chrome-extension://`, `moz-extension://`,
`safari-web-extension://`, `safari-extension://`, or
`ms-browser-extension://`, skip reporting. The error still propagates
to `console.error` via the browser's default behavior; we just don't
treat it as ours.
Closes#818
`reasonix code` was passing `opts.model ?? "deepseek-v4-flash"` into
chatCommand + the system-prompt builder, so a user with preset=pro or
preset=auto in their config was silently downgraded to flash. Resolve
the preset (`loadPreset()` → `resolvePreset()`) and use its model id
instead — mirrors the same fix#819 landed on the desktop path.
Original implementation by @rokyplay in #820; cherry-picked here as a
standalone fix so it can land independently of the typeahead/steer
work in that PR.
Co-authored-by: rokyplay <[email protected]>
* fix(cli): route bare project launches to code mode
Detect project-like working directories for bare reasonix invocations so filesystem tools are rooted at cwd, while preserving explicit chat and first-run setup behavior.
* fix(test): import React for plan confirm tests
Reframes subagent iters from "hard budget" to "checkpoint cadence":
the subagent yields a `paused` event when its per-window iter count
runs out, the parent decides to either accept the partial state or
call spawn_subagent again with `resume_session` to continue. Total
iters bounded only by parent's own budget + natural termination.
Built on the existing session-persistence layer — pause leaves
messages on disk, resume reloads them. Prompt-cache prefix is
byte-stable across pauses so resumption is essentially free.
Validated end-to-end against the real DeepSeek API: phase 1 spawns
with max_iters=2, subagent pauses with a resume_session; phase 2
resumes with that token, subagent completes the remaining 8 of 10
topics in the new window.
What changed:
- loop.ts + loop/types.ts: new onIterBudgetExhausted option
(default "summarize" for top-level chat, "pause" for subagents);
pause yields a `paused` LoopEvent role with the session name.
- subagent.ts:
- Child loop runs with onIterBudgetExhausted=pause + minted
session subagent-<runId>-<ts>.
- SubagentResult gains paused / pausedSession.
- formatSubagentResult on pause emits {success:false, paused:true,
resume_session, note} — the note teaches the parent how to
resume in-band.
- spawn_subagent JSON arg gains resume_session; max_iters loses
minimum/maximum (no clamp).
- MIN/MAX/DEFAULT_MAX_ITERS gone; one internal DEFAULT_PAUSE_EVERY
= 16. clampMaxIters → parseMaxIters (no clamp).
- On resume, prepend a one-line nudge to the user task so the
model doesn't read lingering "finalize NOW" hints from the
previous window as still in force.
- skills.ts: frontmatter max-iters no longer clamped at a cap;
values below 1 still fall back. Doc rewritten as pause cadence.
PR #822 widened the cap 32 → 256 as a measurement step. Real-API
probes showed the model picks sensible values across task sizes —
confirming the cap was theater. This PR removes the cap entirely
and replaces it with a mechanism that scales with whatever the
work actually needs.
Closes#783
* experiment(subagent): widen iter cap 32 → 256, add telemetry to evidence model picks
Goal: empirically test whether the model picks pathological values for
`max_iters` (the kind we worried about — 1 or 9999) when given a much
wider range. If real workloads consistently land in a sensible band
(say 5-64), the cap was always theater and the next PR can remove it.
Changes:
- `subagent.ts` MAX_MAX_ITERS 32 → 256; tool description updated to
match. MIN stays at 1.
- `skills.ts` SKILL_MAX_ITERS_MAX 32 → 256; auto-injected skill docs
reworded so authors don't read 32 as the natural ceiling.
- New `IterCapSource` field on SpawnSubagentOptions + a single-line
stderr emitter so we can grep what each spawn resolved to and where
the value came from (json-arg / type / frontmatter / default).
- App.tsx skill subagentRunner now propagates `skill.maxToolIters`
(it didn't before — a latent divergence from the `reasonix code`
setup path that meant chat-mode skills silently ignored their
frontmatter `max-iters`).
- `REASONIX_ITER_CAP_TELEMETRY=off` opt-out; test setup turns it off
so CI logs stay quiet.
- Tests updated to assert the new bound and to cover 128 (in-range).
Mid-experiment safety:
- Cap still exists at 256 — the pause/resume work is not yet shipped,
so an extreme model pick can't burn through unbounded budget.
- 70% loop warning + 3-iter end-of-budget hint + budgetUsd cap all
still in effect.
* remove iter-cap telemetry after real-API validation
Probe results (deepseek-v4-flash, max_iters arg picked by the model
against the new 256 ceiling):
tiny task → 3
medium task → 30
large task → 80 (also auto-escalated to pro mid-loop)
unbounded → 256 (hit the ceiling, but the prompt said "unbounded
audit, take as many tool calls as needed")
No pathological 1, no hallucinated 999 → real values, scales with the
task description. The cap-as-safety-theater hypothesis holds.
This commit drops the experiment-only scaffolding while keeping the
substantive change (32 → 256 cap + the App.tsx skill maxToolIters
propagation fix it surfaced):
- emitIterCapTelemetry function gone
- IterCapSource type, itersSource / itersRaw fields gone
- callers in App.tsx, setup.ts, subagent.ts no longer compute or pass
the source tag
- scripts/iter-cap-experiment.mjs deleted
- REASONIX_ITER_CAP_TELEMETRY opt-out in tests/setup-lang.ts deleted
The native redirect parser called `pathMod.resolve(cwd, target)` for
every redirect target, so `2>nul` (Windows habit) and `2>/dev/null`
(POSIX habit) both opened a real file at `<cwd>/nul` or
`<cwd>/dev/null`. On Windows this materialized a stray `nul` file at
the project root containing whatever stderr was meant to be discarded
("File Not Found" from `dir`, typically).
Detect the two well-known aliases — case-insensitive `/dev/null` on
any platform, plus `nul` on win32 only (it is a legitimate filename
on POSIX) — and route them to `os.devNull` instead of the cwd.
The desktop JSON-RPC entry built CacheFirstLoop without passing
autoEscalate, so it defaulted to true regardless of preset. Picking
`flash` in the UI (advertised as "cheapest · predictable") still let
the loop escalate flash → pro on hard turns, billing users at pro
rates. The TUI's applyPresetLive already wires autoEscalate from the
resolved preset; do the same in buildRuntimeFor.
* chore(docs): move new landing + download site into docs/ for GitHub Pages
Routes:
- `/` (docs/index.html) — new editorial landing
- `/download.html` (docs/download.html) — smart-mirror download page
- `/configuration.html` — existing bilingual config guide,
untouched, still served alongside
The new design's components moved from `download-site/src/` to
`docs/src/`; the index now also carries the SEO bundle from the
previous landing (canonical, hreflang, og:, twitter:, JSON-LD
SoftwareApplication + WebSite) so search rankings don't drop.
Nav gains a "Guide" link pointing at `configuration.html` since
the in-page #config section is a quick reference, not a replacement
for the full guide.
`_headers` / `_redirects` are dropped — those were Cloudflare Pages
features and don't apply to GitHub Pages.
`term-anim.js` was only used by the old landing; deleted.
`styles.css`, `guide.css`, `i18n.js`, `guide-i18n.js`, `motion.js`
stay because `configuration.html` still references them.
`sitemap.xml` gains the download page entry.
* feat(web): EN/中 language switch + restyle configuration guide to match
Three changes ride together:
- **Language switch.** New `src/i18n.jsx` exposes `LangProvider`, `useLang`,
and a `t({zh, en})` helper. The nav now carries an EN/中文 toggle that
persists to `localStorage` under `reasonix.lang` and reflects in
`?lang=…` for deep-linking. Every prose string in nav, hero, install,
agents (three pillars), features, config (MCP/Skills/Memory/Slash),
community, roadmap, FAQ, footer, download page, mirrors grid, and CLI
alt block is now bilingual. `configuration.html` uses the same storage
key via `i18n.js`, so switching language on any page propagates to the
others.
- **Guide restyle.** `configuration.html` no longer ships its own
navy-palette chrome; it now loads `src/fonts.css` + `src/styles.css`,
uses the same nav + footer markup as the new design (active "Guide"
link in the accent colour), and `guide.css` was rewritten to use the
new design tokens (--cream, --accent, --rule, --serif, --mono) so the
article body — TOC, callouts, cmd tables, code blocks, CTA — sits
cohesively inside the warm-sepia aesthetic of the rest of the site.
- **Live community stats.** Community card on the landing now fetches
the real star count, fork count, and contributor list from the GitHub
REST API, replacing the mockup's fixed 1,128 and 24-initial placeholder.
Adds `download-site/` — a static React (UMD + Babel standalone) site with
two routes:
- `/` (index.html) — editorial landing page: hero with an animated terminal
replay of an actual reasonix code session, CLI install panel, three-pillar
agent breakdown, feature grid, configuration explorer (MCP / Skills /
Memory / Slash), community card with live GitHub stars + contributor wall,
roadmap, FAQ.
- `/download` (download.html) — smart-mirror download page. On load, races
HEAD probes against R2 and GitHub Releases, highlights the fastest as
"Fastest", and offers a per-platform installer link. Three platform tabs
(macOS / Windows / Linux) with first-launch caveats (Gatekeeper, SmartScreen,
AppImage chmod + libfuse2).
Substitutions from the mockup:
- Version `0.30.5` → `0.42.0-3` everywhere (mirrors / hero / footer / nav /
AppImage chmod example / terminal replay).
- File names match the actual `tauri-action` bundle output.
- Mirror list trimmed from {R2, Gitee, GitHub} to {R2, GitHub}; the Gitee row
in the matrix went away when we dropped that mirror upstream.
- Hero stats updated (test count → 2837).
- Community card fetches real GitHub repo metadata + contributors from
api.github.com instead of the hand-rolled chart and 24 placeholder initials.
- "新账号有免费额度" wording removed — DeepSeek pulled that perk in 2026-05.
Implementation notes:
- React + ReactDOM pinned to `cdn.jsdelivr.net` (better mainland-CN access
than unpkg). Babel standalone same CDN.
- `src/fonts.css` is a system-font stack — no external font CDN. The Google
Fonts <link> the mockup shipped with would degrade ugly on CN networks
exactly where the page matters most.
- `tweaks-panel.jsx` (dev-only design knob panel) is not copied; `app.jsx`
was simplified accordingly.
- `_headers` sets MIME type for `.jsx` (Babel needs `text/babel`-ish) and
basic security headers.
- `_redirects` maps `/download` → `/download.html` for clean URLs.
Deploys to Cloudflare Pages — no build step, root dir = `download-site`,
auto-deploys on push to main. README covers the manual setup.
GitHub Actions → Gitee bandwidth is unreliable enough that even
small files (47 MB rpm, 49 MB deb) hit the 3-min per-file timeout.
The runners live in US Azure regions and the path back into
mainland China is throttled / lossy; that's structural and not
something a longer timeout or more careful retry logic will fix.
R2 (via Cloudflare's edge) is fast enough from China to serve as
the primary mirror for CN users, plus the download page's latency
probe picks the best mirror per visitor. Gitee was supposed to be
the CN-native fallback; without reliable upload there's nothing to
fall back to.
Removes the Mirror to Gitee step and the helper script. GITEE_TOKEN
secret can stay or be deleted at the maintainer's discretion — it's
no longer referenced.
Last run got stuck for 15+ min uploading what should have been a
~50 MB file — Gitee accepted the connection then stalled, and
undici's default headersTimeout (5 min) wasn't aggressive enough
to free the loop, so the rest of the batch never ran.
Wrap each upload in an AbortController with a 3-min cap. Files
that don't complete in that window are reported as failures and
the loop moves on, matching the per-file error isolation added in
the previous fix.
Two robustness fixes on top of v0.42.0-3 mirror run #4:
- Gitee free accounts cap individual release assets at 100 MB. Our
AppImage (118 MB) was hanging the upload until undici's 5-min
HeadersTimeoutError fired, which crashed the whole script and
left assets queued after it unmirrored. Now skip files > 90 MB
with a clear log line; users still get those from GitHub / R2.
- Per-file uploads now catch their own errors and continue. A
flaky single upload no longer kills the rest of the batch.
Script still exits non-zero at the end if any upload failed, so
the workflow stays red.
R2 mirror was already passing end-to-end on the prior run.
Gitee's POST /repos/{owner}/{repo}/releases rejects an empty body
with 400 "发行版的描述不能为空" (release description cannot be empty).
The previous default kicked in only when the env var was unset; when
the GitHub release has no notes, the workflow passes RELEASE_BODY=""
which bypassed the `??` fallback.
Treat empty / whitespace-only body as "no body" and substitute a
link back to the GitHub release. Keeps mirror-only metadata
discoverable and lets the run succeed regardless of how thorough
the maintainer was with release notes.
Gitee's GET /repos/{owner}/{repo}/releases/tags/{tag} returns
200 OK with the literal JSON body `null` when the tag has no
release yet, not 404 like every other release API. The script
read .id off that null and crashed before the create path could
run. Treat null/missing-id as "no release exists" and fall
through to the POST /releases create branch.
Two issues surfaced on the first real run (v0.42.0-3):
- Gitee path `reasonix/deep-seek-reasonix` 404'd; the actual repo is
`reasonix/DeepSeek-Reasonix` (case-sensitive on Gitee). Fixed.
- Gitee failing took out R2 because step-level `if:` defaults to
`success()`. Added `continue-on-error: true` to both mirror steps
and `if: always() && ...` to R2 / its aws-cli setup so the two
targets are now fully independent — one failing surfaces a failed
workflow but doesn't suppress the other.
Summary step now reports per-mirror status (✓ / ✗ / skipped) and
exits non-zero if any required mirror failed, so the run stays red
in the Actions UI even though individual steps soft-failed.
Add argCompleter: "skills" to the /skill command so users see a
picker with available user-defined skills (project + global scope)
when typing '/skill ' — excludes built-in skills to reduce noise.
- Add "skills" to the argCompleter type union in SlashCommandSpec
- Register argCompleter on the skill command spec
- Add SkillStore-based resolver in useCompletionPickers
A new workflow fires on `release: published` (and is manually
runnable for backfills). It downloads the GH release assets,
creates / reuses a Gitee Release of the same tag, and uploads
each asset; in parallel it syncs the same files to R2 under
`<tag>/` and `latest/`.
Both mirror steps gate on their secrets being present, so the
workflow no-ops cleanly until tokens are configured. Required
secrets:
- GITEE_TOKEN
- R2_ACCESS_KEY_ID, R2_SECRET_ACCESS_KEY, R2_ACCOUNT_ID, R2_BUCKET
Refs #802
* fix(desktop): bundled CLI loads on installed targets; drop CDN fonts
Two unrelated issues both surfaced as a black-screen on the v0.42.0-2
release.
CLI sidecar: tsup was emitting `dist/cli/index.js` as an ESM bundle
with `commander`, `ink`, `undici`, etc. left external. That's fine
for `npm i -g reasonix` (npm brings the deps), but the desktop ships
`dist/cli/` as a static resource with no `node_modules` next to it,
so the spawned Node process died on `ERR_MODULE_NOT_FOUND` for the
first import and the IPC channel never came up → empty UI. Switch
the CLI entry to a self-contained bundle: `noExternal: [/.*/]` plus
`platform: "node"`, with `react-devtools-core` whitelisted as
external (it's an optional peer dep that ink dynamically pulls only
when devtools are enabled, which we never do).
undici's dispatcher uses `require()` at runtime; in ESM output the
esbuild shim refuses dynamic require. Banner-inject a `createRequire`
into `globalThis.require` so the shim picks it up.
Drop a one-line `dist/cli/package.json` with `{"type":"module"}` so
Node skips the CJS-first parse attempt and the
MODULE_TYPELESS_PACKAGE_JSON warning.
Fonts: `index.html` loaded IBM Plex from googleapis.com, which the
bundled CSP (`style-src 'self' 'unsafe-inline'; font-src 'self'
data:`) blocks. Switch to `@fontsource/ibm-plex-{sans,mono,serif}`
so the woff2s are bundled into `dist/assets/` at build time —
identical typeface, zero runtime network. The previously-imported
`@fontsource-variable/inter` + `jetbrains-mono` packages were dead
weight (CSS never referenced those families); removed.
Enable tauri's `devtools` feature while the desktop is prerelease —
F12 is what surfaced both bugs, and it stays useful while the
desktop is being shaken out. Revisit before stable.
* test(bundle-smoke): assert runtime deps are inlined, not external
Companion to the CLI bundling change: the smoke guardrail was the
inverse of what we now want — it asserted ink was kept external so
npm could resolve it from the user's tree. The desktop sidecar
runs from a static `dist/cli/` with no node_modules, so external
imports are exactly the failure mode we're guarding against now.
Flips the assertion: no `dist/cli/*.js` should `import from "commander"
| "ink" | "undici"` — those are the three that broke v0.42.0-2.
StreamingCard re-ran split('\n') + wrapToCells() over the whole
accumulated text on every chunk. wrapToCells walks each grapheme
through Intl.Segmenter (~3.7µs/char), so a 5000-char reply costs
18.5ms per frame at 20Hz — well over the 50ms budget.
Cache the wrap and re-fold only the last logical line on monotonic
append; fall back to a full recompute on shrink (abort), resize,
or any non-prefix change. ReasoningCard's StreamingPreview and
SettledPreview now share the parent's wrap result instead of
each running their own flatMap.
Also bumps the live token calibration interval from 500 to 1000
chars — the post-fix calibration frame became the dominant cost
and t/s precision is already an approximation.
Closes#798
The macos-13 Intel runner pool on GH is heavily throttled — v0.42.0-1
sat queued for hours. Tauri 2 ships a `universal-apple-darwin` target
that lipos x86_64 + arm64 builds into a single fat binary, so one
Apple Silicon runner now produces a Mac DMG that installs on both
Apple Silicon and Intel.
Restructures the matrix entry so `rust` is the comma-separated list
fed to dtolnay/rust-toolchain (both real targets need installing for
the universal build) and `tauri` is the target name fed to
`cargo tauri build`. Other shards just repeat their triple in both
fields.
Drops the macos-x64 row entirely. The universal DMG covers the same
hardware that macos-x64 shard was producing for.
v0.42.0-0 run got past compile + bundle (MSI included — numeric
prerelease works as expected) but died at "GITHUB_TOKEN is required"
when tauri-action tried to create the draft release. The previous
codesign failure on v0.42.0-desktop.0 masked this: the build never
reached the upload phase, so nobody noticed the missing token.
tauri-action v0 needs GITHUB_TOKEN in env to call the GitHub API for
draft creation + asset upload. Wires `secrets.GITHUB_TOKEN` into all
three build-step variants (unsigned, Windows signed, macOS signed).
Windows matrix shard produced its full set of artifacts in the
previous run before failing the upload:
Reasonix_0.42.0-0_x64_en-US.msi
Reasonix_0.42.0-0_x64-setup.exe (NSIS)
+ .sig files for both
#794 used `secrets.WINDOWS_CERTIFICATE != ''` directly inside step
`if:` conditions. GitHub Actions rejects that at workflow-validation
time — secrets context isn't available to job/step conditionals.
Result: every push to main / PR branch produced a workflow-file-issue
failure run, and the v0.42.0-0 tag run never even started.
Lifts the presence check into a job-level `env:` that resolves at
job-start (where secrets context IS accessible). Steps gate on the
"true"/"false" string instead. Same three-way split as #794, just
working syntax.
Releasing v0.42.0-desktop.0 surfaced this: when an APPLE_* or
WINDOWS_CERTIFICATE secret is unset, GitHub Actions fills the env
var with an empty string, and tauri-action interprets "env defined"
as "try to sign". `security import` of an empty cert fails on macOS;
signtool fails the same way on Windows.
Splits the single Build Tauri bundle step into three mutually
exclusive variants gated on whether the certificate secret is
actually non-empty:
- unsigned (Linux always; Win/macOS when no cert)
- Windows signed (matrix.os == windows-latest && cert set)
- macOS signed + notarized (startsWith macos- && cert set)
Today only the Tauri updater key is configured, so every shard takes
the unsigned path. Wiring stays in place for when code-signing
secrets land.
README had no mention of the Tauri desktop bundle, so users wouldn't
know it exists. Adds a short section under Install: where to grab
installers, the prerelease caveat (unsigned bundles), and the two
one-line gotchas users hit on macOS (xattr) and Windows (SmartScreen).
The previous exit watcher took the Child by move and blocked on
child.wait(), with no way to interrupt it from outside. RpcHandle
stored only stdin, so the only thing keeping Node alive-or-not was
the stdin pipe closing on parent exit — fine in the common case but
leaks the child if Node is mid-tool-call when Tauri exits.
Replaces the watcher with a recv_timeout loop on a kill-signal mpsc:
RpcHandle holds the Sender, dropping the handle disconnects the
channel, the wait thread sees Disconnected and calls child.kill()
followed by wait() to reap. Natural exit (try_wait returns Some) is
detected on the 500 ms tick and clears RpcState so a future rpc_spawn
isn't blocked by stale state.
Tauri 2's process exit doesn't always run managed-state drops, so
RunEvent::ExitRequested also invokes rpc_kill explicitly — belt-and-
braces.
`rpc_kill` is exposed as a tauri command for a future UI affordance
(restart RPC button); not wired to a button yet.
Skills that runAs=subagent were hard-capped at the spawn default of
16 tool calls — no way to raise it from the frontmatter. Review /
exploration playbooks with bigger codebases run out and stop with
"Tool budget exhausted at 16 calls". The setup.ts run_skill bridge
ignored skill.maxToolIters because the field didn't exist.
Adds `max-iters` to the parsed frontmatter (clamped to [1, 32] to
match the spawn_subagent JSON-schema bounds), wires it through to
spawnSubagent, and documents it in docs/configuration.html plus the
/skill new stub. Invalid / out-of-range values fall back: junk text
→ undefined (default 16), >32 → 32, <1 → 1.
Closes#783
Two prerequisites for the desktop's first prerelease bundle.
- Cargo.toml + tauri.conf.json + desktop/package.json were all stuck
at 0.0.0. tauri-action doesn't auto-rewrite them from the tag, so
the artifact filenames would have been Reasonix_0.0.0_x64-setup.exe
and the updater's version compare would be broken. New
scripts/sync-desktop-version.mjs reads the tag (or GITHUB_REF_NAME /
TAG env var) and writes the SemVer to all three files. Wired into
release.yml between `npm ci` and the CLI build step.
- CSP was `null`. Switched to a minimum self-only policy with the
usual escapes for inline styles, fonts, and Tauri IPC origins
(`ipc:` + `http://ipc.localhost`). Only applied to the bundled
build, dev server is untouched.
Updater pubkey was already set on a previous pass; nothing to do
there. Code-signing certs (Windows EV, macOS Developer ID) are a
later step — first prerelease can ship unsigned with the usual
SmartScreen / Gatekeeper warnings.
* fix(desktop): wire path_access gate and scope right-panel to this session
Two desktop-side gaps from the same field report:
- path_access requests hung forever. desktop.ts's pauseGate listener
handled run_command / run_background / choice / plan_* but had no
case for path_access, so any outside-sandbox read (e.g. the model
trying `/tmp/foo` on a Windows workspace) parked the tool call with
no UI surface. Now emits `$path_access_required` and renders a
PathAccessApprovalCard (allow once / always allow prefix / deny).
Response reuses `confirm_response` since both gates return a
ConfirmationChoice.
- The right-panel Files tab was dumping the entire workspace tree
(up to 800 entries) overlaid with `git status` dots and polling
every 5s, against the mockup's intent. That mockup was a curated
"files in context" view — only files the agent has read or written
this session, status `c` for reads and `m` for writes. Rewrote
CtxFiles to consume the session-tracked list directly; dropped the
`list_workspace_tree` / `git_status` invokes (Rust commands left
in place but no longer called). Tree falls out naturally from the
small flat list via parent-dir grouping. Status `m` never downgrades
back to `c`.
multi_edit's per-edit paths are extracted so a batch refactor surfaces
all touched files.
* fix(desktop): rename global .caret → .stream-caret, drop dead tree rule
The streaming-text indicator's `.caret` was a global selector. The
old CtxFiles also used `<span className="caret">` for its expand
arrow, and `.tree .node .caret` only overrode width/height/display/
color/flex-shrink — `background: var(--accent)` and the 1Hz
`animation: caret` leaked through, painting a flashing accent square
next to every tree node. Renaming the streaming class breaks the
collision, and now-unused `.tree .node .caret` goes with it.
YOLO mode already auto-allows shell tools via setup.ts's `allowAll`
getter, but filesystem tools went through `safePath` → `path_access`
gate unconditionally, so an outside-sandbox read like `/tmp/foo` would
still pause the loop waiting for user approval. autoResolveVerdict
now returns run_once for path_access in yolo (run_once rather than
always_allow so a transient YOLO session can't pollute the on-disk
allowlist).
CLI TUI also routes path_access through autoResolveVerdict so the
three surfaces (CLI / ACP / desktop) all converge on the shared rule.
52 commits since 0.40.0. Headline is the ACP three-stage rollout
(NDJSON framing → tool_call streaming → request_permission bridge)
plus three flags that close the headless-caller story: --transcript
for cost-tracking, --yolo to skip plan checkpoints without config
mutation, --mcp + --mcp-prefix so downstream adapters can bridge
their own MCP servers without touching the user's config.
Other shipped lifts: flash → pro auto-escalation on consecutive
read-only tool calls (caps the dead-end fishing-trip cost), read_file
outline support for Python / Go / Rust / Markdown, a wait_for_job
exit-only mode that turns a 5-minute download into ONE tool call,
/btw for side questions that don't pollute context, user-defined
memory types with priority + expiry, status-bar field toggles, and
a wave of desktop UI surfaces gaining real data.
Field-reported fixes: /new now reloads REASONIX.md without a restart
(#778 bug 2), the dashboard search toggle no longer one-way-traps
users whose config lacks an explicit "search" field (#778 bug 1),
preset switches preserve persisted reasoningEffort (#775), markdown
emits OSC-8 hyperlinks, embed batch responses tolerate missing inputs,
@-mention paths handle CJK, jobs settle running state across the
Windows taskkill window, and more.
Full notes in CHANGELOG.md.
The dashboard's search toggle reads `cfg.search !== false` and treats
missing as on, so the button renders ON even when `~/.reasonix/config.json`
has no `"search"` field at all. A user who reads the config file first,
sees no entry, opens the dashboard expecting OFF, and clicks "to enable
it" actually goes `undefined → false` — which matches the report on
#778 (config still shows `"search": false` after the click).
GET now persists the resolved default (`true`) on first read when the
field is missing, so on-disk state always matches what the dashboard
displays. Subsequent clicks toggle a real boolean and the config
mirrors the button state from then on. Idempotent on configs that
already have an explicit search field.
Refs #778 (bug 1 of 2)
`reasonix acp` is missing the MCP-server bridging that `reasonix run` and
`reasonix chat` already have. Headless ACP clients (Paperclip's
reasonix-local adapter, etc.) need to plumb domain-specific tool servers
to the agent without forking config — same shape as #766/#767.
Lifts the MCP load loop from run.ts:81-142 into a `loadMcpServers` helper
and calls it inside `buildSession` so the tools are bridged into the
toolset registry BEFORE the prefix is computed (matters for the cache key).
Failures stay non-fatal — a broken side-concern server logs to stderr and
the session keeps running.
Disposes spawned MCP children when the ACP server's stdin closes.
Closes#779.
Editing REASONIX.md and running /new currently leaves the in-memory
system prompt pointing at the old content — applyMemoryStack runs once
at startup, gets baked into ImmutablePrefix.system, and clearLog()
doesn't touch the prefix to keep the prefix-cache warm.
Accept the cache miss when the user actually changed something. Add an
optional rebuildSystem closure on CacheFirstLoop; /new re-runs it,
compares against the current system, and only invalidates the cache
when the string changed. Closures captured at the chat / code entry
points point back at applyMemoryStack / codeSystemPrompt — same args,
fresh disk read.
A reload prints " · REASONIX.md / project memory reloaded" next to
the usual /new banner so the cache miss isn't surprising.
Refs #778 (bug 2 of 2)
waitForJob currently races closedPromise + outputPromise + timer, so
any new output (curl progress, install spinner, watcher tick) wakes
the wait and the model fires another round-trip. On a 90s download
that's 30+ tool calls.
Add `waitFor: 'exit' | 'output-or-exit'`, default `'exit'` — drop
outputPromise from the race in exit mode. Raise timeoutMs cap from
30_000 to 300_000 (server-side block costs no tokens, so one 5-min
wait_for_job covers an end-to-end download). Update run_background +
wait_for_job descriptions and the code-mode shell-tool prompt to
steer the model toward bg-jobs for one-shot long work (curl/wget,
big installs, big builds), not just dev servers.
Closes#776
#770 reported that reasoningEffort silently reverted to "max" after
updating, requiring the user to re-set it via the dashboard every
time. Tracing it: the update wasn't the cause — every preset-apply
path was overwriting the persisted effort with the preset's default
(all three canonical presets bundle `reasoningEffort: "max"`). Any
click on a preset card in the desktop UI, any `/preset` slash, and
the ModelPicker outcome handler all called
`saveReasoningEffort(p.reasoningEffort)` and stamped "max" over
whatever the user had stored.
Three call sites now only persist `savePreset`; the live
`loop.configure({ reasoningEffort })` stays so the in-session bundle
effect is preserved. Persistence of effort becomes user-driven only
(dashboard effort dropdown or future explicit slash). Next-launch
`loadReasoningEffort()` then returns the user's stored choice
instead of the silently-rewritten preset default.
Adjacent fix in src/cli/commands/desktop.ts:buildRuntimeFor —
loadReasoningEffort() was being read for `ctx` but never passed to
the `CacheFirstLoop` constructor, so the desktop runtime loop
always ran at the default "max" regardless of the persisted value.
Now passed through.
Regression test in tests/preset-effort-isolation.test.ts mocks
saveReasoningEffort / savePreset and verifies the slash handler
calls savePreset but never saveReasoningEffort, while the live loop
still gets the preset's bundle effort applied.
Per-invocation override of editMode for plan-checkpoint gates only.
Mirrors the existing editMode = "yolo" semantics in
src/core/pause-policy.ts — shell, edit, and any future gates still
bridge to the client via session/request_permission.
Headless callers should not have to write to ~/.reasonix/config.json
just to skip plan modals when running unattended.
Refs: #765
The old `esengine/reasonix` URL still resolves via the GitHub redirect
but star-history.com follows the canonical slug, so the chart was
quietly diverging from the real star series after the repo rename.
Updates the link + three picture sources in both READMEs to
`esengine/DeepSeek-Reasonix` and drops the `timeline&logscale` style
in favour of the simpler `date` projection.
Adds the three oosmetrics achievement badges (Top 2 in Agents, Top 3
in LLMs, Top 3 in CLI — all by 7-day velocity, as of 2026-05-12) to
both README.md and README.zh-CN.md, plus a scheduled GitHub Action
(weekly Monday 09:00 UTC + manual dispatch) that runs
oosmetrics/health-check-action@v1 to open a summary issue with rank
deltas + new achievements.
Workflow uses only the default GITHUB_TOKEN with issues:write — no
extra secrets to configure.
Three small UI surfaces were showing values that looked dynamic but
were actually frozen at build time or hardcoded — fine for a design
sketch, wrong for a live agent UI.
settings.tsx (preset cards):
Dropped `speed` ("180 t/s" / "84 t/s") and `bench` ("MMLU 88.5" /
"AIME 79.8") rows. These were build-time literals presented next
to the contractual `ctx` / `out` caps, so users read all four as
authoritative model metadata. ctx + out stay (those *are* contract).
Re-add speed / bench when we have a source of truth that updates
with the model, not as inline constants.
cards.tsx (PlanCardView badge):
The "运行中" pill rendered unconditionally — a plan with every
step `done` still flashed "running". Extracted `derivePlanBadge`
to fold items into one of err / warn / run / ok / run for failed
/ blocked / active / all-done / todo respectively, reusing the
existing `.pill-tag` color variants.
live.tsx (ToolRunningCard skeleton):
Three `skel-line` placeholders rendered above the real `live-log`
when both existed, so the user saw a fake gradient stack glued on
top of actual streaming output. Switched to else-branch — skeleton
only when there is nothing real to show.
* feat(acp): --transcript flag for headless cost capture
Tees raw LoopEvents through writeRecord/recordFromLoopEvent during
session/prompt so headless ACP callers can parse usage, cost, and
prefixHash without driving the TUI. Reuses the JSONL shape chat and
code already emit; zero changes to transcript helpers.
Single-session-per-process — mirrors chat/code behavior; the JSONL
stays cleanly seekable.
Adds tests/fixtures/acp-driver.ndjson as scaffolding for future
end-to-end ACP smoke tests, per maintainer ack on #765.
Refs: #765
* test(acp): assert fixture sessionId is a placeholder
Adversarial review noted that piping acp-driver.ndjson as-is into
the binary produces ERR_INVALID_PARAMS "unknown session" with no
hint about the substitution requirement. Lock in the placeholder
contract so anyone editing the fixture sees the test fail with a
clear comment instead of discovering the trap at runtime.
Auto-preview's symbol outline was TS-only. Any non-TS file longer
than 200 lines dropped into the preview path with no navigation map —
just head 80 + tail 40 and an opaque "N lines omitted" marker. The
model had nothing to range-read against, so for Python / Go / Rust /
Markdown files the "scope your read" workflow stopped working past
the threshold and the model either guessed or full-read.
Adds per-language regex extractors dispatched on extension:
- TS/JS/TSX/MJS/CJS — existing top-level export logic (parity preserved)
- Python — top-level def / class (indent-sensitive, skips methods)
- Go — top-level func / type / var / const, methods captured by name
- Rust — fn / struct / enum / trait / impl / mod / type / const / static,
impl block target type extracted (incl. impl<T>, impl Trait for X)
- Markdown — headings at all levels, fenced code blocks ignored
Outline module lives in src/tools/fs/outline.ts. Header wording goes
from "N top-level exports" to "N symbols" so it fits all languages;
elision text follows. Per-entry shape unchanged for TS — the kind +
name still appear after the line marker, just no longer hardcoded to
"export".
Picked regex per language over tree-sitter because the published WASM
parsers are 5-50MB each — too much install weight for "show me the
top-level symbols". Tree-sitter remains a viable upgrade if the regex
extractors start hitting precision limits in real use.
The existing flash→pro escalation only fires on "repair signals"
(SEARCH-mismatch / scavenged / truncated / repeat-loop). A model
stuck reading file after file without ever writing or producing a
final answer never trips that trigger — every read returns cleanly,
so from the harness's view the turn looks healthy while the user
watches the bill climb.
#681 hit this exact shape: 34 tool calls / 142 log messages, top-5
all `read_file`, ¥3.41 spent on flash before the user aborted. The
underlying issue is "flash too weak for this task"; the right fix is
to detect the stuck-in-reads pattern and switch to pro mid-step.
Adds `ReadOnlyLoopTracker` (default threshold 8, env-tunable via
`REASONIX_READONLY_LOOP_THRESHOLD`). Each successful tool result
either bumps the streak (read-only) or resets it (mutating). When
the streak crosses threshold, set `_escalateThisTurn = true` and
yield a one-shot warning — same escalation contract as the existing
failure-signal path. `autoEscalate=false` still blocks; the user
keeps that lever.
Threshold of 8 is on the conservative side — bursty read-heavy
tasks (e.g. "read these 5 files then edit one") still finish on
flash; the trigger only catches genuine unproductive loops.
Closes#681.
The picker's prefix regex was ASCII-only:
/(?:^|\s)@([a-zA-Z0-9_./\-]*)$/
So `@中文/` failed the `$` anchor on the first non-ASCII byte and
`detectAtPicker` returned null. The picker disappeared, Tab had
nothing to drill into, and the user couldn't enter a Chinese-named
folder via @.
Swap the inner char class for `[\p{L}\p{N}_./\-]` with the `u` flag.
Same change on `AT_MENTION_PATTERN` so the expander recognises the
completed mention too.
Closes#749.
#760 added the keystroke handler that lets users type blind while
scrolled up. It also added a `useChatScrollState((s) => s.pinned)`
subscription inside `AppInner`, which re-renders the whole subtree
every time scroll state ticks.
Move the handler into a leaf component the same way
`InputAreaWithHistoryHint` already isolates its `pinned` read. The
leaf renders `null` and registers `useKeystroke` against
`enabled && !pinned`; AppInner just hands it `input` / `setInput` /
`onReturnToBottom`. Behavior identical; AppInner now stays still on
scroll events again.
When the user scrolls up to read chat history, PromptInput is unmounted
and keystrokes are silently dropped. Add an App-level keystroke handler
that captures printable characters, backspace, and Enter (returns to
bottom) when pinned=false, so the user can type blind while reading
history and see their input when they scroll back — Claude Code parity.
Co-authored-by: rokyplay <[email protected]>
Extract `createMcpRuntime` from `chat.tsx` into a non-tsx module
`cli/commands/mcp-runtime.ts` and import from both `chat` and `desktop`.
chat.tsx re-exports the public types for backwards compat.
In `desktop.ts`:
- Each `Tab` now owns an optional `mcpRuntime` plus a `mcpStatuses` map.
`bridgeTabMcp` lazily constructs the runtime, wires a lifecycle sink
that updates the per-spec status, and calls `reloadFromConfig` against
the tab's loop so MCP tools register into the live prefix.
- `closeTab` calls `runtime.closeAll()` so MCP children exit cleanly.
- `mcp_specs_add` / `mcp_specs_remove` trigger `bridgeTabMcp` so live
config edits reach the runtime without restarting the tab.
- `$mcp_specs` now carries `status` + optional `statusReason` /
`toolCount` per spec. `bridged` stays as a coarse "all connected"
flag.
The right-panel Tools tab renders the per-spec dot — green for
connected, yellow pending for handshake / configured, grey for failed /
disabled — and the row text shows the live state (tool count, failure
reason).
Closes#753.
Lists project- and global-scope memory entries beside the chat. The
desktop command opens a `MemoryStore` per tab and emits the entries as
a new `$memory` event on tab open. Each row shows the scope badge +
description, matching the v4 mockup. Empty state keeps the existing
placeholder copy.
Refresh is currently tab-open only — when the agent writes a new
memory via `update_memory`, the panel reflects it on the next tab open
/ reload. Live refresh on tool result can come later if it bites.
Closes#754.
Modified files (yellow dot) and in-context files (green dot) now show
beside their row, matching the v4 mockup's `data-s="m"` / `data-s="c"`
hooks (CSS was already shipped).
- **Modified**: new Tauri command `git_status(root)` runs `git status
--porcelain -z`, parses index/worktree codes into coarse kinds. The
tab polls every 5s and on workspace switch; returns empty (silent)
outside a git repo or when `git` is missing.
- **In context**: reducer scans `tool.intent` events for the known
file-reading tools (`read_file`, `list_directory`, `directory_tree`,
`search_files`, `get_file_info`, `glob_files`) and accumulates each
path arg. `$session_loaded` rebuilds the set from loaded segments so
resumed sessions show their dots without re-reading anything.
Closes#756.
System prompt + tool specs are constant per tab. Compute their token
count via `countTokens` at tab open, emit as a new `$ctx_breakdown`
event (with `reservedTokens` field), and render the band on the right-
panel meter alongside cached / used / free.
Cache-hit/miss numbers from the API include the reserved prefix once
the cache warms up, so the visual subtracts `reserved` from those
buckets to keep the segments disjoint. With a cold cache, the
reserved tokens land in `cacheMiss`; subtract from `used` instead.
Off by at most one turn of arithmetic; not exact, but doesn't double-
count visually.
Closes#755.
The desktop runtime doesn't actually bridge MCP yet — the
`$mcp_specs` event is emitted with `bridged: false` indefinitely, so
the Tools tab was painting every server as perpetually "loading". Read
the absence of bridging as the truthful "configured but not active in
this tab" state. When desktop-side MCP bridging lands (separate scope),
the `bridged: true` path already maps to "ready" with no further UI
change.
Part of #744.
Click a directory row to fold or unfold its descendants. Tracks a
`collapsed` set of paths and walks each entry up the parent chain
(reconstructed from the flat depth-first list) to decide visibility.
File rows lose their pointer cursor since they're not interactive.
Adds a `.caret` slot with chev / chev-right icons so the affordance is
visible. Dirs default to expanded — collapsing is opt-in and resets
when the workspace switches.
Part of #744 — depth-2 fetch from the Tauri side stays the same; lazy
deeper fetch can come later if anyone hits the bottom.
The right context panel was a placeholder per #744. This first pass
wires the two tabs whose data is reachable without big new plumbing:
- Files: new Tauri command `list_workspace_tree(root, maxDepth)` walks
the workspace up to depth 2, skipping hidden + standard noise dirs
(`node_modules`, `target`, `dist`, `build`, `out`), capped at 800
entries. Front-end renders the design's `.tree` markup with depth
indentation, refetches on workspace switch.
- Tools: switched from the per-message tool-call histogram to the real
MCP server list using `state.mcpSpecs` + `state.mcpBridged`. Each row
shows transport + ready/loading + parse error if any.
- Memory: kept placeholder but pulled the inline styles into a shared
`.ctx-empty` class.
- Rules: still editMode-driven (no per-pattern allowlist exposed to the
desktop yet) but the items now reflect what each mode actually
permits, instead of two hardcoded rows.
- Meter: bumped the context max from 128K to 1M to match the V4
catalog.
Reserved-tokens bucket and a real file-tree expand interaction stay
deferred — both need event-shape / Tauri additions and were called out
as separate stages in #744.
The model picker still listed `deepseek-chat` / `deepseek-reasoner` with
128K / 64K context — both stale. The CLI canonicalized on
`deepseek-v4-flash` / `deepseek-v4-pro` (presets.ts) at 1M context
(telemetry/stats.ts) a while back; the desktop UI never caught up, so the
settings page contradicted the status-bar label ("DEEPSEEK-V4-FLASH").
Pull the model card metadata, composer preset labels, and the default
modelLabel fallback into line with the CLI source of truth.
Closes#745
When `request()` did `Promise.race([transport.send(), promise.then(() => undefined)])`,
the `.then()` derivative was a fresh promise whose rejection only chained
through Promise.race's internal subscriber. On Node 20 that subscriber doesn't
reliably suppress unhandledRejection once the race has already settled — so
when send wins the race and the pending request later times out, the derived
chain rejects with no live handler and the CLI crashes mid-session.
Use the two-arg form `promise.then(() => undefined, () => undefined)` so the
derivative is always fulfilled. The original rejection still propagates to the
caller via `await promise` below.
Adds a regression test using a silent-server transport where `send()` resolves
immediately and the response never arrives — exactly the shape of the crash
report. The `unhandledRejection` handler must not fire.
On Node ≥ 24, Windows child processes killed via `taskkill /T /F` often
never emit a `close` event — libuv's stdio handle lingers even though the
process is reaped. `JobRegistry.stop()` waited up to 5s on `closedPromise`,
gave up, then returned a snapshot with `running: true` even though we'd
just killed the process. Vitest then asserted on that ghost-running state
and the entire test (and pre-push verify) failed.
Two pieces:
- Settle the record on `exit` in addition to `close`. `exit` fires the
moment the OS reaps the process, well before stdio drains.
- If neither fires by the SIGKILL deadline, assume the kill landed and
mark the job dead anyway. We issued `taskkill /T /F`; trust it.
Same fallback in `shutdown()` for the multi-job case.
The bottom-bar folder indicator was display-only, while the model /
currency / theme / settings segs next to it are all clickable. Wire
the same WorkdirPop the title header uses so users can pick a recent
workspace (or browse for a new one) without scrolling back up.
Anchor the popover above the statusbar — extend the Anchor type with
`bottom`, and use `position: fixed; bottom: ...` when set so the
popover sits cleanly above the trigger instead of trying to render
below the viewport edge.
Picking "new" in the /session or launch picker called
`setActiveSession(undefined)`, propagating an undefined `session` to
`CacheFirstLoop`. `this.sessionName` became null, and every
`appendSessionMessage` short-circuited on the `if (this.sessionName)`
guard — the new chat never landed on disk.
Mint a fresh `${base}-${YYYYMMDDHHMMSS}` name at both pickers so the
loop has somewhere to write. Seconds-precision stamp avoids
back-to-back-click collisions; the base is the current session minus
any prior 12/14-digit timestamp suffix, falling back to `default`.
Closes#737
`stop()` and `shutdown()` legitimately need >5s on Windows because
`taskkill /T /F` is async and the SIGKILL race inside `stop()` waits
up to 5s for `close` to fire. Vitest's default 5s test timeout was
killing the test before `stop()` could return, masking the real
behavior with "Test timed out".
Bump the three affected tests to a 15s budget. The underlying paths
still complete in ~1-3s on healthy runs; the wider window only matters
when taskkill is slow to propagate.
Two follow-ups from the #734 merge that didn't justify another round
on the contributor's branch.
1. PlanConfirm.tsx — document what `EXPANDED_MODAL_OVERHEAD_ROWS = 12`
and `EXPANDED_DETAIL_CHROME_ROWS = 4` actually count. Both are
derived from the card chrome (header / step list / dividers /
footer hints / picker); without the comment, the next person who
reflows the modal won't know which constant to retune.
2. tests/plan-confirm.test.tsx — drop the inline
`text.replaceAll("\x1b", "").replace(/\[[0-9;]*m/g, "")` helper for
the `strip-ansi` package. The inline version only handled SGR
subset; `strip-ansi` covers OSC 8 hyperlinks (which #730 now emits
in plan markdown bodies) and CSI subparam edge cases. Promoted
`strip-ansi` from a transitive dep (via `string-width`) to an
explicit devDependency so the import doesn't break if the parent
chain shifts.
Lockfile changed because `npm install` resynced the existing 0.39.1
→ 0.40.0 version drift and dropped now-orphaned `patch-package`
transitive entries — both pre-existing maintenance debt, no upgrades
on this project's own deps.
* fix(plan): stabilize expanded approval modal layout
Keep the expanded plan confirmation view from clipping or jumping while scrolling, and document the new Ctrl+P summary/detail toggle.
* fix(tests): restore React value imports for JSX runtime
Keep JSX-based Ink tests using value imports so Vitest can execute them during verify and push hooks.
Requested in #725. Borrowed from Claude Code: while you're deep in a
coding turn, sometimes you want to ask the model a quick unrelated
question without breaking the conversation flow or eating turns of
context budget. `/btw` runs the question against a fresh blank-slate
message list, displays the answer inline, and never touches
`loop.messages` — the next normal turn sees the same context it would
have seen if `/btw` had never been typed.
Implementation lives in the same App.tsx submit branch as `/resource`
and `/prompt`: intercept the command before the synchronous slash
dispatcher, call `loop.client.chat()` with `[system, user]` only,
push the answer through `log.pushInfo` with a `≫ btw` header.
The system prompt instructs the model to answer concisely, in plain
prose, with no tool calls or follow-up questions. The command runs at
the loop's current model (so `/preset flash` before `/btw` still saves
money on side questions).
Registry entry in `SLASH_COMMANDS` (chat group, `<question>` argsHint)
means the command surfaces in `/help`, the slash-suggestions palette,
and the `+ N advanced` count.
i18n strings:
- `app.btwUsage` — shown when `/btw` is typed bare
- `app.btwHeader` — the `≫ btw` answer-card header
- `app.btwFailed` — title for the warning card on API failure
Closes#725
Reported in #728: after a single round of dialogue the blue cursor in
the composer disappears and the user can no longer tell where typed
characters will land. Regression from #672, which traded the
hardcoded `cursorVisible = true` for `useSlowTick() % 2 === 0`.
The slow-tick frame is driven by Ink's shared animation timer, which
the TUI suspends whenever the conversation is idle:
const tickerSuspended = modalOpen || (!busy && !isStreaming);
When the timer pauses, Ink's `useAnimation` stops advancing but keeps
returning the last frame value. If a streaming turn ran for an odd
number of seconds, the frame freezes on 1 (or 3, 5, …), so
`frame % 2 === 0` evaluates to `false` and the cursor stays blanked
indefinitely. The user only sees the cursor on the empty-input first
mount (frame 0) — every later idle state inherits whatever parity the
last active stretch happened to land on.
Add `useCursorBlink()` in `ticker.tsx` which combines the slow tick
with the ticker-active state: while suspended, force visible; while
active, blink each second as designed. Replace the single inline
expression in `PromptInput.tsx`.
Regression test in `tests/cursor-blink.test.tsx` mounts a probe inside
an active TickerProvider, advances fake timers past a slow tick so the
raw frame is odd, then rerenders with the provider suspended and
asserts the probe still reads `ON`. Without the active-guard it reads
`OFF` (the original bug).
Closes#728
Reported in #727: SiliconFlow's `Qwen/Qwen3-VL-Embedding-8B` model
sometimes returns fewer entries in `data[]` than the number of inputs
in the request. Hit by index-build at chunk 8 of 72, with
`OpenAI-compatible response missing embedding at index 8`, which
hard-aborted the whole index pass — the user lost 71 already-embedded
chunks and had to switch models. The pure-text sibling
`Qwen/Qwen3-Embedding-8B` does not exhibit this.
The OpenAI-compat client used to validate full coverage with:
for (let i = 0; i < out.length; i++) {
if (!out[i]) throw new EmbeddingError(`... missing embedding at index ${i}`);
}
That was correct against strict providers but wrong as a hard error
against providers that silently drop inputs. `embedAll`'s contract
already supports `Array<Float32Array | null>` and the index builder
already handles `null` slots by logging via `onError` and skipping
the chunk.
Change the OpenAI-compat path to match that contract:
- `requestOpenAICompatEmbeddings` now returns
`Array<Float32Array | null>` instead of throwing on partial
responses. Other validation (invalid index, non-array embedding,
HTTP errors) still throws.
- `embedAllOpenAICompat` walks the returned array and routes each
`null` slot through `opts.onError` so the index builder prints
`! skipped path:start-end: provider dropped input N from the batch`
for the dropped chunks and keeps going.
- `embedOpenAICompat` (single-text path) keeps the strict throw — if
the provider rejects a single input there is nothing else to return.
Regression tests in `tests/semantic-embed-tolerant.test.ts` cover
both the SiliconFlow VL case (partial batch → partial result + per-
slot onError) and the single-text refusal (still throws).
Closes#727
Reported in #724: when /user/balance returns both USD and CNY entries
(e.g. USD 4.99 top-up + dust CNY 0.47), the TUI status row, doctor
check, desktop kernel, and dashboard cockpit all rendered just the
first array entry — typically CNY in that order — making the account
look almost empty even though the user has real USD balance.
Five call sites were doing `balance_infos[0]!`:
- `src/cli/ui/useSessionInfo.ts` (initial fetch + refresh)
- `src/cli/commands/desktop.ts` (Tauri kernel `$balance` event)
- `src/cli/commands/doctor.ts` (api-reach check, both branches)
Add `pickPrimaryBalance(infos)` in `src/client.ts` that walks the array
and returns the entry with the largest `total_balance`. For the
common single-wallet account the behaviour is unchanged (the only
entry wins); for multi-wallet accounts the wallet the user actually
funded surfaces correctly.
`doctor`'s api-reach check additionally enumerates every wallet when
there are multiple, so a diagnostic now shows
`/user/balance ok — 4.99 USD + 0.47 CNY` instead of hiding one half.
The dashboard cockpit reads `stats.balance` which is constructed from
`balanceRef.current` (the primary surfaced by `useSessionInfo`), so
this fix propagates to the dashboard wire shape without separate
plumbing.
Unit tests in `tests/pick-primary-balance.test.ts` cover the empty
case, single-entry passthrough, the issue-#724 USD+CNY case, the
zero-USD fallback, and the tie-break invariant.
Closes#724
Reported in #723: assistant replies containing `[text](url)` render as
blue underlined text but aren't actually clickable on hover — supporting
terminals (kitty, iTerm2, Windows Terminal, VSCode) need the OSC 8
hyperlink escape sequence around the label.
The `osc8()` helper in `src/cli/ui/markdown.tsx` was already named for
this — it just never emitted the escape. The `_target` parameter was
prefixed with an underscore because the function ignored it.
Wire it up properly:
- `osc8()` now wraps its child in `<Transform>` that emits
`ESC ]8;; URL ESC \ ... ESC ]8;; ESC \` around the rendered text.
Accepts `React.ReactNode` so it can wrap an `<Inline>` subtree (links
with bold / em / codespan inside).
- The `case "link"` branch of `InlineToken` now routes through `osc8()`
with `l.href` instead of a styled-but-inert `<Text>`.
- `SpanText` in `src/cli/ui/markdown-view.tsx` (used by PlanConfirm /
PlanRefineInput) gets the same treatment so plan-modal links and
file refs are also clickable.
Frame renderer at `src/frame/ansi.ts:146` already emits OSC 8
unconditionally; this matches that convention — terminals that don't
support OSC 8 silently discard the sequence.
Closes#723
Reported in #721: typing in the dashboard composer feels laggy on long
sessions. Root cause is that every keystroke commits to `input` state,
which forces ChatPanel to walk its entire vnode tree on each frame.
ChatMessage was already wrapped in memo (#560), so historical bubbles
short-circuit individually — but Preact still has to map() over every
message, evaluate the per-row `Boolean(streaming && streaming.id === m.id)`
discriminator, and diff each ChatMessage element. For a session with
100+ messages the per-keystroke work is enough to drop frames.
Move the message-list render into a `<ChatFeed>` sub-component and wrap
it in memo. With `messages` and `streaming` refs both stable while the
user is typing, memo bails the whole feed out — keystrokes no longer
touch the feed at all. SideRail and ChatStatusBar get the same
treatment so /overview poll churn and input edits don't repaint the
right-rail progress bars and statusbar.
Closes#721
* feat(desktop): wire up stubbed UI surfaces, drop roadmap-only tabs
A pass over the desktop client looking for UI that *renders* without
actually doing anything. Found a fair amount of theater.
- context panel "工具" tab was showing a hardcoded list of fake MCP
servers (filesystem/shell/search/edit, made-up tool counts, fake
"ready" dots). Replace with real tool-call frequency from the
current session's assistant messages; empty state when there are
none yet.
- sidebar footer's "审批规则" and "设置" rows both invoked the same
onOpenSettings callback. Route 审批规则 to the rules page via a new
initialPage prop on SettingsModal; drop the stray ⌘, accelerator on
the rules row since it doesn't open settings any more.
- settings nav had three pages whose body was literally a "在路线图上 /
即将开放" card with no controls: MCP, Skills, and (kept) Memory.
Drop MCP and Skills from the nav. Memory page stays — its copy
about CLAUDE.md / AGENTS.md injection is at least true.
- add /export and /lang slash commands. The composer's slashIcon
table already had icons for both — they were just never wired.
/export reuses the existing exportConversation; /lang flips between
en / zh-CN via the existing i18n setLang.
- ⌘, toggle, command palette, title bar, and status bar now go
through a single openSettingsAt(page) helper so the modal opens on
the right tab from each entry point.
* feat(desktop): restore MCP + Skills settings pages, now wired to backend
The previous commit on this branch dropped the MCP and Skills tabs as
roadmap-only placeholders. That was wrong — the CLI has both features
and the design mockup keeps tabs for them. Bring them back, properly
hooked up this time.
Backend (src/cli/commands/desktop.ts):
- new RPC commands: mcp_specs_get / mcp_specs_add / mcp_specs_remove
/ skills_get
- new emitted events: $mcp_specs (parsed specs + bridged flag) and
$skills (project + global + builtin)
- specs are validated through parseMcpSpec before persisting; add /
remove round-trip through readConfig / writeConfig
- skills load via SkillStore({ projectRoot: tab.rootDir }), so they
follow the current workspace and re-emit on switchWorkspace
- both fire on initial $ready and on tab_open
MCP page (settings.tsx PageMCP):
- lists every configured spec with name + transport summary
- "移除" button → mcp_specs_remove
- input + 添加 button → mcp_specs_add (parser-validated)
- header notes that the desktop session doesn't itself bridge MCP
yet, so changes take effect in TUI sessions; once we add the
bridge in desktop.ts the bridged flag flips and the caveat
disappears
Skills page (settings.tsx PageSkills):
- one card per skill: /name, scope, runAs, model override, full
description, file path
- read-only — skills are markdown files on disk
* fix(desktop): settings body scrolls when content exceeds viewport
.settings is a grid (200px + 1fr) with fixed height; .settings-main is
flex column with .settings-head (intrinsic) + .settings-body (flex: 1,
overflow-y: auto). Skills page can render dozens of cards — once the
total exceeds the modal height, .settings-body wasn't scrolling
because .settings-main, a grid item with the default min-height: auto,
would let its content expand it past the grid track. The .settings
overflow:hidden then clipped the bottom instead of yielding a scroll
inside .settings-body.
Add min-height: 0 to .settings-main so the grid track bounds it, and
.settings-body's overflow-y:auto kicks in normally. All pages benefit;
Skills (variable count) and MCP (long URLs) are the visible wins.
The card-based UI rebuild had dropped the .palette-* styles, so Cmd+K
was rendering unstyled. Bring it back as .cmdk-* matching the mockup —
grouped (导航 / 动作 / 目录 / 设置), Search head icon, item-count footer.
While there: pull the rest of the mockup polish.
- splash intro on first launch (per session): plankton drift + whale
silhouette glide + Reasonix wordmark reveal, ~3.3s, skippable by
click / Esc / Enter / Space, sessionStorage-gated so HMR doesn't
re-trigger it.
- workdir popover anchored to the main-head breadcrumb (also Cmd+O),
lists Settings.recentWorkspaces, current dir checkmarked, falls back
to the existing pickWorkspace dialog from a "browse local…" button.
- move the transient flashToast from bottom-center to bottom-right so
it stops landing right on top of the Review/Auto/YOLO switch in the
composer foot.
i18n: palette.group{Nav,Action,Workspace,Settings} + palette.countSuffix
+ workdir.{title,searchPlaceholder,empty,browse} for both en and zh-CN.
Final ACP slice tracked in #103. Internal PauseGate requests
($confirm_required / $plan_required / $checkpoint_required /
$revision_required / choice) now surface to the ACP host as outbound
`session/request_permission` requests, and the host's response is
mapped back into the Reasonix verdict shape and resolved into the gate.
A Zed / JetBrains / AionUI host can now drive a real flow — including
shell command authorization forwarded to mobile via AionUI / Feishu —
end-to-end.
Mechanics:
- AcpServer gains sendRequest(method, params) with id tracking +
Promise-based resolution. Inbound responses (id + result|error,
no method) route to the matching pending entry. close() rejects
all in-flight outbound calls.
- src/acp/gates.ts maps each PauseGate kind to the right
PermissionOption list (allow_once / allow_always / reject_once)
and converts the optionId in the response back into the internal
verdict shape. Allow_always carries a command-prefix glob
(`{firstWord} *`) or the path_access allowPrefix so the same
decision auto-resolves next time via the existing pause-policy.
- acpCommand registers a global pauseGate.on listener that uses
AsyncLocalStorage to find the currently-running session and
forwards the gate request. Gates outside any active session
(rare — initialization races) get cancelled cleanly. The shared
auto-resolve policy (review/auto/yolo) still runs first, so
/run_command in yolo mode bypasses the host as expected.
13 new tests covering: outbound sendRequest happy-path and error
path, close() rejecting in-flight requests, permissionOptionsFor +
verdictFor mapping for shell / plan_proposed / plan_checkpoint /
plan_revision / choice, and an end-to-end requestPermissionForGate
round-trip via the live server.
Refs #103
Builds on the stage-1 NDJSON foundation from #714. Internal tool events
now surface to ACP hosts as the corresponding session/update variants,
so a Zed / JetBrains / AionUI client sees real-time tool execution
matching what the TUI / desktop already show.
Mapping (in src/acp/dispatch.ts):
- tool.preparing → tool_call (status=pending, kind classified from
name)
- tool.intent → tool_call_update (in_progress) + a follow-up
tool_call carrying rawInput (parsed from args JSON if valid, else
the raw string)
- tool.result → tool_call_update (completed | failed) with the
output wrapped as content[].content.text, clipped at 8000 chars
with a truncation suffix
`toolKindFor()` maps internal tool names to the ACP-spec kinds:
read (read_file, glob, list_directory, …), edit (write_file,
multi_edit, …), search (search_content, search_files), execute
(run_command, run_background), other (everything else).
7 new tests in tests/acp.test.ts covering each variant + the
classification table + the clip threshold.
Refs #103
First slice of the ACP (Agent Client Protocol — agentclientprotocol.com)
support tracked in #103. Spawns reasonix as an ACP agent on stdio
NDJSON JSON-RPC 2.0; the cache-first loop and prefix hashing are
untouched, only the IO layer changes.
What stage 1 covers:
- `reasonix acp` subcommand with --dir / --model / --preset / --budget
- src/acp/ — JsonRpc types + NDJSON `AcpServer` (one object per line,
no embedded newlines, per the transport spec)
- initialize handshake with capability negotiation
- session/new — builds a per-session CacheFirstLoop with its own
toolset rooted at cwd (or the cwd from the request)
- session/prompt — drives one turn, streaming `agent_message_chunk`
and `agent_thought_chunk` via session/update notifications; returns
`{ stopReason: end_turn | cancelled | error }` on completion
- session/cancel — notification aborts the in-flight turn cleanly,
leaving the session reusable for the next prompt
What's deferred to stage 2 / stage 3 (tracked in #103):
- tool_call / tool_call_update notifications (stage 2)
- session/request_permission for $confirm_required / $plan_required /
$checkpoint_required gates (stage 3)
- plan updates and authorize round-trips
- session/load (loadSession capability advertised as false for now)
Tests: 10 in tests/acp.test.ts covering framing, method/notification
dispatch, parse-error response, internal-error response, and the
initialize handshake contract.
Hardcoded four types (user / feedback / project / reference) didn't scale
for teams whose memory bucket actually wants distinct categories — non-
negotiable security rules, design-system conventions, deploy checklists,
etc. Without a real type they all collapse into `reference` and the model
treats a security constraint with the same weight as a style note.
Changes:
- MemoryEntry.type relaxed to `BuiltinMemoryType | (string & {})`; the
four built-ins stay in BUILTIN_MEMORY_TYPES for UI / docs.
- MemoryEntry gains optional `priority: low|medium|high` and
`expires: project_end`. Both round-trip through frontmatter.
- config.memory.customTypes — new ReasonixConfig field. Each entry can
set a default priority + expires for its type name.
loadMemoryTypeRegistry() merges built-ins with the config overlay
(rejecting bad names and built-in collisions).
- applyUserMemory now scans for high-priority entries (own field OR
the type's config default) and prepends a `# HIGH PRIORITY
constraints (must observe)` block with `!!! [scope/type/name]`
headings ahead of the regular memory index — so security-class rules
get the strongest framing the system prompt offers.
- `/memory list --type X` filters by type; list rows get `⚠` for high
and `·` for low priority.
- `/memory clear project confirm` additionally removes any global-scope
entry with `expires: project_end` (lifecycle tied to the project).
- The `remember` tool drops its hardcoded enum, surfaces the config-
declared custom types in its description, and accepts `priority` /
`expires` parameters.
Behavior is fully backward compatible: existing memory files without the
new fields parse and inject exactly as before; an empty config produces
zero behavior change.
Closes#709
Replace the ad-hoc components.tsx / toolRenderers.tsx tree with a card
system organized per kind (plan, reasoning, shell, tool, diff, error,
approval, etc.), each with a tone palette and built against the design
mock-ups in IBM Plex.
UI surface:
- Composer gains a Review / Auto / YOLO mode switch wired to
settings.editMode and a working preset dropdown (auto / flash / pro).
Paperclip and image buttons now open a file picker and insert the
pick as an @-mention. Narrow-width adaptation hides labels first,
then shrinks the model pill, before anything overflows.
- Title bar gets a real "more" menu (palette, export, clear, settings).
Status bar exposes currency toggle (CNY / USD) instead of a no-op
language toggle. ⌘B toggles the sidebar, ⌘⌥B the context panel.
- YOLO triggers a hatched red sub-header strip under main-head with a
one-click "back to Review" button, so the dangerous mode is never
silent.
- Toast styling that got lost in the stylesheet swap is restored.
Backend:
- emitSessions includes meta.summary, and runTurn writes a 60-char
summary on the first user input of a session, so the sidebar shows
real chat titles instead of `desktop-202605121013-1`. Main-head H1
falls back to the first user message of the in-flight session.
Everything is wired to the existing RPC contract (settings_save,
mention_query / preview / picked, session_load / delete, the five
pending kinds). No new transport.
- vary the right-side color per badge so they stop reading as one dark blob; keep labelColor 161b22 for cohesion. add npm/CI/node logos. drop the static color override on CI so the badge reflects real build status.
- point contrib.rocks at the canonical esengine/DeepSeek-Reasonix; the old esengine/reasonix worked via GitHub redirect but contrib.rocks served a stale 9-author snapshot. switching the cache key forces a regen with all 18.
npm-only release. The Tauri desktop source is in the repo and the CLI
subcommand works, but installer bundles for macOS / Windows / Linux
don't ship this round (separate release once signing's settled).
Highlights:
- Tauri desktop client with multi-tab concurrent runtimes (#689)
plus a near-full polish pass: wallet balance, version chip, active-
plan rail, abortable pause-gates, edit-gate pill, en + zh-CN i18n,
shared pause-policy module dedup'd with the CLI TUI (#701)
- checkpoint API + git-changes panel in the embedded dashboard (#682)
- outside-sandbox file access approval modal (#696)
- MCP loading pill + readiness gate on tool dispatch (#687)
- escalate-after flag for flash → pro threshold (#699)
Fixes:
- CardStream Maximum-update-depth crash, quantize window so boundary
cards stop oscillating (#700, #702)
- `reasonix code` bridges config key to env + lazy subagent client so
fresh installs can reach the setup wizard (#703)
- pinned-mode scroll shrinks coalesced (#666), generic CSI key decode
(#692), shell-confirm preview clamp (#691), frontmatter BOM/folded
lines (#690), MCP error classification (#688), and more
`reasonix code` crashed at boot with "DEEPSEEK_API_KEY is not set" for
two reasons stacked:
1. code.tsx never bridged ~/.reasonix/config.json → process.env the way
chat.tsx / desktop.ts / run.ts do. A key the user stored via
`reasonix setup` was invisible to `code`.
2. buildCodeToolset eagerly constructed a DeepSeekClient for the
subagent runner. With no env key, the constructor throws — before
chatCommand mounts the wizard that would prompt for one.
- code.tsx now calls loadDotenv() + bridges loadApiKey() into env at
the top of codeCommand, mirroring chatCommand's setup
- setup.ts defers the subagent DeepSeekClient to first dispatch so
toolset construction succeeds even when no key is configured yet
- new tests/code-setup-lazy-subagent.test.ts pins the invariant
Same shape as #549. In pinned mode scrollRows tracks maxScroll, and
maxScroll = inner.height - outer.height. The items useMemo depends on
both scrollRows and outer.height, so a sibling row toggling (ToastRail
appearing, ThinkingRow flipping) shifts outer.height by ±1 → window
moves → a card straddling the live↔spacer boundary flips → inner.height
changes by Δ → setMaxScroll → scrollRows changes → useMemo recomputes →
card flips back. With flash streaming compounding inside the same React
batch, the chain reaches MAX_NESTED_UPDATES and aborts inside ink's
useBoxMetrics (#700).
Quantize the window position to VISIBLE_BUFFER_ROWS buckets. Sub-bucket
scrollRows / outer.height wiggles now map to the same window, so items
is referentially-stable across them and the feedback loop dies on the
first re-render.
- extract computeCardStreamItems as a pure exported function for tests
- new tests/card-stream-items.test.ts asserts live-set stability across
every sub-bucket scrollRows delta and a range of outer.height values
Closes#700
* fix(i18n): point session banners + overflow error at /new and /sessions
The top-level /forget command was removed in the slash refactor, but
the resumed-session and new-session banners + the context-overflow
error still told users to type it. Point them at the surviving paths
instead: /new for a fresh start, /sessions ([d] to delete) for
manage / rename / drop.
Closes#697
* feat(desktop): surface version + wallet balance, fix ⌘K Settings
Tauri shell had no visible version or DeepSeek balance, and ⌘K's
Settings was a stub toast despite SettingsPanel being mounted.
- $settings now carries VERSION → version chip in Sidebar brand
- new $balance event polls /user/balance on startup, after each
turn, and after key/workspace changes → wallet card in Sidebar
- ⌘K Settings opens the existing panel; About shows real version
- ⌘K gains New/Close tab, Stop turn, Copy/Export reply, Pick workspace
* feat(desktop): localize UI strings (en + zh-CN) with live toggle
Tauri shell was a mix of English labels and Chinese hints with no
way to switch. Add a small React i18n module (localStorage + listener-
based re-render), seed en / zh-CN dictionaries, and surface a Language
picker in Settings.
- new desktop/src/i18n/{index,en,zh-CN}
- migrate ⌘K palette items, sidebar nav + wallet label, App toasts,
composer placeholder + kbd hints, plan/choice modal placeholders
- Settings grows a Language section; auto-detect from navigator.language
on first launch, sticky via reasonix.lang
* feat(desktop): active-plan rail + checkpoint card, abortable plan gates
Desktop dropped plan_checkpoint and plan_revision pause-gate requests on
the floor and abort only flipped the per-turn AbortController, so once
mark_step_complete fired the user was wedged with no UI response and no
way out.
- pause-gate: new cancel(id) using existing safeCancelVerdict
- desktop CLI: per-tab pendingGateIds + completedStepIds; abort now
drains gates via cancel(id), emits $plan_cleared
- desktop CLI: emit $plan_required steps, $checkpoint_required (with
done/total), $revision_required, $step_completed, $plan_cleared
- desktop UI: state grows activePlan, pendingCheckpoints,
pendingRevisions; reducer wires resolve_plan(approve) → activePlan,
resolve_revision(accepted) → swap remaining steps
- desktop UI: new ActivePlanRail above messages (collapsible, progress
bar, per-step risk + result), CheckpointCard (continue/revise/stop),
RevisionCard (accept/reject/cancel); Stop button in rail when busy
- i18n: plan / checkpoint / revision strings in en + zh-CN
* feat(desktop): localize Settings panel, drop ThinkingBar Stop button
Settings panel still rendered every section label, hint, and option
description in hardcoded English. Toggling the language picker did
nothing for the panel itself.
ThinkingBar had its own Stop pill on the right while the composer's
send button already turns into Stop when a turn is in flight. Two
buttons for the same action.
- migrate every SettingsSection label / hint / option name + desc
through t(); editor presets and api-key inline buttons too
- new settings.* keys in en + zh-CN
- ThinkingBar: drop onStop prop + button + .thinking-bar-stop CSS
- App.tsx: stop passing onStop={abort} to ThinkingBar
* fix(desktop): yolo + plan-rail bugs; dedupe auto-resolve policy
Two real bugs from the desktop diverging from CLI TUI behavior:
1. YOLO still asked at every plan_checkpoint. Two causes:
a. Desktop UI's editMode union used "default" but config.ts canonical
values are "review" | "auto" | "yolo". loadEditMode() coerces
anything else to "review", so picking "default" silently wrote
review and every checkpoint paused.
b. Even with the right wire value, the desktop's pauseGate.on listener
had no auto-resolve branch — only CLI TUI App.tsx did.
2. ActivePlanRail never cleared. No "plan done" signal existed; rail
lingered after the final mark_step_complete.
Fixes:
- new src/core/pause-policy.ts — one source of truth for editMode→gate
rules; CLI TUI App.tsx and desktop CLI listener both call
shouldAutoResolveCheckpoint / autoResolveVerdict instead of inlining
the same `mode === "auto" || mode === "yolo"` check
- desktop CLI listener auto-resolves plan_checkpoint via the shared
helper, still emitting $step_completed so the rail ticks
- desktop CLI emits $plan_cleared on turn_complete when all steps done
- desktop UI: editMode union retyped to "review" | "auto" | "yolo"
end-to-end (App, Header pill, SettingsPanel, protocol); CSS class
.edit-pill-default renamed to .edit-pill-auto
- ActivePlanRail: optional onDismiss × button for manual clear of plans
that arrive with no structured steps (and thus no turn_complete trigger)
The hardcoded threshold of 3 repair signals escalates too eagerly on long subagent runs where transient tool failures are expected and recoverable on flash. Exposing this via `escalation.failureThreshold` in config and `--escalate-after` on the CLI lets users tune escalation to their workload without forking the loop, while preserving the existing default and behaviour for everyone else.
The top-level /forget command was removed in the slash refactor, but
the resumed-session and new-session banners + the context-overflow
error still told users to type it. Point them at the surviving paths
instead: /new for a fresh start, /sessions ([d] to delete) for
manage / rename / drop.
Closes#697
Filesystem tools now route any absolute-system path that escapes the
project sandbox (`/Users/foo`, `/etc/...`, `C:\Users\...`) through a
new PathConfirm modal: allow once / always allow this directory / deny.
Mirrors the existing run_command flow — a shared PauseGate kind
`path_access`, a per-project `pathAllowed` list persisted in
~/.reasonix/config.json, and a session-scoped run-once cache so
follow-up reads under an approved directory don't re-prompt.
Closes#684
* feat: checkpoint API + git changes panel with zero external deps
* fix(changes): Cross-site scripting vulnerability as the output of this final HTML sanitizer step may contain double quotes when it reaches this attribute definition.
* fix(changes): The file may have changed since it was checked
* fix(comment): shorten block comment to comply with policy
* fix(file-read): TOCTOU race + path traversal guard
Reasonix enables xterm modifyOtherKeys=2 at startup. Under that mode,
terminals re-encode any printable key whose Ctrl variant would produce
a control byte — `@` (^@=NUL), `[` (^[=ESC), `\`, `]`, `^`, `_` — as
`\x1b[27;<mod>;<cp>~`. The parser only had hardcoded entries for the
Tab / Enter modifier sequences, so those printables hit lookupCsi,
returned null, and were dropped silently. Reported under ghostty on
Ubuntu 25.10; the same shape also affects any xterm-compatible host
that honors the mode.
Adds a generic decoder for both the xterm `27;mod;cp~` and Kitty
`cp;mod u` / `cp u` envelopes, mapping back to the keystroke that
would have arrived as a bare byte without the mode.
Closes#683
A 30-line python heredoc pushed the SingleSelect and footer past the
viewport so users couldn't see (or pick) "allow once / always / deny".
Clamp the preview to (totalRows - 18) lines with a "… N more lines
hidden" hint, leaving the action footer on screen at every terminal
height.
Closes#680
* fix(skills,memory): handle BOM, folded lines, and quoted values in frontmatter
The three local copies of the frontmatter parser all skipped files with a
UTF-8 BOM, dropped indented continuation lines, and left wrapping quotes
in description values. Consolidates them into one parser that strips the
BOM, folds indented continuations onto the preceding key, and unwraps
matching single/double quotes after folding.
Closes#678
* fix(frontmatter): guard against prototype-pollution keys
The KEY_RE regex matches `__proto__` / `constructor` / `prototype`, so a
bracket write `data[key] = value` could mutate Object.prototype. Switch
the accumulator to a Map (no prototype to pollute), filter forbidden
keys at both the set and materialization sites, and return a
null-prototype object. Resolves CodeQL js/prototype-pollution-utility.
Native shell that drives a new `reasonix desktop` JSON-RPC subcommand
over stdio. Each tab owns an independent CacheFirstLoop, workspace,
session, and file/symbol index so two projects can stream in parallel
without crossing context.
Extracts buildCodeToolset into src/code/setup.ts so the desktop and
the `code` command share an identical tool surface. While extracting,
wires up web (web_search / web_fetch) and skill (run_skill +
subagent runner) tools — they were exported but never registered.
pauseGate confirm / choice / plan requests route via AsyncLocalStorage
so concurrent turns can't cross approvals. CacheFirstLoop._turn now
advances past loaded assistant messages on resume — the frontend's
turn-keyed message map would otherwise treat a fresh streaming
response as a duplicate of an historical message.
Release workflow builds Tauri bundles for linux-x64, macos-arm64,
macos-x64, windows-x64 on tag push and uploads to GitHub Releases.
Signing keys flow through env (Apple notary, Windows Authenticode,
Tauri updater); see desktop/SIGNING.md.
Raw Node error codes and bare HTTP status lines from SSE/Streamable-HTTP transports leave users guessing at the next step. Mapping DNS/connection/TLS codes and 401/403/404/5xx responses to targeted `try:` hints turns `reasonix mcp inspect` output into something users can act on without reading the source.
Tool calls invoked during MCP handshake were surfacing transport errors because the bridge had no signal that the server was still connecting. A per-server readiness deferred lets dispatches wait (capped at 30s) instead of failing, and a status-bar pill makes the otherwise-invisible background load legible to the user.
#632 actionable-error work stopped at 429 + 403 — generic 5xx still
fell through to the catch-all "rephrase the query / switch engine"
message, which is the wrong advice for a transient server-side
failure. Add serverError5xx + fetchServerError5xx pointing the model
at a browser sanity-check and a 30s retry instead.
Existing webSearch 503 test tightened from `/web_search 503.*try:/`
to assert on the new `retry in 30s` substring; a parallel webFetch
502 test added in the same shape.
Credit to @MyPrototypeWhat — #671 surfaced the gap and the 503 test
case lands with this PR.
#670 landed with console.warn for the buggy-readOnlyCheck surface, but
the rest of the project writes diagnostics via process.stderr.write
(see commit.ts, the mcp-stdio dropped-line trace, etc.). Align the two
catch blocks to match. Test updated to spy on process.stderr.write
instead of console.warn.
No behavior change — both routes land on stderr; this is purely a
consistency fix so future grep-for-diagnostics stays one-shot.
Closes#629.
Two catch blocks treat a throwing readOnlyCheck as 'not read-only' and
move on:
- src/tools.ts isReadOnlyCall — used by plan-mode refusal
- src/loop.ts isMutating — used by the storm-breaker window
If the check itself has a bug, nobody sees it; the tool just silently
behaves as if it were mutating. Log the exception on console.warn at
each catch so the bug surfaces during development without changing
default-on-throw semantics.
* feat(mcp): add REASONIX_DEBUG_MCP env var to surface dropped stdio lines
Closes#630.
The MCP stdio transport silently discards lines that fail to parse as
JSON-RPC, since servers typically emit non-JSON banners during startup.
That hides real wire-level bugs — truncated or corrupted frames produce
empty tool results with no clue why.
Gate a stderr trace behind REASONIX_DEBUG_MCP=1 so the noise only shows
up when a developer opts in.
* test(mcp): wait on child exit instead of fixed 250ms sleep
Fixed-time waits flake under cold Node spawns on slow CI (Windows
runners routinely exceed 250ms). The messages() iterator returns when
the transport closes, and Node guarantees stdout 'data' events fire
before 'close', so by the time the iterator returns every malformed
line has already been routed through the synchronous catch.
Also added a '0' case to actually distinguish 'off' from 'on' (the
prior 'truthy non-1' case only covered 'true', which was redundant
with the empty-string case).
* feat(cards): polish user / reasoning / task to match design tokens
UserCard: drop accent stripe — user is a conversational anchor, not
status. Use neutral CARD.user (muted ◇ + bg-elev pill) and prefix the
body with a fg.sub ↳ anchor.
ReasoningCard: tighten the four-tier render. Streaming → tail-3 with a
⋮ overflow marker (was tail-4, no marker). Settled-short shows the
whole body with anchor; settled-medium splits head + tail with a mid
`⋯ N lines elided` row. XL (≥800 tok) drops the head and surfaces a
`⋯ N ¶ + ~T tok scrolled past · /reasoning last` line — the head at
that scale is almost always restating a prompt the model has moved
past. Empty reasoning (model skipped thinking) renders a grayed
PILL_SECTION.empty pill + italic "no thinking — direct answer" hint
so the absence is explained, not silently missing. Body anchor ↳
shows only when the absolute start is visible.
TaskCard: section pill with status-mapped tones (task / taskDone /
taskFailed) replaces the bare glyph + "step N/M" prefix. Subtitle
becomes "N / M Title". Step rows wrap the target in a PILL_PATH chip.
* feat(composer): blink the prompt cursor at 1Hz via slow tick
cursorVisible was hardcoded true. Drive it from useSlowTick() so the
block cursor toggles each second when the input is idle. During
typing, value/cursor changes already drive re-renders so the blink
doesn't interfere visibly.
* feat(shell-confirm): show cwd + timeout / wait info rows
The modal previewed the command but not where or for how long it would
run, leaving the user to infer cwd from session context and trust the
default 120s timeout silently. Surface both as faint info rows below
the `$ command` line — `cwd ~/projects/reasonix`, `timeout 120s` for
run_command, `wait 3s` for run_background when waitSec is set.
Threading: PausePayloadMap.run_command and run_background gain
optional cwd + timeoutSec / waitSec fields; shell.ts computes
effectiveTimeout before gate.ask so the modal sees the same number the
runtime will enforce; App.tsx pendingShell mirrors the wider payload.
Audit casts still see {command} — the extra fields are ignored at the
audit boundary on purpose.
tests/shell-tools.test.ts: the regression test now uses toMatchObject
to accept the wider payload while still asserting kind + command.
Two related UX failures landed together because users couldn't tell what
was actually controlling the model:
1. Users saw `● auto` in the StatusRow (which is the EDIT-GATE mode) and
assumed it was the preset. Running `/preset pro` left both visible
`auto` indicators (StatusRow + LiveRows ModePill) unchanged, because
neither rendered the preset — usePresetMode's React-state mirror was
never wired to the agent store, and the slash handler didn't call
setPreset / dispatch at all.
2. People reach for `/model <id>` instead of `/preset` to switch models.
`/model` only touched `loop.model`, leaving `autoEscalate` whatever
the active preset had set — so `/model deepseek-v4-flash` from the
default `auto` preset still let flash escalate to pro on hard turns.
And nothing wrote `cfg.preset`, so relaunch silently reverted.
Changes:
- StatusRow: prefix the edit-gate mode label with `edits:` (new i18n key
`statusBar.editsLabel`) and render a new `▴ <preset>` pill after it.
Pill falls back to the short model name when the user is on a model
outside the three presets. Hidden below 60 cols (same pattern as
WALLET_MIN_COLS).
- `StatusBar.preset` + new `session.preset.change` event, reducer entry,
and a mount-only useEffect in App that seeds the initial value from
loop state so the first paint is correct.
- `/preset` slash handler now dispatches the preset change and persists
via new `savePreset()` (mirrors saveReasoningEffort). `/model` does
the same: turns off `autoEscalate` (manual pick = explicit pin),
dispatches inferred preset (pro/flash/null), and persists when known.
- ModelPicker `kind:"select"` and `kind:"preset"` outcomes get the same
treatment, plus the dashboard's `applyPresetLive`.
After: switching to pro via `/preset` or `/model` shows `▴ pro` in the
status bar, sticks across the session (no silent escalate-back), and
survives relaunch.
When an Esc abort tears down multiple subagent cards at once, each card's re-measurement called setMaxScroll synchronously, snapping scrollRows N times and bouncing the viewport past one screen. Holding a trailing-edge target on a microtask flush collapses the burst into one settled transition while keeping grows immediate so streaming output stays pinned without latency.
A user pasted `D:\VS_project\...\GraspAnalysisCommand.cpp` inside the
workspace; the model hallucinated "I cannot access the filesystem"
and ran `web_search` for a private local cpp file instead of just
calling `read_file`. The Path-conventions block only documented
POSIX-absolute as accepted, leaving Windows drive-letter paths to
the model's imagination — which here defaulted to "refuse".
`safePath` already accepts any shape that resolves inside the sandbox
(src/tools/filesystem.ts), so this is purely a prompt clarification
plus an explicit ban on the refusal patterns we observed in the wild:
shape-based refusals, "no filesystem access" claims, and `web_search`
fallbacks for local paths.
Hotfix for 0.39.0 install failure: the `postinstall: patch-package`
hook + missing `patch-package` runtime dep + missing `patches/` in the
files array meant fresh `npm install` / `npx reasonix@latest` runs
crashed before the binary was usable. 0.39.0 has been deprecated on
npm and `latest` rolled back to 0.38.0.
Removes the patch-package machinery entirely — it can't work for a
published library since npm hoists `ink` out of reasonix's own
`node_modules`. The ink alt-screen render fix (#639) will return via
a forked ink + `npm:` alias (#663) in a later release.
Piggybacks three PRs that landed since 0.39.0:
- #632 fix(web): actionable web_search / web_fetch errors
- #661 feat(composer): Ctrl+X opens \$EDITOR
- #662 feat(composer): Ctrl+P / Ctrl+N picker navigation
When any of the three input-prefix pickers is active — slash command
(`/`), @-mention file picker, or slash-argument enum picker — Ctrl+P
and Ctrl+N now move the highlighted row up/down, matching what ↑/↓
already do. Falls through to prompt-history recall when no picker is
open, so single-key bash parity is preserved.
Previously Ctrl+P/N always handed off to history recall regardless of
picker state — reported as keymap inconsistency in issue #647 (the
external-editor change is its own PR; this is the keymap half).
Implementation: `App.tsx` wraps `recallPrev` / `recallNext` from
`useInputRecall` in two memoized callbacks that consult atState /
slashArgMatches / slashMatches first (priority matching the existing
↑/↓ handler's order), and routes them into `PromptInput` instead of
the raw recall functions.
Closes#647
Composes a long prompt in the user's preferred editor instead of
typing it inside the TUI. Match for opencode's `<C-x>e` and codex's
`<C-g>` (issue #647).
Editor resolution follows the standard Unix precedence: $GIT_EDITOR →
$VISUAL → $EDITOR. Picked an explicit GIT_EDITOR-style fallback over
hardcoding nano/notepad so the user's existing shell config carries
through. Missing-editor and non-zero-exit cases surface as a warning
card in the chat log; on success the buffer is replaced with whatever
the user saved (one trailing newline stripped, since most editors
auto-append one).
Implementation notes:
- New action flag in multiline-keys (`openExternalEditor: true`) so the
pure reducer stays testable and PromptInput just signals up.
- App.tsx flips raw-mode off around the spawn so the editor can use
cooked line-buffered input; bracketed-paste / alt-screen are managed
by the editor itself via DEC mode 1049.
- Spawn uses `shell: true` so $EDITOR strings like `nvim --noplugin`
or `code --wait` split correctly across platforms (same shape as the
existing `commit.ts` editor invocation).
Refs #647 (the picker-keymap half of that issue is a separate change).
* fix(web): make web_search and web_fetch errors actionable
Bare HTTP status codes and terse refusal messages gave the model no signal about what to do next, leading it to either retry blindly or abandon the tool. Each error now carries a short " — try: …" tail tailored to the failure mode (429 backoff, 403 client-block, timeout, oversize body, unreachable SearXNG, invalid URL) so the model can self-correct without a human in the loop.
* style(tests): reformat web-tools assertions for biome
Biome's formatter flagged the existing single-line `expect(...).rejects.toThrow(...)` calls as needing the multi-line layout. Reformat to satisfy the formatter so `npm run lint` is clean.
The reporter showed a JSON snippet rendered as
`{ "apiKey": "..." }` inside a code fence — the
model emitted literal HTML entities instead of `"`. marked passes the
entities through verbatim (its tokens carry the raw text, not HTML-
escaped output), and our renderer rightly hands that to the terminal
unchanged. Terminals don't render entities, so they leak as visible
`"` / `&` / `<` etc.
This is a known LLM artifact: models sometimes HTML-escape inside code
blocks, especially on JSON / HTML / XML output, because their training
saw a lot of HTML-encoded code in web posts and docs. Both Claude Code
and Cursor decode entities at the rendering boundary; doing the same
here.
Scope: only code blocks and inline code spans (the contexts where
models leak entities the most). Prose paragraphs are left alone — if
someone genuinely writes "use the `&` entity to escape ampersand"
in non-code text, the entity name stays visible. Numeric forms
(`"` / `"`) and the five common named forms (quot / apos /
amp / lt / gt / nbsp) decode; unknown names pass through so we don't
corrupt prose that quotes entity names.
Closes#657
UserCard ran every user message through `<Markdown>`, so pasting code
or stack traces into the composer caused the displayed card to silently
reinterpret markdown punctuation: `*foo*` rendered italic, `# title`
collapsed into an H1 (the `#` vanished), `[label](url)` rewrote to an
underlined link with the URL hidden, four-space-indented lines
restyled as a code block, etc. The model still received the full
verbatim text — but the user's visible round-trip (`what I sent` →
`what I see in history`) was wrong.
Render as a plain `<Text>` instead. Assistant turns keep Markdown
(that's the only place formatted output belongs).
Closes#655
In a real review session, the model called `read_file({})` (missing
required `path`), got the standard "missing required parameter ..."
error back, and the very next turn issued the *exact same* call — same
empty args, same tool. Same error came back. After the second rejection
it gave up tool-calling entirely and went to summary. The existing
StormBreaker uses a 6-call window with threshold=3 across all tools, so
the two-in-a-row malformed-args shape never tripped it.
ToolRegistry now tracks the per-tool fingerprint of the last call that
failed schema validation (JSON parse error or missing required param).
On the second consecutive identical malformed call to the same tool the
result switches to a sharper "same call just failed validation — DO NOT
retry with identical args" plus `consecutiveMalformed: true` so callers
can spot it programmatically. Any successful validation for that tool
clears its streak; per-tool tracking keeps interleaved unrelated tools
from interfering.
Closes#651
Node's built-in fetch is undici under the hood, but undici ignores the
standard proxy env vars unless you explicitly install a ProxyAgent on
its global dispatcher. Users behind a corporate or local proxy were
getting opaque connection failures from every network surface — DeepSeek
API, web search, model list refresh, version check — even with
HTTPS_PROXY set in their shell, because none of those calls ever saw the
env var.
src/net/proxy.ts reads HTTPS_PROXY → HTTP_PROXY → ALL_PROXY (upper-case
preferred, lower-case fallback — matches curl precedence) and installs
an undici ProxyAgent as the global dispatcher. Wired at the top of
src/cli/index.ts so every fetch closure constructed later (DeepSeek
client, web tools, doctor's reach check) inherits the dispatcher.
/doctor now reports the active proxy as a check row — username/password
in the URL are redacted before printing so the output is safe to paste
into bug reports.
Closes#646
EditMode is "review" | "auto" | "yolo", but loadEditMode's ternary only
recognized "auto" and dropped everything else — including yolo — to
"review". /mode yolo writes the right value to disk via saveEditMode,
but the next read silently downgrades it.
Downstream: src/cli/commands/code.tsx:111 registers the shell tool with
`allowAll: () => loadEditMode() === "yolo"`. Because that getter never
returns "yolo", the shell tool always falls through to the pauseGate,
and the user sees the approval modal even though they're "in yolo".
Same demotion bites the App's initial editMode state in
src/cli/ui/hooks/useEditGate.ts:38 on every relaunch.
Closes#644
Plan progress (the `N/M done` counter on the live card and the resume
banner) is only ever advanced by the model calling `mark_step_complete`
after each step. When the model skips that call — and DeepSeek doesn't
always make it — the counter stays at `0/N` even though the work is
finished, and on resume the user sees `0/9 done` next to a plan they
know they completed an hour ago. There was no escape valve.
Two changes:
1. New slash subcommand `/plans done <id>` (single step) and
`/plans done all` (every remaining step). Updates completedStepIds,
persists .plan.json, dispatches plan.step.complete so live UI ticks.
Wired through new SlashContext callbacks that App.tsx owns, so the
in-memory ref stays in sync with disk and the next mark_step_complete
call (if it ever comes) won't re-add a duplicate.
2. Strengthened MARK_STEP_COMPLETE_DESCRIPTION — explicit MANDATORY
marker, explanation of the visible failure mode (0/N on resume),
and explicit "late is still better than never" so the model can
recover at end-of-turn if it noticed it skipped earlier steps.
Closes#641
If the user has scrolled up in the chat history and a pauseGate request
arrives — shell command, plan proposal, plan checkpoint, plan revision,
or ask_choice — the modal mounts at the bottom of the chat area, which
is off-screen below the scroll position. The picker captures arrow
keys, so the user can't scroll back down to see the options either,
and looks stuck.
Calling chatScroll.jumpToBottom() once at the top of the pauseGate
listener flips pinned back on; the modal's useReserveRows triggers
setMaxScroll, which snaps scrollRows to the new bottom under the
existing pinned-mode invariant.
Closes#642
[email protected]'s log-update tracks previousLineCount as logical newlines, not
visual rows. When any rendered line wraps because its visual width
exceeds terminal columns — which happens on CJK / ambiguous-width
content under East Asian terminals — the clear region on the next frame
undershoots the actual on-screen footprint and the bottom of the
previous frame survives. The reported symptom on Windows Terminal at
120×30 with zh-CN content is a duplicated status bar (two horizontal
separators stacked) and stale residue creeping up from below.
shouldClearTerminalForFrame already handles the overflow case, but it
gates on Yoga's outputHeight — which can itself undercount visual rows
for the same width-misjudgment reason, so the fallback misses exactly
the cases that trigger the bug.
Fix: in alt-screen mode, take the clearTerminal path unconditionally.
Alt-screen has no scrollback, so per-frame clear costs nothing visible;
incrementalRendering is already off (chat.tsx:571) so we're paying the
full-frame stdout cost regardless. Patched via patch-package so the fix
survives reinstalls until the same shape lands upstream.
Closes#639
github/[email protected] compiles patterns with `new RegExp(str)`,
which doesn't accept the PCRE `(?i)` inline flag — it throws
`Invalid regular expression: Invalid group` on the first pattern
and the whole label job dies before tagging anything (run 25649833795).
Switch every entry to the `/pattern/i` literal form the action
parses out of slash-delimited strings. Behavior is unchanged
(still case-insensitive); the YAML just speaks JS regex now.
Validated locally: all 14 patterns compile, 17/17 realistic
issue fixtures match the expected labels.
The agents.md open spec (Linux Foundation, 60k+ projects, broad
ecosystem support — Codex, Cursor, Aider, Gemini CLI, JetBrains
Junie, etc.) is the convergence point for "single agent-instruction
file at project root." Forcing a separate REASONIX.md next to an
existing AGENTS.md fragments memory and adds to the file-proliferation
problem the spec was designed to fix.
readProjectMemory now walks REASONIX.md → AGENTS.md → AGENT.md and
takes the first that exists. Writes (# quick-add, dashboard editor)
target whichever file is already on disk, defaulting to REASONIX.md
for fresh projects. AGENT.md drops out of FOREIGN_PLATFORM_FILE_MARKERS
since we now read it instead of flagging it as a foreign workspace.
Closes#635
Two GitHub Actions that fire on `issues: [opened, edited]`:
- `issue-similarity.yml`: actions-cool/issues-similarity-analysis posts
a comment with the top related issues (threshold 0.7) so a reporter
notices duplicates like #633 → #624/#625 without us hand-replying
every time.
- `issue-labeler.yml`: github/issue-labeler applies area / kind labels
by regex on title + body. Config in `.github/issue-labeler.yml` covers
bug / enhancement / documentation / question / dashboard / rendering.
Both use the default GITHUB_TOKEN — no secrets to provision. Judgment
labels (good first issue / rfc / tracking / duplicate / wontfix) stay
maintainer-driven.
The catalog already declares `requiredEnv` (github → GITHUB_PERSONAL_ACCESS_TOKEN
and friends), and `StdioTransport` already accepts an env overlay — but the
bridge call sites never threaded one through. Users had to export the var in
their shell and relaunch.
Adds `mcpEnv: Record<serverName, Record<envName, string>>` to ReasonixConfig,
keyed off the `name=` prefix in the --mcp spec. Stdio specs merge the entry
over process.env at spawn; SSE / streamable-HTTP ignore it (no child process).
Empty-string values are dropped so a blank in config doesn't blank out a
real env var.
Also collapses the four duplicate `spec → transport` ternaries (chat, run,
mcp-inspect, reconnect) into one `buildTransportFromSpec` helper so future
transport additions land in a single place, and pipes the same env lookup
into `/mcp reconnect` so a respawn after a token rotation picks up the new
value.
`reasonix mcp install` now also prints the `mcpEnv.<name>` shape next to its
"needs:" line, pointing users at config.json directly instead of leaving
them to discover the key.
Closes#376
Stable SSH tunnels need a deterministic port. Adds `--dashboard-port`
on `chat` and `code`, plus a `dashboard.port` config key, so the
embedded server binds to the same port across restarts. Resolution
order: flag > config > ephemeral (current behavior). Out-of-range
values warn + fall back; pinned-port EADDRINUSE surfaces through the
existing auto-start failure toast so the user knows the port is
contended instead of silently rolling onto a different one.
Closes#624
* feat(doctor): add --json flag for structured machine-readable output
Enables programmatic consumption of doctor results by CI pipelines and tooling that need to parse health-check status without scraping human-formatted output. Each check now carries a stable `id` so downstream consumers can key off specific checks rather than brittle label strings, while exit-code semantics and the default text output remain unchanged.
* test(doctor): use vi.stubEnv for env isolation in --json tests
Vitest's `vi.stubEnv` and `vi.unstubAllEnvs` provide automatic restoration of environment variables between tests, eliminating the manual save/restore boilerplate that's easy to get wrong. Collapsing the multi-line import also keeps the test file consistent with single-line import style elsewhere.
* feat(ui): add /copy — vim-style copy mode for SSH-friendly chat copy
Drag-select can't extend past the alt-screen viewport in SSH / mosh / tmux,
because the alt-screen has nothing scrollable above it. /copy gives users a
keyboard-driven path to yank chat text without depending on terminal selection.
j/k or arrows move the cursor by line, v starts/cancels a selection, y or
Enter writes the selection through OSC 52 (with the existing temp-file
fallback for >75 KB or terminals that don't honour OSC 52). g/G jump to
top/bottom; q/Esc exits without yanking.
Snapshot is taken at mount (frozen view), spans user / streaming / reasoning
cards; tool / diff / etc. are skipped. Headers are navigable but excluded
from yank, so cross-card selections come out clean.
Closes#614
* docs: add CLI reference — every subcommand, slash, keybinding
Until now /help and /keys were the only way to discover the full surface.
Both READMEs now link to docs/CLI-REFERENCE.md, which mirrors the in-app
content so it's greppable from the repo and indexable on the website.
Includes a copy/paste section with the SSH-alt-screen explanation and
both escape hatches (/copy and --no-alt-screen).
* docs(site): link CLI reference from index footer + configuration CTA
Adds a "CLI reference" entry in the index.html footer's Docs column and
in the configuration page's outro CTA cluster, pointing to the new
docs/CLI-REFERENCE.md. Mirrored in i18n.js + guide-i18n.js for both EN
and zh dictionaries.
* feat(tools): add delete_file / delete_directory / copy_file
The model could only delete or copy files via run_command (rm/cp), but
neither rm nor cp is on BUILTIN_ALLOWLIST — every call hit the user
confirmation gate. Three new sandbox-scoped tools eliminate that
friction:
- delete_file(path) — fs.unlink, refuses directories
- delete_directory(path) — fs.rm recursive by default; recursive:false
falls back to fs.rmdir for empty-only
(Node's fs.rm without recursive rejects
every directory, so the empty-dir path
needs the rmdir variant)
- copy_file(source, dest) — fs.cp recursive, refuses overwrite
All three resolve through the existing safePath() check so paths
outside the sandbox are rejected the same way write_file / edit_file
already are. No description bloat — short single-line teaching plus
the parameter shapes are enough.
12 new tests cover happy paths, refusal conditions (directory /
file mismatch, non-empty refusal, overwrite refusal), parent-dir
auto-creation, sandbox escape rejection, and the read-only-mode skip
(allowWriting:false leaves all three out).
Also extend the plan-mode write-tool list in src/code/prompt.ts so
the model knows these will be bounced under /plan.
* perf(tools): compress run_command / run_background descriptions
Tool descriptions ship in every API request as part of the prefix.
run_command's description was the largest single contributor — six
bulleted constraint paragraphs spanning ~200 tokens, much of it
re-explaining the same shell semantics. run_background then claimed
"Same shell constraints as run_command" but proceeded to re-list a
subset of them anyway.
Compress without losing substance:
- run_command: lead with the one-line summary, then condense the six
constraint bullets into one paragraph that lists supported /
unsupported / cd-doesn't-persist with the same concrete examples
but no prose padding. Drops ~120 tokens per request without losing
any information the model needs.
- run_background: drop the duplicate constraint listing (still
inherits from run_command), keep the Vite gotcha (high-value pitfall
the model gets wrong) and the "use this for npm dev / uvicorn /
tsc --watch" guidance. Drops ~60 tokens.
Net per-request prefix saving: ~180 tokens. Across a typical 50-turn
session that's ~9000 tokens off the parent prompt.
The subagent loop has used a setResultAugmenter-driven budget tail since
0.36 — when within BUDGET_WARN_THRESHOLD of the per-spawn cap, every
tool result picks up `[budget: K of N tool calls left — wrap up soon]`,
and at 0 left a stronger finalize-NOW form. The parent CacheFirstLoop
exposed the same setResultAugmenter hook on the registry but never
wired a consumer, so the model running in the main session had zero
runtime visibility into its iter budget. The user-facing 70% warning
fires to the TUI, not to the model — when it hits iter 60 of 64 it
still has no signal it's about to be force-summarized.
Wire an analogous augmenter on the parent loop (threshold 5, slightly
wider than subagent's 3 since the parent's default 64-cap is 4× larger)
and reset the per-step counter at step entry so consecutive turns don't
accumulate. Constructor checks ToolRegistry.hasResultAugmenter first so
subagent's pre-installed child-registry augmenter survives — the
constructor must not clobber it.
Also flag wait_for_job as parallelSafe + stormExempt: concurrent waits
on different jobs are safe, and polling-loop is the intended pattern so
the storm breaker shouldn't trip on it.
* feat(prompt): add audit-mode rails for review/critique tasks
When the user asks Reasonix Code to audit its own architecture, the
existing "cite or shut up" rule covers absence claims but doesn't
catch the more common audit-mode failure: confident, well-structured
proposals built on factually wrong premises about runtime behavior,
fabricated quantities, or recommendations that contradict pinned
memory.
Adds a six-bullet section after "Cite or shut up": auto-preview is
for locating not auditing, flag→consumer trace before claiming
runtime behavior, no fabricated percentages, schema-cost accounting
for new-tool proposals, MEMORY.md as design constraint, and
user-facing ≠ model-facing as a category-error guardrail.
Closes#610.
* prompt: tighten rails #2 and #6 from real audit-session failure modes
Audit session run against the original 6-rail section (#610) showed
two failures the wording didn't catch:
1. **Inventory-claim hallucination.** Asked which tools have
`stormExempt: true`, the model enumerated 6 file-system tools as
having it — only 2 actually do. The rail said "trace flag to
consumer", which the model interpreted as "for one named tool",
not "for an inventory claim covering many tools." Add an explicit
inventory clause: grep the flag, don't enumerate from memory.
2. **Library API → dead-code mischaracterization.** The model
labeled `registerSubagentTool` "dead code from CLI perspective"
on the basis of a clean grep in `src/cli/`. It's a deliberate
library export consumed by embedders via `src/index.ts`. The
rail enumerated three surfaces (slash / tools / UI); add a fourth
(library) so library exports aren't mistaken for unused code.
Two-test bump on tests/code-prompt.test.ts so the tightened wording
can't silently regress.
* prompt: broaden rail #1 to cover doc / state claims, not just runtime
Second audit session run against the tightened rails (#611) showed
the same head-only-then-conclude failure mode again, this time on a
plan-doc file rather than runtime code: the model read the head of
docs/plans/architecture-refactoring-roadmap.md, saw "8 services
still use singletons", and asserted the plan was now stale —
without reading the rest of the doc to check for a "Status: done"
section that might have been there.
The original rail was scoped to "runtime behavior" because that was
the loop.ts dispatcher case from #610. The same blind spot applies
to any file: don't conclude what's in the elided middle off head +
tail. Broaden the wording to cover runtime behavior, current
architectural state, and doc freshness explicitly.
One test bump on tests/code-prompt.test.ts so the broader scope
can't silently regress to runtime-only.
The split-string approach (codeRooted + session + nativeTools as separate
t() calls) dropped the comma+space between rootDir and session in both
EN and zh-CN, and locked the word order across languages. Fold the four
fixed segments into a single codeRooted template with {rootDir} /
{session} / {tools} / {semantic} placeholders so each locale owns its
full sentence and translators can reorder freely.
Add tests/startup-banner-i18n.test.ts to lock both rendered banners.
* feat(i18n): localize confirmation modals, HintRow, and remaining cards with zh-CN
* feat(i18n): localize pickers (SessionPicker, ModelPicker, SlashSuggestions, AtMentionSuggestions) with zh-CN
* feat(i18n): localize StatsPanel, WelcomeBanner, ctx-breakdown with zh-CN
* fix: adjust zh-CN translations based on user feedback
* feat(i18n): localize web search errors, startup message, and doctor diagnostics with zh-CN
* fix: remove duplicate namespaces from rebase and reformat
The subagent sink mirrors every child LoopEvent (assistant_delta /
reasoning_delta / tool_call_delta) into useSubagent's inner branch.
The map callback always allocated a new array reference, so React
re-rendered App.tsx + SubagentLiveStack on every child delta — with
3 parallel subagents streaming, that was 90+ no-op re-renders/sec
each forcing a Yoga layout pass. Closes#554.
Pull the inner/progress/phase logic into a pure reducer that returns
prev by reference when no row would change, and also memoize
ToolCard's spawn_subagent JSON.parse so the inflight-context tick
doesn't re-parse 8 KB on every passing tool start/finish.
The always-visible composer hint row hardcoded English labels and omitted the `^U` clear chord, leaving it undiscoverable without reading source. It also referenced a non-existent `composer.hint` key that would leak the literal path to users when no abort hint was active. Routing the row through `HintRow` with proper i18n keys keeps the chord vocabulary discoverable in both locales and removes the broken key fallback.
Layer 1: rewrite the "Delegating to subagents" section in code/prompt.ts
and the spawn_subagent tool description from "when to delegate" to
"default: don't delegate". Lead with the two narrow exceptions where a
spawn pays for itself (parallel fan-out, >10-read context blow-up) and
name the anti-patterns explicitly (single grep, 1-3 file cross-ref,
"keep my context clean for one question").
Layer 2: track per-session spawn count + cumulative subagent tokens in
the registerSubagentTool closure. After each spawn, append a hint to
the JSON tool result. Soft note from spawn 2 onward, strong "justify
the next spawn" hint past 5 spawns or 50k tokens. The hint surfaces
on the model side via the same shape as the existing per-child iter
budget hint (subagent.ts:189), so the model already knows how to read
it.
Layer 3 (single-call refusal gate) deferred until we see whether 1+2
moves the storm pattern in #415 / #553.
Closes#553.
Rolling #594 into 0.37.0 since the version was bumped but not yet
tagged or published to npm. Tag will land on this commit so the
published 0.37.0 contains the fix, no 0.37.1 needed.
The empty-state guard checked !hasConversation && !busy && !isStreaming
but missed the slash-suggestions overlay. Pressing `/` from the home
screen left the bordered welcome card mounted in the flex column while
SlashSuggestions rendered below, producing interleaved frame output
where the card border drew through the menu rows.
ESCALATION_CONTRACT was a const with `deepseek-v4-flash` baked in,
interpolated into three system prompts at module load. A pro session
got told it was running on flash, so when the user asked "which model
are you?", pro answered "flash" — accurately reading what the prompt
told it.
- Convert ESCALATION_CONTRACT → escalationContract(modelId): pro tier
gets a short "you are the escalation tier" note (no <<<NEEDS_PRO>>>
ladder, since pro can't escalate to itself); other tiers get the
contract with the actual model id interpolated, plus an explicit
"if asked which model you are, answer `<id>`" line.
- DEFAULT_SYSTEM (cli/index.ts) → defaultSystemPrompt(modelId), called
per chat / run / bare-reasonix invocation against the resolved model.
- CODE_SYSTEM_PROMPT split: the public-API const stays at the
historical flash phrasing for backward compat; codeSystemPrompt now
takes opts.modelId and the code command threads in opts.model.
- DEFAULT_SUBAGENT_SYSTEM split into a memory-stable base + per-spawn
contract appended against the spawn's resolved model id.
Closes#582
A skill whose frontmatter omits `description:` was silently dropped
from the prefix index, but `/skill <name>` still ran it from disk —
so it worked in the install session and vanished in the next one,
with no diagnostic.
- POST /api/skills/<scope>/<name> now validates frontmatter via
validateSkillFrontmatter() and returns 400 instead of writing a
skill the model will never see.
- applySkillsIndex no longer filters out blank-description skills;
it injects them with a placeholder line that names them and tells
the model to flag the missing frontmatter to the user.
Closes#583
clearLog() truncated the live session jsonl in place, so users running
/new lost every previous turn — the dashboard's Sessions tab faithfully
reported one row because there was one file. Rotate the live jsonl plus
sidecars to <name>__archive_<ts> so the prior conversation survives in
Sessions. sessionName is unchanged, so the prefix cache stays warm.
The __archive_ infix sits outside the ${name}- resume-prefix matcher,
so archives don't get auto-resumed on next launch.
Closes#587
chatCommand used to `await runtime.addSpec(raw)` once per server
before render() — every handshake (100ms-2s) blocked the alt-screen
from coming up, so users with MCP configured saw a black screen
on startup.
Now mcpRuntime exposes a setLifecycleSink(sink) hook. chatCommand
hands the empty mcpServers array off to App immediately; App.tsx
swaps in a log-routing sink on mount and fires runtime.addSpec
(spec, loop) for each requested spec in the background. As each
server bridges, hot-add pushes its tools into loop.prefix and
setLiveMcpServers refreshes the /mcp panel live. Lifecycle events
(handshake / connected / failed / slow) flow into the in-app log
instead of stderr — stderr writes during alt-screen would corrupt
the UI.
UI now paints immediately even with N MCP servers configured.
Servers that fail to connect just stay unavailable; their tools
never bridge — same end state as before, just without the wait.
Adds src/cli/ui/BootSplash.tsx — a full-screen splash that AppInner
returns from before its first real paint, gated by a 1.4s timer
(one whale-spout cycle). Two purposes:
- Hides the brief alt-screen-blank gap on cold launch (heavy
AppInner first-paint cost stays under the splash).
- Brand mark always lands clean instead of flashing raw mount
state.
Splash content:
- ANSI Shadow REASONIX wordmark (6-row block letters, brand color)
- Three-tone shaded whale silhouette (░ outline / ▒ midtone /
▓ inner) with eye, mouth, tail flukes
- 7-frame spout animation cycling at 200ms (idle → rising →
peak with droplets → dispersing)
- Wave line below shifting one column per frame
- 'loading...' indicator with cycling dots
App.tsx wires bootReady state + setTimeout, returns <BootSplash />
until ready.
useLanguageReload() returns a counter that increments on
runtime language changes — same shape as before, just owns its
own useState + onLanguageChange subscription. Lets App.tsx drop
the onLanguageChange import.
Step 7/7 of #565 phase 1. App.tsx LOC unchanged (one import line
in, two hook lines out).
usePresetMode(model) bundles the three model-mode states:
- preset: "auto" | "flash" | "pro" (initial seeded from model)
- proArmed: /pro pending for next turn
- turnOnPro: current turn is on v4-pro (arming consumed or
⇧ pro auto-escalation fired)
App.tsx loses three useState calls plus the inline narratives.
The states and their setters are destructured back so handleSubmit
+ startDashboard's handlers stay structurally identical.
Step 6/7 of #565 phase 1. App.tsx 3701 -> 3695.
useHookList(initialProjectRoot) returns hookList + a reloadHooks
helper that bundles loadHooks() + state replacement. The two
slash callbacks (`/hooks reload`, `/cwd`) and the dashboard
mutation surface now call reloadHooks(projectRoot) instead of
duplicating the loadHooks + setHookList pattern.
App.tsx drops the loadHooks + ResolvedHook imports along with
the inline initial-load comment and the three duplicate
load-and-set blocks.
Step 5/7 of #565 phase 1. App.tsx 3715 -> 3701.
useWorkspaceRoot(launchRoot) returns currentRootDir +
setCurrentRootDir + currentRootDirRef and runs the ref-mirror
effect. App.tsx loses one useState, one useRef, one useEffect,
and the long inline narrative explaining what each
rootDir-dependent surface reads.
The /cwd slash handler still composes the swap (re-register
tools + reload hooks + re-bootstrap semantic) — only the state
+ ref ownership moves into the hook.
Step 4/7 of #565 phase 1. App.tsx 3723 -> 3715.
Bundles pendingEdits ref + pendingCount mirror + pendingTick +
syncPendingCount + editMode + editModeRef + saveEditMode
persistence + the 1.2s mode-flash effect into one hook in
src/cli/ui/hooks/. App.tsx loses three useState calls, two refs,
two effects, and several long inline narratives — those are now
single-line field docs on the EditGate interface.
Note: the tool interceptor stays in App.tsx for now — it's tangled
with review-modal state (pendingEditReview / editReviewResolveRef /
turnEditPolicyRef), which want their own hook in a follow-up.
Step 3/7 of #565 phase 1. App.tsx 3760 -> 3723.
Bundles ongoingTool / toolProgress / statusLine state + the
progressSink wiring + the turn-end clear() into one hook in
src/cli/ui/hooks/. Long inline narratives explaining the
pulse-spinner row / progress frame / silent-phase status line
move out of App.tsx; the hook's name carries the role.
Step 2/7 of #565 phase 1. App.tsx 3785 -> 3760.
DECSET 2004 / modifyOtherKeys / DECSET 1007 setup+cleanup moves
to its own hook in src/cli/ui/hooks/. App.tsx no longer owns the
escape-sequence dance; the long inline narrative collapses to one
line documenting the only non-obvious choice (1007 over full
mouse tracking).
Step 1/7 of #565 phase 1. App.tsx 3816 -> 3785.
After A+B (#573) the App-level render cost on scroll was gone, but
Yoga still had to lay out every card in CardStream's inner Box on
every frame — for a 50-card history, that's hundreds of rows
re-measured per scroll tick.
This PR adds card-level virtualization. Each card is wrapped in a
MeasuredCard that captures its row height via useBoxMetrics and
reports it to the chat-scroll store. CardStream then walks the cards
once per render, computes the cumulative offset of each, and decides:
- live render the card (it's inside the viewport ± 30-row buffer, OR
its height isn't cached yet so we need to measure it), or
- collapse it into a spacer Box of the cached height.
Adjacent collapsed cards merge into a single spacer, so the off-screen
ranges add up to one Yoga node above and one below the visible cards.
Total inner-Box height stays exact, so marginTop={-scrollRows} still
lands on the right rows and maxScroll is correct.
Edge cases:
- New cards (id not in heights map) always render live so the first
measurement happens. Once cached, they collapse next frame.
- Streaming cards re-measure on every render — their height changes
and the cache stays fresh through the same path.
- pruneCardHeights drops heights for cards that disappear from the
list (resumed sessions, /clear), so the map can't grow unbounded.
For a session with 50 cards and ~600 row total height, only the ~5-10
cards under the viewport go through Yoga per scroll. The off-screen
work that was making long sessions feel sluggish is now gone.
Wheel/arrow ticks were re-rendering all of AppInner — 3,800 lines and
122 hook calls — even though the actual UI delta was a single
marginTop change in CardStream. Each scroll paid the full hook-eval
tax before Yoga layout and Ink commit could even start.
The fix has two parts:
1. New chat-scroll store under src/cli/ui/state/. Same useSyncExternalStore
pattern as the agent store — selectors subscribe per-slice, actions
are stable refs. CardStream now reads scrollRows directly from it;
App.tsx only takes the action callbacks (which never change identity).
The "reading history" branch that depended on `pinned` moves into
InputAreaWithHistoryHint, a leaf that subscribes to pinned in
isolation. Net: scroll ticks no longer re-render App.tsx at all.
2. Visual polish.
- Wheel/PgUp/PgDn step from 8 to 5 rows. Smaller jumps read as
smoother continuous motion in a cell-based TUI.
- The "↑ earlier" line is now a live position indicator
("↑ N / M rows above — K more · PgUp / wheel / ↑").
- The indicator briefly switches to the accent color on every
applied delta (scrollVersion bump), so the user gets visual
confirmation the wheel registered before the new frame paints.
Removes the old src/cli/ui/hooks/useChatScroll.ts; nothing else used it.
Hotfix: the squash merge of #571 landed with a 5-line block comment
that violates tests/comment-policy.test.ts (cap is 3 lines). The
fixup commit was pushed to the branch after the auto-merge had
already fired, so it never made it onto main.
Wheel-up felt laggy because every tick paid a full 16 ms wait before
any visual feedback — schedule() was trailing-edge: first call started
a setTimeout, the actual setScrollRows didn't run until the timer
fired. With Ink's reconcile + Yoga layout on top of that, a single
wheel tick took 30-50 ms to land visibly.
Two changes:
1. Leading-edge schedule. First call applies the delta immediately
(instant feedback on first wheel tick), opens a 16 ms window during
which subsequent calls accumulate into pendingDelta, and lands one
trailing flush. Fast scrolls still produce only one re-render per
window, but the user no longer waits for a slow tick to feel.
2. Split arrow step from page/wheel step. SCROLL_ARROW_ROWS stays at
3 (fine-grained ↑/↓). New SCROLL_PAGE_ROWS = 8 covers PgUp/PgDn
and the wheel-via-DECSET-1007 path. Each wheel tick now travels
roughly a third of a typical viewport instead of three lines.
Vertical-jitter reports were tracing back to the 16ms (60Hz) flush
default — on winpty/MINTTY/ConEmu/tmux/high-latency-SSH the cursor-up
repaint can't atomically swap the frame at that rate, so users see
the old frame's bottom rows briefly through every redraw. 50ms (20Hz)
is still continuous-feeling for streaming text and stops the bobbing
on every terminal we've seen affected. Override via REASONIX_FLUSH_MS
when running on a terminal with atomic frame swap.
REASONIX_UI=plain is removed: it was the nuclear escape hatch for the
same problem, but it suppresses every live row (streaming text, tool
spinner, plan progress, undo banner, subagent stack, status line) —
i.e., most of what makes the TUI useful. The slower default flush
addresses the same terminals without that tradeoff.
Adds a dedicated configuration guide page (docs/configuration.html)
covering MCP, skills, memory, hooks, permissions, web search, and
the semantic index — bilingual (en/zh) with scrollspy TOC.
Landing page: hero gets a real-metric strip (counts up once when
scrolled into view), orbital SVG decoration, status pill. The
"Configure in five minutes" teaser block links into the guide.
README cleanup: pulls Configuration into prime real estate, collapses
the chat-vs-code / working-folder / first-skill detail into a
<details> block, drops the standalone Web Search section (now
covered by the guide), tightens install copy. Mirrored in zh-CN.
SEO: correct og:url (was pointing at the wrong repo path), canonical,
hreflang en/zh-CN/x-default, JSON-LD SoftwareApplication + WebSite
on landing, TechArticle + BreadcrumbList on guide, Twitter card
metadata. Adds docs/robots.txt and docs/sitemap.xml.
Perf: stripped scroll-reveal, card spotlight + 3D tilt, capability
marquee, backdrop-filter on metrics row, fractal-noise overlay,
content-visibility, gradient-text shimmer, and section-beam
animations after they made the page feel laggy. Background is now
fully static — dot grid, three glow blobs, horizon hairline.
Only one-shot animation left is the metric count-up; the brand
mark, status dot, and terminal caret keep their tiny scoped pulses.
Surfaces a SingleSelect modal for the terminal theme preference. Bare
\`/theme\` opens the picker; \`/theme <name>\` keeps its existing
"persist and report" behaviour. Moves the slash entry from the
advanced group to setup and adds high-contrast to the arg completer.
Adapted from J3y0r's PR — repointed onto current main (which had
since reformatted App.tsx around the InflightProvider wrap from
#566) and the count test in tests/ui-slash-suggestions.test.tsx
updated from 12 → 11 advanced commands now that /theme has moved
out of the advanced bucket.
Thanks @J3y0r for the contribution.
Closes#557
Tool spinners occasionally kept spinning after the underlying work had
finished. The cause: status was set imperatively from paired tool_start
/ tool events, and every code path that exits a dispatch had to
remember to emit the closing event — normal return, throw, abort,
storm-breaker, network drop. Miss one and the card was stuck.
Switch the running flag to a derived view:
- New InflightSet (src/core/inflight.ts) with add / delete / has /
subscribe + notify-on-mutation. Parallel finally-driven cleanup is
the contract: the language guarantees finally on every exit path,
so there's no closing event to forget.
- CacheFirstLoop holds one. runOneToolCall adds the call's id at
function entry and deletes it in finally; the chunk-loop pre-adds
before yielding tool_start so the very first card render already
reflects the running state. clearLog drains the set on /new.
- LoopEvent.tool_start / tool now carry callId — same id used as the
inflight key. TurnTranslator threads it into Scrollback.startTool,
which uses it as the card id so the card and the inflight key match.
- InflightProvider + useIsInflight (src/cli/ui/state/inflight-context.tsx)
expose the set as a React context backed by useSyncExternalStore.
ToolCard's toolStatus consults the hook for "running"; card.done is
no longer the spinner discriminator, only terminal flavor (ok /
rejected / aborted / error).
Tests:
- tests/inflight.test.ts — InflightSet contract: idempotent add,
notify-only-on-change, listener errors don't break the gate, clear,
finally-on-throw, finally-on-abort, parallel allSettled.
- tests/loop-inflight.test.ts — runOneToolCall finally clears the
set on success and on tool throw; tool_start carries callId
matching the inflight key; clearLog drains.
Out of scope (follow-up): subagent runId in the same set; deriving
streaming/reasoning running flags. Both are mentioned in the issue
but live behind different leak surfaces; the tool-card path is the
one users see most.
Chrome's "Page not responding" dialog fires on the dashboard chat tab
once a session accumulates enough messages. Repro condition: long
streaming turn or several concurrent jobs broadcasting at once.
Two cooperating bugs on the chat feed's hot path:
1. Every assistant_delta event hit setState synchronously. The model
streams ~20 deltas/sec; each one re-rendered ChatPanel, which
.map'd over every historical ChatMessage with no memoization, so
each one re-ran marked.parse + (for tool messages) hljs syntax
highlight on UNCHANGED content. Long sessions = N grows = main
thread starves.
2. The `streaming` prop fed to historical ChatMessage flipped between
`null` (no streaming) and `false` (streaming-but-not-this-message)
across turns, so even with memo, `null !== false` would force
every historical message to re-render every time streaming
started or stopped.
Fix:
- Wrap ChatMessage in `memo` from preact/compat so historical messages
with stable `msg` refs short-circuit re-renders.
- Cast the per-row streaming prop to a boolean so historical
messages get a stable `false` and memo's shallow compare actually
bails out across streaming-on/off transitions.
- Coalesce assistant_delta into a single rAF-batched setStreaming.
Multiple deltas in the same frame collapse into one state commit;
the streaming bubble's re-render rate is capped at the display
refresh rate. assistant_final + SSE reconnect + unmount each
cancel the pending flush so the buffer can't leak across turns.
Closes#551
When the sandbox root contained another product's data dir (Hermes
Agent's SOUL.md, skills/, memories/, etc.), the model would browse
those files and infer it was a sub-profile or runtime layered on top of
the host product. The system prompt defines the assistant as a
standalone coding assistant; the workspace contents shouldn't override
that.
Two layers:
- Top-of-prompt identity section names the failure mode explicitly:
workspace files describe the user's project, never what Reasonix is.
Calls out SOUL.md / AGENT.md / PERSONA.md / foreign skills+memories
trees / a foreign REASONIX.md as not-the-spec, and tells the model to
answer "who are you?" from the prompt instead of running ls.
- detectForeignAgentPlatform(rootDir) flags the workspace at launch if
one of those markers sits at the root, and the code-mode banner adds
a one-line warning suggesting --dir <real-project>. Conservative
signal: lone skills/ doesn't trigger (common in coding repos);
skills/ + memories/ pair does.
Closes#550
When a tool awaits pauseGate.ask (plan_checkpoint, plan_proposed, etc.),
the gate's promise ignores AbortSignal. Esc-during-busy fires
loop.abort(), but the awaiting tool fn never returns, so:
- busy stays true forever — PromptInput stays disabled.
- The pending modal (or its plan card) can't be dismissed.
- /new is silently dropped by handleSubmit's `if (busy) return`,
so the user can't even wipe the session to start over.
Add pauseGate.cancelAll() that resolves every outstanding request with
its kind's safe-cancel verdict (deny / cancel / stop / cancelled). Wire
it into a resetPendingModals helper that also clears every pending*
modal state, and call it from both Esc-during-busy and apply-slash-
result's clear branch. The awaiting tool fn now returns or throws
cleanly, busy clears, and the user can recover.
The "↑ earlier" hint was rendered conditionally on scrollRows > 0, as a
sibling of the measured outer Box. That tied outer.height to scrollRows:
toggling the hint changed outer.height by one row, which changed
maxScroll, which pinned-mode wrote back as scrollRows, which toggled
the hint again. With streaming content compounding inside the same
React batch, the chain reached MAX_NESTED_UPDATES = 50 and aborted with
"Maximum update depth exceeded" inside ink's useBoxMetrics.
Reserve the hint row unconditionally so outer.height is independent of
scrollRows. Trade is one row of permanent reservation; the loop is
gone.
The picker UI sorts suggestions by usage count (slashUsage) but the
Enter-time substitution recomputed the list without it, so the list
the user navigated and the list dispatch indexed into were ordered
differently. The shared slashSelected index then dereferenced a
different command than the highlighted row.
Pass slashUsage through so both calls produce identical orderings.
Rolling PR #538 into 0.36.0 since the version was tagged but not yet
published to npm. Tag will be moved to this commit so the published
0.36.0 contains the fix, no 0.36.1 needed.
SlashSuggestions called useColor / useStdout / useState before two
early-return branches (matches === null, matches.length === 0), then
useEffect afterward. When matches flipped from non-null/non-empty to
either of the early-return states and back, React saw 4 hooks one
render and 3 the next — "Rendered more hooks than during the previous
render" crash, killing the whole TUI.
Hoist windowStart computation + the useEffect above the early
returns. Compute against `matches ?? []` so the math is well-defined
when matches is null (windowStart resolves to 0, the effect no-ops
because state already equals 0). The early-return JSX branches stay
unchanged below.
Regression test rerenders the component through
non-empty → null → empty → non-empty and asserts no throw.
* chore(release): 0.36.0
* test(status-row): pin status-line version assertion to live VERSION import
Hardcoded "v0.35.0" string broke on every release bump. Reading from
src/version.js means future releases don't need a coordinated test
edit alongside the package.json bump.
* test(mcp): bump startup-summary timeout to 15s — chronic flake under suite load
captureStartupState dynamically imports chat.js + tools.js inside the
test, which can blow past Vitest's 5s default when the worker pool is
saturated (148 test files, lots of cold cache). Passes in isolation,
flakes under `npm test` parallel load. 15s adds headroom without
slowing the happy path.
Bracketed-paste markers (DECSET 2004) don't arrive on every host —
multiplexers strip them, some web-SSH gateways drop them, certain
Windows pipes never forward them. When they're missing, a multi-line
paste arrives as raw bytes; each \r in the chunk gets dispatched as
an Enter event; PromptInput submits the partial buffer; the loop
fires a fresh agent call per line. Reporter saw multi-line paste
trigger multiple submits in a row.
Heuristic rescue at the parser entry point: when a chunk in idle
state contains 2+ line breaks, OR a single line break with non-empty
text on both sides, AND no ESC bytes (would indicate a real key
sequence) AND no existing paste markers, wrap it in synthetic
\x1b[200~ … \x1b[201~ before processing. Routes through the existing
paste accumulator so it lands as ONE paste event with the whole blob.
Asymmetric tradeoff is intentional — a false-positive paste makes the
user re-press Enter; a false-negative paste fires N prompts and burns
N agent calls. The detector errs toward paste.
Bare \r and \r\n stay typed-Enter (terminal-converted CRLF is one
keystroke, not two breaks). "abc\r" stays typed-then-Enter, so a
fast typist's batched chunk still submits.
Updated the printable-coalescer split test to use \t since \r/\n now
route through the heuristic rescue when surrounded by text.
Closes#522
When the user picked Refine on PlanConfirm and typed their suggestion,
the model never saw the text. `handleStagedInputSubmit` built a rich
`synthetic` string with the feedback embedded but only resolved the
PauseGate with `{ type: "refine" }` — no payload. submit_plan threw
the bare `Error("user requested refinement")`, the model received
that as the tool result with zero context, and proposed a near-
identical plan, which fired PlanConfirm again. From the user's
perspective the suggestion was silently dropped.
The PlanVerdict union didn't even allow a feedback field, so the
omission was structural. The CheckpointVerdict pattern (already
shipping for revise-at-step) had the right shape; submit_plan just
never adopted it.
Pipe feedback through PlanVerdict for all three outcomes (refine /
approve / cancel) and surface it in the tool result string so the
model sees the user's exact words. Drop the dead `synthetic` that was
being built and discarded; keep `marker` and emit it via `pushInfo`
so the user gets a visible confirmation in chat scrollback right
after they hit Enter.
Closes#533
The /api/events endpoint snapshots only `busy-change` on (re)connect.
When the SSE connection drops mid-task — proxy timeout, browser
background-tab throttle, or Node event loop blocked past the 25s ping
window during heavy work — every assistant_delta / assistant_final /
tool / modal-up event fired during the disconnect window is lost.
EventSource auto-reconnects, but the new stream only carries new
events. If the disconnect happened before the end-of-turn
busy-change(false), the UI is wedged on "busy" forever and the
completed reply never appears. Reopening the dashboard URL was the
only escape, since fresh page load fetches /api/messages.
On reconnect (every onopen after the first), refetch /api/messages
and /api/modal to recover canonical state. Streaming + active-tool
slots reset since they're transient — the next delta will repopulate
streaming, the next tool_start will repopulate active-tool. First
open is skipped because the boot effect already fetched canonical
state.
Closes#521
* fix(tui): enable DECSET 1007 alternate-scroll so wheel scrolls on cloud/web terminals
Previously we relied on the implicit "terminal translates wheel→↑/↓ in
alt-screen" behavior. That only holds on local desktop terminals
(xterm/iTerm/Windows Terminal/Alacritty) where alt-scroll is on by
default. Web/cloud/SSH terminals (xterm.js, code-server, Cloud Shell,
mobile SSH clients, tmux without `mouse on`) don't ship with that
default, leaving the wheel as a dead key — the most common
"can't scroll" report.
Explicitly request the behavior via DECSET 1007 (alternate-scroll) on
mount, reset on unmount. Falls back silently on terminals that don't
recognize 1007. Native drag-select and right-click are untouched —
no Shift bypass needed.
`--no-mouse` opts out for the rare user who'd rather suppress the
sequence entirely.
* fix(tui): disable Ink incrementalRendering to drop render ghosting
Incremental render diffs against an internal "what's on screen"
snapshot. The diff drifts when:
- string-width misjudges CJK / emoji ZWJ cell width and Ink
miscomputes the affected region
- async terminal-event bytes (DA replies, mouse, focus) interleave
between Ink's cursor-positioning writes
- terminal resize races a flush
When the diff drifts, stale rows survive the redraw — the residual
"ghost" class users have been reporting on cloud/web terminals.
Full-frame redraws sidestep the snapshot. Cost: more stdout bytes per
flush. At 60Hz default flush, local terminals are unaffected; remote
SSH only feels it during sustained high-rate streaming, where the
existing REASONIX_FLUSH_MS escape hatch can drop to 30Hz.
Replace hardcoded English strings in 8 card components (Ctx, Error, Reasoning, Search, Streaming, SubAgent, Tool, Usage) with t() calls. Pluralization handled at the call site via singular/plural key pairs (Chinese maps both to one form). Adds cardTitles + cardLabels namespaces to EN.ts / zh-CN.ts / types.ts.
Levenshtein-rank registered command names against unknown slash input; surface up to three closest candidates inline in the dispatch response. Falls back to the existing "(try /help)" hint when nothing is within distance threshold. Closes#17.
Collapse case-variant PATH / PATHEXT keys (Path / PATH / path) into one normalized entry before passing env to child_process.spawn on Windows, and read PATH / PATHEXT case-insensitively in resolveExecutable so the spread env (which is a plain object, not the case-insensitive process.env Proxy) still resolves bins. Refs #520 — does not auto-close; awaiting reporter verification that Machine PATH inheritance is restored.
Slot a theme step between language and apiKey so the rest of the wizard renders in the chosen theme. Live preview updates as the user navigates the list; default highlight lands on the currently-resolved theme; commit writes through writeConfig. Sample tile exercises tone.accent / tone.info / tone.ok / tone.warn / tone.err + fg.meta. Closes#492.
Rework SlashSuggestions windowing so grouped headers are budgeted into the visible row count and selection moves through commands without skipping group rows. Wrap StatusRow children with flexShrink/height/wrap=truncate so the status bar no longer collapses under the suggestion popup. Surface /language as a visible setup command. Filter order in suggestSlashCommands now also exposes code-group commands in bare browsing — flagged for follow-up if undesired.
We write to stdout at the streaming flush rate, and the terminal has
to interleave those writes with its own native drag-select highlight
repaints. At 30Hz (33ms) the terminal can't keep up — selection
feedback visibly lags during model output. Now that mouse mode is
off (#514) and users actually use drag-to-select again, this is the
load-bearing perf knob.
50ms (20Hz) still feels smooth on every modern terminal we test on
(WT, WezTerm, iTerm2, Alacritty, Ghostty) and cuts the write rate by
33%, leaving terminal repaint enough budget to keep selection
highlights snappy. `REASONIX_FLUSH_MS=33` brings the old behavior
back for anyone who actively prefers it.
* fix(tui): drop xterm mouse tracking; ↑/↓ scroll chat, Ctrl+P/N owns prompt
Multiple users reported they can't copy text and can't scroll. Both
trace to the same root cause: we enabled DECSET 1000 + 1006 mouse
tracking so the wheel could route through `mouseScrollUp/Down`. The
side effect is that every terminal we know about then refuses to
start a native drag-select on click, blocks right-click, and on
ConPTY / multiplexer setups can drop the wheel events entirely (so
neither path scrolls).
Architecture flip:
- Don't enable mouse tracking. Bracketed paste + modifyOtherKeys stay.
- ↑/↓ at the App level always scroll chat, no buffer-state gating.
Terminals translate the wheel to ↑/↓ in alt-screen mode, so the
wheel still scrolls chat — for free, in every terminal.
- Ctrl+P / Ctrl+N take over what ↑/↓ used to do in PromptInput:
cursor up/down inside a multi-line draft, falling back to prompt
history when no cursor move is available (readline parity).
- /keys + tipMouseClipboard rewritten to reflect the new bindings;
the old "hold Shift to drag-select" workaround is gone — drag
works directly now.
Cost: power users who liked the wheel-scroll-while-typing affordance
have to switch to PgUp/PgDn or empty their prompt. Worth it given
how many users hit the copy-paste wall.
* fix(tui): update prompt hint row + stale comments to reflect ↑↓ scroll / Ctrl+P/N history binding
* fix(tui): don't scroll chat when a picker owns ↑/↓ (slash / @-mention / slash-arg / shell-confirm)
Two compounding bugs sent self-hosted DeepSeek users back to the
official endpoint regardless of how they configured the client:
1. config.baseUrl was a dead field. Every `new DeepSeekClient()` call
site (App.tsx, commit.ts, doctor.ts, run.ts) constructed the
client without passing baseUrl, so it always fell back to the
`DEEPSEEK_BASE_URL` env var or `https://api.deepseek.com`. The
dashboard settings panel saved the value but nothing read it.
2. isPlausibleKey enforced the `sk-` prefix, so the wizard / setup /
`/feedback` settings rejected any token that didn't look like an
official DeepSeek key — even when the user had pointed baseUrl at
their own deployment.
Adds `loadBaseUrl` (env > config > undefined) + `saveBaseUrl`, plumbs
the loader into all four client construction sites. Relaxes
isPlausibleKey to a generic typo guard (16+ chars, no whitespace) so
self-hosted token formats work; the real auth check is the first API
call against baseUrl.
Closes#502
The dashboard health card, overview cockpit, and /feedback diagnostic
all decided "up to date" via `latest === installed` string equality.
That fires false-positive "needs update" / "(latest: 0.31.0)" pills
whenever the cached latest is older than the installed version — for
example after publishing 0.35.0 while the 24h cache still holds the
prior latest.
Switch all three sites to `compareVersions(installed, latest) >= 0`.
Add a tiny dashboard/src/lib/version.ts so the browser bundle has the
same comparator the CLI uses (no cross-package import).
Closes#510
`reasonix update` previously always emitted `npm install -g`, which
clobbered bun/pnpm/yarn installs and was unpredictable under nvm/fnm
where ambient npm may resolve to a different node runtime than the one
running the binary.
Detection (`detectInstallSource`) reads argv[1] and matches each
manager's unique global path segment:
- `_npx/`, `.pnpm/...dlx/`, `npx/` UA → npx
- `.bun/`, `bun/install/` → bun
- `pnpm/global/` → pnpm
- `yarn/global/`, `.yarn/global/` → yarn
- `node_modules/reasonix/` → npm
- otherwise → unknown
Plan emits the matching command per source. For npm we additionally
pin `--prefix=<extracted-prefix>` so nvm/fnm runtime switches don't
redirect the install elsewhere. For unknown source we refuse with a
manual hint listing all four commands and exit 1 — no silent npm
fallback.
Closes#506
PATH refreshes per-shell on Windows, so a dashboard process started
before the Ollama install (or before a Terminal restart) inherits a
stale PATH and `where ollama` returns nothing — even when the daemon
the user launched from the tray icon is fully serving requests.
Two changes:
- findOllamaBinary falls back to %LOCALAPPDATA%\Programs\Ollama\
ollama.exe when `where` fails. spawn() for `serve` / `pull` now uses
the resolved path so those buttons survive a stale PATH too.
- ready no longer requires binaryFound. The embedding pipeline only
talks to the HTTP API; the binary is only needed for daemon-start
and model-pull, which have their own UI guards.
Closes#504
* chore(format): reuse fmtPct for cache-hit display; keep cachePct numeric
Drop the duplicate `formatCacheHitPct` helper added in #503 — `fmtPct`
in `dashboard/src/lib/format.ts` already does the same `(n*100).toFixed(1) + "%"`
shape and is the canonical formatter for the rest of the panels.
In `/status` (`observability.ts`), keep `cachePct` as a number through
`renderTinyBar` and only `.toFixed(1)` at the template-string boundary,
so we don't round-trip through string + `Number()`.
* chore(release): 0.35.0
* feat(ui): version badge in status row + /feedback opens issue with diagnostic clipboard
When a user hits a bug, the first question back is "what version" — and
the only way to find out today is to drop to the shell. Filing the
issue itself means leaving the TUI, finding the repo URL, then either
remembering or re-collecting version / OS / terminal / Node / locale /
model. Both papercuts are easy to fix from the prompt-input surface.
- StatusRow shows a `v<VERSION>` pill on the right cluster, gated to
cols ≥ 70 so it doesn't crowd narrow terminals.
- New `/feedback` slash: gathers version + platform + os release +
TERM_PROGRAM/TERM + Node + locale + model + sessionId, writes a
paste-ready Markdown block to the clipboard via the existing
`writeClipboard` helper, then opens the GitHub new-issue URL in the
default browser via a new cross-platform `openUrl` (win32 cmd /c
start, darwin open, linux xdg-open). No-ops under CI / when
REASONIX_NO_OPEN is set.
- Diagnostic body contains exactly the seven advertised fields and
nothing else — `tests/feedback.test.ts` pins the field set and asserts
no API keys / file paths / transcript content can leak through.
Closes#499
* feat(ui): pre-fill /feedback issue body via URL + surface chip in status row
Two follow-ups so the affordance actually gets discovered and used:
- The issue page now opens with the diagnostic block already in the
textarea via `?body=<urlencoded>`. Most users won't notice we copied
to clipboard; pre-filling the URL is the obvious path. Clipboard
stays as belt-and-suspenders for when the URL fails to open.
- StatusRow shows a `⚑ /feedback` hint after the version pill at
cols ≥ 100 so users see the command exists. Narrower terminals (70–99
cols) still get the version, just without the hint.
- Body length is capped at 6000 chars before encoding so a runaway
diagnostic can't blow past the URL limit.
* feat(ui): expand /feedback diagnostic with flicker-relevant fields
The original block had version + platform + TERM_PROGRAM + Node + locale
+ model + session — fine for "agent ran the wrong tool" reports, but
useless for the rendering / flicker reports we actually field. Adds the
fields that come up first when triaging those:
- terminal size (cols×rows) — lots of repaint bugs only repro at
specific widths
- env markers that change the rendering pipeline: COLORTERM,
WT_SESSION, TMUX, SSH_TTY, WSL_DISTRO_NAME — TERM_PROGRAM alone can't
distinguish cmd / WSL / SSH-tunnelled terminals
- theme name — different themes use different background fills, flicker
is often theme-dependent
- edit / plan mode — decides which surfaces are mounted, changes
repaint cadence
- latest version compare — surfaces "you're on an old build" without a
follow-up question
- reasoning effort + MCP server count — incidentally cheap, occasionally
load-bearing for cost / latency reports
Still no transcripts, paths, workspace name, or env outside the
hand-picked safe list. New tests pin the exact field set so future
fields can't sneak in unannounced.
The design-doc page chrome (`.toc` / `.section` / `.subsec`) was tuned
on a larger display and reads as too tight on a 13" laptop at 100%
zoom. Sidebar section headers at 10px with 0.14em tracking are the
worst offender — section labels also wrap mid-word in the 240px column.
- `.page` sidebar column: 240px → 260px so 2–3 word section labels fit.
- `.toc h1` 14 → 15px; `.toc .sub` 11 → 12px.
- `.toc-section` 10 → 12px and tracking 0.14em → 0.08em (lower so the
size bump doesn't fight the letter-spacing).
- `.toc li a` 12.5 → 14px with `line-height: 1.4` and
`overflow-wrap: anywhere` for graceful wraps on longer labels.
- `.section > .lede` 13 → 15px; `.subsec > p` 12.5 → 15px (line-height
1.6 already applied).
- `.subsec > h3 .desc` 12 → 13px.
- `.swatch .hex` 10.5 → 11.5px; `.scale-row .lbl` 10.5 → 11.5px (and
width 70 → 76px to keep the new monospace digits aligned).
Mirrored verbatim into `docs/design/agent-dashboard.html` per the
"keep CSS in lockstep with the mockup" comment at the top of app.css.
Closes#461
Two new agent-facing tools so "add a skill that does X" / "wire up a
postgres MCP server" work as normal chat requests instead of forcing the
user out to slash commands:
- `create_skill` — pre-fills frontmatter (description / runAs /
allowed-tools / model) from structured args and writes through a new
SkillStore.createWithContent that reuses the same path resolution +
collision check as `/skill new`.
- `add_mcp_server` — builds a `name=...` spec for stdio / sse /
streamable-http transports, optionally hydrates from MCP_CATALOG,
runs the existing preflight (filesystem sandbox-dir check), and
appends to cfg.mcp via writeConfig. Refuses name collisions.
Active on next launch — no live MCP client churn this session.
Both are registered alongside the existing native tools in
`reasonix code` so they're available wherever filesystem / shell are.
Closes#494
The banner already detected `Open Questions` / `Risks` / `Unknowns` headings
but the questions themselves were never shown — PlanConfirm rendered either
a step list or a 24-line body cap, both of which can hide the block. Refine
mode then reopened a blank input with no echo of the questions, so the user
either invented an answer or hit Enter and we asked the model to re-derive
its own questions on a follow-up turn.
- Extract the matching block (heading down to next same-or-shallower heading)
via `extractOpenQuestionsSection` and render it under the banner regardless
of steps / body cap.
- Forward the extracted block to `PlanRefineInput`, which now renders the
questions above the input on `mode === "refine"`.
- Replace the blank-refine synthetic that asks the model to re-derive
questions with one that tells it to pick safe defaults and call them out.
- Move all plan-flow strings (PlanConfirm / PlanRefineInput /
PlanCheckpointConfirm / PlanStepList counter line) through `t()` under a
new `planFlow` namespace in EN + zh-CN.
Closes#477
A single popular symbol could match 200+ lines in a big file (App.tsx,
loop.ts) and eat the entire byte budget before the walk reached any
other file. Truncation marker fired, every other matching file got
zero coverage, and the caller saw a wall of one file's hits with no
hint that distribution was wider than that.
Three knobs:
1. MAX_HITS_PER_FILE = 30. Beyond that, the per-file output ends with
"[rel: N more matches in this file — re-grep with a tighter
pattern or use read_file to see them]". One bullhorn file can no
longer dominate the byte budget.
2. After each file completes, if printed bytes have crossed 80% of
the byte budget, remaining files switch to histogram form
("rel: N matches"). A one-line notice marks the flip so the
caller knows distribution from this point on is summary-only.
3. New `summary_only:true` arg skips line content entirely and
returns just the histogram. Useful for "where does this exist at
all" before drilling in with a targeted read_file.
Closes#489
The child loop's tool-iter cap was enforced from the outside only;
the subagent's system prompt never said "you have N tool calls", and
the child had no way to know which iteration it was on. The visible
failure mode was an explore subagent burning all 20 iters mapping the
territory, then hitting the cap mid-thought and emitting a partial
summary the parent had to re-dispatch from.
Two pieces:
1. spawnSubagent now appends a one-paragraph budget notice to the
child's system prompt — literal "Tool budget: you have N tool calls"
with the resolved cap baked in. Applies to default, typed
(explore/verify), and caller-supplied system prompts uniformly.
2. ToolRegistry gains setResultAugmenter(), a final-stage post-hook
on dispatch. spawnSubagent installs one that counts dispatches and
appends "[budget: K of N tool calls left — wrap up soon]" once the
child is within 3 iters of the cap, escalating to "0 left —
finalize NOW" on the last call.
Static prompt + dynamic countdown together: prompt sets expectation,
countdown forces reckoning when the budget is actually tight.
Closes#488
When the auto-preview path fires (file > 200 lines, no head/tail/range
given), the head 80 + tail 40 slice rarely covers the full export list
of a real file. Callers had to follow up with a search_content grep to
locate "where is function AppInner defined" before they could pick a
useful range.
Now the auto-preview embeds a top-level outline between the head slice
and the omitted-marker — function / class / const / interface / type /
enum names with their line numbers, capped at 30 entries (first 25 +
last 5 + an elide marker). One round-trip, not three.
Closes#487
Each PgUp / PgDn / arrow / wheel tick used to call setScrollRows
synchronously, so a single mouse-wheel gesture (10-30 events) triggered
10-30 full Yoga layout passes over the entire card tree. Layout cost
scales linearly with history length, which is what made long sessions
feel laggy.
Accumulate the delta into a ref and flush once per ~16ms. Net effect:
one setState per scroll burst regardless of event volume. jumpToBottom
cancels any pending delta so End still feels instant.
Closes#482
The dashboard's initLangFromServer() had two branches when localStorage
disagreed with the server config:
1. If `rx.langExplicit` was set (user picked a language in dashboard
panel at some point) → POST localStorage value back to server
2. Otherwise → adopt the server value
Branch 1 silently clobbered CLI-side `/language` changes. Sequence:
- User picks zh-CN in dashboard once → rx.langExplicit=1, rx.lang=en
(or whichever)
- User later runs `/language zh-CN` in the CLI → server config is
now zh-CN
- User opens dashboard tab (or browser restores it from a previous
session) → init runs → POSTs localStorage's old value back, server
flips to en, CLI's choice is lost on next launch
Server config is the single source of truth. localStorage is purely a
render-cache to avoid first-paint flicker — never push it back.
Removes EXPLICIT_KEY / isExplicit / markExplicit entirely; the stale
key in existing users' localStorage is harmless dead data.
Two layers around the new TipCard:
1. /keys — make the slash command real
It was already referenced in the edit-gate tip's footer ("Run /keys
anytime for the full list") but no handler existed; typing /keys hit
the unknown-command branch. Add the spec under "info", a handler
that pushes a multi-section TipCard with the full reference, and a
`postKeys` callback on SlashContext wired to log.pushTip.
The reference is sectioned: keyboard / mouse / copy-paste /
edit-gate. Each section has its own subtitle and aligned key column.
2. First-run mouse + clipboard tip
SGR mouse tracking captures the wheel for chat scroll but also eats
the terminal's native right-click-paste — without explanation users
think the prompt is broken. Add a one-time tip mirroring the
edit-gate pattern: pushed on first launch, suppressed thereafter via
a `mouseClipboardHintShown` flag.
TipCard now supports multiple sections (single-section tips just have
one un-titled section). The previously-shipped tipEditBindings is
re-wrapped in a single section; behavior unchanged.
i18n: keysReference (4 sections, ~25 rows) + tipMouseClipboard (1
section, 3 rows) + handlers.basic.keysNeedsTui in EN.ts and zh-CN.ts;
matching shape in types.ts. The i18n /keys row already existed but its
description was outdated — refreshed in both languages.
The edit-gate one-time tip currently renders as raw multi-line text
inside a stepProgress LiveCard — `✓` glyph (success semantic, wrong
for educational content) plus a manually-inlined `▸ TIP:` prefix,
columns aligned with hand-counted spaces that wrap badly on narrow
terminals, and the "shown once" disclaimer crammed into the body
parenthetical.
Replace it with a dedicated `TipCard` kind:
- Single `ⓘ` glyph in accent color, no duplicated prefix
- Topic + "shown once" badge in a header row (justified)
- Each row is its own `<Text>` with real column alignment driven by
stringWidth (works for CJK widths too)
- Footer separated from body by a blank row, dim color
- No border — tips are scrollback content, not modal
i18n: `tipEditBindings` becomes a structured `{topic, rows, footer}`
object across types.ts / EN.ts / zh-CN.ts. New helper `tObj<T>(path)`
in i18n/index.ts for non-string entries; the existing `t()` is
unchanged. Adds a tiny `tipShownOnce` string for the badge.
Adds a `pushTip()` method on Scrollback alongside `pushInfo()`; the
new `tip.show` event flows through the same reducer / dispatch pipeline
as every other card kind.
* feat(at-picker): rebuild as file browser with streaming search
Empty / trailing-slash queries (`@`, `@src/`) browse one directory level
with a single readdir — folders selectable, drill via Tab. Any non-slash
filter (`@foo`, `@auth/log`) kicks off a cancelable streaming walk across
the full tree, batching matches into the popup as they're found, with a
`searching… N scanned` footer while in flight.
Replaces the upfront 500-file walk that was unusable on large repos —
on a 5k-file tree the cap evicted ~90% of paths before ranking, leaving
the picker effectively empty.
- walkFilesStream: cancelable streaming walker; powers search mode
- listDirectory: single-level browse, no recursion; powers browse mode
- parseAtQuery: splits `dir/filter` with trailing-slash awareness
- listFilesWithStatsAsync now delegates to walkFilesStream (no behavior
change for existing callers)
- expandAtUrls + helpers split into at-mentions-url.ts to keep
at-mentions.ts under the 800-line ceiling
Closes#478
* fix(scroll): route mouse wheel via SGR mouse tracking
Enable DECSET 1006 + 1000 at startup so the terminal reports wheel
events as `\x1b[<btn;col;row;M` mouse sequences instead of translating
them to ↑/↓ key presses. The chat-scroll handler routes the resulting
mouseScrollUp/Down events to scrollback, bypassing the arrow-key path
entirely — the wheel now scrolls chat regardless of buffer state, while
↑/↓ keys retain their existing PromptInput bindings (history recall on
empty buffer, cursor motion otherwise).
The SGR mouse parser already lived in stdin-reader.ts; this just
turns on the terminal-side feature so events actually flow.
Cost: terminal-native drag-to-select needs a modifier (Shift on Windows
Terminal / Alacritty / WezTerm, Option on iTerm2) — same trade-off as
tmux, Claude Code, Cursor's terminal.
Two bugs in one issue.
1. **↑/↓ stopped recalling history.** 9254d3a unbound history from
arrows because Windows Terminal + ConPTY can translate mouse-wheel
events to ↑/↓ keystrokes — wheel-up was clobbering the prompt with
a recalled message. The fix moved history to Ctrl+P / Ctrl+N.
That was the right call for legacy ConPTY users but broke the
universal CLI muscle memory for everyone else (bash / zsh / fish
all bind ↑ to history). Linux / macOS / modern Windows Terminal
users don't have the wheel-translation problem in the first place.
Restore ↑/↓ on empty buffer = history; keep Ctrl+P / Ctrl+N as
the wheel-immune fallback. The App-level keystroke handler still
routes ↑/↓ to chat-scroll once the user is unpinned (subsequent
wheel events keep scrolling), so the only regression for legacy
ConPTY is the FIRST wheel-up from a pinned position recalls a
prompt. Documented; ⌃P/N is one keystroke away.
Drops the now-dead `chatScrollHandoff` plumbing.
2. **Doctor reported "tokenizer not found" when it was installed.**
The tokenizer ships under `data/` in the npm tarball and the
runtime resolver in tokenizer.ts has three candidates including a
`createRequire("reasonix/package.json")` probe — finds it
reliably. The doctor had its own resolver that walked
`dist/cli/commands/doctor.js → ../../../data/`, which broke after
the lazy-import refactor in #467 emitted the doctor at
`dist/cli/doctor-HASH.js` (one level shallower). Walked above the
package root and reported missing.
Reuse the runtime resolver (now exported) so the two paths can
never disagree.
The status row was reading status.cost (turn) and status.cacheHit
but ignoring two fields the reducer already populates:
status.sessionCost (running USD total) and status.balance (DeepSeek
wallet, refreshed on every submit). balanceColor() with red/orange
thresholds even sat in tokens.ts unused.
New WalletPill segment renders right of the cache pill:
⛁ ¥1.20 spent / ¥45.32 left
with thresholded color on the balance number. Shown only when
the terminal is ≥90 cols and at least one of the two values is
known, so narrow sessions don't wrap.
PromptInput: friendlier placeholder copy ("ask anything") and the
hint footer now uses keycap/label spacing (⇧⏎ instead of
shift/alt+⏎) for a less command-line-jargon read.
The /tool slash command was removed in #453 but its supporting
plumbing was left behind: every tool result was still being pushed
into a useRef array, with no consumer ever reading it. Long-running
sessions accumulated full Read/Grep/Bash output indefinitely and ran
out of heap.
#465 reports a JS heap OOM after ~2.6 hours on v0.31.0; this leak
matches the failure shape (mark-compacts ineffective, 4GB ceiling).
#459 follow-up. When `/cwd` swaps the workspace root, FS/shell/memory
tools were re-registered against the new path but `semantic_search`
kept pointing at the OLD root — meaning queries silently searched
the previous project's index, or the tool stayed registered when
the new dir had no index at all.
Split semantic re-bootstrap from the sync `reregisterTools` callback:
- `reregisterTools` stays sync (FS/shell/memory must land before the
next tool dispatch).
- New `reBootstrapSemantic(root) => Promise<{ enabled }>` reads disk
to probe index compatibility, registers `semantic_search` if found,
unregisters it otherwise.
App.tsx fires the async tail with `void ...then(postInfo)` so the
slash dispatch returns synchronously (matches the codebase's
fire-and-forget pattern documented in slash/dispatch.ts). User sees:
▸ workspace switched to /new/path
▸ semantic_search re-pointed at /new/path ← if compatible
▸ semantic_search disabled (no compatible index in /new/path)
← if not
Same machinery handles the launch path — `code.tsx` now calls
`reBootstrapSemantic(rootDir)` instead of bootstrap directly so
the unregister-on-skip behavior is exercised on every entry path.
Stage 2 follow-up to #464. Continuing the profile-driven trims.
The dashboard server module (src/server/index.ts plus its ~4200 LOC
of transitive dashboard code) was being eagerly imported into App.tsx
even when --no-dashboard was set or auto-start hadn't fired. Move it
to a dynamic import inside startDashboard's startup IIFE — it's
already async, so the await import() is free in the structural
sense.
Measurable hot-path delta is small (~4ms within noise) but it shaves
real bytes off the first-paint module graph and removes a synchronous
dependency on the entire server tree. Cold paths benefit too.
Also adds two strategic marks (`app_render_start`, `app_inner_start`)
for future profiling. They're harmless when the env var is off and
expose the React-component-body boundary in the dump, which makes
the existing `first_paint` delta self-explanatory.
Findings from the deeper investigation (now reverted as noisy diagnostics):
- App's disk-hitting useState initializers (loadHooks, loadSlashUsage,
loadEditMode, hydrateCardsFromMessages) are all sub-ms each.
Deferring them buys nothing measurable.
- The 280-300ms gap between `app_inner_start` and `first_paint` is
React reconciliation + Ink's terminal commit + the first useEffect
flushing. Trimming further requires reducing initial render
complexity, not deferring side work.
Stage 3 (CI budget gate) remains deferred — the platform-dependent
nature of these numbers makes a hard threshold fragile. Profile
harness is already documented in-tree via the env-var hint
(`REASONIX_PROFILE_STARTUP=0 to silence`).
Stage 1 (#466) showed module-load was 57% of cold-start cost (436ms
of 764ms total on this Windows box). Every `reasonix <subcommand>`
invocation was eagerly loading every other command's module —
including chat.tsx → App.tsx → React/Ink. `reasonix version` paid
for the chat UI it doesn't need.
Move every `import { fooCommand } from "./commands/foo.js"` into a
dynamic `await import()` inside the relevant `.action()`. tsup
splits these into separate chunks automatically; Node only loads
them when the user invokes that subcommand.
Measured impact:
reasonix code (hot path, 5 runs avg): 778ms vs 764ms baseline
→ +14ms regression (within measurement noise; the 388ms that
used to live in `cli_module_loaded` now lives in
`code_command_enter` since code.tsx is dynamic-imported)
reasonix version: ~140ms vs ~440ms baseline → 290ms saved
reasonix --help: ~140ms vs ~440ms baseline → 290ms saved
Cold-path commands (version, --help, doctor, commit, sessions,
events, replay, diff, mcp *, update, index) all benefit. They
no longer pay the ink/react/dashboard import cost.
Hot path (`code` / `chat`) is roughly neutral. Real wins on hot
path will come from trimming first_paint (316ms, 41% of total) —
follow-up.
Test fix: bundle-smoke.test.ts asserted `from "ink"` lived in
dist/cli/index.js specifically; with code-splitting the import
moves to a chunk file. Updated assertion to scan all dist/cli/*.js.
The semantics are preserved — ink stays external (not bundled),
just no longer in the entry chunk.
#464 plan was profile-first; this lands Stage 1.
Adds src/cli/startup-profile.ts with markPhase/dumpStartupProfile
gated behind REASONIX_PROFILE_STARTUP=1. When unset (default), every
call is a no-op — zero cost in normal runs.
Marks placed at:
- cli_module_loaded — top of the bin entry, after all transitive imports
- chat_command_enter / config_loaded
- mcp_launch / mcp_connected_M_of_N (only when MCP specs exist)
- code_command_enter — top of `reasonix code`
- semantic_bootstrap_start / _done_(enabled|skipped)
- ink_render_call — just before `render(<Root/>)`
- first_paint — App's first useEffect after mount, also dumps the profile
Baseline collected on this Windows box (no MCP, semantic index already
built):
436ms cli_module_loaded (+436)
3ms code_command_enter (+3)
2ms semantic_bootstrap_start (+2)
2ms semantic_bootstrap_done_enabled (+2)
3ms chat_command_enter (+2)
0ms config_loaded (+0)
2ms ink_render_call (+1)
316ms first_paint (+316)
─── 764ms total
Read: module-load (Node + transitive imports) is 57% of total, first
paint (Ink render + React commit) is 41%. Everything else is noise.
Stage 2 should target lazy-loading heavy import dependencies that
land synchronously today (DeepSeek client, Ink, dashboard server,
embedding provider). MCP serial setup hypothesis from the issue
needs a real config to confirm — punted until we have a measured
multi-MCP run.
Stage 3 (CI budget assertion) deferred until Stage 2 trims have
landed and we have stable numbers to set thresholds against.
#459 is a meta-issue with three first-five-minutes UX papercuts.
This lands two of them; startup-perf (part 3) needs profiling
first and gets a separate issue.
## Part 1: at-mention picker — subsequence fallback
The picker rejected anything that wasn't a substring match, so
typing `atmnt` for `at-mentions` returned nothing. Adds a fuzzy-
subsequence scorer as a fallback after substring lookup misses.
Substring hits still win — class 0/1/2 cap at 29_999, subseq
starts at 30_000. Fuzzy scoring rewards consecutive runs and
basename-anchored matches, penalizes total path length.
Files walking + cap-aware UI hints already existed (the audit
showed them at useCompletionPickers.ts:102 and
AtMentionSuggestions.tsx:55–77). The missing piece was ranking.
## Part 2: /cwd slash command
The plumbing was already there: `codeMode.reregisterTools(root)`
exists in code.tsx, App.tsx already comments "/cwd mutates this
state to swap the workspace mid-session". The slash command
itself was just never wired.
Wires it end-to-end:
- SlashContext gets a `switchCwd(path) => { ok, info }` hook.
- App.tsx implements switchCwd: stat + isDirectory check,
reregisterTools(newPath), setCurrentRootDir, reload hooks.
- New `/cwd` (alias `/sandbox`) command in the code group.
- Handler in handlers/edits.ts.
- EN + zh-CN strings added.
Out of scope: semantic-index re-bootstrap on cwd swap (current
bootstrap runs once in code.tsx). Tracked as a follow-up.
## Part 3 (deferred)
Slow startup needs profiling before redesign. Will open a separate
issue with a concrete "mark phases, defer post-mount" plan.
Three quality polishes to the filesystem toolbelt, all small, all
addressing real friction the model hits often.
glob — new tool. Mtime-sorted file walk with picomatch glob syntax
(**/, *.{ts,tsx}, etc.). Default sort=mtime desc so "what did I
touch lately" works out of the box; sort=name for deterministic
listings. Skips deps by default, capped at 200 results (1000 max)
with overflow notice. Different from search_files (substring on
basename) and search_content (greps file bodies).
search_content — new `context: N` param mirroring `grep -C N`.
Output uses ripgrep convention: `:` after the line number on hits,
`-` on context lines, `--` separating non-adjacent windows.
Adjacent windows merge automatically so a hit at line 42 and 44
with context:1 produces one continuous block. Capped at 20 lines
on each side to keep the maxListBytes budget intact.
multi_edit — reshape from single-file `{ path, edits: [...] }` to
cross-file `{ edits: [{ path, search, replace }, ...] }`. Reads
each touched file once, applies edits in array order against an
in-memory buffer (so a later edit can match text inserted by an
earlier one), validates everything, then writes all touched files.
ANY validation failure → ZERO writes (true atomicity at the
validation layer; sequential disk writes after that). Output
header now reports both "N edits across M files".
This is a hard schema break for multi_edit, but it shipped
unreleased six hours ago — no consumers to migrate.
Test coverage: 24 new cases (glob: 6, context: 4, multi_edit: 8
covering single + cross + atomic + missing-file). 2243 pass on
verify.
submit_plan is the heavy gate (user approval, per-step checkpoints,
plan-mode toggle); ask_choice is the branching primitive. Neither
covers "I have 4 things to do, let me record them and tick them off
as I go" — that's prose-list territory today, which means lost
context the moment the loop folds history.
todo_write fills the gap: replace-set semantics, no approval pause,
no file writes. Validated: at most one in_progress, status enum,
non-empty content+activeForm. readOnly=true so it stays callable in
/plan mode (recording intent during planning is exactly when it's
most useful).
Wired into reasonix code with an onTodosUpdated callback hook for
future TUI surfacing (live progress strip, etc.). System prompt
gains a "When to track multi-step intent" section telling the model
to reach for it on 3+ step tasks instead of inlining "1. ... 2. ..."
in prose.
N edit_file calls for a single-file rename burns a tool round-trip
per site and isn't atomic — a mid-batch failure leaves the file half-
edited. multi_edit takes an array of {search, replace} entries,
applies them sequentially against an in-memory buffer, and only
writes once all succeed. Any failure (search not found, ambiguous
match, empty search) → no edits are written.
Per-edit rules match edit_file: exact whitespace-sensitive search,
must be unique at the moment that edit applies. Sequential semantics
mean edit N+1 can match text that edit N inserted.
Closes a concrete pain point flagged when surveying the toolbelt
against typical multi-site refactor flows.
Closes#451
UI flicker (section 3 of #451) is already tracked in #412.
1. expandAtMentions treated `@<dir>` as a `not-file` skip — the model
never saw what was in the directory. It now resolves the path, walks
the project root with the existing gitignore layers, filters to
entries under the directory, and inlines a `<directory>` block
capped at DEFAULT_AT_DIR_MAX_ENTRIES (200). `@docs/` and `@docs`
resolve to the same key, so trailing-slash typing doesn't double-fire.
2. listFilesWithStatsSync / listFilesWithStatsAsync called only
ent.isFile(), which returns false for symlinks. Symlinked source
files were silently dropped from the picker. Both walkers now stat
through symlinks; symlinks-to-files come back, symlinks-to-dirs
stay dropped (cycle risk), broken links stay dropped (nothing to
point at).
Two related plan-mode UX gaps.
1. PlanLiveRow had nothing to dock. `case "plan_proposed"` dropped the
gate payload's steps/summary, and the approve path never dispatched
plan.show — so no card with variant: "active" ever existed and the
filter in isActivePlanInFlight returned null. Stash steps/summary in
the existing refs on plan_proposed, materialize the active card on
approve, and drop+re-show on revise-accept so the dock tracks tail
rewrites instead of silently going stale.
2. "Checkpoint — step done" fired after every mark_step_complete even
in auto/yolo, defeating the whole point of those modes (shell and
edit-gate already self-skip). plan_checkpoint now checks editModeRef
and, in auto/yolo, resolves the gate with "continue" without UI.
Per-step rollback snapshot still runs so /restore granularity stays.
* slash: unified preset+model picker, grouped suggestions, kill 11 commands + harvest/branch
The slash surface was 58 commands deep with no organization, two confusable
options for "fresh start" (/clear vs /new), separate preset and model commands
that solved the same user question ("what AI am I using"), and two heavy
features that almost nobody opted into. Pulled all of that apart.
Picker
* ModelPicker now shows the 3 presets at the top with cost/headline copy and
the model catalog below; auto-detects which preset the loop currently matches
(model + effort + autoEscalate) so the cursor lands on the active row. Both
/preset (no arg) and /model (no arg) open it.
SlashSuggestions
* SlashCommandSpec gains a `group` field (chat / setup / info / session /
extend / code / jobs / advanced). Suggestion palette renders section headers
on a bare /; advanced rows hide behind a "+ N advanced · type to search"
footer until the user types a letter. /help walks the same registry, so
there's one source of truth.
Telemetry
* New ~/.reasonix/slash-usage.json counter (read-modify-write, atomic rename)
feeds suggestSlashCommands so frequent commands sort first within a prefix.
emitSlashInvoked is now wired to the events.jsonl sidecar.
Removals (commands)
* /models, /keys, /resume, /semantic — redundant with picker / /help / /doctor.
* /clear merged into /new (now an alias) — the visual-only clear was the most
common confusion source ("why does /clear keep my context?").
* /effort, /rename, /forget, /apply-plan, /think, /tool, /mcp browse — second
pass; either covered by other UI (sessions picker has rename/delete; preset
locks effort) or self-described as fallback / debug.
Removals (features)
* /harvest and the Pillar-2 plan-state extractor (src/harvest.ts).
* /branch and the parallel-sample selector (src/consistency.ts,
src/loop/branch.ts). Streaming/branching coupling, BranchCard,
branch_start/progress/done events, transcript planState/harvestedTurns,
--harvest/--branch CLI flags, all gone.
* benchmarks/harvest/ deleted; ARCHITECTURE.md collapsed from four pillars
to three; README + zh-CN + dashboard/PARITY updated.
i18n
* Cleared dead keys for every removed command (handlers.basic.helpHelp..helpExit,
keys*, semantic, resume*, models*, harvest*, branch*, effort*, think*, tool*,
apply-plan*, slash.harvest, slash.branch, ui.harvest*, ui.branch*).
Tests: 138 files / 2192 tests pass. Public API drops harvest, runBranches,
TypedPlanState, BranchSummary, etc.; consumers using those break intentionally.
* ci: drop harvest-bench dry-run step
Follows the harvest feature removal — benchmarks/harvest/ no longer exists,
so the CI step was breaking on ERR_MODULE_NOT_FOUND. τ-bench dry-run stays.
Configurable API URL / key / model / request body for embeddings, replacing the Ollama-only setup. Adds a provider abstraction in src/index/semantic/embedding.ts, index identity check + abort wiring through the builder, API-key redaction in dashboard/status output, and en-US + zh-CN strings for the new provider UI.
Most handler files were already 80%+ i18n'd from prior work, but
four files had drift:
- web-search-engine.ts — 0 t() calls, the entire help text plus
switch confirmation was hardcoded English. Whole new
handlers.webSearchEngine namespace (~12 keys).
- mcp.ts — 5 hardcoded usage / unknown-server / "(none)" /
reconnect-not-wired strings; added under handlers.mcp.
- plans.ts — the archive row template ("✓ {when} {N} steps · …"),
"complete" verb, and the /stop abort line. Added under
handlers.plans.
- semantic.ts — code-mode-only refusal + "checking…" status.
Added under handlers.semantic. Note this file uses two t()
instances side-by-side — the local @/index/semantic/i18n one
stays for the existing slashHeader/slashEnabled keys, and the
main @/i18n/index t (aliased as tMain) is added for the two new
strings.
zh-CN translations included for all ~22 new keys.
Test plan: full suite 2301 pass, tsc + biome clean.
Two patterns rolled into one PR:
1. Wire seven existing ui.* keys that had been defined in EN.ts /
zh-CN.ts but never actually called: ephemeralSession,
resumedSession, newSession, restoredEdits, resumedPlan,
tipEditBindings, dashboardAutoStartFailed. The keys had drifted
into dead code — same pattern that bit the loop.* namespace
before #445.
2. New app.* namespace (~24 keys) covering every other hardcoded
user-facing string in App.tsx:
- walk cancel (with / without remaining count)
- edit-mode cycle (review / auto / yolo)
- reject / auto-approve / flip-to-auto messages
- dashboard stopped, /restore code-mode-only
- hash-memory note (with translated scope + verb)
- bash-mode + memory-write failures
- hook headers (UserPromptSubmit, Stop)
- @mentions / @url expansion + failure
- shell confirm (deny / always-allow / running / starting)
- checkpoint saved
- plan continue / stop / revise
zh-CN translations for all 31 new keys.
Test plan: full suite 2301 pass, tsc + biome clean.
Two small follow-on batches after #445:
1. hooks.formatHookOutcomeMessage — was hardcoded
\`hook \${tag} \\`\${cmd}\\` \${decision}\${truncTag}\`. Pulls
the structural words (\"hook\", decision verb, \" (output truncated
at 256KB)\") into a new \`hooks.*\` namespace. The technical bits
(tag, cmd) stay verbatim — they're identifiers, not prose.
2. loop/force-summary.ts — three user-visible strings:
- \"summarizing what was gathered…\" (status during summary call)
- the fallback when the model emits hallucinated tool-call markup
instead of prose
- the error template when the fallback summary itself crashes
New \`summary.*\` namespace covers all three. zh-CN translations included.
Decision verbs (block / warn / timeout / error) are translated via a
small \`hooks.decision\${Capitalize}\` lookup so the formatter still
takes \`outcome.decision\` (the typed enum) as input.
Test plan: full suite 2301 pass; tsc + biome clean.
Yields like 'session budget exhausted', 'aborted at iter X/Y',
'preflight: request ~X/Y tokens', and the post-turn fold/forcing-
summary status lines were all hardcoded English. The loop.* i18n
namespace had 7 keys defined but never wired — placeholders from a
previous attempt that drifted away from the actual call sites.
This PR replaces the dead namespace with 20 keys that match the
actual yield shapes, wires t() at every site, and adds zh-CN
translations.
Categories covered:
- budget (exhausted / 80% warning)
- /pro armed
- aborted-at-iter / tool-budget-warning
- preflight (status + folded / no-fold-left)
- escalation (flash → pro / auto-escalation)
- storm-broken (stuck retry loop / suppressed-N-times)
- history compaction (status + folded / aggressively-folded)
- forcing summary (context-guard exit)
Behavior preserved: tests pin runtime to EN, so existing assertions
on the English text still pass. The dead loop.* keys (budgetWarning,
budgetRefusal, contextWarning, escalationWarning, toolFailure,
interrupted, loopStopped) had zero callers across src/ and tests/
and are removed as part of the namespace cleanup.
formatLoopError, reasonPrefixFor, and errorLabelFor were all
hardcoded English. A Chinese user hitting a 503 / 401 / context
overflow saw raw English (and on top of that, the new 5xx outage
notice from #440 was also English).
Move the strings to a new errors.* i18n namespace covering:
- context overflow (with V4/legacy limit mention)
- 401 auth / 402 balance / 422 param / 400 bad request
- 5xx head + reachable / unreachable / two action variants
- reason prefix and label for budget/aborted/context-guard/stuck
- "(no message)" fallback for empty error bodies
zh-CN translations included. Existing tests still cover EN (vitest
setupFile pins runtime to EN); two new tests flip to zh-CN to confirm
runtime switch actually translates.
Stacked on #440 — merge that first.
* fix(loop): friendly DeepSeek 5xx error with reachability probe
Raw `DeepSeek 503: <body>` was bubbling straight to the UI. Users on
flaky DS days couldn't tell if it was DS-side (their service was
overloaded) or Reasonix-side (we crashed). The header comment in
loop/errors.ts even claimed retry.ts swallowed all 5xx — but retry.ts
returns the last response instead of swallowing, so 5xx did reach the
formatter and just fell through to a passthrough branch.
Now formatLoopError takes an optional probe result. The catch in
step() detects 5xx, fires a 1.5s `/user/balance` probe, and passes
the result back. Three message variants:
- no probe → DS-side outage notice + retry hints
- probe reachable → "main API answered, /chat/completions failing"
- probe down → "DS unreachable from your network — check net"
All three include "this is a DeepSeek-side problem, not Reasonix" and
a status-page link so users know where to look.
* test: avoid CodeQL js/regex/missing-regexp-anchor on URL substring match
Use toContain('status.deepseek.com') instead of /status\.deepseek\.com/
— same assertion semantics, dodges CodeQL's high-severity false positive
on unanchored URL regex.
Plans whose completionRatio is 0 (submitted but no steps marked
complete yet) showed a hardcoded English "idle" pill — surrounding
"active" / "done" pills already used t().
Add plans.idle to en.ts ("idle") and zh-CN.ts ("未开始"), and route
the idle branch of statusPill() through t().
Two related fixes for non-English first-runs:
1. Add a language step at the very start of the setup wizard.
Cursor defaults to detectSystemLanguage() result. Selection saves
immediately, so all later wizard steps render in the chosen
language. Re-runs (`reasonix setup`) start there too — cursor
defaults to currently saved language so Enter is a no-op for
users who don't want to change it.
2. Localize every hardcoded string in the wizard via a new wizard.*
i18n namespace (~30 keys, EN + zh-CN). Previously a Chinese user
who hit /language partway through never saw zh-CN copy because
the wizard rendered raw English. Now language → applies → review
step renders in zh-CN.
Why this matters: Intl.DateTimeFormat().resolvedOptions().locale
isn't always correct (terminal env strips LANG, CI returns "C", etc.),
and the prior workflow only let users discover /language *after*
finishing setup in English.
Tests: ink-testing-library renders the Wizard and confirms the
language step is shown first with both options visible, in EN and
zh-CN. wizard.test.ts → wizard.test.tsx (now contains JSX).
Closing audit of the #369 split: every slash command tagged with how
the dashboard handles it (panel / chat-box / tui-only).
Findings after C + D:
* ~20 slashes have a dedicated panel or modal — Settings (presets,
effort, model, /pro, budget gauge, loop control, language), MCP,
Permissions, Hooks, Skills, Memory, Plans, Sessions, Usage, plus
the C-bucket pickers (SessionPicker, CheckpointPicker, MCP
marketplace, plan replay viewer).
* ~38 slashes work as-is via the chat box — short text outputs
(/help, /keys, /status, /cost, /context, /think, /retry, /compact,
/update, /doctor, /init, /semantic, …) plus admin / code-mode
niches (/walk-around, /resource, /prompt, …). No structured-output
gaps remain after C + D — the long-standing Memory / Permissions /
Hooks / Skills / Plans / Usage panels already cover every command
whose payload warranted a dedicated UI.
* Stays TUI-only by design: /exit (no live process to kill from web),
the raw keyboard shortcuts (Esc / Shift+Tab / Ctrl-L / Ctrl-O / u
/ space).
Bucket A and B turned out empty after the C/D work — no commands
need a chat-box rendering tweak, and no commands need a new
structured-output panel. PARITY.md is the source of truth going
forward; add a row when a new slash lands.
This wraps up #369 — the umbrella issue closes with this PR.
Final stage of #428. Adds a Loop section to SettingsPanel for the
auto-resubmit timer.
Design — two states from one component:
* Idle → 6 quick interval buttons (30s / 1m / 5m / 15m / 1h / 6h) plus
a custom field with s/m/h unit selector, a multi-line prompt
textarea, and a Start button. Cost hint reads "each iteration costs
~$X.XXXX (last turn)" pulled from /api/overview stats so the user
knows what an unattended overnight loop will run.
* Running → live countdown ("fires in 1m 24s"), iter counter, the
prompt verbatim (max 120px scroll for long prompts), and a Stop
button.
Implementation:
* dashboard/src/lib/loop-control.ts — pure helpers: INTERVAL_PRESETS_MS
table, parseCustomInterval (s/m/h → ms with 5s..6h clamp),
formatRemaining (5m 12s / 2h 45m / 0s for races past zero).
* SettingsPanel polls /api/loop/status every 5s; a separate 1s tick
interpolates the countdown locally between syncs (clamps to 0 if
the next-fire moment passes between polls).
* Page-reload mid-loop reads /api/loop/status and re-renders the
running panel from server state — no double-start risk because the
Start button only renders in idle state.
Wraps up bucket D — all four targeted slashes (/pro, /budget, /model,
/loop) are now panel-driven.
Fourth stage of #428. Replaces the read-only active-model code line
with a select driven by /api/models, plus an inline pricing line.
* New /api/models GET — returns the cached model catalog
(string[] | null), the live current model, and the DEEPSEEK_PRICING
table so the SPA can render input/output USD per 1M tok without a
second source.
* DashboardContext.getModels callback; App.tsx ref-mirrors useSessionInfo's
models so the dashboard server (frozen at boot time) sees fresh
catalog without re-mint.
* SettingsPanel ModelRow component: graceful fallback to the existing
read-only display when the catalog is null/empty (network failure
or in-flight). Live model is always selectable, even if the catalog
hasn't echoed it yet (preset overrides, custom IDs).
* Save flows through the existing D-1 applyModelLive path — same as
/model <id> slash.
Closes#432
Third stage of #428. Replaces a typed-input form with a state-driven
budget gauge that reads at a glance and turns the common bumps into
single clicks.
Design:
* Off → quick-cap row ($1 / $5 / $10 / $25 / $50) + custom field. No
number to type for the common case.
* Running (<80%) → spend / cap progress bar + bump suggestions
(1.5× / 2× / 4× current cap, snapped to a "nice" round number per
size bucket) + Clear.
* Approaching (≥80%) → amber tone + "loop will refuse past 100%" line
+ bump suggestions promoted to primary buttons.
* Exhausted (≥100%) → red tone + "next turn refused" line + same
bumps.
Implementation:
* dashboard/src/lib/budget.ts — pure helpers: BudgetState union,
deriveBudgetState, bumpSuggestions, budgetTone, QUICK_CAPS_USD.
niceUp() subtracts an FP epsilon before ceil so 0.4 × 1.5 doesn't
bump 0.6 to 0.7.
* SettingsPanel: BudgetSection consumes derived state and renders
off / running / warn / exhausted variants. Same gauge shape across
all three live states (just colour + helper text differ).
* Overview cockpit: budgetKpi reuses deriveBudgetState + budgetTone
so threshold logic lives in one place.
* /api/settings GET adds sessionSpendUsd from ctx.getStats so the
panel renders without a second /overview round-trip.
* 12 new unit tests for the derivation and bump rounding.
* feat(dashboard): server surface for /pro / /budget / /model / /loop (#429)
First stage of #428 (bucket-D of #369). Server-side plumbing for the
slash-only knobs the web should drive directly: /pro arming, /budget,
/model, and /loop. No SPA UI yet — D-2..D-5 each ship a panel section
against this surface.
* /api/settings GET exposes proNext / budgetUsd / model from live
loop state alongside the existing persisted fields.
* /api/settings POST validates and routes each new field to the
matching ctx.*Live callback. budgetUsd accepts null for "off".
* /api/loop/{status,start,stop} (new endpoint) drives the auto-resubmit
timer the same way the /loop slash does. start enforces 5s..6h range
and a non-empty prompt.
* DashboardContext gets matching callbacks: applyModelLive,
setProNextLive, setBudgetUsdLive, getLoopRunStatus, startAutoLoop,
stopAutoLoop.
* App.tsx wires each callback against existing live methods on
CacheFirstLoop and the useLoopMode hook. No new state.
/harvest and /branch are deletion-bound features and are deliberately
out of scope here — see #428 follow-up.
Closes#429
* feat(dashboard): compute panel section — /pro one-shot (#430)
Second stage of #428. Adds a Compute section to SettingsPanel for the
/pro one-shot toggle.
* Single-row section under the existing Defaults block: button toggles
arm / disarm — same path as the slash; auto-disarms after the next
turn fires.
* Section header lives even with one row so D-4 (model picker) and any
future compute knobs cluster here naturally.
* i18n: en + zh-CN strings for the section + row + helper note.
/harvest and /branch were originally bundled into this stage but
dropped — both are deletion-bound features.
Closes#430
First stage of #428 (bucket-D of #369). Server-side plumbing for the
slash-only knobs the web should drive directly: /pro arming, /budget,
/model, and /loop. No SPA UI yet — D-2..D-5 each ship a panel section
against this surface.
* /api/settings GET exposes proNext / budgetUsd / model from live
loop state alongside the existing persisted fields.
* /api/settings POST validates and routes each new field to the
matching ctx.*Live callback. budgetUsd accepts null for "off".
* /api/loop/{status,start,stop} (new endpoint) drives the auto-resubmit
timer the same way the /loop slash does. start enforces 5s..6h range
and a non-empty prompt.
* DashboardContext gets matching callbacks: applyModelLive,
setProNextLive, setBudgetUsdLive, getLoopRunStatus, startAutoLoop,
stopAutoLoop.
* App.tsx wires each callback against existing live methods on
CacheFirstLoop and the useLoopMode hook. No new state.
/harvest and /branch are deletion-bound features and are deliberately
out of scope here — see #428 follow-up.
Closes#429
Final stage of #416. /replay [N] now broadcasts a read-only viewer
modal to the web dashboard so the plan archive (summary + steps +
markdown body) is visible alongside the existing TUI scrollback card.
* New `viewer` member on the ActiveModal discriminated union — sibling
to `picker`, but read-only: only `close` flows back through
/api/modal/resolve. Splitting them keeps the picker schema clean
rather than carrying empty `actions: []` on every viewer payload.
* useViewerBroadcast helper alongside usePickerBroadcast.
* App.tsx intercepts result.replayPlan, packages a snapshot
(title with #idx/total · relative time, structured steps with
done/queued status, markdown body, archive basename as meta), and
feeds it to the hook. The existing log.showPlan call is unchanged
so the TUI scrollback card still renders.
* SPA ViewerModal renders the steps as a list (✓ for done, · for
queued) plus the markdown body and a single Close button.
* Server tests cover the dispatcher: close happy path, rejection of
non-close actions, 503 when the resolver is not wired.
Wraps up bucket-C of #369. All five originally TUI-only pickers
(/resume, /restore, /mcp browse) plus the read-only /replay viewer
are now drivable from the web with no TUI keyboard required.
* feat(dashboard): picker modal kind for web parity (#417)
First stage of #416 (bucket-C of #369). Lays the protocol primitives so
the five existing TUI-only pickers (SessionPicker, MCP marketplace,
checkpoint restore, plan replay, edit walkthrough) can be driven from
the web in C-2..C-5 without redoing transport work.
* New `picker` member on the `ActiveModal` discriminated union plus
`PickerResolution` / `PickerAction` / `PickerItem` types.
* `POST /api/modal/resolve` dispatches `picker` actions: pick / delete /
rename / new / install / uninstall / load-more / refine / cancel.
`refine` and `load-more` keep the picker open so the TUI's filter
state stays in lockstep across surfaces.
* Generic `PickerModal` SPA component with filter input, scrollable
rows, action buttons gated on `modal.actions`, and rename / new
inline forms.
* `usePickerBroadcast` hook + App.tsx-owned resolver / snapshot refs so
C-2..C-5 picker components only need the hook to participate.
No picker is migrated yet — that arrives in C-2 (#418).
* feat(dashboard): wire SessionPicker through picker modal protocol (#418)
Second stage of #416. SessionPicker (the simplest existing TUI picker —
no pagination, no async, ~5 actions) now broadcasts modal-up snapshots
to the web dashboard and resolves pick / delete / rename / new / cancel
from /api/modal/resolve.
* SessionPicker.tsx accepts an optional `pickerPorts` prop bundle and
feeds usePickerBroadcast a snapshot mapped from the existing sessions
list (id=name, badge=branch, meta=turns/cost).
* App.tsx wires a memoized pickerPorts (broadcast + resolver/snapshot
refs from C-1) and passes it to the picker mount.
* TUI keystroke handling unchanged — broadcast is purely additive.
Validates the C-1 (#417) protocol foundation against a real picker with
no dashboard-side regressions.
* feat(dashboard): checkpoint picker for /restore (#419)
Third stage of #416. Bare /restore (no name argument) now opens an
interactive CheckpointPicker — covering both the TUI side (the command
was text-only before) and the web dashboard via the picker modal
protocol from C-1.
* New CheckpointPicker.tsx mirrors SessionPicker shape: arrow-key
navigation, ⏎ to restore, [d] to forget, esc to quit. Rows show
short id + name + relative age + file count / size.
* /restore handler returns openCheckpointPicker:true when called with
no argument; /restore <name|id> still resolves directly to keep the
one-shot path working.
* App.tsx mounts the picker, gates hotkeys behind it, and routes
outcome → restoreCheckpoint / deleteCheckpoint with a summary line
on success.
* usePickerBroadcast wires the same modal-up/down + resolvePicker
pipeline as C-2; web sees pick / delete / cancel actions.
* feat(dashboard): wire McpMarketplace through picker protocol (#420)
Fourth stage of #416. /mcp browse now broadcasts a picker snapshot to
the web dashboard with installed/source-tagged badges, popularity
meta, and the full action set: install / uninstall / refine /
load-more / cancel.
* installOrToggle split into doInstall + doUninstall so the web's
explicit `install` / `uninstall` actions don't accidentally toggle
on the wrong button (TUI Enter still toggles for keyboard
ergonomics).
* Snapshot builder extracted to a pure
`buildMarketplacePickerSnapshot` so the entry-to-item mapping can
be unit-tested without mounting Ink + the registry network call.
* refine and load-more keep the picker open (per C-1 design); cancel
closes it via the existing onClose hook.
* hasMore wired from `state.handle.cache.pagination.nextCursor` so
the dashboard's "Load more" button only shows when more pages exist.
* McpHub forwards pickerPorts from App.tsx to the marketplace tab;
the live tab is unchanged.
* feat(dashboard): picker modal kind for web parity (#417)
First stage of #416 (bucket-C of #369). Lays the protocol primitives so
the five existing TUI-only pickers (SessionPicker, MCP marketplace,
checkpoint restore, plan replay, edit walkthrough) can be driven from
the web in C-2..C-5 without redoing transport work.
* New `picker` member on the `ActiveModal` discriminated union plus
`PickerResolution` / `PickerAction` / `PickerItem` types.
* `POST /api/modal/resolve` dispatches `picker` actions: pick / delete /
rename / new / install / uninstall / load-more / refine / cancel.
`refine` and `load-more` keep the picker open so the TUI's filter
state stays in lockstep across surfaces.
* Generic `PickerModal` SPA component with filter input, scrollable
rows, action buttons gated on `modal.actions`, and rename / new
inline forms.
* `usePickerBroadcast` hook + App.tsx-owned resolver / snapshot refs so
C-2..C-5 picker components only need the hook to participate.
No picker is migrated yet — that arrives in C-2 (#418).
* feat(dashboard): wire SessionPicker through picker modal protocol (#418)
Second stage of #416. SessionPicker (the simplest existing TUI picker —
no pagination, no async, ~5 actions) now broadcasts modal-up snapshots
to the web dashboard and resolves pick / delete / rename / new / cancel
from /api/modal/resolve.
* SessionPicker.tsx accepts an optional `pickerPorts` prop bundle and
feeds usePickerBroadcast a snapshot mapped from the existing sessions
list (id=name, badge=branch, meta=turns/cost).
* App.tsx wires a memoized pickerPorts (broadcast + resolver/snapshot
refs from C-1) and passes it to the picker mount.
* TUI keystroke handling unchanged — broadcast is purely additive.
Validates the C-1 (#417) protocol foundation against a real picker with
no dashboard-side regressions.
* feat(dashboard): checkpoint picker for /restore (#419)
Third stage of #416. Bare /restore (no name argument) now opens an
interactive CheckpointPicker — covering both the TUI side (the command
was text-only before) and the web dashboard via the picker modal
protocol from C-1.
* New CheckpointPicker.tsx mirrors SessionPicker shape: arrow-key
navigation, ⏎ to restore, [d] to forget, esc to quit. Rows show
short id + name + relative age + file count / size.
* /restore handler returns openCheckpointPicker:true when called with
no argument; /restore <name|id> still resolves directly to keep the
one-shot path working.
* App.tsx mounts the picker, gates hotkeys behind it, and routes
outcome → restoreCheckpoint / deleteCheckpoint with a summary line
on success.
* usePickerBroadcast wires the same modal-up/down + resolvePicker
pipeline as C-2; web sees pick / delete / cancel actions.
* feat(dashboard): picker modal kind for web parity (#417)
First stage of #416 (bucket-C of #369). Lays the protocol primitives so
the five existing TUI-only pickers (SessionPicker, MCP marketplace,
checkpoint restore, plan replay, edit walkthrough) can be driven from
the web in C-2..C-5 without redoing transport work.
* New `picker` member on the `ActiveModal` discriminated union plus
`PickerResolution` / `PickerAction` / `PickerItem` types.
* `POST /api/modal/resolve` dispatches `picker` actions: pick / delete /
rename / new / install / uninstall / load-more / refine / cancel.
`refine` and `load-more` keep the picker open so the TUI's filter
state stays in lockstep across surfaces.
* Generic `PickerModal` SPA component with filter input, scrollable
rows, action buttons gated on `modal.actions`, and rename / new
inline forms.
* `usePickerBroadcast` hook + App.tsx-owned resolver / snapshot refs so
C-2..C-5 picker components only need the hook to participate.
No picker is migrated yet — that arrives in C-2 (#418).
* feat(dashboard): wire SessionPicker through picker modal protocol (#418)
Second stage of #416. SessionPicker (the simplest existing TUI picker —
no pagination, no async, ~5 actions) now broadcasts modal-up snapshots
to the web dashboard and resolves pick / delete / rename / new / cancel
from /api/modal/resolve.
* SessionPicker.tsx accepts an optional `pickerPorts` prop bundle and
feeds usePickerBroadcast a snapshot mapped from the existing sessions
list (id=name, badge=branch, meta=turns/cost).
* App.tsx wires a memoized pickerPorts (broadcast + resolver/snapshot
refs from C-1) and passes it to the picker mount.
* TUI keystroke handling unchanged — broadcast is purely additive.
Validates the C-1 (#417) protocol foundation against a real picker with
no dashboard-side regressions.
First stage of #416 (bucket-C of #369). Lays the protocol primitives so
the five existing TUI-only pickers (SessionPicker, MCP marketplace,
checkpoint restore, plan replay, edit walkthrough) can be driven from
the web in C-2..C-5 without redoing transport work.
* New `picker` member on the `ActiveModal` discriminated union plus
`PickerResolution` / `PickerAction` / `PickerItem` types.
* `POST /api/modal/resolve` dispatches `picker` actions: pick / delete /
rename / new / install / uninstall / load-more / refine / cancel.
`refine` and `load-more` keep the picker open so the TUI's filter
state stays in lockstep across surfaces.
* Generic `PickerModal` SPA component with filter input, scrollable
rows, action buttons gated on `modal.actions`, and rename / new
inline forms.
* `usePickerBroadcast` hook + App.tsx-owned resolver / snapshot refs so
C-2..C-5 picker components only need the hook to participate.
No picker is migrated yet — that arrives in C-2 (#418).
Flicker reports keep landing without the one piece of info that
discriminates the bug — the terminal host (VSCode/Cursor xterm.js vs
standalone Windows Terminal / iTerm2 / etc.). The shell field on the
generic bug template was the wrong axis. New template asks for host +
version, env vars (TERM_PROGRAM/VSCODE_INJECTION/WT_SESSION), and ships
copy-paste diagnostic snippets so users do not have to know how to
introspect their own terminal.
Two stacked rules + five-segment status row + per-card breathing room
made history scroll read as scattered fragments. Tighten three things:
- Settled cards drop the marginTop the active form keeps, so scrollback
collapses to flat lines instead of one blank between every card.
- ModeStatusBar drops its dashed rule; StatusRow's solid rule already
separates the chat from bottom chrome.
- StatusRow drops session-cost + wallet segments (StatsPanel and
UsageCard already surface those); only turn cost + cache stay.
- Settled CardHeader filters faint string meta (1.2KB / 2.34s / exit N
on OK cards) and drops the right slot so spinners don't linger in
scrollback. Colored badges (rejected, retry) still render.
ui-status-row-balance reduced to the cells StatusRow now renders;
wallet/session currency coverage stays in ui-stats-panel-currency
and ui-usage-card-balance.
The Install block dropped readers at `npx reasonix code` with no
mention of the global-install path, and the README never named the
five subcommands a new user actually has to choose from. The website
already has a CLI panel but the section had no anchor, so the README
couldn't link to it.
- Name `npx` as the recommended path; point users at `reasonix update`
if they want the global install.
- Add a five-row cheatsheet (code / chat / run / doctor / update) so
newcomers don't have to guess. Defer the long tail (replay / diff /
events / stats / index / mcp / prune-sessions) to `--help` and the
CLI panel on the website.
- Mirror in zh-CN.
- Add `id="cli"` to the website's CLI section so the README link
resolves.
Bracketed-paste content was always converted to a `[paste #N · …]`
sentinel chip, even when the user pasted a single word or a number.
That made the composer feel hostile to common one-shot paste usage —
copying an identifier or a URL out of another window and dropping it
mid-sentence shouldn't leave a chip in the buffer.
Inline the content verbatim when it has no newline AND fits under
INLINE_PASTE_THRESHOLD (200 chars); fall back to the sentinel chip
for anything longer or multi-line. The model still receives the full
paste text either way — this is display-only.
projects[] is keyed by absolute rootDir, so on Windows two sessions
that resolve the same physical directory to different drive-letter or
component casing (PowerShell's `F:\Reasonix` vs bash/MINGW's
`f:\reasonix`) miss the persisted "always allow" entry from the prior
session and re-prompt every turn.
Add findProjectKey() that prefers the exact match and, on win32,
falls back to a case-insensitive scan. Use it in load / add / remove
/ clear so any-cased rootDir consolidates onto the existing key
instead of forking a duplicate. Non-Windows lookups remain
case-sensitive — Linux paths really are.
Two paths bypassed the cards' model snapshot:
- Dashboard preset change (POST /settings → applyPresetLive) reconfigured
the loop but never dispatched session.model.change, so subsequent
reasoning/streaming cards still rendered the old model badge.
- /pro consumed a single-turn escalation without telling the cards, so
the armed turn ran on v4-pro but the badge stayed on the base model.
applyPresetLive now dispatches session.model.change. reasoning.start /
streaming.start carry an optional model id; the loop's currentCallModel
getter feeds it through TurnTranslator.flushBuffers so the badge tracks
the model that actually produced the output.
Three contributor-led follow-ups: storm guard exempts safe inspector
reads (#388 by @ctharvey), wait_for_job replaces polling loops with
one blocking call (#390 by @ctharvey), and /skill new finally
provides the missing scaffold for user skills (#394).
* feat(skills): /skill new scaffolds a stub + README walkthrough (#366)
User feedback: wanted to install a frontend-writing skill, "no
discoverable entry point". The /skill list empty state told users
WHERE skills live but not HOW to author one — and there's no remote
registry to install from.
Adds the missing creation step:
- /skill new <name> → writes <project>/.reasonix/skills/<name>.md
- /skill new <name> --global → writes ~/.reasonix/skills/<name>.md
The stub carries the minimal frontmatter (name + description) plus
a comment block listing the optional knobs (runAs, allowed-tools,
model). Refuses to overwrite existing files; rejects invalid names
via the existing isValidSkillName regex.
Empty /skill list now surfaces the new scaffold + an explicit "no
remote registry yet" line so users don't keep hunting for a
marketplace that doesn't exist. Catalog + README in EN + zh-CN
gain the "author your first skill" path. The /skill list footer
mentions /skill new alongside show / run.
* fix(skills): atomic create with wx flag — close TOCTOU race CodeQL flagged
CodeQL flagged the existsSync→writeFileSync sequence as a potential
file-system race. Switch to writeFileSync with `flag: "wx"` so the
existence check IS the atomic write — if a parallel process landed
the file between our check and write, EEXIST surfaces and we report
the conflict instead of silently overwriting.
Keep the folder-form pre-check for a cleaner error message when the
collision is on the dir-style skill (`<name>/SKILL.md`).
Sweep of the 0.30.2 / 0.30.3 launch-day bug + onboarding queue:
resume now restores cache+context+cost (#364), model pill follows
/model + /preset switches (#372), bare /model opens an interactive
picker (#371), three more Shift+Tab encodings for PowerShell /
modifyOtherKeys / Kitty (#373), defensive stdin drain on exit kills
the fish/bash escape-leak (#365), and --dir / pinned workspace get
surfaced in the welcome banner, /status, sandbox errors, and the
README (#370).
Reporter saw `^[]11;rgb:...^[\^[[33;1R^[[?62;1;4c` printed by fish /
bash right after exiting reasonix. Those bytes are RESPONSES — OSC 11
bg-color, CPR cursor-position, DA1 device-attributes — sent by the
terminal in reply to queries the runtime / a dep emitted during
session startup. The dist bundle has none of those query bytes
itself, so the source is bun's tty feature-detection path or a
transitive dep doing color-scheme detection.
Whoever sent them, the responses sat in stdin's queue until reasonix
exited. The parent shell then read them and rendered the bytes as
input.
Add `drainTtyResponses(50ms)` and call it in chat.tsx's exit finally,
after `runtime.closeAll()`. Best-effort: sets raw mode, reads-and-
discards anything still queued for 50ms, restores cooked. No-op when
stdin isn't a TTY or raw mode isn't available.
0.30.3's alt-screen default is the upstream mitigation (DECSET 1049
flushes the input queue on most terminals); this is the program-side
mitigation that's independent of which terminal the user is in.
User feedback (multiple data points): beginners hit the default
cwd-scoped behavior and conclude Reasonix can't read folders other
than where they launched it. The capability already exists via
`reasonix code --dir <path>`, but nothing in the UI tells you so
until you read --help.
Three onboarding surfaces now make it discoverable:
- WelcomeBanner shows a "▸ workspace · /path (relaunch with --dir
<path> to switch)" line in code mode. Visible only on the empty
state, so it doesn't survive past the first turn.
- `/status` includes a workspace line:
workspace /path · pinned at launch (relaunch with --dir <path>
to switch)
- The filesystem sandbox-escape error now points the user at --dir
instead of just dropping a raw "path escapes sandbox root":
path escapes sandbox root (X): Y — workspace is pinned at
launch; quit and relaunch with `reasonix code --dir <path>` to
work in a different folder
Plus a Getting Started callout in both READMEs explaining --dir and
why mid-session switching isn't a thing (message log + memory paths
get tangled with stale roots, so the design pins at launch).
No new slash command, no /cwd. The agent's system prompt already
says mid-session switching was removed by design.
`/model <id>` required typing the model id by hand and `/models` was
a separate read-only listing. New users had no obvious way to switch
without prior knowledge of the catalog.
Bare `/model` now opens a modal picker that mirrors SessionPicker's
shape: arrow-key list, ⏎ confirm, [r] refresh the API catalog, esc
cancel, current model marked. The list seeds from the live DeepSeek
catalog (`useSessionInfo` already fetches it on mount); when the
catalog hasn't loaded yet the picker falls back to the four known
DeepSeek ids so it's never empty on first open. The current model
is always included even when the API didn't return it.
Confirming a row routes through `loop.configure({ model })` AND the
`session.model.change` event added in #372 — so the badge on the
NEXT card pill reflects the new selection.
`/model <id>` typed entry continues to work for power users.
Recognized only the bare xterm `\x1b[Z` back-tab. PowerShell 7.x on
some Windows hosts emits the modifier-encoded `\x1b[1;2Z`; modern
Windows Terminal in modifyOtherKeys mode (which we enable on
startup) emits `\x1b[27;2;9~`; the Kitty keyboard envelope is
`\x1b[9;2u`. None of these matched, so the edit-mode cycle was
silently dropped on PowerShell.
Add all three variants to `stdin-reader.ts` CSI_TAIL_MAP and to the
Ink-fallback `key-normalize.ts` recovery table. `/mode` slash command
remains as a typed fallback for any future terminal that emits a
form we haven't seen yet.
`state.session.model` was set once in `initialState()` and never
mutated. `/model <id>` and `/preset {auto,flash,pro}` only routed
through `loop.configure({ model })`, never into the agent store —
so the next `streaming.start` / `reasoning.start` / "thinking · X"
card snapshotted the launch-time model id, even when the model that
actually answered the turn was different.
Add a typed `session.model.change` event the model handlers dispatch
through `ctx.dispatch`. Reducer mutates `state.session.model` (with
referential identity preserved when the id is unchanged) and the
existing snapshot logic in `makeReasoningCard` / `makeStreamingCard`
picks up the new value automatically. Cards already opened keep
their captured model — that snapshot is intentional so mid-turn
escalation doesn't relabel completed reasoning.
`SessionMeta` only carried `totalCostUsd` and `turnCount`, so on every
resume `/status` showed:
- 0 context — `lastPromptTokens` came from `turns[0]?.usage`, and
`turns` is empty before the first live turn fires
- 0% cache hit — `aggregateCacheHitRatio` summed `turns[]` only
The next API call would still read the cached prefix and answer
correctly (turn 1 in the user's log shows 366,976 / 367,085 cache
hits), but the panel reported "no context" until that call landed.
Persist the missing fields after each turn (`patchSessionMeta`) and
seed them on resume (`stats.seedCarryover`). `aggregateCacheHitRatio`
and `summary().lastPromptTokens` now fall through to the carryover
when no live turn has run yet.
* feat(ui): row-precision virtual scroll on Ink 7 + React 19
Bump ink 5.2→7.0.2 + react 18.3→19.2; drop react-reconciler/yoga-layout.
Retire src/renderer/ (cell-diff + ink-compat shim) — Ink 7 ships native
equivalents for every motivation: alternateScreen, useAnimation,
useWindowSize, useBoxMetrics, synchronized output, incrementalRendering.
Default to alt-screen so the resize-ghost / scroll-yank class of bugs
disappears. `--no-alt-screen` opts back into scrollback for users who
need chat output preserved in shell history on exit.
Row-precision virtual scroll with reading mode: scrolling away from
bottom hides PromptInput and replaces it with a "📖 reading history —
End / PgDn to return" indicator. PgUp/PgDn/End owned by App; ↑/↓ on
an empty buffer hand off to chat scroll via PromptInput; App takes ↑/↓
directly when busy or in reading mode (PromptInput can't process them).
Wheel events translate to ↑/↓ in raw mode, so the same paths cover wheel.
Ctrl+P/N keeps the prompt-history binding (wheel-immune).
Drop <Static> — incompatible with alt-screen (no scrollback to shelter
committed cards across resize-reflow). React.memo on CardRenderer plus
the reducer's reference-stable card array skips reconciler cost on
unchanged cards. CardStream renders all cards inside an overflow:hidden
Box; inner Box's marginTop=-scrollRows shifts content; useBoxMetrics
reports inner/outer heights so App can clamp scroll bounds.
CardStream.isSettled covers task / plan / subagent kinds. PromptInput's
useReserveRows quantizes to 4-row buckets so per-keystroke layout doesn't
churn. TickerProvider migrated to Ink 7's useAnimation. Modal-open
condition collapsed from 14 OR'd checks into one reused boolean.
Migrate inline tests (markdown, plan-confirm) off the cell-diff renderer
to ink-testing-library. Remove dead alt-screen.ts; strip stale comments
referencing removed scrollback-mode workarounds.
* test(ui): provide fake stdin for Ink 7 raw-mode check in CI
Ink 7 calls setRawMode on stdin during render(); CI's process.stdin
isn't a TTY so it throws "Raw mode is not supported". Pass a minimal
EventEmitter-based fake stdin (setRawMode no-op, isTTY=true) alongside
the existing fake stdout. Affects four tests that import render directly
from ink for in-process render-and-assert: ui-session-picker-currency,
ui-stats-panel-currency, ui-usage-card-balance, ui-status-row-balance.
* test(ui): extract makeFakeStdin/Stdout to shared tests/helpers/ink-stdio
The official @modelcontextprotocol/server-filesystem refuses to start
when its sandbox directory is missing and prints a raw Node stack
trace, leaving the user without an actionable next step.
- preflightStdioSpec validates every positional path arg before
spawn and throws a one-line error: "create it with: mkdir -p '<path>'"
- The first-run / reconfigure wizard now stat()s the directory the
user typed for filesystem MCP and offers Y/Enter to mkdir -p,
N/Esc to enter a different path.
Adds SearXNG as an alternative web_search engine, switchable via /search-engine slash command or ~/.reasonix/config.json. Mojeek stays the default — zero risk for existing users.
CLI shows session cost in the wallet's currency (¥ for CNY wallets,
$ for USD), but the dashboard always used `fmtUsd()` which prints
the raw stored USD with a `$`. CNY users saw `$0.5190` in the
dashboard for the same session that read `¥0.024` in the CLI — both
the symbol AND the magnitude diverged because no conversion happened.
- New `fmtCost(usd, currency, fractionDigits?)` helper in
`dashboard/src/lib/format.ts`. Mirrors the CLI's `formatCost()` —
CNY converts via `USD_TO_CNY = 7.2`, USD passes through, undefined
defaults to CNY.
- `overview.ts` current-session cost + cost-trend day average now
thread `c.balance?.currency` into `fmtCost()`.
- `chat.ts` SideRail cost / budget rows and ChatStatusBar
turn / session cost rows pull currency from `stats.balance[0]`.
- Existing `fmtUsd()` kept as-is for places where USD is intentional
(Claude-equivalent comparisons in usage.ts) — those stay USD because
Claude's API is USD-priced regardless of the user's wallet.
Pain point @dacec354 raised twice: while the model writes a long plan
or todo list, the streaming card only shows the last 4 lines, so the
content scrolls past before you can read it. And once a long reply
settles, you may want to fold it back down — but `<Static>` already
flushed the bytes to scrollback so that half can't be unwound.
This collapses both requests into one keystroke: `ctrl-o` toggles
"expanded" mode on the live streaming card. Expanded shows the last
60 visual lines (capped so the card can't swallow the whole viewport)
plus a `⋯ N earlier lines above` hint when content overflows.
Collapses back to the 4-line preview. Auto-resets to collapsed at the
end of every turn so each new reply starts compact.
The same `(LIVE)` constraint covers #337's fold-toggle ask: only
not-yet-committed cards are addressable. Settled cards live in Ink's
`<Static>` which writes terminal scrollback once, no take-backs.
The `expanded ⌃o` / `preview ⌃o` pill in the card header advertises
the keybind so users discover it without reading docs.
`splitCardStream` only treated the LAST card as live; everything before
it was committed to Ink's `<Static>`. When the model streamed reasoning
THEN content (or kicked off a tool card), the reasoning card was
no longer last — so it got frozen into `<Static>` while still
`streaming: true`. `reasoning.end` later set `streaming: false` on
the cards array, but `<Static>` doesn't re-render frozen items, so the
"reasoning…" header kept its spinner indefinitely.
Fix: live-vs-committed split now scans for the FIRST unsettled card
and keeps everything from there onward in the live tree. Cards only
move into `<Static>` once they're settled AND every earlier card is
too — preserving the in-order append contract `<Static>` requires.
`suppressLive` semantic preserved: still hides the trailing live card
when the modal owns the screen.
Two new regression tests cover the reasoning + streaming case (must
stay live) and the all-settled case (must commit in order).
Same bug shape as the StatusRow / UsageCard / StatsPanel set that #272
already fixed — `SessionPicker` was still doing
`¥${totalCostUsd * USD_TO_CNY}` so USD-wallet users saw ¥-formatted
costs in the session list.
- `SessionMeta` gains `balanceCurrency?: string`. App.tsx writes the
live wallet currency alongside `totalCostUsd` on each turn save, so
every persisted session knows what currency its cost is denominated
in.
- `SessionPicker` accepts a `walletCurrency` prop and falls back to
each row's `meta.balanceCurrency`. Prop wins (live value > stored).
In-app picker (`/sessions`) gets the live ref from App; pre-mount
picker in `chat.tsx` doesn't have a balance fetched yet, so it
relies on the stored per-session value.
- Cost rendering routes through the shared `formatCost()` helper that
the rest of the cost UI already uses.
- Regression test asserts USD wallet → `$0.05`, CNY wallet → `¥0.36`,
no-prop + stored-USD → `$0.05`, neither → unchanged `¥0.36`.
- StreamingCard renders a `42 t/s` pill in the live header and a
`1.2k tok · 42 t/s` summary on the settled card. Computed via the
bundled DeepSeek tokenizer; gated below 4 tokens / 500 ms so the
pill never shows obviously-bogus rates while the first chunk lands.
Re-renders piggyback on the slow tick so the rate keeps updating
even when chunks stall briefly.
- The auto-mode undo banner now accepts a `space` keystroke to pause
the 5-second countdown indefinitely. While paused the bar freezes
at the captured fraction, the badge swaps to "Ns · paused", and
pressing space again resumes from where it stopped. The hint row
on edit-mode entry mentions both `u` and `space`.
The `u` and `space` keybinds share the same modal-and-prompt-empty
gating, so neither steals input while the user is typing.
Aliasing `from "ink"` → ink-compat in the CLI bundle made every
TUI bug invisible to `npx tsx` repros and forced cell-diff regressions
onto users only. Issue #346 (ShellConfirm ghost rendering) was a pure
cell-diff bug; the cleanest fix is to remove the alias and let
production take real Ink the same way source mode does.
- tsup: drop the `ink` alias and `noExternal` for ink/ink-text-input;
bundle keeps `from "ink"` external
- package.json: ink + ink-text-input move to runtime dependencies
- markdown-view: switch the only `inkCompat.*` namespace user back to
`import { Box, Text } from "ink"`
- bundle-smoke: invert the alias assertion to expect ink stays external
useCursor() in PromptInput keeps its cell-diff import; without a
CursorContext provider it no-ops, so it's harmless under real Ink.
Anonymized DeepSeek dashboard from a real Reasonix user
(2026-05-01, used with permission): 435M input tokens, 99.82%
cache hit, ~$12/day on v4-flash vs ~$61 the same workload would
cost without the cache.
Lives at benchmarks/real-world-cache/ alongside an explanation of
the four mechanisms (ImmutablePrefix + AppendOnlyLog +
VolatileScratch + auto-compact) that produce the hit rate. README
gets a NOTE callout pointing at it — answers the recurring "isn't
this just DeepSeek's prefix cache?" pushback with concrete numbers
instead of a re-derived napkin.
Switch the X-axis branch of `moveTo()` from CUF (relative cursor right,
`\x1b[NC`) to CHA (absolute column, `\x1b[N+1G`). Y-axis stays on
CUU/CUD since we don't track absolute terminal rows.
Relative column moves accumulate drift across frames: if any earlier
write miscounted cell width — wide-char disagreement (`▸` U+25B8 in
"narrow" fonts that render 2-cell), `▎` ambiguous-width on terminals
that font-detect East Asian width, OSC8 hyperlinks parsed as visible
chars, etc. — the cursor's actual column desyncs from what the
renderer thinks. The next CUF lands at the wrong column, ghost-rows
get written into hint lines, and the modal "shifts" as users navigate
(symptom in #346 issue screenshots).
Anthropic's Claude Code TUI hit the same class of bug
(anthropics/claude-code#14208) and the fix was the same: prefer CHA
over CUF/CUB so column targeting is immune to per-cell width
miscounts. Fix is invisible on terminals where our width math was
already correct; on terminals where it wasn't, no more accumulating
drift.
Add `aliases?: readonly string[]` to SlashCommandSpec so /quit + /q
resolve to /exit, /? to /help, /reset to /new, /lang to /language —
all from a single declaration on the spec instead of ad-hoc handler
mirrors scattered across handlers/basic.ts + handlers/language.ts.
dispatch, suggestSlashCommands and detectSlashArgContext all route
through one resolveSlashAlias() built from SLASH_COMMANDS at module
init. Suggestion rows surface aliases dimly (` · /quit /q`) so they
stay discoverable without polluting the autocomplete list with
duplicates. Dashboard /api/slash response now exposes the field too.
When a markdown table is too wide for the viewport, FallbackTable
flattens it into key/value lines. The previous implementation
iterated headers first, then rows-within-each-header — so a 3×N
table came out as N "Component:" lines, then N "What:" lines,
then N "Manual TCs:" lines. The user couldn't tell which value
belonged to which row.
Reproduction (issue #340): a planning table for 9 components
rendered as 9 grouped Component lines, 9 grouped What lines,
9 grouped Manual TCs lines — visually a list, not a table.
Swap loop order: iterate rows first, then write all columns
inside each row block, separated by a blank row between rows.
Output now reads top-to-bottom as one logical row at a time.
When the model called submit_plan with a markdown body but no
structured steps, the Approve plan modal showed only the
warning banner + the choice list — the actual plan content
was hidden behind the collapsed tool-call card in scrollback.
Users had no way to see what they were approving without
hunting up through the transcript.
- Render the plan body via MarkdownView when no steps are
supplied. Steps still take precedence when present (they
are the canonical structured view).
- Cap inline preview at 24 lines; surface "… N more lines
above in scrollback" when the body exceeds that. Reserve
budget grows with whichever body section is being shown.
Tests cover the three branches: body-only, steps-present,
and truncated-body-with-overflow-hint.
The TUI's session-cost figure ($X session) reset to $0 on every
resume because SessionStats was rebuilt empty even when the disk
meta still held the cumulative totalCostUsd from prior runs.
Reproduction (issue #333): hello → exit → resume → expense
accumulator displays 0 instead of the prior session total.
The persistence path was already correct — App.tsx writes
`{ totalCostUsd, turnCount }` into the session meta after every
turn. Only the read-back was missing.
- SessionStats gains a `seedCarryover()` once-at-construction hook
that adds prior totals to the in-memory totalCost / summary.turns
without polluting the live `turns[]` array (which intentionally
holds only this run's per-turn records).
- CacheFirstLoop now calls `loadSessionMeta()` on resume and seeds
the carryover when prior messages exist. Fresh sessions are
unaffected — undefined meta fields short-circuit the seed.
Tests cover the carryover math (telemetry.test.ts) and the
end-to-end loop wiring (session.test.ts).
* fix(markdown): stop linkifying "e.g" / "i.e" / drop OSC 8 garbage (#330)
Two coupled bugs in the markdown file-ref linkifier:
1. FILE_REF_RE matched English abbreviations because the extension
class was `{1,6}` — `e.g`, `i.e`, `a.m` all qualified.
2. `osc8()` baked OSC 8 escape bytes (\x1b]8;;...\x07) into Text
content. The cell-diff renderer's wrapLine strips zero-width chars
(ESC, BEL) but keeps the printable body, so terminals received
plain `]8;;file://e.ge.g]8;;` characters — visible garbage on
any terminal, with no working hyperlink anywhere.
The fix:
- Tighten FILE_REF_RE post-match: require either path-shape (slash),
line-number suffix, or extension >= 2 chars. `src/foo.ts`,
`package.json`, `util.c:42` still match; bare `util.c` no longer
does (acceptable — rare in prose).
- Strip the OSC 8 escape from `osc8()` — keep color + underline
styling so file refs stand out, but do not emit hyperlink bytes.
The renderer would need per-span hyperlink propagation through
nested HostText flattening to support real OSC 8; that's a
separate refactor. Until then, no link beats broken link.
- Plumb a `hyperlink` prop on ink-compat Text so the future
per-span fix has a place to land.
Regression test mounts Markdown through the reconciler and asserts
the byte stream never contains `]8;;` for `e.g` / `i.e` samples.
* fix(renderer): trail-clear shrunk rows in cell-diff (#330)
Defensive against terminal-state desync. The cell-diff renderer
skips cells where prev and next are byte-equal — including the
trailing EMPTY cells of a row that shrank. If the terminal's
actual state diverged from prev (e.g. a stray ESC body slipped
through earlier rendering), those skipped trailing cells retain
stale chars from prior frames.
This was the second half of issue #330: with the markdown OSC 8
garbage previously sourcing the desync, the option-list modal
rendered "allow always" + "mand, ask again next time" leftover
on rows that originally held a longer hint.
- New `clearToEOL` patch type → serializes to `\x1b[K`
- After diffEach, sweep rows: if next's row ends earlier than
prev's content extent, emit clearToEOL past the last visible
cell. Bounded — at most one clearToEOL per row that shrank.
- Two regression tests cover the modal-shrink case and verify
no clearToEOL is emitted for same-width swaps.
The .chip-f class has cursor:pointer + a hover style, so every chip
looked clickable. In skills, plans, and hooks the chips were laid out
as filter buttons (one hardcoded "active") but had no onClick — clicks
did nothing. Other panels reused chip-f for non-interactive count
indicators, which had the same misleading hover affordance.
Real filters wired:
- skills: All / Project / Global / Builtin filters the list by scope
- plans: All / Active / Done filters by completion status
- hooks: Resolved + each event filters the matrix to rows whose hooks
fire on the selected event (matrix columns still show all events)
Static indicators marked with the new `chip-f.static` modifier (cursor
default, no hover lift). Sessions count, permissions Project/Builtin
counts, usage records/log size, tools total + plan-mode flag, chat
mode label, semantic index status, and semantic config-tag chips all
no longer pretend to be clickable.
CSS: new `.chip-f.static` + `.chip-f.static:hover` rules disable the
interactive affordances without duplicating the chip styling.
Document the chunked-parallel dispatcher and the two knobs that govern
it (REASONIX_PARALLEL_MAX, REASONIX_TOOL_DISPATCH=serial), plus the
list of built-in tools that opt in via parallelSafe.
Closes the docs portion of #325. Observability-event work (chunk-start
in events.jsonl) is deferred — the existing test suite already validates
the timing, ordering, and barrier guarantees, and the kernel event log
is a heavier surface that can wait until a real ops need surfaces.
Replace the serial `for...of + await` tool dispatch with chunked
parallel scheduling: consecutive `parallelSafe` calls race together;
unsafe calls form serial barriers. Tool yields and history append
preserve declared order regardless of which call settles first.
- Loop dispatch chunks consecutive parallelSafe calls; unsafe call
ends the current chunk and runs alone
- runOneToolCall extracts per-call lifecycle (PreToolUse + dispatch +
PostToolUse) so chunks can fan out via Promise.allSettled while the
loop body keeps yielding events in declared order
- New env knobs: REASONIX_PARALLEL_MAX (cap, default 3, hard max 16)
and REASONIX_TOOL_DISPATCH=serial (escape hatch)
- SubagentEvent gains a stable runId per spawn; useSubagent keeps an
array of in-flight activities; SubagentLiveStack renders 1 → rich
card, 2..max → compact rows, >max → "+N more" fold
Tests cover the four guarantees: parallel timing, serial barrier on
mixed safe/unsafe, declared-order yields under racey completion, and
both env-knob overrides.
Two task shapes repeat often enough to warrant first-class support
without needing a skill:
- explore — wide-net read-only investigation (20-iter budget)
- verify — narrow yes/no check with evidence (8-iter budget)
Add an optional `type` field to the spawn_subagent schema. When set,
the type supplies the system prompt and default iter budget. Caller-
supplied `system` / `max_iters` override the type's defaults.
Prompts live in src/tools/subagent-types.ts so subagent.ts stays under
the 500-line target.
Closes#319
Subagents have always had a configurable maxToolIters internally, but
the public spawn_subagent schema exposed only task/system/model. Every
spawn paid the 16-iter default, even narrow verify-style tasks that
want fewer or broad explore tasks that want more.
Add an optional `max_iters` integer field to the schema, clamp at the
boundary to 1-32 so a stray prompt can't request thousands, and pipe
through to spawnSubagent. Non-numeric / missing values fall back to
the registration-time default (still 16).
Closes#318
Skill frontmatter `allowed-tools` was parsed but ignored — every subagent
inherited the parent's full registry minus spawn_subagent / submit_plan,
which gave skill authors no way to scope a child to read-only or
task-specific tools.
Plumb the parsed list through SpawnSubagentOptions; when present, fork
via new forkRegistryWithAllowList helper instead of forkRegistryExcluding.
NEVER_INHERITED still wins so spawn_subagent stays out even if the
skill's allow-list names it. Validate at spawn time — if the allow-list
names a tool the parent doesn't have, return a structured error result
naming the missing tool, no API call burned.
Direct (non-skill) spawn_subagent calls still see full inheritance —
the tool schema is unchanged.
Closes#317
No live render path — `App.tsx` mounts `StatsPanel`, which has its own
`ChromeRow` that diverged from `ChromeBar` and is the bar users actually
see. Only references are a CHANGELOG history line and one test
description string ("'w \$0.91' style").
The two formatter helpers `ChromeBar` once owned (`formatBalance` /
`formatBalanceLabel`) already live in `theme/tokens.ts` after #272 / #313.
After #272 fixed StatusRow / UsageCard / ChromeBar BalancePill, three
display sites still hardcoded `$` and ignored the wallet currency:
- StatsPanel.ChromeRow (the live top bar) — cost label `[$0.0058]`
- StatsPanel.ChromeRow — balance label inline-formatted, bypassing the
shared formatBalance helper from #272
- useSubagent end-event summary — ` · $0.0123` cost suffix
Now all three route through formatCost / formatBalance and follow the
live wallet symbol. Render tests added in ui-stats-panel-currency.test.tsx
covering USD / CNY / no-wallet variants.
useSubagent gets a `getWalletCurrency` thunk (not a snapshot value)
because subagent runs can outlive a balance refresh — the thunk reads
the latest currency at end-event time.
Out of scope: ChromeBar.tsx (orphan, no live render path), DiffApp.tsx
(dev tool comparing historical USD numbers), BudgetRow (USD by definition,
user sets `--budget` in USD). SessionPicker tracked separately in #312.
* fix: Currency for USD wrong afeter TUI redesign.
* red: tests for the currency bug
* Fix implementation
* fixup: collapse tokens helpers + fix UsageCard cost bug
Addresses the two review comments on this PR:
1. Undefined-currency fallback now defaults to CNY for all three helpers
(formatBalance, formatCost, balanceColor) — matches pre-fix unconditional ¥.
2. Seven helpers (formatCNY, formatBalance, formatBalanceLabel,
formatWalletDisplay, formatCost, balanceColorCny, balanceColorForBalance)
collapsed to three: formatBalance, formatCost, balanceColor.
Also fixes a separate bug surfaced while collapsing: UsageCard turn cost
(header) and session cost (body) used formatCNY, which was unconditional ¥
regardless of wallet currency. They now use formatCost(…, balanceCurrency)
and follow the wallet symbol like StatusRow does.
Render tests added for UsageCard turn/session cost in USD wallet mode.
---------
Co-authored-by: esengine <[email protected]>
PR2 under #307. Three more pieces that didn't depend on `this`:
- new `src/loop/types.ts` — `EventRole`, `BranchSummary`, `BranchProgress`,
`LoopEvent`. The public-API re-export from `loop.ts` is preserved
(`export type { ... } from "./loop/types.js"`), so consumers importing
from `reasonix` see no change.
- new `src/loop/branch.ts` — `summarizeBranch` lives next to the types
it produces.
- new `src/loop/hook-events.ts` — `safeParseToolArgs` + `hookWarnings`.
These format hook outcomes as `LoopEvent`s and were the only callers
of `formatHookOutcomeMessage` / `HookOutcome` from `./hooks.js`, so
those imports leave `loop.ts` too.
`loop.ts`: 1414 → 1332 lines. No public API change. `npm run verify`
green (2336 pass / 1 skip).
PR1 under #307. Six functions and three constants that don't touch
`this` had no business living inside the `CacheFirstLoop` class file.
- new `src/loop/escalation.ts` — `parseEscalationMarker`,
`isEscalationRequest`, `looksLikePartialEscalationMarker` plus
`NEEDS_PRO_MARKER_PREFIX` / `NEEDS_PRO_MARKER_RE` /
`NEEDS_PRO_BUFFER_CHARS`. The streaming chunk consumer + post-call
retry path call these as plain functions now.
- `src/loop/errors.ts` gains `reasonPrefixFor` + `errorLabelFor` next
to `formatLoopError`. They share the same `"budget" | "aborted" |
"context-guard" | "stuck"` reason union and were the only callers.
`loop.ts`: 1463 → 1414 lines. No public API change — these were all
private / file-local. `npm run verify` green (2336 pass / 1 skip).
The chain-of-regex approach was tripping CodeQL across three rules
(bad-tag-filter, incomplete-multi-character-sanitization,
polynomial-redos) on the same set of patterns:
- `<tag[\s\S]*?</tag>` misses `</tag >` (whitespace before `>`) and
re-exposes `<tag` after one removal pass on `<scr<tag>ipt>`-shaped
input.
- `<[^>]+>` doesn't handle attribute values containing `>` (rare but
legal in unquoted contexts) and is the canonical "incomplete
sanitization" footgun.
Replaces both with a `node-html-parser` walk:
- `htmlToText` parses the input, removes `script / style / noscript /
nav / footer / aside / svg` blocks via `querySelectorAll`, then
walks the surviving tree and emits text with `\n` breaks at the
block-level tags we care about (`p`, `div`, `br`, `h1-6`, `li`,
`tr`, `section`, `article`).
- `stripHtml` (used by `parseMojeekResults`) becomes `parseHtml(s).text`.
- `decodeHtmlEntities` stays — kept for the post-parser pass since
parser-decoded text can still contain numeric entities in edge
attribute contexts.
- 5 MB input cap retained.
`node-html-parser` 7.x: 25 KB gzip, zero deps, ~30k packages
depend on it, active maintenance. Lighter than `parse5` for our
use case (we don't need full HTML5 conformance — just the tree).
21 web-tools tests pass unchanged; 2336 total tests green.
- src/cli/ui/Wizard.tsx — quoteIfNeeded escaped `"` but not `\`. A
trailing backslash on the input would consume the closing quote
when a downstream parser un-escaped the result. Escape `\` first
(CodeQL js/incomplete-sanitization).
- src/cli/ui/clipboard.ts — temp filename was `reasonix-clip-${Date.now()}.txt`,
predictable + collides under sub-millisecond bursts. Switched to
`randomUUID()` (CodeQL js/insecure-temporary-file).
- tests/slash.test.ts — `/kb.example.com/` matched too broadly (`.`
matched any char, no anchors). Tightened to
`/\bkb\.example\.com\b/` (CodeQL js/incomplete-hostname-regexp +
js/regex/missing-regexp-anchor).
136 wizard + slash tests pass unchanged.
Drains the last 2 file-system-race warnings in code/edit-blocks.ts.
Replaces the existsSync precheck + separate read/write pair with a
single fd-scoped flow:
- Try `openSync(path, "r+")` first. ENOENT → file doesn't exist:
bail with `file-missing` (when SEARCH is non-empty) or fall through
to atomic create.
- Atomic create is `openSync(path, "wx")` — fails on EEXIST so a
concurrent writer that filled the slot between our `r+` ENOENT and
our create can't be silently clobbered.
- Modify path keeps one fd open through fstat → read → ftruncate →
write. ftruncate sets the new length first (so a shorter result
doesn't leave stale tail bytes), then we overwrite from offset 0.
The 22 edit-blocks tests pass unchanged.
1 file-system-race warning still open (`usage.ts:103` compaction);
needs temp-file + rename, separate PR.
Drains the last 2 file-system-race warnings in cli/ui that were
exists→write rather than stat→read.
The original `appendBulletToFile` had two races:
1. `existsSync(path)` then `writeFileSync(path, header)` — between the
check and the write a concurrent appender could create the file,
and our writeFileSync would clobber it with a fresh header (losing
their bullet).
2. `readFileSync(path)` then `appendFileSync(path, …)` — peeking the
trailing byte to decide whether we need a leading `\n`, then a
separate append. A concurrent writer that added their own newline
in between would cause us to insert a redundant blank line.
Fix:
- Atomic create-or-fail via `openSync(path, "ax")`. EEXIST means
another process won the race; we fall through to the append branch
rather than clobbering.
- For the append branch, open with `a+` once and do the trailing-byte
peek + write on the same fd. `O_APPEND` means each `writeSync`
atomically lands at end-of-file regardless of concurrent appenders.
20 hash-memory tests pass unchanged.
3 file-system-race warnings still open: edit-blocks.ts (×2) and
usage.ts:103. They need different surgery (`r+` + ftruncate /
read-modify-write or temp-file + rename); separate PR.
Same fix shape as #298 — open once, do the size check and the read
against the same fd. The read on filtered semantic indexes also gets
to enforce its size threshold against the actual bytes we're about
to load, not a stat result that could be stale by the time we look.
- src/index/semantic/chunker.ts:209 per-file read in the indexer —
re-checks `maxFileBytes` against `fh.stat()` before reading
- src/server/api/semantic.ts:200 `/api/semantic/status` index
summariser — was `statSync().size` then `readFileSync`
- src/cli/ui/slash/handlers/semantic.ts:78 `/semantic` slash status —
was `fs.stat` then `fs.readFile`; estimate fallback for >10MB stays
the same, just bound to the fd's stat
- src/telemetry/usage.ts:74 compactUsageLogIfLarge — folds the
separate stat / read try-blocks into one fd-scoped sequence
5 file-system-race warnings remain — those are exists→write or
read→write patterns (`hash-memory.ts`, `edit-blocks.ts`,
`usage.ts:103`); separate PR with `openSync(path, "ax" | "r+")`.
Same fix shape across three files: open once, use fstat + read against
the same fd. The fd binding pins the inode for the lifetime of the
operation so a concurrent rename / replace / unlink during the call
can't desync the size or mtime we just observed from the bytes we're
about to read.
- src/tools/filesystem.ts:127 read_file body — was `fs.stat` then
`fs.readFile`; switches to async `fs.open` + `fh.stat` + `fh.readFile`
- src/server/assets.ts:36 mtime-keyed asset cache — was `statSync`
then `readFileSync`; switches to `openSync` + `fstatSync` + chunked
`readSync`
- src/server/api/skills.ts:72 per-skill listing — same shape; also
drops the redundant `existsSync` precheck that was a separate race
in the same chain
9 file-system-race warnings remain — those are exists→write or
read→write patterns that need a different fix (open with `ax` / `r+`
flags); separate PR.
Phase-2 PR under #290 (start of the feature-cluster phase). The
/apply and /discard slash callbacks move into one hook (93 lines).
The hook owns the partition / snapshot / save / sync sequence and
returns thin string-builders that AppInner forwards to its log.
Drops `partitionEdits` (unused after extraction) and `savePendingEdits`
(only used by the extracted callbacks) from App.tsx's imports.
App.tsx: 3361 → 3304 lines.
Phase-1 PR under #290 — biggest single extraction so far. The /loop
slash command's entire lifecycle moves into one hook:
- the activeLoop state + the four refs (mirror, timer handle, firing
flag, and the timer scheduler effect itself)
- startLoop / stopLoop / getLoopStatus
- the timer scheduler useEffect (35 lines)
External consumers no longer poke at refs directly. The hook exposes:
- startLoop / stopLoop / getLoopStatus (forwarded to slash handlers)
- isLoopActive() — replaces all `activeLoopRef.current` checks (Esc
handlers, apply-slash-result)
- isLoopFiring() / clearFiringFlag() — replace the cross-component
`loopFiringRef.current` reads in handleSubmit's cancel guard
- activeLoop — reactive state for the LoopStatusRow render
apply-slash-result.ts's context shape switches `activeLoopRef:
MutableRefObject<...>` to `isLoopActive: () => boolean`. Cleaner —
slash handlers don't need to know about the ref shape.
App.tsx: 3499 → 3400 lines.
Phase-1 PR under #290. The Ctrl+C / SIGINT exit handler now lives in
its own hook: it returns the `quitProcess` callback and registers /
deregisters the SIGINT listener on its own. AppInner just calls
`useQuit(transcriptRef)` and forwards the returned function to the
slash dispatcher and Ctrl+C interceptor.
The "why process.exit, not Ink exit" rationale moves with the code
into the hook's docstring — that's the only place future callers
need to read it.
App.tsx: 3499 → 3483 lines.
Phase-1 PR under #290. The transcript writer becomes its own hook —
takes the transcript ref + the model/prefix metadata it needs to
stamp on each record, returns the LoopEvent writer that AppInner
forwards into stream subscribers and slash handlers.
Drops `recordFromLoopEvent` + `writeRecord` from App.tsx's import
block since the hook now owns those.
App.tsx: 3499 → 3493 lines.
First Phase-1 PR under #290. Lifts the bash-style ↑/↓ history recall
out of AppInner: the two `useRef`s (`promptHistory`, `historyCursor`)
and the two `useCallback`s (`recallPrev`, `recallNext`) are now
co-located in `src/cli/ui/hooks/useInputRecall.ts`.
The hook returns four functions — `recallPrev` / `recallNext` for
PromptInput, plus `pushHistory` (called on every successful turn) and
`resetCursor` (called once on submit). Existing callers that wrote
`promptHistory.current.push(text)` switch to `pushHistory(text)`;
`historyCursor.current = -1` becomes `resetCursor()`.
`apply-slash-result.ts` had the only out-of-component reference to
the ref — its context shape now accepts `pushHistory: (s: string)
=> void` instead of the raw `MutableRefObject`. Cleaner contract.
App.tsx: 3499 → 3479 lines.
* fix(redos): close polynomial backtracking in 4 regexes
CodeQL js/polynomial-redos flagged four regexes whose backtracking
shape is O(n²) on adversarial input. None are reachable from a real
attacker today (the inputs are model output / our own URL constants),
but the patterns are easy to fix and the alerts were noise.
- at-mentions.ts:319 — `/\.+$/` on path-like tokens. Loop-slice instead.
- client.ts:95 — `/\/+$/` on baseUrl. Loop-slice instead.
- scavenge.ts:67/75/86 — three DSML matchers (`<X>[\s\S]*?</X>` shape)
on reasoning_content. Adds a 100 KB input cap with an early-bail
note; the matchers themselves stay readable.
Per CodeQL's third remediation example, bounding the input length is
a valid fix when the regex is hard to rewrite — scavenge is best-effort
and the cap is well above any plausible legitimate reasoning_content.
* fix(web): drain CodeQL warnings on htmlToText
htmlToText leaned on a chain of regex replacements that CodeQL flagged
across six rules — bad-tag-filter, incomplete-multi-character-
sanitization, polynomial-redos (×2), double-escaping. None were
exploitable in our pipeline (output goes to the LLM, not a browser),
but the patterns had real correctness bugs visible to the model:
- `<script[\s\S]*?</script>` missed `</script >` (whitespace before
`>`) and could leave `<script` behind on the second pass when an
outer match revealed a previously-hidden inner opening.
- Chained `decodeHtmlEntities` replacements ran `&` before `<`,
so `&lt;` decoded to `<` instead of literal `<`.
Rewrites both:
- `stripTagBlock(s, tag)` — indexOf-based scan with explicit tag-
boundary check (avoids matching `<scriptfoo>`) and tolerant close
matching (`</tag …>` with whitespace).
- `decodeHtmlEntities` — single regex pass with an entity map plus
`&#nnn;` / `&#xHH;` numeric-entity handling. No more order bugs.
- 5 MB input cap on htmlToText so any residual quadratic patterns
(e.g. the kept `<[^>]+>` strip) stay bounded.
21 web-tools tests still pass.
* chore(tsconfig): add @/* path alias for src; migrate slash handlers
The 16 files under src/cli/ui/slash/handlers/ sit four levels deep, so
every import to a top-level module read "../../../../i18n/index.js" or
the equivalent. The depth was load-bearing for nothing — it just made
moves and reviews painful. Adds a single \`@/* → src/*\` alias to
tsconfig.json and mirrors it in vitest.config.ts (esbuild via tsup
already picks up tsconfig paths transparently).
Migrates only the four-level offenders for now. Three-level imports
(siblings within cli/ that resolve to "@/cli/...") are left alone —
the relative form is arguably clearer when the import target is a
neighbour. A follow-up can tighten that if it's worth the churn.
Build, typecheck, and full test suite all pass on the migrated paths.
* fix(jobs): wait for actual close event after SIGKILL, not a fixed timer
stop() had two timing races. Both manifested as the same flake — the
returned snapshot's `running` flag could still be true even though the
test (and the user) just told us to stop the job.
1. SIGKILL phase used a fixed 800ms timer, then returned regardless of
whether the OS had reaped the process tree. Under Windows scheduler
load, taskkill /T /F on a 3-level tree (npm → node → vite) can take
over a second to propagate before Node's `close` event fires.
2. SIGTERM phase awaited `readyPromise`, which is dual-purpose: it
fires on either a startup ready-signal regex match OR child exit.
If the job had already matched a ready signal, `readyPromise` was
already resolved, so the SIGTERM grace race short-circuited
immediately and we'd jump to SIGKILL with zero pause.
Adds `closedPromise` — fires only on close/error, never on ready
signal — and uses it for both the SIGTERM grace race and the post-
SIGKILL wait, with a 5s ceiling on the latter so a wedged kernel
can't hang us indefinitely.
* refactor(filesystem): extract edit + search bodies into src/tools/fs/
filesystem.ts had grown to 681 lines, with three of the registered
tools — edit_file, search_files, search_content — carrying most of
the weight in their inline `fn:` bodies. The diff helpers (renderEditDiff,
lineDiff) were also trailing the registration code with no good reason
to live in the same file.
- src/tools/fs/edit.ts — applyEdit + lineDiff + renderEditDiff (the LCS-based diff renderer is now in the same file as its only caller).
- src/tools/fs/search.ts — searchFiles + searchContent share a SearchContext shape so each tool's `fn:` becomes a one-line dispatch.
- src/tools/filesystem.ts — registration entries kept; bodies are now thin pass-throughs.
`lineDiff` is re-exported from filesystem.ts so the existing test import
(`tests/filesystem-tools.test.ts`) doesn't move.
No public API change. No behavior change. filesystem.ts: 681 → 486 lines.
* fix(filesystem): close stat→read race in search_content (CodeQL)
Replaces the separate `fs.stat(full)` + `fs.readFile(full)` pair with a
single `fs.open` → `fh.stat` → `fh.readFile` sequence so the size check
and the actual read bind to the same fd / inode. No TOCTOU window.
Functionally equivalent: oversized files still skip cheaply (we never
read past the size check), small files still read in one shot.
shell.ts had grown to 847 lines, mixing three unrelated concerns:
allowlist parsing (which is pure string work and the security gate),
process spawning (which carries all the Windows / PowerShell / GBK
workarounds), and tool registration with the ToolRegistry. Each lives
in its own file now:
- src/tools/shell/parse.ts — tokenizer, allowlist, RISKY_ARGS demotion
- src/tools/shell/exec.ts — runCommand, prepareSpawn, killProcessTree, all the Windows quirks
- src/tools/shell.ts — registerShellTools, NeedsConfirmationError, format helpers, plus re-exports
No public API change — every name still importable from ./shell.js.
No behavior change. shell.ts: 847 → 304 lines.
loop.ts had grown to 1724 lines, mixing the CacheFirstLoop streaming
class with a dozen helper functions across four unrelated concerns:
message healing, oversized-result shrinking, thinking-mode flags, and
DeepSeek error formatting. Each concern now lives in its own module
under src/loop/, and loop.ts re-exports every public name so external
callers don't move.
No behavior change. loop.ts: 1724 → 1459 lines.
* fix(benchmark): drop useless \$ escapes in tdd-eval prompt string
The h1 task description string used `\${file}::\${fullName}` inside a
regular `"..."` literal. The backslashes are no-ops (JS quietly drops
unrecognized escapes in regular strings) but trip CodeQL's
js/useless-regexp-character-escape rule. Identical resulting string,
cleaner source.
* fix(jobs): wait for actual close event after SIGKILL, not a fixed timer
stop() had two timing races. Both manifested as the same flake — the
returned snapshot's `running` flag could still be true even though the
test (and the user) just told us to stop the job.
1. SIGKILL phase used a fixed 800ms timer, then returned regardless of
whether the OS had reaped the process tree. Under Windows scheduler
load, taskkill /T /F on a 3-level tree (npm → node → vite) can take
over a second to propagate before Node's `close` event fires.
2. SIGTERM phase awaited `readyPromise`, which is dual-purpose: it
fires on either a startup ready-signal regex match OR child exit.
If the job had already matched a ready signal, `readyPromise` was
already resolved, so the SIGTERM grace race short-circuited
immediately and we'd jump to SIGKILL with zero pause.
Adds `closedPromise` — fires only on close/error, never on ready
signal — and uses it for both the SIGTERM grace race and the post-
SIGKILL wait, with a 5s ceiling on the latter so a wedged kernel
can't hang us indefinitely.
TODO/HACK markers without a (#nnn) issue anchor are debt leakage —
they accumulate without ever being tracked. Require the anchor; bare
markers fail the comment-policy gate.
FIXME is banned outright: either fix it now or open an issue and turn
it into a TODO(#nnn). The marker without follow-through is just noise.
Translator-note comments in i18n files ("english version", "中文版",
etc.) restate what the strings already say — i18n entries are
self-documenting.
src/ currently has zero violations of any of these rules, so this is a
floor-keeper, not a cleanup.
jobs.test.ts / loop.test.ts / bundle-smoke spawn real processes and
load the tokenizer cold; on Windows under load these intermittently
miss their wall-clock budget. One retry absorbs the scheduler
hiccup; a real failure still re-fails on the second run.
handleSettings read cfg once up front, then per-field either called a
self-contained helper (setLanguage / saveApiKey / saveReasoningEffort)
or mutated the snapshot and called writeConfig — so a combined POST
like { lang, baseUrl } would write lang via the helper, then clobber
it with the stale snapshot in the writeConfig branch.
Single read up top, all field updates accumulate into one cfg, single
writeConfig at the end. Runtime side-effects (setLanguage,
applyPresetLive, applyEffortLive) fire after the disk write succeeds
so disk + runtime state can't diverge mid-request.
Closes#274
The `glob` arg was always a `name.toLowerCase().includes(...)` substring
filter, so `*.ts` matched the literal three-char filename instead of
TypeScript files. Param name advertised glob, behavior didn't.
Now glob via picomatch when the value contains `*`, `?`, `{`, or `[`;
case-insensitive substring otherwise so existing `.ts` / `test` callers
keep working. Patterns containing `/` match against the rel-path
(enabling `src/**/*.tsx`), basename otherwise.
Closes#273
Aligns search_files with search_content + directory_tree: skip the
existing SKIP_DIR_NAMES set (node_modules / .git / dist / build /
.next / target / .venv) by default, accept include_deps:true to opt
back into walking them. Fixes the surprising mismatch where
search_content("foo") and search_files("foo") had different default
scopes.
Closes#267
Inside `"..."` the parser treated any `\X` as a generic escape and
dropped the backslash, so `dir /b "C:\Users\foo\.bar"` ran against
`C:\Users\foo.bar`. Restrict the escape to `\"` and `\` only —
everything else stays literal so Windows path separators survive.
Single `isDqEscape` helper now shared by `tokenizeCommand`,
`detectShellOperator`, `splitOnChainOps`, and `parseSegment`.
Closes#265
* feat(mcp): registry-backed marketplace + CLI/Ink/dashboard surfaces
Was: 5-entry hardcoded catalog. Now: live marketplace pulling from
registry.modelcontextprotocol.io (primary), smithery.ai (fallback),
bundled catalog (offline last-resort). 24h cache, schema v2, lazy
per-page loading so first list returns ~30 entries in ~1s.
CLI: `reasonix mcp {list,search,install,browse}` — browse is an Ink
TUI (type-to-filter, ↑↓ pick, Enter install, Tab load 5 more pages,
Esc quit).
Dashboard: MCP panel grows a "marketplace" chip beside all/live/
unbridged. New endpoints: GET /mcp/registry, POST /mcp/registry/install.
Install writes the spec to config.json (same path as manual /mcp/specs
POST).
Cache file moves to ~/.reasonix/mcp-registry-cache.json with a
schemaVersion gate; older blobs are silently rejected and refetched.
MCP_REGISTRY_PAGE_LIMIT env var caps how far an eager load walks
(rarely needed since pagination is now on demand).
* feat(mcp): smithery detail-fetch — install Smithery-only entries
Smithery's listing endpoint omits install metadata, so previously any
Smithery-sourced entry surfaced a "not yet supported" hint. Now `mcp install`
(CLI + dashboard) lazily fetches `/servers/<qualifiedName>` detail and
maps the connection to a runnable spec:
http → remote streamable-http with deploymentUrl
stdio → npx -y @smithery/cli run <qualifiedName> (via new extraArgs
field on RegistryInstall, threaded through specStringFor)
Verified live: `exa` → `exa=streamable+https://exa.run.tools`,
`hugeicons/mcp-server` → `mcp-server=npx -y @smithery/cli run hugeicons/mcp-server`.
Both CLI and dashboard install paths share the same lazy-detail fall-
through. 6 new tests cover http/stdio mapping, 404 fallback, and
extraArgs spec generation.
* test(shell): SpyGate denies instead of approving — kills 5s flake
The "passes the correct kind to the gate" test only asserts what the
gate received; it doesn't care whether the command runs. The old
SpyGate returned `run_once`, so the dispatch went on to spawn `npm i`
in an empty tmp dir. On Windows under concurrent load (full suite +
antivirus + npm cold start) the spawn could exceed the 5s test
timeout, then the afterEach `rmSync` hit EPERM because npm still had
the dir open.
Switching the gate's response to `deny` short-circuits the dispatch
before any spawn. Test runs in ~50ms instead of 1-5s, and the EPERM
failure mode goes away. The assertion (kind + payload were forwarded
correctly) is unchanged.
* test(mcp): anchor mock-URL prefixes with trailing slash
CodeQL flagged `url.startsWith("https://registry.modelcontextprotocol.io")`
in the test's inline fetch mock — without a trailing `/`, an attacker-
controlled URL like `https://registry.modelcontextprotocol.io.evil/`
would also match. Not actually exploitable since the URL is generated
by our own fetcher (the test mock just routes calls), but the rule is
correct in principle and trivial to satisfy.
Adds the trailing slash to every mockFetch host key plus the inline
matcher. All 34 tests still pass.
* feat(mcp): /mcp browse slash + dashboard cards/uninstall + iconUrl
Three improvements driven by user feedback after the marketplace v1:
1. **/mcp browse slash command** — opens an Ink marketplace modal inside
the chat session. Type to filter, ↑↓ pick, Enter installs (or
uninstalls if already present), Tab loads 5 more pages, Esc closes.
No more "exit chat to run external `reasonix mcp` command" friction.
2. **Dashboard cards now show icons + installed-state badge**, and the
detail pane gets: full description (no truncation), runtime/transport
meta line + actual on-disk spec when installed, required-env card,
homepage link, and an explicit "restart required" hint. Lift iconUrl
out of the official registry's `icons[]` and Smithery's `iconUrl`.
3. **Uninstall button** — a marketplace entry whose spec already lives
in config.mcp[] swaps Install → Uninstall (calls existing DELETE
/mcp/specs). Detail pane carries the matching badge.
NOT in this PR: live hot-reload after install. `ctx.reloadMcp` was
declared but never wired in `chat.tsx`, so install/uninstall still
needs a `reasonix code` restart. Both UIs say so honestly. Real
hot-reload is a separate refactor.
* feat(mcp): hot-reload — install / uninstall now bridges live without restart
Closes the last gap in the marketplace flow: previously the user
installed an MCP server through the slash modal or dashboard, the spec
got written to config.json, and we had to tell them "restart `reasonix
code`". `ctx.reloadMcp` was declared on DashboardContext but never
wired in chat.tsx, so it was always undefined.
Refactor: chatCommand's inline MCP-init loop becomes an `McpRuntime`
object (createMcpRuntime in chat.tsx) with addSpec/removeSpec/
reloadFromConfig methods. The runtime owns:
- clients, summaries, registered-tool-names per spec
- hot-add path that calls loop.prefix.addTool for every newly
bridged tool
- hot-remove path that closes the client + unregisters tools +
calls loop.prefix.removeTool
New on the supporting types:
- ToolRegistry.unregister(name)
- ImmutablePrefix.removeTool(name) — same cache-miss cost as addTool
Wiring:
- chat.tsx passes runtime → Root → App → both modal/dashboard surfaces
- SlashContext gets a `reloadMcp` field (for future slash handlers)
- DashboardContext.reloadMcp is set by App.tsx
- /mcp browse modal calls reloadMcp after install/uninstall;
failure falls back to the old "restart required" message
- POST /mcp/registry/install and POST/DELETE /mcp/specs all call
ctx.reloadMcp() and surface bridged: true/false in the response
- Dashboard panel shows "installed + bridged → spec" when hot-reload
succeeded, falls back to plain "installed" otherwise
CLI `reasonix mcp install` still says "restart required" — it runs
in a separate process from any active chat session, so it can't reach
into a different process's runtime. The slash + dashboard surfaces
inside the same session do hot-reload.
* feat(mcp): unify /mcp into a single tabbed hub + cap dashboard list height
User feedback after the marketplace landed: the McpBrowser ("/mcp")
and the new McpMarketplace ("/mcp browse") felt like the same feature
because the visual style overlapped and the verb "browse" collided
with the existing component name "Browser".
Fix: wrap both in a single McpHub modal with two tabs.
- `/mcp` → opens the hub on Live (or Marketplace if no servers attached)
- `/mcp browse` (also `/mcp install`, `/mcp marketplace`) → opens on Marketplace
- Tab key cycles tabs; the previously Tab-bound load-more in
Marketplace moves to PgDn so the wrapper owns Tab cleanly
- Slash result loses openMcpBrowser/openMcpMarketplace; gains
openMcpHub: { tab: "live" | "marketplace" }
- Tests in tests/slash.test.ts updated to match the new shape
Dashboard list height: `.sessions-grid` had `min-height: 540px` but
no ceiling, so a long marketplace list pushed the right detail pane
off-screen. Adds `max-height: calc(100vh - 140px)` so the list scrolls
internally (`.ssl-rows` already has overflow-y: auto). Affects all
panels using the grid (sessions, mcp, etc.); same UX win for any
long left-column list.
* fix(mcp): /mcp opens hub even with native tools (code mode)
In `reasonix code` mode, `tools` is seeded with native filesystem /
shell / memory / plan / choice tools, so `loop.prefix.toolSpecs` is
never empty. My earlier guard required all three (servers + specs +
toolSpecs) to be empty before opening the hub on the marketplace tab,
which meant `/mcp` in code mode silently fell through to the printed
fallback text dump — exactly what the user reported.
Simplified: interactive `/mcp` always opens the hub. Live tab when at
least one server is bridged, Marketplace tab otherwise. The text dump
is only reachable via `/mcp text` (replay / non-TTY scenarios).
Tests: renamed two assertions to `/mcp text`, added a new case that
exercises the code-mode regression directly (mcpSpecs present but
servers empty → opens hub on marketplace).
* fix(dashboard): cap marketplace list height — was still scrolling the page
The previous attempt added `max-height: calc(100vh - 140px)` to the
grid container, but CSS Grid items default to `min-height: auto` (which
means "content size"), so the children — `.sessions-list` (with the long
registry list) and `.sessions-detail` — grew past the grid's max-height
and dragged `.app-body`'s overflow-y along, pushing the right detail
pane below the fold. Symptom user reported: "I scroll to the bottom
and the right detail pane is gone."
Fix is the standard CSS Grid + inner-overflow recipe:
- Add `grid-template-rows: minmax(0, 1fr)` so the row resolves to the
grid's available height (capped by max-height) rather than to
children's content size.
- Add `min-height: 0; min-width: 0` to both grid items so they
actually shrink to fit the track. With min-height: 0, their inner
`.ssl-rows { overflow-y: auto }` and `.sessions-detail { overflow:
auto }` rules finally take effect — list scrolls internally, detail
pane stays visible at all viewport sizes.
Affects every panel using `.sessions-grid` (sessions, mcp, …) — same
UX win for any long left-column list.
* fix(mcp): load-more button — distinct exhausted state + lift hardcoded caps
Two bugs the user reported in the dashboard marketplace:
1. Click "load more" → no visible response. Cause: dashboard sent
`limit=50` hardcoded, so even after the server walked more registry
pages the response was sliced to the same top 50. Fix: track
`displayLimit` in panel state, bump by 50 on each click, send as
query param.
2. Server-side hardcoded caps (`pages` / `maxPages` clamped to 50,
`limit` clamped to 200) hit a wall after a few clicks regardless
of cache depth. Lifted to 200 / 200 / 1000.
3. When the registry is genuinely exhausted, the old footer just
showed dim "all pages loaded" text — visually indistinguishable
from a disabled button, so the user thought clicks weren't
registering. New footer:
- active: primary button with "load 50 more · showing X / Y"
label so the count visibly grows after each click
- exhausted: distinct success-tinted card with ✓ marker
Side effect: `q`-search now also benefits from raised caps. With
matchTarget early-stop the server still returns fast even when caps
are higher.
* fix(server): asset cache uses mtime, not "once per process"
Caused real friction during dashboard development: change panels source,
run `npm run build`, refresh browser → still see old UI because the
running reasonix server cached `dashboard/dist/app.js` in memory at
first read and never re-reads. Required a full restart to pick up any
dashboard rebuild.
Switched to mtime-keyed cache: re-stat each request, re-read body if
mtime advanced. `dashboard/dist/app.js` is ~800KB so the stat-then-
hit-cache path is microseconds. The previous "ONE read per process"
optimisation was guarding against ~zero cost.
Show what the badge looks like before anyone has earned it, so
prospective advocates can see the target. Uses the for-the-badge
shields.io style in the project's lavender brand colour; metadata
badges at the top stay flat-square for information density.
Point active users at the Show and tell discussion category and
preview a forthcoming Reasonix Advocate badge for sustained advocates.
Word of mouth is the only growth channel for a zero-marketing-budget
project, so make the ask explicit.
* fix(shell): demote destructive flags on allowlisted commands (#257)
Allowlist matched on leading tokens only, so `git branch -D`,
`find -delete`, `git diff --output=...`, `npx eslint --fix`, etc.
flowed through without confirmation. Add a per-prefix RISKY_ARGS
table that demotes specific tail tokens back to the confirm gate;
both `--flag value` and `--flag=value` forms are caught. Chains
inherit via the existing per-segment isAllowed call.
* fix(shell): also demote tree -o and find -fprint0 (#257)
Follow-up audit caught two more write-anywhere paths on otherwise-
allowlisted inspection tools: `tree -o FILE` writes the tree output,
and `find -fprint0 FILE` writes NUL-separated paths. Same risk class
as the `git diff --output=` family already covered.
The /svg?type=Date endpoint was returning empty for this repo (likely
because the cumulative-by-day shape needs more data points). /chart with
type=timeline + logscale renders correctly from day one and reads better
when the y-axis range is small.
The post-stop/shutdown asserts were racing Windows taskkill /T tree
propagation, occasionally catching a transient `runningCount === 1`
right after the stop promise resolved. Poll up to 2s for the value to
settle to 0 — distinguishes "persistently wrong" (real bug) from
"momentary race during reap" (not a bug).
Add custom OG social card (1280×640), star-history chart in both READMEs,
FUNDING.yml so the Sponsor button shows up. Goal: when someone lands here
from a shared link or GitHub explore, the first impression and signal of
seriousness should be higher than a default-rendered repo page.
The marketing site had drifted from the project. Bring it back in line with
the post-0.26 README:
- Hero: drop "Ink TUI" / "No LangChain" / "DeepSeek V4" pin; replace the
three hardcoded-number stats (90.2% / ~98% / 100%) with qualitative tags
- Why Reasonix: reorganize the six cards as four architectural pillars
(matching ARCHITECTURE.md) plus two community/positioning cards
- In the box: expand from six to twelve capabilities, matching the README's
feature-grid.svg — adds plan mode, permissions, dashboard, sessions,
semantic search, auto-checkpoints, /effort, replay, event log
- Benchmarks: remove the hardcoded-numbers table; keep methodology + repro
command + link to the harness directory
- CLI: refresh command list and flags to current 0.26 surface
- New Community section with contrib.rocks wall + good-first-issue /
discussions / contributing links
- Footer: drop Changelog (we don't keep one), add Releases / Benchmarks /
Contributors links
i18n.js: rewrite both dicts; 118 keys × 2 with verified 1:1 parity. CSS:
new .community styles, .stat-num resized for qualitative tags, .feat-grid
responsive breakpoints expanded for the wider 12-card layout.
GitHub strips CSS from HTML tables, so the previous <table>-based pillar
and capability sections rendered as plain rows. Move both to custom SVG
assets that match the existing hero-terminal.svg design language —
dark cards (#0a0c10), gradient icons (teal/blue/purple), Inter + JetBrains
Mono typography.
- pillars.svg / pillars.zh-CN.svg: new 2x2 grid of the four architectural
pillars from ARCHITECTURE.md, with deep-link anchors below
- feature-grid.svg / feature-grid.zh-CN.svg: rewritten as a 3x4 grid of
twelve concrete capabilities (was 6 cards with hardcoded "94% live cache
hit" copy that violated the no-hardcoded-numbers rule)
README drops the HTML <table> markup, halving its line count.
\x1b[2J on Windows PowerShell 5.1's legacy conhost scrolls the visible
viewport into scrollback rather than truly erasing it. Each terminal
resize was pushing the current input/toolbar into scrollback, and a
later grow-resize pulled those rows back into the viewport — visible
to the user as duplicated input bars.
Use the same rewind-and-clear pattern (\r\x1b[<N>A\x1b[J) already
used by commitScrollback / emitStatic. \x1b[J fills with spaces in
place, no scrollback push. Platform-neutral, no Windows branch.
The slash form didn't need any chat state — it just deleted idle session
files from disk. Belongs as a CLI subcommand. Adds --days and --dry-run
flags (the slash form had neither).
reasonix prune-sessions # default 90d, deletes
reasonix prune-sessions --days 30
reasonix prune-sessions --dry-run # preview, no delete
Removed:
- /prune-sessions slash handler + registry entry
- pruneUsage / pruneNone / pruneInfo i18n strings (EN + zh-CN)
- slash schema entries for "prune-sessions"
- tests covering the slash form
Updated:
- /doctor's stale-session warning now points at `reasonix prune-sessions`
- i18n schema gains cli.pruneSessions, ui.pruneDaysHint, ui.pruneDryRunHint
Part of #243. /init stays slash (it leverages the live edit-gate;
not actually a CLI shape on closer look). /dashboard stays dual.
/clear rename pending RFC.
Tests: 2254 pass.
/setup just printed a static "exit and run reasonix setup" reminder.
The actual `reasonix setup` CLI subcommand is unchanged; we just
removed the slash command that pointed at it.
Part of the #243 inventory cleanup. Net -5 LOC across handlers,
commands, i18n (EN + zh-CN), and tests.
Tests: 2254 pass.
PR-D from #244. Closes the gap between the normal-fold threshold (50%)
and the force-summary cliff (80%): when a turn lands in 70-85%, the
recent K turns alone are already big enough that a normal fold (tail =
20% of ctxMax) wouldn't buy meaningful headroom. The aggressive tier
shrinks the tail to 10% of ctxMax — sacrifices some recent context
for a real reset.
Decision matrix now:
ratio > 0.8 → exit-with-summary
ratio > 0.7 → fold (tail = 10% ctxMax) [aggressive]
ratio > 0.5 → fold (tail = 20% ctxMax) [normal]
else → none
The status line and warning text both surface "aggressive" when that
tier fires, so users know why recent turns were trimmed harder than
usual.
Implementation:
- PostUsageDecision now carries `tailBudget` and `aggressive` fields
when kind === "fold". loop.ts passes tailBudget through to
compactHistory (which already accepted keepRecentTokens).
- decideAfterUsage hoists the alreadyFolded short-circuit above the
fold-band checks so neither tier re-fires within a turn.
Tests: 2243 pass (was 2242; +1 covering the aggressive band yields a
warning matching `aggressively folded` and a status with `aggressive`).
- Add sameMcpServerSummary(a, b) for logical identity (ref or label+spec).
- Add replaceMcpServerSummary(servers, target, updated) for immutable list update.
- Replace inline prev.map(...) in App.tsx with the helper call.
Co-authored-by: Charles H <[email protected]>
PR-B from #244: closes the foot-gun left over from #238 / #241.
Before this PR, /compact called loop.compact() → ContextManager.inPlaceCompact(),
which mutated mid-history tool result bodies. Cache-aware analysis (#238) showed
that path costs more than it saves: shrinking 50% of prompt size while
invalidating 100% of cache from the mutation point on. The 95% preflight valve
was the second caller of the same path.
What changed:
- /compact handler now calls loop.compactHistory() (the cache-safe fold from
#241) via the existing async-via-postInfo pattern (mirrors /dashboard).
Sync return is "folding…"; result lands as a follow-up info line.
- 95% preflight: tries fold first (one summary call, append-only) instead of
in-place compact. If fold can't shrink anything, surfaces the warning and
lets the request go (the user can /clear).
- loop.compact() public method removed. ContextManager.inPlaceCompact()
removed. shrinkOversizedTool* helpers stay (still used by session
heal-on-load and tests).
- 80% force-summary warning text updated: now mentions /compact since the
name is safe to recommend.
User-visible:
- /compact name kept (muscle memory + short to type), behavior is now
cache-safe fold. Old behavior is gone.
- /help text updated to reflect the new semantics.
- tests/preflight.test.ts: warnings now report fold result instead of
pre-compacted tool count; the "nothing to fold" path replaces the old
"nothing to auto-compact".
Tests: 2233 pass. Typecheck clean.
Closes#243's foot-gun deletion concerns.
- applyMcpAppend() now returns a new McpServerSummary with updated
report.tools.items and toolCount, built via object/array spreads.
- Original target object is never mutated.
- ApplyAppend type returns McpServerSummary instead of void.
- kickOffMcpReconnect captures the return value and updates its local target.
- App.tsx stores MCP servers in local state and immutably replaces the
matching summary after append-drift.
- Both biome-ignore/noExplicitAny suppressions removed.
Co-authored-by: Charles H <[email protected]>
Pulls the four ad-hoc compaction mechanisms behind one component
(see #244 for the full architectural rationale):
- decideAfterUsage(usage, model, alreadyFoldedThisTurn) returns
"fold" / "exit-with-summary" / "none" — the policy that used to
live as inline if-blocks in step()
- decidePreflight(messages, toolSpecs, model) is the local outgoing
estimate gate (>95% of ctxMax)
- fold(model, opts) replaces compactHistory's body
- inPlaceCompact(maxTokens) replaces compact's body and is also
what the 95% preflight calls — the one remaining cache-breaking
path, marked for removal in PR-B
- trimTrailingToolCalls() factors out the in-flight tool_calls tail
drop used before forced-summary
loop.ts methods become thin delegators: compact / compactHistory keep
their public signatures (slash handlers and tests untouched);
forceSummaryAfterIterLimit stays in loop.ts because it's tightly
coupled to LoopEvent yielding.
All thresholds and the summary-marker constant moved to
context-manager.ts. No values changed.
Tests: 2235 pass (no test changes). Typecheck clean.
When a turn's response shows promptTokens > 50% of the model's context
window, replace the older portion of the log with a single synthesized
assistant summary and keep the trailing turns whose token weight fits
in 20% of ctxMax. One cache break per fold; cache rebuilds in ~1 turn,
then the conversation continues under the cap until the next fold.
Without this, append-only sessions grow unbounded — by the time
prompt > 80% of ctxMax, the existing force-summary path fires every
turn ($0.07/turn purgatory until /clear or /compact). Fold prevents
ever reaching that cliff.
Sized so:
- tail budget = 0.2 * ctxMax → ~30% headroom before next fold
- min savings fraction = 0.3 → no fold if head wouldn't shrink the
log meaningfully (avoids re-fold thrash on stable post-fold logs)
- summary call uses deepseek-v4-flash + high effort, ~$0.07 each
Validated on a real 20-turn DeepSeek session with ctxMax pinned at 50k
(scripts/probe-long-session.mts):
turn 10: 52% trips → fold fires → 42 msgs → 19, prompt 25k → 13k
turn 11: cache rebuilds to 84% within one turn
turn 16: 51% trips again, fold fires
total cost across 20 turns: $0.0381 (vs $0.0493 without fold)
total mutations: 2 (= the 2 folds, nothing else)
Closes#236.
* perf(loop): drop in-place auto-compaction — was destroying prompt cache
DeepSeek prompt cache is prefix-exact: mutating any byte of an old
message invalidates every cached token after that point. We were
calling compactInPlace() in five places (turn-end, post-tool-args,
40-80% proactive, 80% reactive, plus the slash command), which meant
long sessions repeatedly traded "smaller prompt" for "0% cache hit
on the rest" — net negative against DeepSeek's 4× cache discount.
Probed empirically (scripts/probe-cache.mjs):
append-only: 98.6% cache hit
one mutation: 0.0% cache hit, lost 4480 cached tokens
long session: ~91% sustained across turns after warmup
Removed the auto-trigger paths entirely. The 80% reactive block now
goes straight to forced-summary instead of trying to mutate-then-bail
(it was already falling through to summary in the common case). The
95% preflight emergency valve and the manual /compact slash command
are kept — they're explicit/last-resort and expected to break cache.
Refs #236
* test(loop): add end-to-end cache-hit probe driving real CacheFirstLoop
Complements scripts/probe-cache.mjs (which probes the API primitive).
This drives the actual loop through 6 real turns and asserts:
- log.compactInPlace() is never called (append-only invariant)
- warm-turn cache hit % stays above 80%
Measured against the live API after the auto-compaction removal:
turn 0: 0.0% (cold cache, expected)
turns 1-5: 99.0, 98.5, 98.0, 97.6, 97.1 — ~98% sustained
total mutations: 0
`run_command` learns the four common shell chain operators (`|`, `||`,
`&&`, `;`) and the seven file redirect operators (`>`, `>>`, `<`, `2>`,
`2>>`, `2>&1`, `&>`). Parsed and spawned natively — no shell is invoked,
so semantics are identical on Windows / macOS / Linux; PowerShell 5.1's
`&&` parse error and the object-vs-bytes pipe gap are sidestepped.
Each chain segment is allowlist-checked independently: `git status |
grep main` now auto-runs when both halves are individually allowed, the
granular-approval behaviour wviana asked for in discussion #231.
The chain parser stays consistent with the project's long-standing
lenient tokenizer — `cargo run -- --flag=1&2` and similar embedded-
operator args stay literal instead of getting POSIX-strict-rejected.
shell-quote is no longer a dependency; `splitOnChainOps` is whitespace-
bounded like the existing `detectShellOperator`.
Mid-pipe `2>&1` correctly merges stderr into the next segment's stdin
without truncating on stdout-end (counter-based close-when-both-ended).
Targets resolve relative to the project root. Heredoc `<<` and
background `&` remain explicitly rejected with clear errors. `\$VAR`
and `\$(...)` pass through as literal characters — no shell expansion.
Closes#232. Driven by discussion #231. PRs: #233 (chain ops), #234
(lenient-tokenizer regression fix), #235 (redirects + mid-pipe `2>&1`).
* feat(shell): support file redirects in run_command (`>`, `>>`, `<`, `2>`, `2>>`, `2>&1`, `&>`)
Phase 2 of the chain-aware run_command rewrite. Each segment now parses
trailing redirects via a single-pass walker (no shell), opens files with
fs.openSync, and hands the resulting fds to spawn's stdio array. Pipe
wiring still applies — `<` overrides pipe-stdin only when explicitly
present; `>`/`>>`/`&>` override the pipe-out / capture-buffer wiring.
Supported per segment (max one per fd):
- `>` stdout truncate
- `>>` stdout append
- `<` stdin from file
- `2>` stderr truncate
- `2>>` stderr append
- `2>&1` merge stderr → stdout (file fd, pipe, or our buffer, whatever stdout points to)
- `&>` both → file (truncate)
Targets resolve relative to the chain's cwd. Multiple redirects to the
same fd are rejected with a clear conflict message.
ChainSegment now carries `redirects: Redirect[]` alongside `argv`. The
old `tokenizeCommand + detectShellOperator` per-segment combo is
replaced with `parseSegment`, a quote-aware single-pass walker that
emits both argv tokens and redirects at the same level — keeps the
lenient embedded-`&`/`|` handling intact (the `cmd1 ; cmd2 -flag=1&2`
regression fix from #234 still passes).
Heredoc `<<` is rejected explicitly. Background `&` is rejected
explicitly (use run_background, not run_command). `$VAR` and `$(…)`
pass through as literal characters — no shell expansion, matching the
existing single-command tokenizer.
Adds 30 new tests in tests/shell-redirects.test.ts covering parser
output and execution; updates the obsolete redirect-rejection tests
in tests/shell-tools.test.ts to cover the new rejection set
(background `&`, heredoc `<<`, missing target, multi-redirect-per-fd).
* fix(shell): hold child.stdin open until both prev streams end on mid-pipe `2>&1`
`cmd1 2>&1 | cmd2` was wiring prev.stdout into child.stdin with default
end-on-source-end, then piping prev.stderr in with `end: false`. When
stdout finished first, child.stdin closed and any subsequent stderr
writes hit a closed stream — output got truncated.
Both branches now pipe with `end: false` and a 2-counter closes stdin
only after both source streams emit `end`. Adds a test that pipes
stderr through to a downstream cat-like process and asserts both
streams reach the destination.
Phase 1 (#233) used shell-quote for chain segmentation, but its strict
POSIX tokenization split `--flag=1&2` into three tokens with `&` as a
background operator — a regression vs. pre-Phase-1 behavior, where the
existing lenient `tokenizeCommand` left embedded `&`/`|`/`;` chars as
literal bytes inside larger tokens.
Replace with a small whitespace-bounded chain splitter that matches the
existing `detectShellOperator` convention: chain ops only count when
they begin a whitespace-separated token. Each segment then runs through
the existing `tokenizeCommand` (lenient) and `detectShellOperator`
(rejects `>`, `<`, `&`, `2>&1`, `&>`).
Recovers:
- `cargo run -- --flag=1&2` — runs (was rejected post-#233)
- `git status ; cargo run -- --flag=1&2` — chain runs, second segment keeps `&`
Drops:
- `git status|grep main` (no spaces) — never worked pre-Phase-1, was a
shell-quote-only side effect; align with the project's
whitespace-bounded operator convention.
Also drops `$VAR` / `$(...)` rejection — these now pass through as
literal arguments, matching the existing single-command tokenizer's
behavior. Models see the literal `$HOME` in echo's output and learn.
Parse chain operators ourselves with shell-quote and spawn each segment
as a separate process — never invoke a system shell. Sidesteps PowerShell
5.1's `&&` parse error and the object-vs-bytes pipe semantics gap on
Windows. Each segment is allowlist-checked independently, so
`git status | grep main` runs when both halves are individually allowed.
Redirects (`>`, `<`, `2>&1`), background `&`, env-var expansion `$VAR`,
command substitution `$(…)`, and subshells `(…)` remain rejected up-front
with clear errors.
Tracks #232, addresses #231.
Two bugs in the Setup screen on Windows / cell-diff renderer:
1. ink-text-input bakes chalk-styled output into the text it returns.
Our renderer strips the ESC byte but keeps the rest, so users saw
literal `[7ms[27m[90mk-...[39m` in the input field. MaskedInput uses
the renderer's <Text inverse> / <Text dimColor> primitives instead.
2. Windows ConPTY splits bracketed-paste wrappers across stdin chunks,
so Ink's parser sees `\x1b[200~` / `\x1b[201~` as printable `[`,
`2`, `0`, `0`, `~` and they leak into the buffer. Strip them at
the input boundary and again at submit.
Also fixes a stale-closure bug where rapid keystrokes from a paste
burst all read the initial empty value, so only the last char survived.
A ref synced on every render lets each keystroke append onto the
latest accumulated value.
Plan execution is continuous after approval — `mark_step_complete` no
longer throws PlanCheckpointError; the model runs all steps in one turn.
Plan card commits to scrollback as the approved snapshot AND renders as
a fixed-height live strip (PlanLiveRow) docked above prompt input via
the windowed-5 step view.
Flicker root cause was orphan unsettled cards (aborted streams that
never fired their .end event) trapping every subsequent card in the
live region — Yoga re-measured the whole live tree on every chunk.
CardStream now allows only the LAST card to be live; earlier orphans
are force-committed to scrollback.
Streaming cards switch to a left ▎ stripe (Card.tsx). Round borders'
top/bottom rows orphaned under the cell-diff renderer's row-promotion
logic when content height changed mid-stream. Stripe rows always carry
both ▎ and content, so promotion is always atomic.
Active-tone color set (TONE_ACTIVE) lifts streaming/running cards one
shade brighter; settled tones unchanged. DiffCard tone bug fixed
(was warn, registry says ok). PlanCard wraps any plan length to a
fixed 5-step window with `✓ ⋯ N done` / `⋯ N upcoming` elision.
API surface: PlanCheckpointError + PlanCheckpointConfirm removed.
mark_step_complete returns the step_completed payload directly.
/stop slash command added (typed alternative to Esc abort).
Cleanup: removed all 7 demo CLI commands (banner / card / flicker /
preview / renderer / select / stress) and their 5 test files. They
duplicated production card components and drifted out of sync.
Two related fixes:
1. SubagentRow was a hand-rolled 9-row block with ▎ left bar drawn on
every row. User reported it didn't match the rest of the card pass —
because it predates the Card primitive entirely. Rewritten on top of
<Card> with round border + violet tone + CardHeader (titleBg pill +
model pill + spinner in `right`). Body collapses from the 9-row
stack into 3 lines (task / last / phase) inside the card. Row count
is still fixed (no per-event growth) so flicker behavior is preserved.
2. CardRenderer had marginTop=1 on its outer wrapper, doubling the
marginTop=1 the Card primitive already adds. Every static-emitted
card carried 2 leading blank rows, accumulating noticeable gaps in
scrollback between cards. Drop CardRenderer's mt; Card primitive
alone owns inter-card spacing.
Three card-header upgrades the user asked for:
1. CardHeader gains an optional `titleBg` that paints the title as a
colored chip — used by ReasoningCard so `reasoning` reads as a
muted-purple block instead of plain bold text. (Borrowed from
PILL_SECTION.reason — already in the theme.)
2. ReasoningCard + StreamingCard surface the snapshotted `card.model`
as a Pill in the header `right` slot. v4-flash / v4-pro / r1 each
get their own color via PILL_MODEL.
3. SubAgentCard children now match card-demo's row format:
▎ [status spinner|✓|✖] [kind glyph] [summary]
Previously the row only had the kind glyph + content; now per-child
running cards spin a tone-colored circle while done ones get a green
✓. Header switches the meta from a static status text to "N running"
when active, mirroring the demo's runningCount.
Original was bold brand-blue spinner + bold brand-blue text + faint
duration with hardcoded `· ` separators. All three fields competed for
attention even though the row is just a "model is busy" hint.
Restraint: drop bold from spinner + label, switch label color to FG.sub
italic (semantic "thinking" via type, not color), accent-purple spinner
for a slower visual pulse, gap={1} for spacing instead of inline `· `
chunks. Reads as one sentence instead of three competing pills.
mount.ts resize() reset promotedRows=0, which made the next commit's
commitScrollback see split.skipped > promotedRows and serialize every
already-scrolled-out row a second time. Each terminal resize stacked
another full copy of the overflowed history into scrollback — visible
as duplicate chrome bars / mode bars climbing up the scroll buffer.
Promoted rows live in the terminal's own scrollback, which the renderer
can't access — so resetting our counter is structurally wrong. Keep
promotedRows; with pendingClear handling the visible repaint, the new
layout's skipped count drives an honest newPromote (often 0 on resize,
since the layout's overflow boundary moves by 1-2 rows max under width
change, not by the entire history).
Also dedup same-dimension resize events — terminals fire 2-3× per
drag and each fires a full commit otherwise.
In `npm run dev` real ink (not the cell-diff renderer) drives layout,
and yoga defaults flex-shrink to 1. When a settled card lands inside
real ink's <Static> column, the box can be shrunk to fit even though no
explicit height is bound — UserCard's Markdown body and ReasoningCard's
SettledPreview both collapsed to 0 rows while the headers survived.
flexShrink=0 on both active and settled wrappers anchors each card to
its content height. The streaming reply was unaffected because its body
alone is already taller than terminal/2 so shrink wouldn't fire.
Adding paddingLeft={2} to the settled-mode wrapper collapsed the layout
so card bodies (UserCard's Markdown, ReasoningCard's BodyLines, etc.)
rendered as 0 rows — only the headers were visible. Card-demo's
StaticRow doesn't apply outer padding either; it pads body sub-Boxes
individually, which is the pattern the live cards used pre-refactor.
Settled mode now mirrors the original outer wrapper shape exactly:
`<Box flexDirection="column" marginTop={1}>`. Bodies render. Active
mode keeps the round border + paddingX=1 + width="100%".
CardStream previously wrapped <Static> in an ActiveCardContext.Provider,
but Static emits its items via bridge.emitStatic which renders them in
an off-tree reconciler — context from the live tree doesn't travel.
Settled cards still rendered with active=true (default) and kept their
borders.
Move the Provider inside the Static children function so it captures
into the per-item subtree that emitStatic actually serializes. Live
path drops its (now redundant) Provider since Card primitive defaults
to active=true.
Two visual bugs after the e78112b border roll-out:
1. Settled cards (in scrollback) carried borders too, but card-demo only
borders the live/active cards — settled rows in demo are flat history
text. Live chat now mirrors that: ActiveCardContext threads
active=false through CardStream's <Static> path, and Card primitive
renders a paddingLeft=2 flat block when not active.
2. Active card width was content-fit, so a narrow reasoning card and a
wide reply card had different border widths in the same column. Adds
width="100%" so every active card stretches to the full available
width and the column reads as a uniform stack.
Also resolves the "reply bottom border missing" symptom — settled reply
cards no longer have a border at all, so the question doesn't arise.
card-demo had a polished round-border + paddingX=1 wrapper around each
card, but the live chat path (src/cli/ui/cards/*.tsx) never adopted it,
so the demo and the actual chat looked completely different. New
primitive `Card({tone, children})` ports that wrapper to the real cards.
Refactored cards now flow through `<Card tone={...}>` with their content
flush left inside the border (paddingX=1 on the wrapper provides the gap;
removed the per-body `paddingLeft={2}` that would have stacked).
Border tone tracks status:
- ok / running / settled — TONE.ok / brand / accent
- error / warn / abort — TONE.err / warn
- meta-info — FG.meta (usage / memory)
LiveCard skipped — it's a one-line transient toast and a 3-row border
would defeat the point. CompactUsageRow path also stays flat.
DEC 2026 sync from 0.24.1 means the border resizing for streaming
content (reasoning/tool/streaming card body growing) lands atomically
per frame; no flicker layered on top of what we already had.
Every card had been hand-rolling its first row with the same
Box/Text/gap=1 incantation, so spacing and color hierarchy drifted
between cards. New CardHeader primitive accepts (glyph, tone, title,
optional titleColor / subtitle / meta / right) and gives 12 cards a
single source of truth:
- glyph + bold title in tone color (titleColor overrides for demoted
cards like usage/memory/user where the bold reads as muted FG.sub)
- subtitle in FG.body (e.g. tool args summary, search query, task
title, subagent name)
- meta items prefixed with `·` separator, joined by ` · `, faint by
default; colored MetaItem variant carries diff +/- counts and
retry/rejected badges without inline JSX clutter
- right slot for ad-hoc inline elements (streaming/reasoning/tool
spinners)
Drops CardBox — it had a ▎ left-bar API but no card actually wrapped in
it (grep returned zero call sites); the inline ▎ each card showed was
hardcoded, and the redesign has no leading bar at all.
Cards converted: User, Streaming, Reasoning, Tool, Task, Plan, Diff,
Usage, Memory, Search, Branch, SubAgent. 12 files, net -55 lines.
Zero flicker risk — pure single-row replacement, same column width per
field. No row count changes.
The CARD constant was the source of truth on paper but most cards
hardcoded glyphs in JSX, so the table drifted from what's rendered.
This pass aligns intent and fixes the worst clashes:
- streaming and task were both `▶` brand-blue and visually
indistinguishable when both surfaced in the same turn. Streaming now
paints `◈` (paired with reasoning's `◆` for the thinking→speaking
arc); task keeps `▶` but moves to TONE.warn so "doing work" reads
separately from "model replying".
- usage is a turn-end summary, not active output — header demoted to
FG.meta; bars + balance keep brand for information density.
- doctor's fail glyph `✗` aligned to error's `✖` for consistency.
- branch in-progress was reusing CARD.streaming.color (brand-blue);
branching is orchestration, paired with subagent under TONE.violet.
- ctx, doctor, branch were absent from CARD; added so future cards have
a token to anchor against. (Existing cards still hardcode glyphs;
consolidation is a follow-up.)
Zero row-count or column-width changes — every replacement is a
single-cell glyph. No flicker risk on top of 0.24.1's sync wrap.
Marked v12's tokenizer ran inline text through HTML escape (& → &,
< → <, " → "), which is correct for HTML output but wrong for a
TUI — both the user-input echo and assistant markdown rendered the raw
entities. v15 keeps token.text literal and only escapes at the HTML
renderer layer, which matches our actual rendering path. Also avoids the
miswidth where a 1-cell `<` was measured as 4 cells (`<`) and clipped
content past the wrap edge.
Commit/static/resize paths buffered bytes into one write but the terminal
could still paint the cleared-then-repainted intermediate state. Wrapping
each frame in BSU/ESU (\x1b[?2026h…l) lets supporting terminals (Windows
Terminal ≥1.18, iTerm2, Kitty, Wezterm, alacritty, foot) swap the frame
atomically; others ignore the unknown CSI. Also folds resize's screen
clear into the next commit so clear+repaint is one sync block.
Five small, related UX improvements riding the yoga + card-migration train:
WelcomeBanner — REASONIX × 🐋 DeepSeek brand row (cyan brand + violet accent
+ whale emoji), tagline, slash-command hints. Drops the hand-painted box-
drawing borders that broke under CJK fonts; uses borderStyle="round" with
yoga's alignItems="center" so layout is correct in any font.
PlanRefineInput — new "reject" mode (red ✗ tone, error palette). The plan-
confirm picker's cancel branch now opens this input so users can attach a
reason like approve / refine already do. Empty Enter = same cancel synthetic
as before; with text = synthetic includes the user's reason. Symmetric with
the "Tab to add reason" pattern on tool-deny.
PromptInput — call useCursor({visible:false}) so the renderer hides the OS
cursor. PromptInput paints its own ▌ block; without this, the OS cursor
showed at screen-bottom too, doubling up.
App.tsx cleanup — dropped 8 unused imports / destructured fields (ApplyResult,
archivePlanState, ReasoningEffort, saveReasoningEffort, writeClipboard,
renderFrame, COLOR, updateAvailable). Flattened currentRootDir to a state
without setter (no caller).
flicker-demo.tsx — committed the previously-untracked debug demo command
(referenced from src/cli/index.ts).
Finishes the card-stream migration (now 17/17 = 100%). Each card replaces
CardHeader + BarRow with a flat layout: a row Box for the header glyph +
title + faint metadata, and paddingLeft={2} child rows for the body.
Cards in this commit:
- DiffCard, SubAgentCard, UsageCard, MemoryCard
- SearchCard, LiveCard, CtxCard, BranchCard, DoctorCard
Visual: tighter, no left bar gutter, headers read like one line of status.
Behavior: identical — just different layout primitive.
The chat-v2 / SimplePromptInput stack was the migration test bed for the
cell-diff renderer. With yoga + isPrimaryRenderer in place, the production
chat path on the v1 PromptInput is the only supported entry point, so v2
is now dead weight.
Card primitives (BarRow / CardHeader / Card.tsx / glyphs.ts) became
unreferenced once every card finished migrating to the flat card-demo
style — yoga handles the alignment they were emulating.
Removed:
- src/cli/commands/chat-v2.tsx, input-demo.tsx
- src/cli/ui/chat-v2-slash.ts, loop-bridge.ts, prompt-input-v2.tsx, use-prompt-history.ts
- src/cli/ui/cards/{Card.tsx,CardHeader.tsx,glyphs.ts}
- src/cli/ui/primitives/BarRow.tsx
- tests/renderer/{chat-v2,chat-v2-slash,loop-bridge,prompt-input-v2,use-prompt-history}.test.tsx
- chat-v2 / input-demo command registrations from src/cli/index.ts
Added: src/cli/ui/primitives/CursorBlock.tsx (the only piece of BarRow.tsx
still needed by ReasoningCard, lifted to its own file).
Replaces our hand-written column/row flex math with Meta's yoga-layout
(WASM, used by real Ink and most React-based TUIs). Layout is now full-spec
flexbox with alignItems/Self/Content, flexShrink/Basis, flexWrap, margin,
min/max, columnGap/rowGap, percent widths.
Why now: the old engine had no cross-axis alignment, so every "center this"
required a nested row+justifyContent hack. With yoga, components describe
intent directly; banner / modal / input layouts collapse to a fraction of
the markup.
Scope:
- Add yoga-layout 3.2.1 dep
- New src/renderer/layout/yoga-layout.ts adapter (LayoutNode -> YogaNode + measure func)
- Rewrite layout.ts: drop layoutBox/Column/Row/intrinsicWidth, walk yoga's
computed positions to populate LayoutRows
- Extend BoxNode + RsxBox + inkCompat.Box prop surface with the new flex props
- BoxSizing.BorderBox; default flex-shrink=1 (CSS, not yoga's 0); root margins
reflected in total render bounds
- isPrimaryRenderer=true: only React renderer in this process, so context-stack
collisions on re-entrant updateContainer go away
- emitStatic via queueMicrotask + reset reservedRows after static bytes -
fixes resume-path layout collision
- Pin Block Elements (U+2580..U+259F) to width=1 alongside Box Drawing
- Per-edge borderColor props now forwarded through inkCompat
- render-to-bytes header trimmed to satisfy comment-policy
Tests: 2187/2187 pass. Two existing border/padding tests updated for yoga's
content-row reservation behavior (more correct than the old engine).
When mcp.initialize() rejects (timeout, bad spec, etc.), the catch
blocks in chat.tsx and run.ts never called mcp.close() — the child
process leaked, readLoop kept running, and on Node 24 the orphaned
rejection fired as an unhandled rejection.
- Lift mcp declaration before try so it's accessible in catch
- Call mcp?.close().catch(() => undefined) in both catch blocks
(guard prevents cleanup masking the original bootstrap failure)
- StdioTransport.close(): child.kill("SIGTERM") throws EINVAL on
Windows; use platform-conditional signal and try/catch to swallow
both EINVAL and failed-spawn errors
Co-authored-by: Charles H <[email protected]>
commitScrollback / commitVirtual / emitStatic all made up to four
sequential opts.write() calls per frame: clear-promote header, promoted
bytes, reserve-grow prelude, and the actual diff patches. Between
writes the terminal could flush, briefly showing blank rows where
content was about to be painted — visible as flicker when ChoiceConfirm
mounts on top of an actively-streaming card (each chunk + the modal
mount each emitting their own multi-write commit).
Now each commit buffers everything into one string and issues a single
opts.write at the end. One terminal flush per frame, no in-between
blank state.
This stacks on top of the previous useStdout fix; the two together
should land the modal-mount flicker.
Root cause of the flicker user reported when ChoiceConfirm (and other
modals) appears while a streaming card is still writing:
`inkCompat.useStdout` was returning `{ stdout: { columns, rows } }`,
a fresh object literal on every render with no `.on/.off/.isTTY/.write`.
viewport-budget.tsx (the row allocator the modal claims rows from)
runs `useEffect([stdout])` to register a "resize" listener — every
render produced a new stdout reference, so the effect re-fired every
render. Inside the effect, `stdout.on("resize", ...)` threw because
`.on` was undefined; throw skipped cleanup; cleanup never landed; the
listener that should have detached on next render never did. The
re-fire + throw + dispatch dance manifested as the flicker.
Fix:
1. New `StdoutContext` carries the real NodeJS.WriteStream (passed in
via mount({stdout})).
2. `useStdout()` now `useMemo`-s the returned wrapper on
(viewport.columns, viewport.rows, real stdout). Stable identity →
downstream `useEffect([stdout])` doesn't re-fire on benign renders.
3. The wrapper exposes viewport-driven `columns`/`rows` (so layout
still reflects the renderer's mounted size, not the host terminal),
plus `.on/.off/.write/.isTTY` proxied to the real WriteStream.
4. `inkCompat.render` threads `opts.stdout` through to mount() so the
chain is wired end to end.
All existing tests still pass (the live-banner-via-shim narrow-viewport
test, useStdout viewport tests, etc.).
Drops CardHeader + BarRow primitives. Both cards collapse to the same
flat header-row + indented body pattern that UserCard adopted in #214.
Error retains its retry meta + truncated stack-trace block (unchanged
behavior, lighter visual chrome). Warn keeps the optional detail meta
on the header line.
* chore(deps): drop ink from runtime dependencies (#160)
The CLI bundle now inlines ink + ink-text-input via tsup's noExternal +
alias chain, so neither package needs to ship at runtime. ink and
ink-text-input move to devDependencies (kept for source resolution
during build / test), and ink-spinner is dropped outright (only ever
referenced in a comment).
vitest gets the same ink → inkCompat alias as tsup so the test suite
runs through the same renderer shim production ships, removing the
last divergence between the two paths.
bundle-smoke already asserts no `from "ink"` literal survives in
dist/cli/; the noExternal extension to ink-text-input means the
bundle has zero `from "ink-text-input"` references too, so a future
regression that breaks either alias fails CI.
* feat(cards): migrate UserCard to card-demo style (#160)
Drops the CardBox left-bar wrapper. The new layout matches card-demo's
flat row aesthetic — accent ›, bold "you", faint relative-time meta,
followed by the user's markdown body indented under it. No more border
or marginLeft offset; cards align to the page's left margin.
This is the first card in the visual migration sweep. Pattern is:
* drop CardBox
* marginTop={1} between cards (was implicit via CardBox)
* header row: glyph + bold word + faint meta
* body indented paddingLeft={2}
Each remaining card (reasoning / streaming / tool / plan / ...) lands
in its own follow-up so before/after diffs stay reviewable.
The CLI bundle now inlines ink + ink-text-input via tsup's noExternal +
alias chain, so neither package needs to ship at runtime. ink and
ink-text-input move to devDependencies (kept for source resolution
during build / test), and ink-spinner is dropped outright (only ever
referenced in a comment).
vitest gets the same ink → inkCompat alias as tsup so the test suite
runs through the same renderer shim production ships, removing the
last divergence between the two paths.
bundle-smoke already asserts no `from "ink"` literal survives in
dist/cli/; the noExternal extension to ink-text-input means the
bundle has zero `from "ink-text-input"` references too, so a future
regression that breaks either alias fails CI.
Adds an esbuild alias on the CLI bundle that resolves every `import …
from "ink"` to src/renderer/ink-compat. Combined with noExternal:
["ink"] this forces the bundle to inline the shim instead of leaving
"ink" as a runtime external. The 3496-line App.tsx and every UI file
that imports Box / Text / Static / useApp / useInput / useStdout /
render now flow through the cell-diff renderer with zero source
changes.
Library + dashboard bundles are unchanged — only the CLI alias.
bundle-smoke gains an assertion that no `from "ink"` literal survives
in dist/cli/, so a future regression that breaks the alias fails the
build pipeline. Doctor command runs end-to-end through the aliased
path; help / version / non-interactive subcommands work.
Tests still resolve the real "ink" package (vitest doesn't go through
tsup), so unit tests stay on the existing path; the bundle test is the
production-correctness check.
New render(element, opts) → { rerender, unmount, waitUntilExit, cleanup,
clear } that mirrors Ink's render API while mounting through the
cell-diff renderer's mount(). Wires resize, Ctrl+C handling
(default-on, opt-out via exitOnCtrlC: false), and useApp().exit()
integration so existing Ink-shaped apps drop in cleanly.
Foundation for the next step: a tsup alias 'ink' → inkCompat that lets
the existing reasonix chat (and its full 3496-line App.tsx) render
through cell-diff without any source changes — replacing the parallel
chat-v2 rebuild track.
7 new tests cover initial mount, waitUntilExit gating, rerender,
Ctrl+C exit, exitOnCtrlC: false, useApp().exit(), and useInput wiring.
handleSubmit detects a leading / and routes to a pure handler map in
src/cli/ui/chat-v2-slash.ts instead of running a turn. Each handler
returns events to dispatch (synthetic user + canned reply, or a
session.reset, or a live.show error) plus an optional exit flag.
/help renders the command list as a regular streaming card so the
markdown view picks up the formatting; /cost reads from agentStore
state and shows current usage; /clear and /new both fire session.reset
which the existing reducer already handles. Unknown commands surface
as an err live card with the offending name.
10 new tests (7 unit + 3 integration through the chat-v2 shell).
runChatV2 accepts session / forceNew / forceResume options; resolveSession
picks the actual name (timestamp suffix on --new, latest prefix on
--resume); CacheFirstLoop({session}) handles persistence so the running
transcript carries across launches.
Resumed sessions replay user-side history as user cards on mount via
AgentStoreProvider's initialCards seed. Assistant content isn't replayed
(no event log on disk yet); fresh turns stream into place.
CLI: `reasonix chat-v2 --session foo` resumes; `--new` forks a fresh
suffix; `--resume` walks to the latest matching prefix. Header shows
the resolved session name when one is active.
The real-loop runTurn now builds a ToolRegistry mirroring chatCommand:
web search/fetch (when searchEnabled()), memory tools (remember /
recall / forget), and ask_choice. The loop is constructed once per
chat session and reused across turns so cache state and the running
transcript carry over.
Tool events flow through the existing makeLoopBridge into tool.start /
tool.end card pairs, so the chat-v2 surface now shows real tool
activity inline (when DEEPSEEK_API_KEY is set). MCP / sessions /
slash commands are still deferred to 5d-23c-e.
New makeLoopBridge() translates LoopEvents into the AgentStore event
shape: assistant_delta opens reasoning / streaming cards and emits
chunks; tool_start + tool produce paired cards with elapsedMs;
assistant_final and done close everything and stamp turn.end with
usage; error closes any open card with aborted=true and fires
turn.abort.
ChatV2Shell takes an injectable runTurn callback. runChatV2 builds the
real one (DeepSeekClient + ImmutablePrefix + CacheFirstLoop) when
DEEPSEEK_API_KEY is set; otherwise the canned demo path still runs so
the UI is explorable without an account.
11 new bridge unit tests; existing chat-v2 tests rewired to the new
runTurn injection point.
chat-v2 splits its card list into settled (user, finished reasoning,
finished tool, completed streaming) and in-flight at every render.
Settled cards go through inkCompat.Static so they emit to scrollback
once and never re-render; only the actively-streaming card stays in
the live region. The viewport's live region is now bounded by the size
of the in-flight card, not by the whole conversation.
MarkdownView drops its useMemo: Static's renderToBytes path uses a
one-shot tree walker without a React dispatcher, so any hook call
inside a Static-promoted subtree throws. Recomputing markdown lines
each render is allocation-light enough that the cache wasn't load-bearing.
The keystroke parser now recognises ESC[200~...ESC[201~ wrappers and
emits the entire payload as a single keystroke, so multi-line pastes
hit processMultilineKey's pasteRequest branch. SimplePromptInput keeps
a per-instance paste registry; each burst gets one PUA sentinel in the
buffer + an inline `[paste #N · Ml · Nb]` placeholder. Submit expands
sentinels back to original content via expandPasteSentinels.
chat-v2 + input-demo enable bracketed-paste mode (ESC[?2004h) on entry
and disable on exit so the wrapper actually arrives.
usePromptHistory hook holds a FIFO of submitted entries. Up arrow on a
boundary saves the current draft, then walks back; down arrow walks
forward and restores the saved draft past the newest entry.
Duplicate-of-latest submissions are coalesced; entries past the cap
(default 100) drop from the front.
chat-v2 wires it into SimplePromptInput's onHistoryPrev / onHistoryNext.
Reuses processMultilineKey from src/cli/ui/multiline-keys.ts so chat-v2's
prompt input shares behavior with the live chat input: backslash line
continuation, ↑/↓ between logical lines, Ctrl+W word delete, Meta+B/F
word jump, Alt+Enter for newline, Enter to submit, history hooks at
buffer boundaries.
Renders each logical line as its own row; cursor lands on the right
(line, col) via useCursor's rowFromBottom. The keystroke parser also
learns Alt+Enter (\x1b\r → meta+return) so the multi-line reducer can
distinguish it from a bare Enter.
chat-v2 now opens an empty conversation with SimplePromptInput at the
bottom. Each Enter dispatches user.submit and plays a stock canned reply
turn (reasoning + streaming + turn.end) — no real model is wired up yet,
but the seam from keystroke → reducer → cards → cell-diff renderer is
fully exercised end-to-end.
Esc on an empty prompt exits; Esc on a non-empty prompt clears (handled
by SimplePromptInput's onCancel semantics).
New SimplePromptInput component built on useCursor + useKeystroke. Handles
printable chars, backspace, delete, enter, ←→, home/end, ctrl+a/e/u/k,
escape (clear when non-empty, cancel when empty). Caret position published
through useCursor so the terminal cursor sits where the user expects.
`reasonix input-demo` exercises the component standalone — submitted
entries land in a Static history list above the prompt.
Adds CursorContext + useCursor() in the renderer. Components register a
target { col, rowFromBottom?, visible? }; mount() reads the latest target
on every frame commit and feeds it into next.cursor.
Also adds a "cursorVisible" patch type so visibility transitions emit
ESC[?25h / ESC[?25l on the diff stream. Foundation for the chat-v2
PromptInput migration — single-line input lands next.
Splits markdown rendering into a pure parser (markdown-lines.ts) and a
cell-diff-renderer view (markdown-view.tsx). chat-v2's reasoning and
streaming card bodies now render proper headings, lists, code blocks,
blockquotes, and inline bold/italic/code instead of a single flat line.
`markdownToLines` is streaming-safe — partial input parses gracefully,
so the same call on every chunk yields a stable line tree.
Mounts AgentStoreProvider through `mount()` instead of Ink's `render()`.
A canned event script drives the real reducer; CardRows read state via
`useAgentState`. No PromptInput yet — Esc / Ctrl+C exits.
Lays the seam for the chat App migration: events → reducer → useState
→ inkCompat tree → cell-diff renderer all proven end-to-end.
- MarkdownWidthCtx + useWidth() propagate available column width into
nested block renderers; width prop is body-width (no double subtraction)
- tableLayout() pure function decides columnar vs fallback layout
- FallbackTable wraps long values under their label; labelPad clamped to
availableWidth-1 so label+value never exceeds card width
- ColumnarTable for tables that fit; HorizontalRule width-bounded
- plainText() exported for test access
- 18 tests: smoke (11), tableLayout fallback decision (2),
FallbackTable width invariants (5 including narrow-width sweep)
Co-authored-by: Charles H <[email protected]>
* feat(renderer): card-demo — full chat lifecycle reference
Demonstrates the design pattern for streaming-TUI cards: every card
type (user, reasoning, tool, plan, response, diff, error) has an
active form that lives in the live region, animating, and a settled
form (typically 1 line) that commits to terminal scrollback once
the underlying work completes.
Auto-replays a fake chat session: user message → reasoning →
shell tool with rolling output → plan with stepwise spinner →
diff → streaming response → error notice. Each card animates
in the live region, then collapses to a single-line summary in
the Static history above. The live region is bounded — at most
ONE active card plus status + prompt — so it never overflows
the viewport, native mouse scroll/select keep working.
This is the pattern Reasonix's actual chat App.tsx should adopt
when migrating to the cell-diff renderer: track in-flight work
in live state, commit completed work to Static. Mirrors how
Claude Code structures its CLI streaming.
Refs #160.
* feat(card-demo): full Reasonix card vocabulary + variants
After surveying src/cli/ui's actual card stream, expanded card-demo
from 7 stages to 13 covering every real card type and lifecycle
variant we ship today:
user → reasoning (R1) → read_file → bash → bash retry/error
→ plan (4 steps with embedded tool ops)
→ write_file rejected → diff → subagent (nested children)
→ streaming response → usage → warn → error
Card behavior matches the live App's CardStream conventions:
- reasoning: active spinner + last 4 token-streamed lines; settled
keeps last 2 lines + "⋯ N ¶ · M tok · /reasoning last"
- tool: tone-colored glyph (▤ read, ▥ write, ▶ bash, ⊙ search,
⌬ fetch, ⊕ mcp); active rolling 5-line tail + elapsed; settled
shows "⋮ N earlier lines" + tail (2-5 lines per tool tone);
rejected = badge replaces body; retry/error = red + ↻ retry X/Y
- plan: ◯/▶/✓/✗/!/s glyphs + "← in progress" marker; settled
keeps full step list (per #160 Plan never collapses to 1 line)
- response: active "writing…" spinner + last 4 lines; settled
keeps full markdown body (or "(truncated by esc)" if aborted)
- diff: file header + first-N hunk preview; +/- coloring
- subagent: ⌬ + nested children with ▎ indent; child cards are
single-line summaries with their own tone/glyph
- usage / warn / error: single-row badges
Wrap helper added so streaming text wraps at ~70 cols and the tail
is computed against actual visual rows.
Refs #160.
* fix(renderer): wide-char width compensation for Ambiguous glyphs
User repro: card-demo in Windows Terminal showed residue chars next to
glyphs like ↻ ▶ ⊞ ◆. East Asian Ambiguous width disagreement —
stringWidth reports 1, the terminal renders 2 (or vice versa on
Western terminals), so the diff cursor model gets out of sync with
where the terminal actually advanced. Subsequent cells land in the
wrong column → leftover chars from the previous frame appear next to
the new content.
Two-part fix:
1. Layout (string-width call site): treat ambiguous chars as wide
(width 2) by default, so the layout reserves enough cells either
way. Box-drawing block U+2500..U+257F is pinned to width 1
explicitly because terminals never render those wide and our
borders depend on it.
2. writeCell, when emitting a Wide cell, runs a leading-space + CHA
compensation:
CHA col+1 ← jump to the right-neighbor cell
stdout ' ' ← pre-write a blank there (covered by wide
glyph if the terminal renders 2-wide; visible
as a clean space if the terminal renders 1-wide)
CHA col ← jump back to the original column
stdout char ← write the actual glyph
cursor.x += 2 ← model advances 2 cells regardless
CHA col+2 ← force the terminal cursor to col+2 so the next
cell write lands in the right spot
~4 extra escape sequences + 1 leading space per Wide cell, only
fires when cell.width === Wide. Empty / narrow cells unaffected.
This is what was making \`↻ retry 1/3\` and \`0.4s\` run together
with stray chars between them, and what made the Plan card render
\`││\` on the right edge.
Refs #160.
* feat(card-demo): real-world plan execution + concurrent active cards
Restructure to match how a real session actually drives cards:
- active state is now an array. Multiple cards can be live at once
(plan stays live while a tool runs below it; subagent stays live
while children animate inline).
- Plan no longer appears all-done in one shot. Steps progress one
at a time: each step starts running, a tool card appears below the
plan card, the tool animates, settles to history, plan step flips
to done, next step starts. Plan card itself never leaves live area
until every step is in a terminal state.
- The fix-failing-test scene now exercises:
* search step (grep) — short tool with rolling output
* write_file rejected mid-plan → step gets blocked → plan retries
via patch tool
* bash test with retry chain (1/3 fails, 2/3 succeeds)
* bash deploy (npm publish)
* full plan settles, diff card pushed, markdown response
streams (header + code block + bullet list)
- Subagent scene: ⌬ card stays live while 4 child rows animate
in sequence (reasoning, grep, read, diff). Each child flips
from running spinner to ✓ in place. CJK streaming response
follows.
- Edge cases scene: aborted reasoning (settles with red glyph +
"(aborted)" badge), MCP tool, web_fetch, compaction warn, rate
limit error, final usage card.
Tools now have per-tone tail length (read/search/fetch = 2 lines,
bash/mcp = 5 lines) matching the real CardStream conventions.
ToolActive carries a `retry` field rendered as `R 1/3` next to the
elapsed timer.
Refs #160.
* feat(renderer): virtual viewport — full layout stays live, PgUp/PgDn scrolls
Adds a scroll: "virtual" mode to mount(). Rather than promoting overflow
rows to scrollback (where they freeze), the entire layout lives in
memory and the visible viewport-1 window slides over it. All animations
keep running for the full layout, even when the user has scrolled away
from the bottom.
mount opts.scroll defaults to "scrollback" — the existing behavior is
unchanged for chat / preview / banner-demo et al. Apps that want
dashboard-style live regions opt in.
Implementation:
- renderVirtual returns the full layout with a windowAt(offset, h)
slicer.
- mount tracks scrollOffset + stickyBottom + lastTotalRows.
- Each commit picks a window: stickyBottom or shrink → snap to
bottom; otherwise hold the user's offset (clamped).
- PgUp / PgDown scroll by viewport-1 rows. Home / End jump to
extremes. After any scroll, stickyBottom re-evaluates against
the new offset so resuming at the bottom auto-follows growth.
stress-demo opts into "virtual" — its 4 concurrent regions can now
exceed the viewport without freezing anything; user scrolls the
viewport over a still-live layout.
Tests: tests/renderer/virtual-viewport.test.tsx (6) — initial bottom
pin, PgUp older rows visible, Home/End jumps, growth-while-sticky
follows latest, growth-after-user-scroll holds position. Uses an
inline virtual-terminal byte parser to read final screen state past
cell-diff fragmentation.
Refs #160.
* feat(renderer): mouse wheel scrolls the virtual viewport
Mouse wheel was being consumed by the terminal's own scrollback and
landed on empty pre-mount terminal output instead of scrolling our
virtual layout.
Fix: enable SGR mouse mode (\x1b[?1000h\x1b[?1006h) on mount when
scroll: "virtual", disable on destroy. Keystroke parser recognizes
button 64 → wheelUp, button 65 → wheelDown. mount's scroll handler
maps wheel events to scrollBy(±3 rows).
Mouse capture is only enabled in virtual mode; scrollback mode
leaves text selection / native scrollback alone for chat-style
apps where the user expects normal terminal behavior.
Tests: keystroke parser cases for SGR `<64;X;YM`, `<65;X;Ym`. Two
virtual-viewport tests cover wheel scrolling and the enable/disable
escape sequences at mount/destroy.
Refs #160.
* fix(renderer): disable mouse mode on any exit path
The bug: enabling SGR mouse mode (\x1b[?1000h\x1b[?1006h) at mount
without disabling it on every exit path leaves the terminal stuck —
mouse clicks and selection get swallowed by escape sequences for
the now-dead process. User has to close the terminal window or
manually emit the disable bytes.
Fix: register `process.on("exit", ...)` to write DISABLE_MOUSE on
ANY process exit (normal, crash, parent-killed). Also intercept
SIGINT/SIGTERM with `process.exit(130)` so Ctrl+C funnels through
the same exit handler. destroy() unregisters these handlers when
mount tears down cleanly.
Idempotent disable: writing DISABLE_MOUSE twice (once from
destroy, once from exit handler) is safe — the disable sequence
just sets a flag in the terminal.
Refs #160.
* feat(renderer): virtual mode enters alt-screen — like the live chat
Aligned mount's virtual mode with src/cli/ui/alt-screen.ts: enter the
terminal's alternate buffer (1049h) so the renderer owns its own
viewport without polluting the user's main shell history. Use button-
event mouse mode (1002, not 1000) for press/drag/release tracking;
SGR coords (1006). Shift+drag still bypasses for native selection.
The escape sequence on enter is now:
\x1b[?1049h\x1b[2J\x1b[H\x1b[?1002h\x1b[?1006h
On any exit (destroy, process.exit, SIGINT/SIGTERM):
\x1b[?1006l\x1b[?1002l\x1b[?1000l\x1b[?1049l
The alt-screen toggle (1049l) automatically restores the user's
pre-mount terminal contents — npm wrapper output, prior shell prompts,
all visible again. No more polluted scrollback after stress-demo
exits, no more stuck mouse mode if the process crashes.
This is what the user meant by "fullscreen": the chat command and
stress-demo now both behave like vim/htop/less — own the viewport,
restore on exit. The scrollback mode (default for chat preview etc.)
keeps the inline behavior where output streams to the user's main
terminal buffer.
Refs #160.
* fix(stress-demo): inline mode + rolling Shell — like Claude Code
After studying claude-code-sourcemap: their CLI runs **inline** for
streaming output (no alt-screen, no mouse capture). Native mouse
selection and terminal scrollback work the user's whole life.
AlternateScreen wrapping is opt-in for explicit modal UIs (plan
mode, etc.) — not the default.
Reasonix stress-demo was wrong to opt into virtual mode. Reverting:
- scroll: "virtual" removed → uses default "scrollback"
- SHELL_WINDOW=5 rolling window restored so the layout fits a
typical viewport (~22 rows)
- alt-screen takeover gone → user keeps native mouse selection
and terminal scrollback
Now matches Claude Code's pattern: streaming dashboards stay inline,
trade-off is older content goes to terminal scrollback frozen (which
is fine, that's how every TUI streaming app works).
Virtual mode stays in the renderer for genuine modal/fullscreen UIs
that explicitly opt in. Not the default.
Refs #160.
* feat(renderer): stress-demo — 4 concurrent live regions
The simple-streaming preview wasn't a real test of the renderer's
value. Plain text streaming on its own is something Ink doesn't
struggle with too much. The actual jitter that #155 reports comes
from STACKED dynamic regions all updating concurrently — Plan card
on top with a spinner, shell command appending output rows below,
streaming response card on top of that, status header ticking, etc.
This subcommand mounts that exact scene:
- status row (ticks every 100ms — elapsed time + cost)
- Plan card (4 steps, step 2 has a spinner ticking every 80ms)
- Shell card (npm test, output rows append every 250ms)
- Response card (text reveals 4 chars every 33ms, wraps mid-phrase)
- hint bar at bottom
All five regions update at independent rates. On Ink, every state
change in any of them re-emits the entire 20-row tree. On the new
renderer, each tick produces patches only for the cells that
actually changed — typically 1-3 cells per tick.
Three tests cover initial paint, ticked state after 1s
(verifying multiple regions are advancing), and ESC-to-exit.
Refs #160. Run `reasonix stress-demo` to see whether the original
jitter problem is actually fixed in the live terminal.
* fix(renderer): re-reserve vertical space when layout grows mid-session
stress-demo exposed a hard correctness bug: live repro showed
spinner glyphs scattered down the left margin overwriting npm dev
output, multiple stacked top borders, scrambled text everywhere.
Root cause: reservation only ran on the first paint. stress-demo's
layout grows over time (Shell card appends rows every 250ms,
Response card text wraps onto new rows as it streams). When the
new layout height exceeded the originally-reserved rows, each
overflowing row triggered a terminal scroll. The diff cursor model
didn't track scrolls, so subsequent relative cursor moves landed
in completely wrong positions — overwriting whatever was at those
real terminal coordinates, including pre-mount scrollback content.
Fix: track reservedRows. On every commit, if the new layout's
height exceeds reservedRows, emit `\n * delta + CSI <delta> A` to
reserve more rows (scrolling once if needed) and bring cursor
back to its model position. Subsequent diffs then use relative
moves within the now-larger reserved region — never past it,
never into pre-mount territory.
Also corrects the off-by-one math from 5d-13: each commit can
extend the reserved area incrementally as content grows.
Refs #160.
* fix(renderer): clip layout to viewport-1 + ink-compat Box default = row
Two fixes from running stress-demo to actual chaos in PowerShell.
1. Layout taller than viewport caused overflow rows to write past
the reserved area, triggering scrolls the diff cursor model
didn't track. Subsequent relative cursor moves landed in
pre-mount terminal territory — Plan spinner cells overwrote
npm dev output, top borders got clobbered by glyphs from
later commits.
Fix: renderToScreen takes an optional maxHeight. mount passes
viewportHeight - 1. When the layout produces more rows than
that, the SKIP rows come off the TOP — so the most recent
streaming content stays visible while the older static chrome
scrolls off the top of the live region.
2. inkCompat.Box defaulted flexDirection to undefined (which our
native Box treats as column). Ink defaults to row. Real
components like the live WelcomeBanner used <Box> for hint
lines expecting row flow; the shim was stacking each Text
on its own line, blowing the layout up to 19 rows.
Fix: ink-compat Box defaults flexDirection to "row" when
not explicitly set.
Refs #160.
* feat(renderer): promote overflow rows to scrollback when layout > viewport
Last fix clipped layout to viewport-1 to stop the diff from corrupting
pre-mount terminal content, but it also meant scrolled-off rows were
never preserved — user couldn't scroll up to see the older state.
Now when layout exceeds viewport-1, the top rows that get clipped are
EMITTED to scrollback explicitly:
1. Track promotedRows — how many top rows have been committed.
2. Each commit, if the new clip count exceeds promotedRows, emit
bytes for those new rows via serializePromoted: clear the live
area, write the promoted rows (cursor advances, they go into
scrollback), reset frame, then repaint the live region below.
3. promotedRows monotonically increases — once a row is promoted,
it stays in scrollback at the state it had when promoted (its
last-known content before scrolling off).
renderViewport replaces the renderToScreen call inside mount: it
returns the visible Screen + a serializer for the promoted slice
of the same layout pass (no double-layouting).
For status / spinner rows whose content keeps changing: when they
overflow, the snapshot at the moment of overflow is what scrollback
keeps. Subsequent commits stop touching those rows. UX-wise this is
similar to how a real terminal scroll preserves output history.
Refs #160.
* fix(stress-demo): rolling Shell window — keep all 4 regions in viewport
Reframing: terminal scrollback is write-once. Once a row scrolls off
the live region, terminals can't update it anymore — animations on
that row are necessarily frozen. The promote-to-scrollback path
preserves the row so users can scroll back, but it'll never re-animate.
The fix isn't more renderer plumbing — it's keeping the demo's layout
inside the viewport so nothing has to scroll off in the first place.
Shell card now shows the last 5 output rows; older rows roll out with
a "(+N earlier)" indicator next to the title. The card stays a
constant ~7 rows tall regardless of how many test lines have arrived.
Status + Plan + Shell + Response + hint now total ~22 rows — fits in
a typical 24-row terminal with all four regions live and animating.
Real chat use cases will use Static for committed messages (which
DOES belong in scrollback) and live region for the in-flight reply
(which fits the viewport). The promote path stays for those cases.
* fix(renderer): full reset on resize — no double-paint
Live repro: shrink the terminal while stress-demo is running. The Plan
card appears stacked twice — one frozen copy above, one live below.
Cause: resize re-rendered through the normal onCommit path, which
saw layout > new viewport-1 and ran promote-to-scrollback. The old
live frame's height (from the bigger viewport) was used to compute
how far up to clear with CSI nA — but CSI A clamps at viewport top,
so the clear missed pre-resize content. Then promoted bytes wrote
visibly into the cleared area, and the diff repainted the live
region below. Net effect: duplicate cards.
Fix: resize is a special event, not a normal commit. Reset frame,
reservedRows, promotedRows; emit `\x1b[2J\x1b[H` to wipe the
visible viewport (scrollback above is preserved by terminals);
then re-render through the normal first-paint path. Pre-resize
content stays in scrollback; current frame paints fresh in the
new viewport size.
Refs #160.
Builds on the spinner state machine: instead of just spinning then
echoing, the response now reveals 3 chars per 33ms, growing in place
in the live area. Spinner glyph keeps ticking (80ms) while text grows.
When fully revealed, a 200ms pause, then the user line + complete
echo land in Static and the prompt comes back.
This is the workload that breaks Ink (#155): a streaming card whose
content grows mid-frame. Each reveal here is ~3 cell writes; the diff
layer doesn't repaint anything else (spinner cell, user line, hint
bar all stay frozen across the reveal). Real LLM streaming, when we
wire it in, slots into the same state — just replace the setInterval
that advances `revealed` with the token-arrival callback.
Response wraps at 60-col viewport — exercises the reveal-across-wrap
case where adding chars at end of one row spills onto the next.
Refs #160.
Enter on a non-slash submission no longer echoes immediately. Shell
enters a "streaming" state: the user line and a Braille spinner row
('thinking…') render in the live area below the Static history,
ticking 80ms/frame. After 1500ms the streaming row commits both the
user line and the echo to Static and the prompt becomes available
again.
This is the core value-prop test for the cell-diff renderer: the
spinner ticks 18-ish times during the stream, each tick is a single
cell change, and the diff emits ~1 patch per frame instead of
re-painting the whole live region the way Ink does. No row-count
churn during the stream → no jitter.
Input is paused while inflight (keystrokes are dropped). The slash
fast-path (/help, /clear, /exit, /unknown) still works because slash
commands return synchronously without entering streaming.
Two new e2e tests in preview.test.tsx assert the spinner appears,
the echo lands after the timeout, and keystrokes during streaming
are dropped. The /clear test was rewritten to use /help submissions
(slash-only) to avoid streaming interference.
Refs #160.
* fix(renderer): anchor cursor to col 0 before the first paint
Bug surfaced live: typing into the preview shell wrote characters at
the wrong screen position because the very first frame's diff started
emitting cells from wherever the terminal cursor happened to sit at
mount time (often mid-line, after the npm dev wrapper output). The
moveTo no-op for (0,0)→(0,0) meant no \r got emitted, so the first
row landed in the column the shell had left the cursor at.
Fix: emit \r CSI J before the first reconciler commit. \r anchors the
cursor at column 0 of the current row; CSI J clears below so any
straggler text isn't visible underneath the live area. Subsequent
diffs already use \r on every row transition, so only row 0 of the
initial paint was vulnerable.
Adds reasonix preview slash commands (/help / /clear / /exit) on top
of 5d-12 since the user was testing them and surfaced the cursor bug.
Also fixes Static so that shrinking items[] resets lastIndex (without
this, a /clear followed by new items wouldn't emit the new ones).
Refs #160.
* fix(renderer): treat OOB cells as EMPTY_CELL in diffEach
Live repro from running reasonix preview:
> 123 ▏ 1 dev <-- our prompt landed on the npm wrapper line
> tsx src/cli/index.ts preview
Enter submit · / for commands · Esc exit
Initial paint mounted on a 24-tall emptyFrame against a 6-row layout.
diffEach iterates the union (24 rows). For y=6..23 prev had EMPTY_CELL
(allocated by emptyFrame), next.cellAt returned undefined (OOB on the
shorter screen). The early-skip required BOTH non-undefined for
cellsEqual, so the OOB case fell through and emitted clear-patches —
~18 rows × viewportWidth cells of cursor moves + spaces. On a 24-row
terminal that ran the cursor past the bottom, scrolling the npm
output up; the header scrolled out of view and the prompt landed
where "> [email protected].1 dev" used to sit.
Fix: coalesce undefined to EMPTY_CELL on both sides before the equality
check. OOB-vs-EMPTY is now a no-op; populated-vs-OOB still emits a
clear (which is correct — the row really shrank).
Two regression tests in tests/renderer/diff.test.ts pin both legs.
* fix(renderer): reserve vertical rows + revert OOB coalesce
User-visible repro: reasonix renderer-demo (and preview) only showed
the bottom row of the layout in PowerShell. Header / prompt rows
appeared to be missing.
Two interacting bugs:
1. mount painted rows top-down using CSI nB cursor moves. When the
shell left the cursor near the bottom of the viewport, every row
transition past the visible region scrolled the terminal up,
pushing earlier-painted rows off-screen. Only the LAST row written
ended up still visible.
Fix: before the first paint, emit `\r \n*(N-1) CSI <N-1>A` to
pre-reserve N rows below the cursor (scrolling up once if needed)
and return to the start. Subsequent moves stay within the reserved
block — no more scrolls.
2. The earlier OOB-coalesce attempt in diffEach treated
prev=undefined / next=EMPTY_CELL as equal, which silently dropped
patches for spaces inside text content (since space cells share
charId/style with EMPTY_CELL). "(none yet)" rendered with cursor
gaps where its space should have been.
Reverted to the original diff predicate. Initial paint now emits
patches for every cell in the new screen (verbose, but correct);
subsequent diffs still coalesce identical cells.
Reservation regression test in mount.test.tsx asserts the
\r\n*8\x1b[8A prelude for a 9-row layout.
Refs #160.
* fix(renderer): reserve N+1 rows so the final cursor park doesn't scroll
Off-by-one in the reservation prelude caused values to drift one row
up after the first paint when the live region used the bottom of the
viewport. Trace: 9-row content + final cursor parks at frame y=9
(one past the last content row). Old reservation only covered 9 rows
(R..R+8); the cursor's final move to R+9 hit the viewport bottom and
scrolled, shifting all painted content up by 1. Subsequent diffs
targeted the now-shifted rows correctly in their own model, but the
already-rendered content had drifted, so visually new values landed
one row above the row where the label sat.
Bump reserve to screen.height (was screen.height - 1) so the parking
row is also pre-allocated. seven-key-trace test confirms the byte
stream produces the right cells; mount.test.tsx regression updated
to assert the new prelude shape.
Refs #160.
First user-facing surface that runs entirely on the new pipeline. Echo
mode for now: header, Static-emitted history, single-line input,
Enter to submit, Esc to exit. Composes everything 5d-2..5d-11 added
(useKeystroke, useApp.exit, Static scrollback, gap, hex colors,
marginTop, useState-driven draft).
State held in refs so a single push("abc\r") that fires four
keystrokes synchronously commits the right text — closure-captured
state would otherwise read pre-update values.
Subsequent PRs grow this shell toward feature parity with the live
chat: model badge, streaming card, tool result rows, slash-commands.
Once it catches up, the existing Ink-based App becomes the legacy
backend.
Refs #160.
Mounts the actual src/cli/ui/WelcomeBanner.tsx — the component the
running app uses today — through our cell-diff renderer with **zero
source changes**. vi.mock substitutes "ink" with the ink-compat shim
at test time, so the production import paths stay intact.
Asserts the frame glyphs, REASONIX brand line, slash hints, in-code
mode tagline swap, dashboardUrl link line, and a narrow viewport
(cols=40). This is the first time a real production component renders
under the new pipeline without being copied or rewritten.
Refs #160. The path forward for full migration: add a runtime
"ink" → ink-compat alias when the new renderer is selected, and
existing components keep working.
Previously useApp() returned a default {exit: noop}. Components inside
a mount tree could call exit() but nothing happened — the host had to
read the user's intent some other way (a Promise resolved from a
keystroke handler, etc.).
mount() now provides AppContext.Provider with a real exit fn. The fn
defers via queueMicrotask so it never fires synchronously inside a
render or effect — that would unmount the tree mid-commit. After
destroy, exit() becomes a no-op, so a stale ref can't fire onExit
later.
mount opt: onExit?: (error?: Error) => void. The host owns the actual
teardown; onExit is just the signal.
Refs #160. Smaller surface than full lifecycle plumbing — covers the
Ink useApp() pattern that DiffApp/ReplayApp/Setup/Wizard rely on.
Reasonix select-demo subcommand mounts a faithful single-select list
through the cell-diff renderer: arrow nav, Enter to submit, Esc to
cancel, disabled rows skip + dim. Real-world pattern that combines
useKeystroke, useState-driven highlight, hex/named-color theming, and
nested column Boxes.
Five end-to-end tests cover initial paint, ArrowDown skipping a
disabled row, Enter on the initial active row, Esc cancel, and
ArrowUp wrap-around.
Refs #160. Together with banner-demo, this proves both static-shaped
content (banner) and interactive-shaped content (select) ride the new
pipeline cleanly.
Adds tests/gitignore.test.ts covering ignoredByLayers (empty layers,
literal dir match, intra-file negation, isDir toggle, out-of-scope
layer skip, fall-through, no-match) and loadGitignoreAt /
loadGitignoreAtSync (missing-file null path, working Ignore from a
real .gitignore in a tmpdir).
11 tests; vitest, lint, typecheck, and full suite (2064 tests) pass
locally. No source changes; no new dependencies.
Closes#139
Co-authored-by: Matt Van Horn <[email protected]>
Locks in the diff pipeline's behavior with CJK and emoji content:
both glyphs of a 4-cell CJK string land, replacing wide content with
narrow leaves no ghost half-cells, narrow→wide growth writes the new
wide char, multiple emoji in a row each appear, a styled CJK char
wraps in the right SGR open/close pair, and wrapping at the viewport
edge keeps the wide glyph intact on the next row.
Refs #160. The renderer's main correctness risk in real Reasonix usage
is wide chars across diffs (Chinese UI strings change between frames
constantly). These tests catch the SpacerTail-not-cleared regression
class up front.
Adds gap to BoxNode with the obvious semantics: in column flow it
inserts N empty rows between siblings; in row flow it reserves N cells
between siblings before flexGrow distribution.
Plumbed through native BoxProps + ink-compat Box. intrinsicWidth now
counts gap*N-1 for row-flow boxes so flex distribution is correct.
gap composes with justifyContent — extra slack from space-between is
added on top of the configured gap.
Refs #160. Used by markdown.tsx, etc.
Implements the "rendered once and never updated" semantic for
inkCompat.Static. Previously the shim just wrapped items in a column
Box, which left them subject to re-diff every frame.
Pipeline: when Static's items array grows, the new items are rendered
offline via renderToBytes and handed to the mount Handle's emitStatic.
emitStatic clears the previous live area, writes the static bytes
(advancing scrollback), and resets the prev frame so the next paint
starts fresh below.
renderToBytes is exposed publicly so apps can stage scrollback content
without React (e.g., a one-shot welcome banner emitted before the live
loop starts).
Refs #160.
Reasonix banner-demo subcommand mounts a structurally faithful version
of the welcome banner — nested Box + marginY + marginTop +
justifyContent="center" + hex colors, useStdout for centering, useKeystroke
for ESC — entirely through the ink-compat shim onto the cell-diff
renderer.
Three end-to-end tests assert frame glyphs, brand line, hint row, ESC
exit, and resize re-paint. The Ink-flavored banner used by the live App
is left untouched on this branch; this is the first concrete proof that
a non-trivial component renders end-to-end through the new pipeline.
Refs #160.
Adds width and height props to BoxNode + BoxProps + ink-compat. Width
overrides intrinsic size for row-flow allocation and clamps to the
parent's available width. Height pads with empty rows when content is
shorter and truncates when content is taller.
Unblocks the height={1} spacer-row pattern (4 components in src/cli/ui
use it) and width-constrained columns (sidebar, picker lists) that
need to land before the main App can migrate off Ink.
Refs #160.
Wires Yoga-style row distribution into the layout engine. Default
(flex-start) preserves current behavior. flex-end pushes children to
the right edge, center splits slack evenly, space-between distributes
the gap between siblings. flexGrow children consume slack first, so
justifyContent silently degrades to flex-start when grow is present —
which matches CSS flexbox.
Plumbed through BoxNode → BoxProps → ink-compat Box so existing Ink
code reading `<Box justifyContent="space-between">` migrates with no
source changes. Three of four uses in the codebase already match this
shape.
Refs #160.
Lets components written against Ink's API render under the cell-diff
renderer with no source changes for the props we cover.
Box: padding{X,Y,Top,Bottom,Left,Right} pass through; margin{X,Y,Top,
Bottom,Left,Right,} translate to a wrapper Box's padding so empty rows
sit above/around the inner box (works in both column and row flow,
since the wrapper carries flexGrow on row participation). borderStyle
takes the string presets, borderColor takes color names + hex.
Text: color, backgroundColor, bold, dimColor, italic, underline,
strikethrough, inverse all stack into the StylePool entry.
Spacer is just <Box flexGrow={1}/>. Static is a flexDirection=column
wrapper — it doesn't yet implement Ink's "settled content stays in
place" semantic; that needs row-level commit isolation, deferred.
Hooks: useStdout reads {columns,rows} from a ViewportContext that
mount() now provides and re-publishes on resize(). useApp returns
{exit} from AppContext (host wires its own exit). useInput translates
each Keystroke to Ink's (input, key) callback shape, with isActive
gating.
Out of scope: width/height (need fixed-size layout), justifyContent,
alignItems, gap, useFocus, Transform, measureElement.
Refs #160.
Lets us exercise the cell-diff renderer against real stdin/stdout
without touching the main Ink-based App. Counter + last-key display,
ESC to exit. Component-level tests cover initial paint, key handling,
and ESC-to-exit through a fake stdin and the test writer.
Refs #160.
Adds the input side of the renderer pipeline so React components can
react to user keystrokes through the same provider/hook idiom they
already use for state.
Architecture:
- parseKeystrokes(chunk) is a pure ANSI escape-sequence parser. Plain
ASCII passes through; \x01..\x1a become ctrl+letter; \r / \n
return; \x7f / \x08 backspace; \t tab; \x1b alone escape; ESC +
printable is meta+char; CSI A/B/C/D arrows; CSI 1;modifier <X>
surfaces shift/meta/ctrl modifiers; CSI 3~ delete, 5~ pageUp,
6~ pageDown, 1~/H home, 4~/F end.
- KeystrokeReader wraps a stdin-like stream (anything with on/off
'data') and emits parsed Keystroke events to subscribers. Sets raw
mode on construction, drops it on destroy.
- useKeystroke(handler) hook subscribes the calling component to the
reader provided via KeystrokeContext.
- mount({ stdin }) constructs the reader, wraps the React tree in
KeystrokeContext.Provider, and tears the reader down on destroy.
Tracking issue: #160.
useState / useEffect / re-render-on-state now drive paints without
the caller manually calling update(). React's reconciler maintains
the host node tree; on every commit we walk it to a LayoutNode tree,
hand it to the diff layer, and write only the changed bytes.
Surface:
const handle = mount(<App />, { viewportWidth, viewportHeight, pools, write });
// setState in App triggers a paint automatically.
handle.update(<NewApp />); // explicit replace also works
handle.resize(cols, rows);
handle.destroy();
Box and Text are now thin wrappers that emit string-typed JSX
intrinsics ('rsx-box' / 'rsx-text'). The reconciler matches the
strings in createInstance and instantiates host nodes; the existing
no-reconciler walker in react/render.ts matches the same strings.
Both code paths converge.
Adds react-reconciler + @types/react-reconciler as direct deps.
Tracking issue: #160.
Closes the offline pipeline of #160. Caller pushes a React tree at
the Renderer; it lays out, diffs against the previous frame, writes
only the changed bytes to the configured sink, and stashes the new
frame for the next call.
const r = new Renderer({ viewportWidth, viewportHeight, pools, write });
r.update(<App />); // first paint — full screen
r.update(<App />); // identical tree — zero bytes
r.update(<AppMutated />); // only the diff
r.resize(cols, rows); // next update full-resets via clearTerminal
r.destroy(); // SGR reset + OSC 8 close
Sink is injected (write: (bytes: string) => void), so tests run
purely in memory via makeTestWriter() — no real stdout, no real
terminal. The same shape will plug into process.stdout.write in
the runtime integration step.
Doesn't yet:
- Drive re-renders from React state (the caller still has to call
update; Phase 5b adds reconciler-driven re-renders).
- Read keystrokes (Phase 5c).
- Replace Ink in Reasonix's CLI (Phase 5d, behind a feature flag).
Tracking issue: #160.
Closes the second-to-last layer of #160. Takes the Patch[] that
diffFrames returns and produces the actual bytes a terminal
understands.
cursorMove → CSI A/B/C/D (vertical first, then horizontal)
cursorTo → CSI <col+1> G (CHA is 1-based)
hyperlink → OSC 8;;<uri> ST (empty uri = close)
clear → \r + CSI <count> A + CSI J (move up N rows, erase to end)
clearTerminal → CSI 2J + CSI H
stdout / styleStr / carriageReturn pass through verbatim — they are
already terminal bytes by the time the diff layer puts them in the
patch list.
dx=0 and dy=0 cursor moves serialize to the empty string (no wasted
escapes), and an empty Patch[] serializes to '' so emitting a frame
with no diff is a no-op.
Tracking issue: #160.
Core of #160 — the algorithm that takes two Screen snapshots and
emits the minimal set of (cursorMove + styleStr + stdout + hyperlink)
patches needed to bring the terminal from the old state to the new.
This is what replaces Ink's bulk eraseLines: unchanged cells produce
zero bytes.
diffFrames(prev, next, pools) → Patch[]:
- viewport size differs → emit clearTerminal + write the full new
screen. Resize is rare; predicting wrap on a different width is
not worth the layout machinery.
- otherwise walk every (x, y) where the cells differ:
- move the cursor there (\r if pending-wrap, then \r + dy + dx)
- transition style if changed (StylePool.transition cached)
- transition hyperlink if changed (OSC 8 open / close)
- skip SpacerTail (the wide glyph already advanced the cursor)
- write the char
- after all changes, restore cursor to next.cursor and reset style /
hyperlink to none so anything we don't own renders cleanly.
Adjacent same-style writes ride on the terminal's natural cursor
advance — no inter-cell cursor moves, no inter-cell style emits.
Tracking issue: #160.
Add back-end language setting support, including initializing language settings from the server and bidirectional synchronization functionality
Expand the language registry to support more languages, and improve language storage and error handling
Fix issue of returning to the chat page after refreshing
Closes the layout side of the renderer feature surface for #160.
Borders compose with padding by sitting outside it:
border-top
padding-top
content (width = inner - borders - padding)
padding-bottom
border-bottom
Five preset styles ('single', 'double', 'round', 'bold', 'ascii')
or a fully custom { topLeft, top, topRight, ... } glyph object —
the latter is what Reasonix's CardBox uses today (whitespace
corners + a single glyph on the left for the accent bar).
Each side toggles independently via borderTop / Bottom / Left /
Right; default-on when borderStyle is set, default-off otherwise.
borderColor sets all four; per-side overrides (borderLeftColor
etc.) win.
intrinsicWidth now accounts for border + padding so flexDirection
row in a parent allocates the correct slot width to bordered
children.
Tracking issue: #160.
Refactors layout from a linear TextRow stream to a 2D structure
where each visual row holds a list of x-positioned fragments.
Necessary for row direction — sibling children need to share rows
at different x offsets, which the previous one-fragment-per-row
shape couldn't express.
flexDirection='row' lays children left-to-right. Each child gets
min(intrinsicWidth, remaining) of the available width. When the
sum of intrinsics exceeds the container, allocations scale
proportionally and children's text wraps inside its narrower slot.
Children with different heights align at the top.
flexGrow distributes leftover width after intrinsics are honored.
The common case — Box flexGrow=1 as a flex spacer between fixed
content — yields '<L> <pad> <R>' style headers without manual
column math.
Default direction stays column.
Tracking issue: #160.
Padding shifts content inward without changing the Box's own width.
paddingTop / Bottom emit blank rows above / below children;
paddingLeft / Right reduce the inner width children lay out into,
and every emitted row carries a leftPad offset that the blit step
honours so writes start at the correct x.
paddingX / paddingY / padding shorthands compose with the side-
specific props — explicit side wins (paddingLeft beats paddingX
beats padding).
Tracking issue: #160.
Lets callers write the renderer surface in JSX instead of building
LayoutNode trees by hand. Box and Text are exported as host markers
(throw if invoked directly); the render() entry walks the React
element tree, recognizes those markers, calls stateless function
components inline, and unwraps Fragments. Output is a Screen.
No reconciler yet — stateful components / hooks / re-render-on-state
don't drive output. The walker is enough for static JSX rendering
and for tests to use familiar JSX syntax. The reconciler comes when
we wire the renderer to actually drive a live UI.
Tracking issue: #160.
Walks a tree of Box and Text nodes and lays them out into a Screen
of the given width. Children stack vertically; nested boxes flatten
in source order. Long text lines wrap at the cell boundary using
grapheme-aware width via Intl.Segmenter + string-width, so CJK and
emoji ZWJ count as one rendered glyph occupying the right number
of cells.
Style and hyperlink on a Text node are interned through the pools
and propagated to every cell the node produces — sets up the diff
layer to compare cells purely by integer ids.
Tracking issue: #160.
Lays down the data structures the cell-diff renderer will read from.
Pure values, no terminal IO; the diff layer (next) reads two Screen
snapshots and emits patches per cell that actually differs.
Three pools collapse high-cardinality runtime values to integer ids
so cell comparison stays in int-vs-int and per-frame allocation
stops being a GC problem at 5K+ cells.
Tracking issue: #160.
Plan card now lives only as a regular inline card in the stream.
No right-side panel, no above-input pinning, no Ctrl+\ toggle.
Layout stayed in 'either-or' / 'both' / 'sometimes-pinned' uncertainty
across PR #127 → #156, and the docking machinery itself was a steady
source of layout instability that no amount of width-conditional
gating fully closed.
Removes:
- src/cli/ui/layout/SidebarPanel.tsx (file)
- tests/sidebar-panel.test.ts (file)
- App.tsx: activePlanCard / rawActivePlanCard / sidebarVisible
derivation, the sidebarOpen state + Ctrl+\ keybind, the
<SidebarPanel> mount, the modal-active gating that only mattered
to suppress the sidebar
- viewport-budget.tsx: 'plan-card' ZoneId entry (no claimers left),
useIsModalActive() hook (only consumer was sidebar)
- CardStream.tsx: excludeId prop (no callers left)
- config.ts: sidebarOpen field + load/save helpers
The plan card itself is unchanged — it's already a settled card
once all steps complete and renders as a regular inline card via
CardStream's existing plan->Static path. Inline plan card has
stable height (no windowing), so it doesn't suffer the live-region
height-flutter issue the sidebar's windowed PlanSection had.
Root-cause fix for the up-down screen jitter dududarochadev reported
in #155 (and the same class of bug we previously masked with
cols-based sidebar gating).
When a plan has more steps than fit in the window (>11), the windowed
plan-section conditionally rendered '(N earlier hidden)' / '(N more)'
hint rows only when N>0. As the running step crossed the window
boundaries those flipped on/off, changing the live region's row count
and triggering Ink's erase-then-reprint to leak the previous frame.
Always render both indicator rows in windowed mode; show the count
when N>0, an empty 1-row placeholder otherwise. Total rendered height
of the windowed plan-section is now stable regardless of how the
running step moves through the plan.
Fix lives on the plan card itself, not behind a width gate, so the
narrow-screen inline-plan path benefits the same way once the same
windowing pattern lands there (currently inline PlanCard doesn't
window, so it's already stable for now).
This is the start of the broader 'live-region row stability' work I'll
track in a follow-up issue — streaming/reasoning preview cards have
the same shape of bug during their initial output ramp.
Per RFC #20 thread, lamyc's ask was "task list collapsed INTO a
sidebar" on portrait/narrow setups. PR #127 shipped a sidebar but
also kept a pinned PlanCard above the input — so on wide screens the
plan rendered twice (sidebar + pinned), and on narrow screens (where
the sidebar refuses to render below 88 cols) the plan was pulled out
of the card stream and pinned above input alone, leaving no inline
plan card at all.
Single rule now:
sidebarVisible = !PLAIN_UI && sidebarOpen && cols ≥ 88 && activePlanCard
- sidebarVisible → CardStream excludes plan; sidebar renders it
- !sidebarVisible → CardStream keeps plan inline; nothing pinned
Drop the pinned PlanCard above input entirely. Drop the unconditional
`excludeId` on CardStream. `PlanCard` is no longer imported in App.
This implements interpretation B+C from the layout discussion:
B) plan fully in sidebar when room exists, no duplicate
C) narrow / portrait → plan stays inline in stream, no sidebar
#147 used "at least one step has left queued" as the proxy for
"plan has been approved". That breaks the post-accept window: once
the user accepts, plan steps may sit in `queued` for several seconds
before the model issues its first tool call — during which the sidebar
should be visible but isn't.
Right discriminator is the approval modal itself. `useIsModalActive()`
is true exactly while PlanConfirm (or any other modal-priority claim)
is up. Drop the "non-queued" check from findActivePlan and gate at
the call site:
- SidebarPanel: `isModalActive ? null : findActivePlan(cards)`
- App.tsx activePlanCard: same shape
findActivePlan stays pure (no hook usage) so it remains unit-testable.
The test that previously locked in "all-queued returns null" now
locks in "all-queued returns plan" — modal-gating is the caller's
contract.
Closes#150 (the user-facing half — bounce wording itself stays as-is).
The plan-mode bounce error and silent write_file are both fundamentally
visual problems: the gate runs before fs writes, but the spinner-then-
JSON-error sequence reads as 'wrote, then failed'; large write_file
content gives no progress signal because formatArgsSummary picks the
short path field.
A. Plan-mode rejection visual
ToolRegistry now adds rejectedReason: 'plan-mode' to the bounce JSON.
The reducer parses tool.end output, sets card.rejected on the marker.
ToolCard swaps the spinner for a red ✗ rejected badge in the trailing
slot and hides the verbose error body — one quick visual cue replaces
a faux-write spinner followed by a wall of JSON.
B. Input size in meta
ToolCard.formatMeta gains a leading '1.2 KB in' fragment when any
string field on args is at or above 1 KB. Generic — no per-tool
special case — so write_file (content), edit_file (long replace),
run_command (long stdin) all benefit. Below 1 KB, nothing shows;
small writes don't get noisy meta.
Tests:
- ui-reducer: tool.end with plan-mode marker flips rejected=true,
regular errors don't trigger.
- tool-card-meta: largestStringInputBytes thresholding + multi-field
selection.
First-run users with a Chinese OS locale saw English by default —
the only signal was config.lang, which doesn't exist on first launch.
Add a third tier between config and the EN fallback: detectSystemLanguage()
reads Intl.DateTimeFormat().resolvedOptions().locale (cross-platform,
no env-var spelunking) and prefix-maps zh* → zh-CN, en* → EN, anything
else → null (falls through).
Priority: user-set config > system locale > EN.
The detection function takes the locale string as a parameter (defaulting
to Intl) so it stays unit-testable without mocking globals.
Add internationalization support for the dashboard, including English and Simplified Chinese.
- Create i18n module to manage language switching and translations
- Replace hardcoded text with translation keys in all panels
- Add language switching functionality to the settings panel
- Implement dynamic loading of translation content
- Update all UI components to use translation functions
Implement runtime language switching, including:
- Add /language command for language switching
- Add Chinese/English translation framework
- Modify state management to support language change events
- Update tests to ensure correct functionality
- Adjust UI components to support internationalized text
User reported the right-side plan sidebar appears during the
PlanConfirm approval modal, before the user has accepted. Same bug
also pinned the plan card above the input prematurely.
Both selectors (App.tsx:297 + SidebarPanel.tsx:39) used the same
predicate: variant === "active" + at-least-one-step-not-done. But
fresh plans have every step in `queued` — the predicate matched
immediately on creation, before approval triggered any state
transition.
Tighten the predicate: "active" now means execution has actually
started — at least one step has left `queued` AND not all steps
are done/skipped. Approval-pending plans (every step queued) and
finished plans (every step done/skipped) both correctly return null.
Exported findActivePlan and added 5 tests covering the regression
plus the surrounding boundaries (variant guards, latest-of-many).
Plan + Error cards advertised inline keybinds in their footers
(`[r] revise` / `[r] retry` etc.) but no handler was ever wired
to scrollback cards — the actual revise/retry flow runs through
PlanConfirm modals via arrow + Enter. Pressing the advertised key
did nothing. Removed the misleading footers; the modal flows are
unchanged.
CtxCard hand-rolled its own header instead of using CardHeader,
breaking the visual contract every other card follows. Routed it
through CardHeader with the same tone/glyph/meta shape.
TaskCard's `meta` ended in a trailing space (`X.Xs · `) and
CardHeader inserts its own space before the trailing badge, so the
rendered output had a double space before the status word.
Also collapsed a dead ternary branch in PlanCard step-color logic
where two arms produced the same value.
UserCard was the only Markdown-rendering card without a CardBox bar —
long pasted prompts wrapped without a continuing accent, breaking the
visual rhythm against the now-accented streaming/reasoning cards.
Audit also turned up the `approval` card kind in cards.ts: declared
in the Card union but with zero producers in src/ or tests/. The
CardRenderer case for it just routed to FallbackCard ("not yet
migrated"). Removed the interface, the union member, and the orphan
case — default branch already catches anything unexpected.
applyEditBlock and edit_file both detect the target file's line ending
(CRLF vs LF) and adapt the model's search/replace text before matching.
Duplicate-match checks, replacement, and diff rendering use the adapted
text. CRLF files are preserved as CRLF; LF files stay LF.
Adds tests for both paths: SEARCH/REPLACE blocks (edit-blocks) and the
native edit_file tool (filesystem-tools), covering LF→CRLF matching,
LF preservation, multi-line CRLF matching, and duplicate-match refusal.
Co-authored-by: Charles H <[email protected]>
PR #126 (0.23.0) gave done assistant Markdown a brand-toned
borderLeft per lamyc's RFC #20 readability ask. The #136 card
redesign extracted CardBox but flipped the done-state color to
FG.faint, defeating the contrast that lets long replies stand
out in scrollback. Now matches the streaming-state color so the
bar reads continuously across the streaming → done flip.
Aborted state stays on FG.faint (correctly de-emphasized).
The /mcp reconnect <name> test fired kickOffMcpReconnect with spec
"node nope", spawning Node against a missing 'nope' module. The
test passed (lifecycle line is returned synchronously) but Node's
MODULE_NOT_FOUND error leaked to stderr in the test runner output.
"node -e 0" exits 0 silently and is cross-platform.
The Reasoning card had three rendering bugs that compounded into a
"feels broken" UX: only one preview line was visible, that line was
the head not the tail of the actual reasoning, and once content
overflowed the viewport the screen jittered on every chunk.
Root causes were three independent issues:
1. The line-budget constant in StreamingCard / ToolCard was off by
two cells, so rendered lines exceeded the terminal width by one
and the terminal wrap-extended each row. Ink's eraseLines(N)
then miscounted against the visible row count and left ghost
rows behind on every render — the visible "jitter."
2. The streaming live region grew row-by-row as text arrived.
Each new line pushed everything below down by one row before
the eraseLines miscount kicked in to make it worse.
3. The settled body sliced last N lines, but reasoning is
typically a single long paragraph — slice(-2) returned the
whole one-line string, then clipToCells truncated from the
head, so the user saw the first cells of the line instead of
the last.
Fixes:
- Wrap card content in `<Box borderLeft borderStyle={{left:"▎"}}>`
via a new CardBox primitive — Ink renders the bar on every
visual row including markdown wrap continuations.
- Streaming preview is fixed at 4 visual rows (live region small
enough that eraseLines miscount can't pile up). Settled
reasoning collapses to last 2 visual rows.
- Pre-wrap content via wrapToCells before slicing, so `slice(-N)`
returns the true visual tail.
- Drop the CardRenderer "yield to content" branch that hid
reasoning entirely while output streamed.
Visual:
- Section + model pills replace the `◆` glyph + emoji prefix.
Model pill color signals model class (flash blue, pro purple,
r1 violet).
- Bar color dims to FG.faint once a card settles — running cards
are accent-bright, done cards are grey.
- Streaming header carries a braille spinner + "thinking…" /
"writing…" status text.
- Settled reasoning header shows duration on the right.
- Settled cards above the tail-2 lines get a single elision row
(`⋯ N ¶ · K tok above · /reasoning last`) instead of a full
head+tail layout.
Closes#132.
Bad-args bugs (e.g. read_file({path:""})) and genuine stuck loops
both used to land in the same place: storm-breaker suppressed the
calls, the loop force-summarized, the turn ended with a loud yellow
"recent-repeat window" warning. Bad-args is the common case and would
self-correct if the model just saw the prior tool error — terminating
the turn forces a /retry that didn't need to happen.
Now the first all-suppressed storm in a turn rewrites the just-
persisted assistant message to preserve the original tool_calls,
stubs role:"tool" responses to honor DeepSeek's "every tool_call
needs a tool message" contract, yields a plain-language warning,
and continues the iter — model gets one shot at a different approach.
Only the second storm in the same turn falls through to the
forced-summary path.
Also softens user-facing copy: "storm-broken" / "recent-repeat
window" / "call-storm suppressed" jargon → "repeat-loop guard" /
"repeated tool call" / "stuck retry loop". Auto-escalation toast
now reads "4× repeat-loop" instead of "4× storm-broken".
Adds REASONIX_STORM_THRESHOLD / REASONIX_STORM_WINDOW env vars for
manual testing of the guard at lower thresholds.
2026-05-02 07:09:58 -07:00
652 changed files with 94888 additions and 15114 deletions
<strong>A DeepSeek-native AI coding agent for your terminal.</strong> Engineered around DeepSeek's prefix-cache, so the savings are real and the loop stays cheap enough to leave on.
<a href="https://oosmetrics.com/repo/esengine/reasonix"><img src="https://api.oosmetrics.com/api/v1/badge/achievement/9e931d80-2050-4b10-902e-44970cc133ad.svg" alt="oosmetrics — Top 2 in Agents by velocity"/></a>
<a href="https://oosmetrics.com/repo/esengine/reasonix"><img src="https://api.oosmetrics.com/api/v1/badge/achievement/556d94b3-61b7-486b-baf2-888b9327deab.svg" alt="oosmetrics — Top 3 in LLMs by velocity"/></a>
<a href="https://oosmetrics.com/repo/esengine/reasonix"><img src="https://api.oosmetrics.com/api/v1/badge/achievement/0f457d4c-efca-4d15-ad2b-139691ff342c.svg" alt="oosmetrics — Top 3 in CLI by velocity"/></a>
</p>
<p align="center">
<img src="docs/assets/hero-stats.svg" alt="94% live prefix-cache hit · ~30× cheaper per task vs Claude Code · MIT terminal-native" width="860"/>
</p>
<br/>
---
<h3 align="center">A DeepSeek-native AI coding agent for your terminal.</h3>
<p align="center">Engineered around prefix-cache stability — so token costs stay low across long sessions, and you can leave it running.</p>
## Quick start
```bash
cd my-project
npx reasonix code # paste a DeepSeek API key on first run; persists after
```
<br/>
<p align="center">
<img src="docs/assets/hero-terminal.svg" alt="Reasonix code mode — assistant proposes a SEARCH/REPLACE edit; nothing on disk until /apply" width="860"/>
</p>
Requires Node ≥ 22. Tested on macOS, Linux, and Windows (PowerShell, Git Bash, Windows Terminal). Get a [DeepSeek API key →](https://platform.deepseek.com/api_keys) · `reasonix code --help` for flags.
<br/>
---
> [!TIP]
> **Cache stability isn't a feature you turn on; it's an invariant the loop is designed around.** That's the whole reason Reasonix is DeepSeek-only — every layer is tuned to the byte-stable prefix-cache mechanic.
## How it compares
> [!NOTE]
> **Real user, single day (2026-05-01):** 435M input tokens, **99.82% cache hit**, ~$12 instead of the ~$61 the same workload would cost with no cache on `v4-flash` — see the [case study](./benchmarks/real-world-cache/README.md). DeepSeek provides the cacheable bytes; the four mechanisms in [Pillar 1](./docs/ARCHITECTURE.md#pillar-1--cache-first-loop) are how Reasonix keeps them cacheable across long sessions.
Plan mode, edit review, MCP, skills, hooks, and sandboxing are all `yes` for Reasonix and most peers — see the feature grid below for what they actually do here.
## Install
Numbers from `benchmarks/tau-bench-lite` (8 multi-turn tasks × 3 repeats, live `deepseek-chat`). [Committed transcripts →](./benchmarks/)
Requires Node ≥ 22. Works on macOS · Linux · Windows (PowerShell · Git Bash · Windows Terminal).
Install Reasonix globally if you want the `reasonix` command available on your `PATH`:
```bash
npm install -g reasonix
reasonix code my-project # paste a DeepSeek API key on first run; persists after
```
Or run it once without installing globally:
```bash
cd my-project
npx reasonix code # always uses the latest package by default
```
Grab a [DeepSeek API key →](https://platform.deepseek.com/api_keys) · `reasonix code --help` for flags.
If you use Reasonix daily, global install is the simplest path. If you just want to try it, use `npx`.
| `reasonix chat` | Plain chat — no filesystem or shell tools. |
| `reasonix run "task"` | One-shot, streams to stdout. Good for pipes. |
| `reasonix doctor` | Health check: Node, API key, MCP wiring. |
| `reasonix update` | Upgrade Reasonix itself. |
Other subcommands (`replay` · `diff` · `events` · `stats` · `index` · `mcp` · `prune-sessions`) are in `reasonix --help` and the [CLI reference](https://esengine.github.io/DeepSeek-Reasonix/#cli).
### Desktop client (prerelease)
A native Tauri client for users who want a GUI over the same loop. Multi-tab, the right-panel shows files the agent has read or edited this session, the same cost / cache / token meters live at the bottom. Same DeepSeek API key, same `~/.reasonix` config — the desktop bundles its own Node runtime, no separate `npm install` step.
Download platform installers from [GitHub Releases](https://github.com/esengine/DeepSeek-Reasonix/releases). The desktop ships as a **prerelease**: the loop and protocol are the same as the CLI, but the UI is still being polished and the installers aren't code-signed yet.
- **macOS** — first launch hits Gatekeeper. One-time fix: `xattr -dr com.apple.quarantine /Applications/Reasonix.app` (or right-click → Open → confirm).
- **Windows** — SmartScreen warns "Unknown publisher". Click **More info → Run anyway**.
- **Linux** — `.deb` and `.AppImage` ship plain, no extra step.
The CLI remains the canonical surface. Anything that lands in the CLI is also available from the desktop's composer.
<details>
<summary><strong>Why DeepSeek-only? — the cache economics</strong></summary>
<summary><strong>Working in another folder · chat vs. code · author a skill</strong></summary>
Cheap tokens alone is half the story. DeepSeek's prefix-cache is **byte-stable**: the cache fingerprints from byte 0 of the prompt. Reasonix's loop is engineered around that — append-only growth, no re-ordering, no marker-based compaction — so the cache prefix survives every tool call.
**Working in a different folder.** Reasonix scopes filesystem tools to the launch directory; pass `--dir` to retarget. Mid-session switching isn't supported by design (memory paths would tangle with stale roots) — quit and relaunch.
By comparison, Claude Code is built around Anthropic's `cache_control` markers (a fundamentally different mechanic). Pointing it at DeepSeek's Anthropic-compat endpoint keeps the cheap tokens but loses the cache hits — markers are ignored, and the underlying prefix isn't byte-stable. Generic-backend tools (Aider / Cline / Continue) hit the same wall from the other direction: their compaction patterns destroy byte stability.
```bash
npx reasonix code --dir /path/to/project
```
At DeepSeek's pricing — $0.07/Mtok uncached, $0.014/Mtok cached — **the difference between 50% and 94% hit is roughly 2.5× on input cost alone.** Same model, same API; the loop's invariants are what changed.
**Picking `chat` vs `code`.**`code` is the default and the only mode with filesystem / shell tools and SEARCH/REPLACE review. `chat` is the lighter, tools-off shell — reach for it when you want a thinking partner with MCP attached but no disk access.
| Reasoning emitted as a structured `thinking` block | R1 sometimes leaks tool-call JSON inside `<think>` tags | a `scavenge` pass that pulls escaped tool calls back out |
| Tool-call args are well-formed JSON | DeepSeek occasionally produces `string="false"` and other malformed fragments | dedicated `ToolCallRepair` heals the common shapes before dispatch |
| Reasoning depth tuned via system-level switches | V4 exposes a `reasoning_effort` knob (`max` / `high`) | `/effort` slash + `--effort` flag for cheap turns |
Cache stability isn't a feature you turn on; it's an invariant the loop is designed around. That's the entire reason Reasonix is DeepSeek-only.
**Author your first skill.** No remote registry — write them directly. Edit the file (`description:` frontmatter + body), then `/skill list`. Add `runAs: subagent` to spawn an isolated subagent loop instead of inlining the body.
```bash
/skill new my-skill # <project>/.reasonix/skills/my-skill.md
/skill new my-skill --global # ~/.reasonix/skills for cross-project use
```
</details>
---
<br/>
## What's in the box
## Configuration
One JSON file at `~/.reasonix/config.json` plus per-project overrides under `<project>/.reasonix/`. The full bilingual reference — every key, every slash command, the on-disk shape of skills/memory/hooks — lives at:
| [MCP servers](https://esengine.github.io/DeepSeek-Reasonix/configuration.html#mcp) | stdio · SSE · Streamable HTTP. One spec format works for both `config.json` and `--mcp`. |
| [Skills](https://esengine.github.io/DeepSeek-Reasonix/configuration.html#skills) | Markdown playbooks the model can invoke. `inline` or `subagent` mode. |
| [Memory](https://esengine.github.io/DeepSeek-Reasonix/configuration.html#memory) | User-private knowledge pinned into the prefix. `user` / `feedback` / `project` / `reference` types. |
| [Web search](https://esengine.github.io/DeepSeek-Reasonix/configuration.html#search) | Mojeek by default; switch to self-hosted SearXNG with `/search-engine`. |
| [Semantic index](https://esengine.github.io/DeepSeek-Reasonix/configuration.html#index) | `reasonix index` — local Ollama or any OpenAI-compatible embedding endpoint. |
<br/>
## What makes Reasonix different
The loop is organized around three pillars. Each one solves a problem generic agent frameworks don't even see — because they were designed for a different cache mechanic.
<sub align="center">
Click through to the full architecture writeup → [Pillar 1 — Cache-first loop](./docs/ARCHITECTURE.md#pillar-1--cache-first-loop) · [Pillar 2 — Tool-call repair](./docs/ARCHITECTURE.md#pillar-2--tool-call-repair) · [Pillar 3 — Cost control](./docs/ARCHITECTURE.md#pillar-3--cost-control-v06)
</sub>
<br/>
## Capabilities
<p align="center">
<img src="docs/assets/feature-grid.svg" alt="Feature grid — cache-first loop, plan mode, MCP first-class, sessions and dashboard, hooks, memory and skills" width="860"/>
| Open community development | yes | — | — | yes |
Reasonix is solo-maintained but designed to grow. Scoped starter tickets — each with background, code pointers, acceptance criteria, and hints — live under the [`good first issue`](https://github.com/esengine/reasonix/labels/good%20first%20issue) label. Pick anything open.
For live cache-hit rates, costs, and methodology, see [`benchmarks/`](./benchmarks/) — the numbers move with model pricing, so they live with the harness, not in the README.
<br/>
## Documentation
- [**Architecture**](./docs/ARCHITECTURE.md) — three pillars: cache-first loop, tool-call repair, cost control
- [**CLI Reference**](./docs/CLI-REFERENCE.md) — every shell subcommand, every slash command, every keybinding
- [**Code of Conduct**](./CODE_OF_CONDUCT.md) · [**Security policy**](./SECURITY.md)
<br/>
## Community
> [!NOTE]
> Reasonix is open source and community-developed. The contributors wall below isn't decoration — every avatar is a real PR that shipped.
Scoped starter tickets — each with background, code pointers, acceptance criteria, and hints — live under the [`good first issue`](https://github.com/esengine/reasonix/labels/good%20first%20issue) label. Pick anything open.
**Open Discussions — opinions wanted:**
**Open Discussions** — opinions wanted:
- [#20 · CLI / TUI design](https://github.com/esengine/reasonix/discussions/20) — what's broken, what's missing, what would you change?
- [#21 · Dashboard design](https://github.com/esengine/reasonix/discussions/21) — react against the [proposed mockup](https://esengine.github.io/reasonix/design/agent-dashboard.html)
- [#21 · Dashboard design](https://github.com/esengine/reasonix/discussions/21) — react against the [proposed mockup](https://esengine.github.io/DeepSeek-Reasonix/design/agent-dashboard.html)
- [#22 · Future feature wishlist](https://github.com/esengine/reasonix/discussions/22) — what would you build into Reasonix next?
**Before your first PR**: read [`CONTRIBUTING.md`](./CONTRIBUTING.md) — short, strict project rules (comments, errors, libraries-over-hand-rolled). `tests/comment-policy.test.ts` enforces the comment ones; `npm run verify` is the pre-push gate. By participating you agree to the [Code of Conduct](./CODE_OF_CONDUCT.md). Security issues → [SECURITY.md](./SECURITY.md).
**Already using Reasonix and willing to help others discover it?** Publish blog posts, articles, screenshots, talks, or videos to [**Show and tell**](https://github.com/esengine/reasonix/discussions/categories/show-and-tell). The project has no marketing budget — community word of mouth is how new users find it. Sustained advocates earn the badge below, displayed next to the contributors wall once awarded:
<img src="https://contrib.rocks/image?repo=esengine/reasonix" alt="Contributors to esengine/reasonix"/>
</a>
**Before your first PR**: read [`CONTRIBUTING.md`](./CONTRIBUTING.md) — short, strict rules (comments, errors, libraries-over-hand-rolled). `tests/comment-policy.test.ts` enforces the comment ones; `npm run verify` is the pre-push gate. By participating you agree to the [Code of Conduct](./CODE_OF_CONDUCT.md). Security issues → [SECURITY.md](./SECURITY.md).
<img src="https://contrib.rocks/image?repo=esengine/DeepSeek-Reasonix&max=100&columns=12" alt="Contributors to esengine/DeepSeek-Reasonix" width="860"/>
</a>
</p>
<br/>
## Non-goals
- **Multi-provider flexibility.** DeepSeek-only on purpose — every layer is tuned around DeepSeek's specific cache mechanic and pricing. Coupling to one backend is the feature.
- **IDE integration.** Terminal-first; the diff lives in `git diff`, the file tree in `ls`. The dashboard is a companion, not a Cursor replacement.
- **Hardest-leaderboard reasoning.** Claude Opus still wins some benchmarks. DeepSeek V4 is competitive on coding; if your work is "solve this PhD proof" rather than "fix this auth bug," start with Claude.
> [!IMPORTANT]
> Reasonix is opinionated. Some things it deliberately *doesn't* do — listed here so you can pick the right tool for your work.
- **Multi-provider flexibility.** DeepSeek-only on purpose. Coupling to one backend is the feature, not a limitation.
- **IDE integration.** Terminal-first. The diff lives in `git diff`, the file tree in `ls`. The dashboard is a companion, not a Cursor replacement.
- **Hardest-leaderboard reasoning.** Claude Opus still wins some benchmarks. DeepSeek is competitive on coding; if your work is "solve this PhD proof" rather than "fix this auth bug," start with Claude.
- **Air-gapped / fully-free.** Reasonix needs a paid DeepSeek API key. For air-gapped or zero-cost runs see Aider + Ollama or [Continue](https://continue.dev).
**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
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.
"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.",
);
returnlines.join("\n");
}
/** Findings prose lives in report.md (hand-written after rendering); this stub keeps the function shape. */
"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.",
"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",
"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:".',
"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)=>{
constanswerLine=extractAnswerLine(reply);
constnums=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".
"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:".',
return{verdict:"fail",note:"no clear color in Answer line"};
},
},
{
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:".',
{id:"m3",level:"medium",task:"A function \`debounceAsync<T extends any[], R>(fn: (...args: T) => Promise<R>, ms: number): (...args: T) => Promise<R>\` in src/util/debounce.ts. Resolves only the latest call's promise; earlier callers reject with an AbortError-like."},
// hard (2) — these touch domain types from the repo
{id:"h1",level:"hard",task:"A function \`extractTestId(file: string, fullName: string, source: string): { id: string, source: 'native' | 'annotation' }\` in src/repair/test-id.ts. If \`source\` contains a '// @reasonix-test-id: <slug>' comment within 3 lines above an it()/test() whose name matches \`fullName\`, return that slug with source='annotation'. Otherwise return \`\${file}::\${fullName}\` with source='native'."},
{id:"h1",level:"hard",task:"A function \`extractTestId(file: string, fullName: string, source: string): { id: string, source: 'native' | 'annotation' }\` in src/repair/test-id.ts. If \`source\` contains a '// @reasonix-test-id: <slug>' comment within 3 lines above an it()/test() whose name matches \`fullName\`, return that slug with source='annotation'. Otherwise return \`${file}::${fullName}\` with source='native'."},
{id:"h2",level:"hard",task:"A function \`pairRedGreen(events: Array<{type:string, test_id?:string, status?:string, ts:number}>): Array<{ test_id: string, red_ts: number, green_ts: number }>\` in src/events/pair.ts. For each test_id, find the most recent fail→pass transition and return one entry per test_id. Ignore test_ids that never went green."},
semanticBanner:"Semantic search isn't enabled for this project.",
semanticBannerDesc:
'Build the index once and the model can find code by meaning ("where do we handle auth failures?") instead of grep on exact strings.',
semanticBannerBtn:"Build it →",
semanticBannerDismiss:"dismiss (don't show again)",
slashCommands:"slash commands",
projectFiles:"project files",
effortTitle:"reasoning_effort — applies next turn",
effortMaxTitle:"max (default — best quality)",
effortHighTitle:"high (cheaper / faster)",
presetTitle:"preset — model commitment",
presetAutoTitle:
"auto — flash baseline; auto-escalates to pro on hard turns (NEEDS_PRO / failure threshold)",
presetFlashTitle:
"flash — always flash; no auto-escalate. /pro still works for one-shot manual",
presetProTitle:
"pro — always pro; ~3× flash cost (5/31 discount). Locks in on hard architecture work.",
editGateTitle:"edit gate — Shift+Tab cycles in TUI",
editReviewTitle:"review — both edits and non-allowlisted shell ask first",
editAutoTitle:"auto — edits auto-apply, shell still asks",
editYoloTitle:"yolo — edits AND shell auto-run, allowlist bypassed",
railSession:"Session",
railTurns:"turns",
railPromptTok:"prompt tok",
railCost:"cost",
railCacheHit:"cache hit",
railToolBudget:"Tool budget",
railSpend:"spend",
railActivePlan:"Active plan",
railProgress:"progress",
statusModel:"model",
statusCtx:"ctx",
statusCache:"cache",
statusTurn:"turn",
statusSession:"session",
statusBalance:"balance",
statusTurns:"{count} turn{s}",
waitingStats:"· · · waiting for live stats",
inflightPhase:"{phase}",
inflightRunning:"running",
inflightThinking:"thinking",
inflightStreaming:"streaming",
inflightWaiting:"waiting",
inflightReasoning:"reasoning {count} ch",
inflightOut:"out {count} ch",
abortBtn:"Abort (Esc)",
confirmBtn:"Apply (y)",
rejectBtn:"Reject (n)",
applyRestBtn:"Apply rest (a)",
flipAutoBtn:"Flip to AUTO (A)",
},
overview:{
loading:"loading overview…",
failed:"overview failed: {error}",
standaloneTitle:"Standalone mode",
standaloneDesc:
"Read-only disk view. Start /dashboard from inside reasonix code for live session state, MCP, and tools.",
cockpit:"Cockpit",
balance:"balance",
tokens7d:"tokens · 7d",
cacheHit:"cache hit",
toolCalls24h:"tool calls · 24h",
budget:"budget",
currentSession:"current session",
noSession:"No live session — /dashboard from inside reasonix code to attach.",
promptTok:"prompt tok",
completionTok:"completion tok",
cost:"cost",
costTrend:"cost · 14 day",
noUsageYet:"no usage yet",
dayAvg:"/day avg",
recentPlans:"recent plans",
noPlans:"No plans yet — submit one with submit_plan.",
toolActivity:"tool activity",
noToolCalls:"No tool calls yet.",
toolsLoaded:"tools loaded",
mcpServers:"mcp servers",
editMode:"edit mode",
version:"Reasonix",
workingDir:"Working directory",
projectRoot:"project root",
noPriorData:"no prior data",
stable:"— stable",
vsPrior:"{arrow} {pct}% vs prior",
active:"active",
allUp:"all up",
yoloWarning:"all prompts bypassed",
checking:"checking",
latest:"latest",
},
usage:{
loading:"loading usage…",
failed:"usage failed: {error}",
records:"{count} records",
dailyUsage:"Daily usage",
dailyMeta:"cost · cache saved · turns",
noData:"No usage data yet — run a turn in reasonix chat / code / run and refresh.",
windows:"Rolling windows",
colWindow:"window",
colTurns:"turns",
colCacheHit:"cache hit",
colCost:"cost (USD)",
colCacheSaved:"cache saved",
colVsClaude:"vs Claude",
colSaved:"saved",
axisTime:"time",
axisUsd:"USD",
axisTurns:"turns",
seriesCost:"cost",
seriesCacheSaved:"cache saved",
seriesTurns:"turns",
mostUsed:"Most used models",
colModel:"model",
},
sessions:{
loading:"loading sessions…",
failed:"sessions failed: {error}",
noSessions:"No saved sessions yet.",
filterPlaceholder:"filter sessions",
msgs:"msgs",
pickHint:"Pick a session on the left to read its transcript.",
resumeTitle:"Resume in TUI",
resumeDesc:
"Mid-session swap requires a restart so the message log can rewind cleanly. Quit your current session, then run:",
loadingTranscript:"loading transcript…",
emptyTranscript:"empty transcript.",
messages:"{count} message{s}",
},
tools:{
loading:"loading tools…",
failed:"tools failed: {error}",
noTools:"No tools registered.",
planMode:"plan mode — writes gated",
colTool:"tool",
colFlags:"flags",
colDesc:"description",
readOnly:"read-only",
write:"write",
flat:"flat",
desc:{
web_search:"Search the public web. Returns ranked results with title, url, and snippet. Call this when the answer depends on current state — events, prices, releases, real-world status.",
web_fetch:"Download a URL and return its visible text content (scripts/styles/nav stripped). Use after web_search when a snippet isn't enough.",
run_command:"Run a shell command in the project root; returns combined stdout+stderr. Allowlisted read-only commands run immediately; mutations are gated by user confirmation.",
run_background:"Spawn a long-running process and detach. Returns a job id for tailing logs, waiting for completion, or killing. Use for dev servers, watchers, and one-shot long jobs.",
job_output:"Read the latest output of a background job. Returns the tail of the buffer and tells you whether the job is still running.",
wait_for_job:"Block server-side until a background job finishes, bounded by timeout. Use instead of polling job_output in a loop.",
stop_job:"Stop a background job. SIGTERM first, SIGKILL after a grace period. Safe to call on an already-exited job.",
list_jobs:"List every background job started this session — running and exited — with id, command, pid, and status.",
remember:"Save a memory for future sessions. Use when the user states a preference, corrects your approach, shares a non-obvious fact, or asks you to remember something.",
forget:"Delete a memory file and remove it from MEMORY.md. Use when the user asks to forget something or a remembered fact is now wrong.",
recall_memory:"Read the full body of a memory file when its one-line summary isn't enough detail.",
read_file:"Read a file under the sandbox root. Supports head/tail/range scoping to save context. Auto-returns a preview for files over 200 lines.",
list_directory:"List entries in a directory. Returns one line per entry, marking directories with a trailing slash.",
directory_tree:"Recursively list entries in a directory as an indented tree. Budget-aware with auto-collapse for large subtrees.",
search_files:"Find files whose NAME matches a substring or regex. Case-insensitive. Skips dependency/build directories by default.",
search_content:"Recursively grep file CONTENTS for a substring or regex. Returns matches in path:line:text format. The right tool for finding references.",
glob:"List files matching a glob pattern, sorted by mtime. Default limit 200, max 1000. Skips node_modules/.git/dist by default.",
get_file_info:"Stat a path under the sandbox root. Returns type, size in bytes, and mtime.",
write_file:"Create or overwrite a file with the given content. Parent directories are created as needed.",
edit_file:"Apply a SEARCH/REPLACE edit to an existing file. The search must match exactly and be unique in the file.",
multi_edit:"Apply N SEARCH/REPLACE edits across one or more files atomically. If any edit fails, no files are written.",
create_directory:"Create a directory (and any missing parents) under the sandbox root.",
move_file:"Rename or move a file or directory under the sandbox root.",
delete_file:"Delete one file under the sandbox root. Refuses directories — use delete_directory for those.",
delete_directory:"Recursively delete a directory under the sandbox root. Pass recursive:false to refuse non-empty directories.",
copy_file:"Copy a file or directory under the sandbox root. Refuses to overwrite an existing destination.",
submit_plan:"Submit one concrete plan for a review gate. Use for multi-file refactors, architecture changes, or anything expensive to undo.",
mark_step_complete:"Mark one step of the approved plan as done. Call exactly once after finishing each step.",
revise_plan:"Surgically replace the remaining steps of an in-flight plan. Done steps are never touched.",
run_skill:"Invoke a playbook from the Skills index. Pass the bare skill name. Subagent-tagged skills spawn an isolated subagent.",
spawn_subagent:"Spawn an isolated subagent for a self-contained subtask. Use for parallel fan-out or when the work needs many file reads.",
todo_write:"In-session task tracker for multi-step work. Replaces the entire list every call. No approval gate or file writes.",
ask_choice:"Present 2-6 alternatives to the user. Use when the user asks for options or you need a preference decision.",
create_skill:"Scaffold a new skill the user can invoke later via /skill. Supports inline and subagent run modes.",
add_mcp_server:"Register a new MCP server in the user's config. Takes effect on the next session. Supports stdio, SSE, and streamable-http.",
},
},
permissions:{
loading:"loading permissions…",
failed:"permissions failed: {error}",
yoloTitle:"YOLO mode",
yoloDesc:
"Every shell command auto-runs, allowlist bypassed. Switch back with /mode review in the TUI.",
project:"project",
builtin:"builtin",
addPrefix:"add a prefix",
addPlaceholder:'e.g. "npm run build" or "deploy.sh"',
clearAll:"Clear all",
alreadyIn:"{prefix} already in list",
added:"added: {prefix}",
removed:"removed: {prefix}",
cleared:"cleared {count} entr{y}",
removeConfirm:'Remove "{prefix}" from this project\'s allowlist?',
clearConfirm:"Wipe every project allowlist entry? Builtin entries are unaffected.",
projectAllowlist:"Project allowlist · {count}",
nothingStored:"Nothing stored yet for this project.",
colNum:"#",
colPrefix:"prefix",
builtinTitle:"Builtin · {count} · read-only",
standaloneWarning:
"Mutations require /dashboard from inside an active reasonix code session — standalone reasonix dashboard can't tell which project's allowlist to edit.",
},
mcp:{
loading:"loading MCP…",
servers:"MCP servers · {count} bridged",
all:"all",
live:"live",
unbridged:"unbridged",
specPlaceholder:"spec — e.g. fs=npx -y @modelcontextprotocol/...",
saved:"saved",
savedRestart:"saved — restart reasonix code to bridge this server",
removed:"removed — restart to drop the live bridge",
removeConfirm:"Remove MCP spec from config?\n\n{spec}",
noServers:"No MCP servers in this session.",
tools:"tools",
inConfig:"in config · not loaded",
unbridgedTitle:"unbridged · in config",
removeBtn:"Remove",
spec:"spec",
whyUnbridged:"Why unbridged?",
whyUnbridgedDesc:
"This spec lives in your config.json but isn't bridged into the live session. MCP servers attach when reasonix code starts; the dashboard alone can't spawn the child process.",
whyUnbridgedHint:"To activate: restart reasonix code, then refresh this dashboard.",
pickHint:"Pick an MCP server on the left to inspect tools / resources / prompts.",
toolsTitle:"Tools · {count}",
resourcesTitle:"Resources · {count}",
promptsTitle:"Prompts · {count}",
colName:"name",
colDesc:"description",
colUri:"uri",
marketplace:"marketplace",
marketplaceSearch:"search the registry…",
marketplaceLoading:"loading registry…",
marketplaceMore:"load 5 more pages",
marketplaceMoreLabel:"load 50 more · showing {shown} / {total}",
marketplaceMoreHint:"fetches more pages from the registry",
noHooks:"No hooks configured. Edit the JSON below to add some.",
colScript:"script",
noProject:"No active project — open /dashboard from reasonix code to edit project hooks.",
saveReload:"Save + Reload",
discard:"Discard changes",
savedReloaded:"saved + reloaded {scope}",
recentRuns:"Recent runs",
noRuns:"No hook runs in the recent session log.",
colWhen:"when",
colPhase:"phase",
colHook:"hook",
colOutcome:"outcome",
},
skills:{
loading:"loading skills…",
filterPlaceholder:"filter skills",
project:"project",
global:"global",
builtin:"builtin",
newSkill:"new skill",
noDescription:"(no description)",
runs7d:"runs · 7d",
pickHint:"Pick a skill on the left, or create a new one above.",
readOnlyBuiltin:"read-only · builtin",
builtinDesc:
"Built-in skills ship with Reasonix; the model picks them up automatically. To customize, create a project- or global-scoped skill with the same name.",
saved:"saved {scope}/{name}",
deleteConfirm:"Delete skill {scope}/{name}?",
reloadHint:"re-loaded on next /new or session restart",
},
system:{
loading:"loading health…",
failed:"health failed: {error}",
healthChecks:"Health checks",
version:"version",
checking:"checking",
latest:"● latest",
outOfDate:"● out of date",
versionPending:"version check pending",
upToDate:"up to date",
latestVer:"latest: {version}",
sessions:"sessions",
ok:"● ok",
memory:"memory",
semanticIndex:"semantic index",
built:"● built",
none:"— none",
runIndex:"run reasonix index to build",
usageLog:"usage log",
backgroundJobs:"background jobs",
noSession:"— no session",
running:"{count} running",
attachHint:"attach a session to see jobs",
shellSpawn:"shell + spawn",
paths:"paths",
home:"home",
sessionsPath:"sessions",
memoryPath:"memory",
semanticPath:"semantic",
usagePath:"usage",
},
plans:{
loading:"loading plans…",
failed:"plans failed: {error}",
noPlans:"No archived plans yet — run a turn that calls submit_plan and mark_step_complete.",
filterPlaceholder:"filter plans",
active:"active",
done:"done",
idle:"idle",
steps:"steps",
pickHint:"Pick a plan on the left.",
noTitle:"(no title)",
stepTimeline:"Step timeline · {done} / {total}",
step:"step {n}",
},
semantic:{
codeRequired:"Semantic — code-mode required",
indexBuilt:"index built",
noIndex:"no index yet",
ready:"ready",
setupNeeded:"setup needed",
installOllama:"Install Ollama",
installOllamaDesc:
"Reasonix doesn't run package managers for you. Install Ollama first, then come back:",
macWindows:"macOS / Windows:",
download:"download from ollama.com/download",
linux:"Linux:",
refreshHint:
"Refresh after install — this panel will offer to start the daemon and pull {model}.",
daemon:"Daemon",
daemonDesc:"ollama is on your PATH but the HTTP daemon isn't reachable.",
startDaemon:"Start daemon",
runsOllama:"runs ollama serve detached",
model:"Model",
modelMissing:"{model} isn't installed yet.",
modelSize:"~270 MB on first pull.",
pulling:"pulling…",
pullModel:"Pull {model}",
indexStatus:"index status",
builtStatus:"● built",
incompatibleStatus:"● incompatible",
chunks:"chunks",
files:"files",
dim:"dim",
size:"size",
lastBuild:"last build",
builtWith:"built with",
currentTarget:"current target",
incompatibleHint:"This on-disk index was built for a different provider or model. Run Rebuild to replace it.",
runIndexHint:"Run an index to enable semantic_search.",
reIndex:"Re-index",
build:"Build",
rebuild:"Rebuild",
stop:"Stop",
provider:"provider",
providerType:"service type",
openaiCompat:"openai-compatible",
apiUrl:"API URL",
apiKey:"API key",
apiKeyStoredNote:"API key is stored in ~/.reasonix/config.json — do not share that file.",
customRequestBody:"custom request body",
invalidCustomRequestBody:"Custom request body must be valid JSON: {error}",
customRequestBodyMustBeObject:"Custom request body must be a JSON object.",
saveBeforeIndex:"Save semantic settings before starting an index.",
extraBody:"extra body",
keepExistingKey:"leave blank to keep existing key",
remoteProvider:"Remote embedding provider",
remoteProviderDesc:
"Configure the full OpenAI-compatible embeddings URL here. Reasonix will send requests exactly to the URL you provide.",
ollama:"ollama",
binary:"binary",
found:"found",
missing:"missing",
daemonStatus:"daemon",
up:"up",
down:"down",
pulled:"pulled",
indexConfig:"index config",
reset:"reset",
excludeDirs:"exclude dirs",
excludeFiles:"exclude files",
excludeExts:"exclude exts",
excludePatterns:"exclude patterns",
glob:"glob",
respectGitignore:"respect .gitignore",
maxFileBytes:"max file bytes",
skipLarger:"skip files larger than ~{size} MiB",
preview:"Preview",
searchPlaceholder:"describe what to find — 'where do we handle abort signals'",
searching:"searching…",
results:"{count} result{s} · {ms}ms · {model}",
noMatches:"No matches above the score threshold.",
previewSummary:"Preview — would index {included} file(s), skip {skipped}",
nothingSkipped:"nothing skipped — all walked files would be indexed.",
firstIncluded:"first {count} included file(s)",
job:"Job",
phaseSetup:"preparing",
phaseScan:"scanning files",
phaseEmbed:"embedding chunks",
phaseWrite:"writing index",
phaseDone:"done",
phaseError:"error",
phaseCancelled:"cancelled",
setupFailed:"setup failed",
stopping:"stopping",
scanned:"scanned {count}",
changed:"changed {count}",
skipped:"skipped {count}",
chunksProgress:"{done} / {total} ({pct}%)",
result:"result",
added:"added {count}",
removed:"removed {count}",
failed:"failed {count}",
skippedFiles:"{total} files ({details})",
rebuildStarted:"rebuild started",
incrementalStarted:"incremental index started",
stopRequested:"stopping requested — current chunk batch will finish first",
/** Browser extensions (userscripts, ad blockers) inject scripts that throw into our window. Their errors land in the global handlers as if they were ours — see #818. Filter them by origin. */
if(ext==="md")return"# Example Document\n\nThis is a sample markdown file.\n\n## Section\n\n- Item 1\n- Item 2\n\n```js\nconsole.log(\"hello\");\n```";
Loaded 100 of 652 files, more files were not shown because too many files have changed in this diff.
Show more
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.