Safety and Recovery
Centaur treats model output, file paths, clipboard contents, and remote MCP requests as untrusted input.
Workspace boundary
Section titled “Workspace boundary”- The active workspace is the complete file read and write boundary.
- Canonical path checks reject traversal and symlink escapes.
- MCP tools cannot choose their own workspace. The root is fixed when the server is launched or installed.
- Undo history is scoped to the workspace that created it.
- Project-check sandboxing:
centaur check --run --sandboxuses macOS Seatbelt or Linux Bubblewrap. If neither backend is available, Centaur refuses the request instead of running the command unsandboxed. Windows checks still use an explicit command list, a scrubbed environment, a timeout, and supervised child-process cleanup, but Windows does not currently have an OS filesystem sandbox backend. - Repair handoffs:
centaur check --run --repairremoves known credential patterns and the workspace, Centaur-home, and user-home roots from captured output. It limits the included output to 6,000 characters. Credential detection is deliberately conservative, so inspect the prepared message before sending it.
Patch transaction
Section titled “Patch transaction”A malformed, missing, ambiguous, stale, or unsafe block stops the entire patch. No partial changes are ever written.
- Centaur parses the complete response.
- Every Search/Replace block is validated and planned in memory.
- The exact resulting diff is shown for review.
- MCP returns a workspace-bound
plan_id; raw unreviewed MCP writes are refused. - Every source file is checked again for changes after review.
- An undo snapshot is written before any target file.
- Files are written through temporary sibling paths.
If a later write fails, Centaur uses the snapshot to restore earlier writes. It reports the recovery command when automatic restoration cannot finish.
Dry runs use the same parser and planner but do not write files or history.
Undo and Recovery
Section titled “Undo and Recovery”Each successful apply records original and applied content. Undo restores a session only when the current files still match the state that session wrote. Later user work is not overwritten silently.
# Revert the latest sessioncentaur undo
# Revert a specific older sessioncentaur undo <session-id>Older history records without applied-state checks are refused. Their original contents remain available for manual recovery. You can inspect .centaur/history/ to manually copy original file contents back if needed.
Context and redaction
Section titled “Context and redaction”Centaur has no Centaur cloud upload. A browser hand-off can disclose your request and selected context to your chosen AI provider. Pasting text or attaching a file may transfer content to that provider before you press Send. Review the selected files and redaction setting before the hand-off.
A configured remote MCP client can receive content returned by get_context. Enable remote access only for a client and workspace you trust.
prepare_handoff never sends context. It records file fingerprints locally and refuses to return detected credentials unless redaction is enabled. The user or host client remains responsible for the separate disclosure action.
Secret scanning is heuristic. Review an export even when no findings are reported.
--redact rewrites only a temporary export copy. It does not clean the source repository or Git history. Redacted lines may no longer be usable as exact Search text.
Destination applications
Section titled “Destination applications”Centaur does not place Chrome, ChatGPT, Claude, or another destination application inside Centaur’s project-check sandbox. Those applications keep their own OS and account boundaries.
For a manual browser hand-off on Windows or Linux, Centaur opens the selected browser and copies bounded text for you to paste and send. On macOS, Centaur can place the hand-off in a verified composer; you still press Send.
Current development builds also offer Code and Research sending routes on Windows that can submit prepared context and capture replies. The public installer has not yet been refreshed for the current interface. Destination support and live verification are limited; see Getting Started for the routes and their current limits. Opt-in automatic sending for authorized agent jobs can skip the Enter confirmation. Sending never approves returned edits.
For a local MCP connection, the client can call only the Centaur tools installed for one canonical workspace. The server does not accept a tool argument that switches to another workspace, and applying an edit requires a reviewed, workspace-bound plan.
Remote MCP
Section titled “Remote MCP”The HTTP transport:
- Binds only to loopback.
- Requires a bearer token.
- Limits request size.
- Rejects unexpected origins.
- Exposes the same workspace-scoped dispatcher as stdio.
Public HTTPS and provider-compatible OAuth must terminate at a trusted tunnel or reverse proxy. Keep
CENTAUR_MCP_TOKENout of command lines, configuration files, logs, and source control.
Local model fallback
Section titled “Local model fallback”Ollama repair is optional and local. Its output is still untrusted patch text. The repaired files return to the same deterministic validation and transactional write path:
centaur --llm auto --clipboard --yesReporting vulnerabilities
Section titled “Reporting vulnerabilities”Use the private security form. Do not post vulnerabilities as public issues or include real credentials, private source, or personal paths in a report.