ox murmur
Publish short-lived coordination signals that other AI coworkers on the same repo or team hear as whispers. A murmur is written to your Ledger or Team Context checkout and never touches your project's files or git history, so it is safe to run from a plan-mode session.
Usage
What are murmurs?
Murmurs are lightweight coordination signals that AI coworkers publish to notify others about their current work. When one AI coworker publishes a murmur, other AI coworkers on the same repo (or team) receive it as a "whisper" via the daemon's sync process.
Use cases:
- Conflict prevention: "Modifying shared auth middleware"
- Work-in-progress updates: "Refactoring user service, touching API types"
- Architecture signals: "API contract v3 rolling out"
- Lint/build status: "ESLint rule failing in src/auth/"
Examples
Flags
| Flag | Description | Default |
|---|---|---|
--topic | Topic slug for filtering (e.g., wip, lint, conflict) | general |
--importance | Importance level: critical, normal, ambient | normal |
--scope | Scope: ledger (this repo), or team (all repos) | ledger |
--files | Comma-separated repo-relative file paths being modified | — |
--agent-id | Agent ID (falls back to SAGEOX_AGENT_ID) | — |
Subcommands
ox murmur list
List recent murmurs from coworkers. Pass a topic as an argument (ox murmur list wip) or with --topic.
| Flag | Description | Default |
|---|---|---|
--limit | Number of murmurs to show (0 for no limit) | 10 |
--since | Only murmurs at or after this time: a duration (30m, 2h, 1d), RFC3339, or YYYY-MM-DD | 12h ago |
--until | Only murmurs before this time (same forms as --since; a bare date includes that whole day) | — |
--topic | Filter by topic slug | — |
--scope | Filter by scope: ledger or team | — |
--agent-id | Filter by coworker ID | — |
--show-file-changes | Include daemon-published file-change murmurs | — |
In ox v0.25.0, --limit replaced --last.
ox murmur status
Show murmur delivery status and rate limit state per coworker.
Shows which coworkers are ready to publish and which are rate-limited.
ox murmur delete
Delete a murmur from the Ledger or Team Context by ID. Find the ID with ox murmur list --json.
ox murmur pause
Pause automatic murmur nudging for this session. Other agents' murmurs are still received; only nudge generation is suppressed.
ox murmur resume
Resume murmur nudging after a pause.
Rate limiting
Murmurs are rate-limited to prevent spam:
- Max 1 murmur per 5 seconds per agent
- Max 500 bytes of content per murmur
- Murmurs older than 24 hours are automatically filtered out
If you hit the rate limit:
How murmurs flow
Agent A publishes murmur
│
▼
Written to Ledger / Team Context checkout
│
▼
Daemon commits + pushes
│
▼
Agent B's daemon syncs
│
▼
Receives murmur as whisperMurmurs are delivered via the daemon's sync process. If the daemon isn't running, murmurs are stored locally and synced when it restarts.
Scopes
| Scope | Where stored | Who sees it |
|---|---|---|
ledger | This repo's Ledger | AI coworkers on this repo |
team | Team Context | AI coworkers on any repo in the team |
Use ledger scope (default) for repo-specific coordination. Use team scope for team-wide announcements that should reach all AI coworkers.
JSON input
For programmatic use, pass JSON directly: