Core Features
Agent Status & Notifications
How Paradev knows what your agents are doing, and how it tells you
The Activity Strip
Each workspace in the sidebar shows an activity strip:
- Running agents and open ports appear inline on the workspace item.
- Running and PR state persist across restarts.
- Workspaces with live work are emphasized.
- Agent chips show only when several agents run in that workspace.
If a workspace shows as running after you've stopped its agent (for example after force-quitting the agent), use Clear Status on the workspace to reset the indicator.
How Status Is Detected
Paradev installs lifecycle hooks and command wrappers into each agent's config (the entries in ~/.paradev/bin and files like superset-hooks). Those hooks report when an agent starts, finishes, or is waiting for input. Status therefore works only for agents launched through Paradev, and removing the hooks disables status and notifications.
The hooks no-op outside Paradev terminals (they check for a Paradev-supplied env var). To remove them from an agent's config entirely, turn off the agent's Paradev hooks toggle in Settings → Agents.
Notifications
- Finished / waiting for input: you are notified when an agent finishes or pauses for your input. Configure sounds in Settings.
- Support varies by agent. Claude Code reports both finished and waiting states. Some agents send no waiting-for-input signal, so you get completion notifications only. See Supported Agents.
- Inline prompts: agents can pause to ask questions, request tool approval, or ask for plan review directly in the chat pane, and the workspace is flagged as needing attention.
Dock Badge
The macOS dock icon shows a badge for workspaces with unread activity or that need your attention.

macOS only shows dock badges when Paradev has notification permission. If you don't see badges, check System Settings → Notifications → Paradev.