For developers

Wakes

Let a coding agent hand off a long command and stop waiting: the same session is told the result the moment it finishes, with no polling. Scripts and agents can also tell you how something stands, and you hear only when that changes.

FreeMacCoding agent

Use itHow it worksLimitsWhere it's kept

Use it

• ~/.jevie/bin/jevie-run --wake "fix any failures" -- npm run test:allThe tests run in the background; the agent is told how they ended, then fix any failures
• jevie_run with command, then, cwd and to: "none"The same from any agent with Jevie's MCP server
• ~/.jevie/bin/jevie-run --to none -- ./build.shYou are told instead, by a notification
• ~/.jevie/bin/jevie-run --to acp:<id> -- make releaseA background Codex, Gemini or OpenCode session is told
• ~/.jevie/bin/jevie-run --cwd ~/Repos/app -- npm testRuns in that folder instead
• ~/.jevie/bin/jevie-run --listThe wakes still waiting, and who is told
• claude --dangerously-load-development-channels server:jevieClaude Code started so wakes arrive whole, not typed
• ~/.jevie/bin/jevie-notify --incident backup --state fail "Backup failed" --detail "rsync exited 23"You are told once, on the Mac and your phone, that the backup is failing
• ~/.jevie/bin/jevie-notify --incident backup --state ok "Backup ran"After a warning or a failure, one Resolved notice closes it
• ~/.jevie/bin/jevie-notify --listEvery incident on record, how it stands and its last detail

How it works

The agent ends its turn instead of sitting on a long build or test run. When the command finishes, the session that started it gets a message with how it ended, the last lines of output, where the full log is, and what you asked it to do next.

Nothing is lost if Jevie is not running when the command ends: the result waits and is delivered when Jevie starts.

An incident is anything a script or agent checks again and again: a backup, a deploy, a disk, a test run. Each check says ok, warn or fail under the incident's name. You are told only when the state changes: when it first goes wrong, when a warning becomes a failure or the other way, and once when it is ok again.

The same state said again updates the record and tells no one, so a check every minute is not a notification every minute. The Mac shows the headline and the detail; your phone shows the headline only, so what a log says stays on the Mac.

Limits

• Only commands started with jevie run are watched.
• The session is found on its own only for Claude Code; other agents are named with --to acp:<id>, or you are told instead.
• A Claude Code session that has ended is not reopened; you are told instead.
• An incident is told only when its state changes; to hear it again, it has to go ok first.
• Your phone shows an incident's headline, never its detail.

Where it's kept

Wakes in ~/.jevie/wakes/<id>.json, runs and their output in ~/.jevie/runs/, incidents in ~/.jevie/incidents.json. Channel sockets in ~/.jevie/channels/<pid>.sock (on Windows, a named pipe per session, \\.\pipe\jevie-channel-…-<pid>).

In Jevie, help wake answers from this page as you type.

Related

Updated 30 October 2026 · Something wrong or missing? Tell us