At a glance
An MIT-licensed coding harness whose Rust runtime implements an adaptive model-and-tool loop, repository and shell mutation, automatic context compaction, durable project memory, delegated agents, MCP, skills, policy rules, OS shell sandboxing on supported platforms, persistent checkpoints, and structured headless execution. The same core is exposed through terminal, desktop, local web, editor, and automation surfaces.
Good choice if
- Multi-provider or self-hosted endpoint workflows that need one harness across terminal, desktop, web, and editor clients
- Long repository tasks that benefit from automatic compaction, durable project memory, resumable goals, and delegated subagents
- Local macOS or Linux execution that needs explicit permission policy, OS shell sandboxing, structured events, and file checkpoints
Check before choosing
- The cache-oriented design is documented, but the project's cost and cache-hit marketing figures are not admitted as independent product measurements
- The OS sandbox is enabled by default for Bash on macOS and supported Linux installations, but Windows shell commands run without that isolation; network access is allowed by default, and users can disable the sandbox
- Workspace file tools remain path-confined, but installed MCP servers, hooks, plugins, language servers, and other trusted extensions have separate execution boundaries; MCP tool calls do not receive Reasonix's per-tool approval flow
See 5 more considerations
- Checkpoints cover previewable Reasonix file-edit tools and conversation state, not Bash, move operations, remote services, or other external side effects; rewind can overwrite file changes made outside Reasonix after the snapshot
- Headless writes require an explicit automatic permission mode; deny rules still apply, but unattended use removes interactive approval and needs independent time, spend, credential, and network limits
- Self-hosted model support means connecting an OpenAI-compatible or Anthropic-compatible endpoint; Reasonix does not bundle a local model runtime
- The local web server binds to loopback without authentication by default; remote exposure requires an explicit token or password and an appropriate network boundary
- The built-in web tool retrieves page content rather than controlling an interactive browser; browser automation would require a separately trusted extension such as an MCP server