Claude Code
Mobile control, approvals, and observability for Claude Code agents
Overview
Claude Code is powerful, but running agents in production hits real walls: background agents die after minutes, tool permissions auto-deny without a human, there's no per-agent isolation, and you can't control anything from your phone.
Nod solves these with two complementary integration paths — the Nod CLI for persistent daemon agents, and the Nod Channel for native Claude Code sessions. You can also build your own connection using the API documentation.
CLI vs. Channel
| Nod CLI | Nod Channel | |
|---|---|---|
| How it works | Persistent daemon wrapping Claude Code | MCP server inside native Claude Code sessions |
| Runs as | Background service (launchd/systemd) | Inside your existing claude or claude --channels session |
| Best for | Always-on agents, scheduled tasks, mobile-first workflows | Interactive coding with Nod powers, multi-session orchestration |
| Agent isolation | Full: per-agent permissions, MCPs, tools, memory, instructions | Session-level: Nod adds communication layer to existing sessions |
| Survives restarts | Yes — OS service with auto-restart and caffeinate | No — lives within the Claude Code process |
| Parallel agents | Multiple daemons, each with scoped resources | Multiple Claude sessions, each with Nod Channel connected |
| Mobile control | Full: chat, approvals, tasks, activity from phone | Full: same Nod app experience |
| Setup | nod connect + nod up | claude mcp add nod-channel |
When to use which
Use the CLI when you want:
- Agents that run 24/7 in the background without a terminal
- Per-agent resource scoping — agent A gets Gmail, agent B gets GitHub
- Custom instructions and memory per agent
- Scheduled tasks that run automatically on cron
- The full "AI workforce managed from your phone" experience
Use the Channel when you want:
- Nod powers inside your regular terminal Claude Code sessions
- Multiple Claude Code sessions working in parallel on the same project, all connected to Nod
- To use
claude --channelswith Telegram/Discord AND Nod simultaneously - Quick setup without daemon management
- Agent teams where each teammate has Nod communication
Using both together
The CLI and Channel aren't mutually exclusive. A common setup:
- CLI daemon for your always-on personal assistant (emails, scheduling, monitoring)
- Channel in your interactive coding sessions when you want to step away and continue from your phone
Both connect to the same Nod app. You see all agents — daemon and channel-based — in one unified dashboard on your phone.