Support
jotkit runs entirely on your machine, so most problems are local and quick to pin down.
Email support@jotkit.dev and include the output of jotkit doctor. That one command reports your Node version, ledger, config, daemon, pairing state and listening agents, and usually identifies the problem on its own.
Start here
jotkit doctorEvery check it prints is either ok or FAIL with the reason. Work down the failures in order, since a stopped daemon makes everything below it fail too.
Common problems
The extension says it cannot reach the daemon
Run jotkit daemon status. If it is running, check that the port it reports matches the port in the extension settings. jotkit falls back to the next free port when 4817 is taken and remembers the one it chose, so the two can drift apart after a port conflict.
The daemon will not start
The error names the real cause. If every port in the scan range is busy, set an explicit one under "daemon": { "port": 4900 } in ~/.jotkit/config.json. If a stale process is holding the lock, jotkit daemon stop --force clears it.
The toolbar does not appear
jotkit stays hidden until you switch it on for a tab. Click the toolbar icon, or pressCmd+Shift+Y (Ctrl+Shift+Y on Windows and Linux). If the shortcut does nothing, check it has not been claimed by another extension at chrome://extensions/shortcuts.
My agent is not picking anything up
Comments tagged reference or inspiration, and comments scoped global, are context rather than work. Runjotkit comments list --actionable to see exactly what an agent would treat as a job.
I lost my pairing code
Run jotkit pair for a fresh one. Old codes expire after ten minutes.
Reporting a bug
Email support@jotkit.dev with:
- the output of
jotkit doctor; - what you expected and what happened instead;
- your operating system and browser version;
- anything relevant from
~/.jotkit/daemon/daemon.logif the daemon is involved.
Your ledger is yours and nothing is sent anywhere automatically, so please include only what you are comfortable sharing.
Security
If you believe you have found a security issue, emailsupport@jotkit.dev with the details rather than posting publicly, and allow a reasonable window for a fix before disclosing.
Everything else
The documentation covers install, pairing, repository scoping, connecting agents over MCP or ACP, the background supervisor, and how the ledger works.