Skip to content

Diagnostics

Diagnostics and Issue Reports

Run the right checks before asking for help, separate daemon problems from client problems, and share only redacted output.

Qi-Xuan LuUpdated 5 min read

At a glance

01

Start diagnostics with /init, origin status, origin doctor, and an MCP dry-run for the client that fails.

02

Good issue reports include environment and redacted diagnostics, not private memory contents or full ~/.origin archives.

01

Run the short checklist

Use the smallest command set that separates daemon health, client wiring, and port conflicts.

If you are in Claude Code, start with /init. If you are in another client, use the terminal commands and the client's MCP status UI.

Diagnostics

# Claude Code
/init

# Terminal
~/.origin/bin/origin status
~/.origin/bin/origin doctor
~/.origin/bin/origin mcp add codex --dry-run
lsof -nP -iTCP:7878 -sTCP:LISTEN

02

Read the failure layer

If status or doctor cannot reach the daemon, focus on runtime setup, service registration, platform paths, and port 7878.

If the daemon is healthy but the client has no tools, focus on MCP configuration, client restarts, and whether the client is launching the expected origin-mcp path.

03

Port 7878 conflicts

Only one Origin daemon should own the local database. A stale daemon from another checkout can make setup look broken even when the current install is fine.

If port 7878 is occupied, identify what process is listening before restarting clients or changing configuration.

04

What to include in an issue

Include the client name, operating system, install path you used, exact command, expected behavior, actual behavior, and redacted diagnostic output.

Mention whether /init or origin doctor passed, and whether a small capture/recall round trip works from any client.

  • Client: Claude Code, Codex, Cursor, Claude Desktop, Gemini CLI, VS Code, or other.
  • Platform: macOS, Linux, Windows, Docker, VM, or WSL if relevant.
  • Runtime: plugin setup, npx setup, source build, or migrated install.
  • Diagnostics: /init output, origin status, origin doctor, and MCP dry-run output after redaction.
Open a GitHub issue

05

What to redact

Do not paste private captures, client names, repo names, API keys, tokens, full session logs, or full ~/.origin archives into public issues.

Replace sensitive project text with placeholders while keeping the structure of the failure visible. If the report is security-sensitive, use the private advisory path instead.

Security reporting

Next

FAQ

Short answers to the adoption questions people ask before and after installing Origin.

Read next