JIXU DOCUMENTATION
Reference TUI
Operate durable Threads from the native Jixu terminal interface.
The jixu command is the reference application built on the same public Harness and Thread path exposed by the Framework.
Installation
npm install -g jixu-ai
jixuThe npm launcher selects the compatible native package. Supported targets are macOS arm64 and Linux x64 with glibc. An unsupported target fails with an actionable message and does not download or compile source as a fallback.
Commands
| Command | Action |
|---|---|
/new | Create and select an empty Thread |
/resume | Select a previous compatible Thread |
/clear | Clear selected Thread context without erasing Event history |
/continue | Continue a paused Thread |
/pause | Pause after the current dispatch boundary |
/approve | Allow the waiting Tool call once |
/deny | Deny the waiting Tool call |
/resolve <occurred|not-occurred|abandon> | Record an operator decision for the current unknown Tool outcome |
/events | Inspect durable Event history |
/state | Inspect the current authoritative projection |
/replay | Rebuild State from Events only |
/fork <event-id> <input> | Continue from an earlier Event as a child Thread |
/mode <standard|ultra> | Change durable Thread reasoning mode |
/config | Edit API, endpoint, Key, model, Tools, and permissions |
/quit | Exit and restore terminal ownership |
Type / to open the current command catalogue. Because these docs follow repository main, the menu remains the authority for what an installed release supports.
Approval and outcome decisions
Approval and outcome resolution answer different questions:
/approveor/denydecides whether a pending Tool may dispatch./resolverecords what external verification established after a dispatched Tool ended with an unknown outcome.
When resolution is required, the Workspace shows the exact Tool, Tool-call identity, error code, and position in the unresolved set. Use the pointer-operable OCCURRED, NOT OCCURRED, or ABANDON UNKNOWN actions, or enter the matching /resolve command.
The TUI resolves one retained Effect at a time. Partial resolution remains visibly waiting; the final decision returns through the ordinary Thread API and Agent continuation rather than changing UI state directly.
Workspace surfaces
The main workspace keeps four questions visible:
- NOW — what observable phase is active;
- PLAN — direct execution or the current accepted Plan;
- VERIFIED — outcomes that have become durable evidence;
- NEEDS YOU — approval or uncertainty requiring intervention.
These surfaces derive from Events, State, and transient Signals. They do not invent hidden reasoning, percentages, or time estimates.
Local configuration
Jixu stores accepted BYOK configuration in:
~/.jixu/settings.jsonThe file is user-only on POSIX systems. Keys remain configuration input; they are never copied into Thread Events.