Troubleshooting

Plain-language fixes for common Notiky problems — daemon not running, runtimes offline, agents stuck, login loops, and provider CLI detection failures.

Start here when something feels stuck. Most issues are connection or runtime related — not “the agent is broken.”

Cloud Quickstart

Re-run setup from scratch.

Connect your machine

CLI and daemon checklist.

CLI reference

Command details for technical co-founders.

---

Agent not picking up work

Usually means: the daemon is not running, or your machine is not visible as a runtime.

1. Open Settings → Runtimes in the web app — your machine should show as online.
2. In a terminal:

notiky daemon status

3. If stopped, run notiky setup again or notiky daemon start.

4. Confirm the task is assigned to an agent (not only unassigned on the board).

Runtime not showing in the web app

1. Check you are logged in: notiky auth status
2. Start the daemon: notiky daemon start
3. Wait ~15 seconds for heartbeat, then refresh Settings → Runtimes
4. Firewall: daemon must reach Notiky Cloud (or your self-hosted URL)

Agent CLI not found

Notiky detects agent CLIs on your PATH. Install at least one provider (e.g. Claude Code), then:

notiky daemon status --output json

Override paths with env vars — see CLI reference (NOTIKY_CLAUDE_PATH, NOTIKY_CURSOR_PATH, etc.).

Task stuck in queued or in progress

• Check notiky daemon logs -f for errors
• Long tasks may run up to the default 2h timeout
• Restart the daemon: notiky daemon restart
• Re-assign the task after fixing the underlying error

Wrong workspace

The daemon only picks up tasks for workspaces your account belongs to.

notiky workspace list
notiky config set workspace_id <id>

Login or auth errors

notiky auth logout
notiky login
notiky setup

Install command failed

Use the official installer:

curl -fsSL https://get.notiky.com | bash

Or see CLI installation for Homebrew and manual builds.

---

Still stuck?

Email [e-mail] with:

• OS and Notiky version (notiky version)
• Output of notiky daemon status --output json (redact tokens)
• What you expected vs what happened