LOCAL-FIRST · MULTI-AGENT-FIRST · OPEN SOURCE
Keep agents moving.Catch what needs you.
Crewlight gathers current AI coding-agent status on your machine, then separates background progress from the sessions waiting for input, permission, or recovery.
v0.5.0 is a stabilization candidate. The latest public release remains v0.4.0.View releases
Attention radar
The core stays close
The daemon listens locally unless you deliberately configure a trusted development path.
Signals over noise
Input, permission, failure, rate limits, and staleness rise above background activity.
Status, not transcripts
Complete prompts, transcripts, tool I/O, and raw payloads stay out of normalized output.
THE ATTENTION MODEL
A small set of states. A much clearer workday.
Crewlight turns source-specific activity into a consistent local view, ordered by what deserves attention rather than by whichever agent spoke last.
Let it run
Running and tool-using sessions stay visible without pulling you away from the task in front of you.
- running
- using_tool
Step in at the right moment
Requests for input or permission become explicit action items instead of disappearing into terminal tabs.
- waiting_input
- waiting_permission
Catch trouble early
Failures, rate limits, and sessions with no recent signal stay easy to distinguish from healthy work.
- failed
- rate_limited
- stale
A BOUNDED LOCAL PATH
Useful context in. Sensitive payloads out.
Every integration crosses an explicit normalization boundary before its status reaches the local daemon or a Crewlight surface.
Read the architecture notes- OBSERVE
Receive explicit activity
Documented hooks, official notifications, or manual commands produce bounded source signals.
No private API scraping - NORMALIZE
Keep only safe fields
Source adapters retain status, identity, location, and short safe messages while dropping complete platform payloads.
Allowlist at the adapter boundary - AGGREGATE
Group current sessions locally
The daemon validates events and groups them with Crewlight-owned, namespaced session keys.
In memory · loopback by default - SURFACE
Show what needs attention
Desktop, companion, dashboard, and CLI turn current state into a readable, read-only view.
Visibility without agent control
ONE LOCAL CORE · FOUR SURFACES
Stay close to the work without living in every terminal.
Crewlight uses a desktop-first hierarchy: a command center for local service controls, a companion when you only need a glance, and developer surfaces when you need detail.
Crewlight Desktop
Home, service controls, diagnostics, integration setup, demo sessions, appearance, and companion controls in one local application.
Command centerFloating companion
A compact, optional surface that keeps active, attention, failed, and stale counts nearby.
Always nearbyBrowser dashboard
A secondary, loopback-only view for current sessions, setup snippets, and local diagnostics.
Read-only viewCLI
Explicit setup snippets, ingest, status, doctor, demo, scripting, and standalone workflows.
Automation surfaceEXPLICIT INTEGRATION BOUNDARIES
Confidence is labeled, not implied.
Different tools expose different public integration points. Crewlight keeps those differences visible instead of claiming every adapter has the same coverage.
Inspect every integration boundary| Source | Current level | Boundary |
|---|---|---|
| Claude Code | Precise | Documented lifecycle hooks; observation only. |
| Codex hooks | Precise lifecycle | Documented session, prompt, tool, permission, and stop events. |
| Codex notify | Narrow official | The documented agent-turn-complete notification. |
| OpenCode | Verification pending | Implemented local plugin events; end-to-end verification remains. |
| Cursor | Manual / experimental | Explicit commands only; no private automatic lifecycle claim. |
| Custom ingest | Manual | Caller-supplied normalized events and bounded local probes. |
THE HONEST BOUNDARY
A radar, not an autopilot.
Crewlight is designed to help you notice current local activity. It deliberately stops before orchestration, surveillance, or cloud history.
No cloud service
Agent state is not sent to a Crewlight-hosted account or observability backend.
No agent control
Crewlight does not approve permissions, answer prompts, or steer agent turns.
No transcript archive
Complete prompts, transcripts, tool input/output, and raw platform payloads are not retained in normalized sessions.
No hidden integration
Public hooks, official notifications, plugins, and explicit commands replace private API scraping or screen watching.
SOURCE AVAILABLE NOW
See the boundary in code.
Crewlight is built in public under the MIT license. Inspect the event schemas, adapter allowlists, desktop surfaces, tests, and release gates before you decide where it fits in your workflow.