01
pair once
agentnoise shows its desktop identity QR and a rotating six-digit PIN. Your phone proves it is in front of the desktop before commands are accepted.
White Noise control plane for local agents
agentnoise
Chat from your phone. Route commands through White Noise. Run Codex, Claude, wiki ingest, and media-aware local jobs through a native Rust helper that teaches the main-chat/work-chat split.
stable White Noise mainline; Dark Matter alpha is separate.
$ agentnoise up
desktop: npub1...
pairing: scan QR, send 6-digit PIN
phone sees: agentnoise is up
timestamp: 2026-05-15T20:31:04Z
workspace: sandbox:/
phone main: /doctor
phone main: /codex fix the broken test
agentnoise opens a work chat
phone work chat: what changed?homebrew
install, pair, keep it reachable
Use Homebrew for the White Noise transport with daemon self-recovery, then run phone-launched jobs from a login-shell worker or supervised tmux worker. The stable formula is agentnoise; new configs default to direct raw agents, with the hardened bondage path still opt-in. The experimental Dark Matter alpha installs as agentnoise-dm.
brew install nvk/tap/agentnoise
agentnoise up --no-listen
brew services start nvk/tap/agentnoise
agentnoise worker start --tmux
agentnoise doctor
release split
mainline stays stable, Dark Matter stays isolated
Current public stable: nvk/tap/agentnoise v0.1.44 for the White Noise mainline. v0.1.44 keeps supervised remote workers alive when a non-interactive keychain restore fails and adds rate-limited daemon recovery for broken discovery, reconciliation, and subscription loops. v0.1.43 mirrors terminal work-chat answers back to the primary launcher chat, so results stay visible even if a mobile White Noise client does not surface a newly-created work chat immediately. v0.1.42 kickstarts the legacy local.agentnoise.wnd LaunchAgent when present, preserving its Keychain authorization while refreshing stale White Noise daemons. v0.1.40 migrates old managed wn paths back to the packaged CLI and restarts wedged White Noise daemons when sends hit closed-socket or broken-pipe failures. v0.1.39 made agentnoise worker start --tmux supervised, so phone-launched jobs keep getting claimed even after transient worker exits. v0.1.38 added first-use guidance: the primary paired chat is the launcher for new work chats, and inside those work chats users can continue in plain text without slash commands. v0.1.37 added /doctor so a trusted paired phone can request the same diagnostics summary as agentnoise doctor remotely. Current experimental alpha: nvk/tap/agentnoise-darkmatter 0.2.0-alpha.10, installed as agentnoise-dm with separate config, data, logs, keychain namespace, service label, and phone pairing.
brew install nvk/tap/agentnoise-darkmatter
agentnoise-dm up --direct-agents
brew services start nvk/tap/agentnoise-darkmatter
agentnoise-dm worker start --tmux
remote diagnostics
ask the host what hurts from the phone
Send /status for live transport, worker, queue, and subscription state. Send /doctor when the host looks stuck: agentnoise replies with the config, launcher, White Noise, keychain, repo sandbox, runtime-store, and CloudDocs warning checks that the local CLI prints.
/status
/doctor
/tail <job>
/cancel <job>
product shots
what the control loop looks like
Generated from a dedicated product stage, not from the marketing page.
media path
pictures, video, audio, PDFs, and wiki ingest
White Noise attachments are saved inside the selected workspace at .agentnoise/attachments/<id>/ and passed to the active job. The supported set mirrors White Noise: JPEG, PNG, GIF, WebP, MP4, WebM, MOV, MP3, OGG, M4A, WAV, and PDF. /wiki jobs use the LLM Wiki ingest framing, and supported media files created by an agent can be uploaded back to chat.
02
chat naturally
Each White Noise chat is its own session. The primary chat is a launcher: use /codex, /claude, or /wiki there to open a work chat. In the work chat, plain text continues the thread; slash commands like /status, /doctor, /use, /cd, and /attachments still work when needed.
03
keep execution local
The phone is only the remote. The repo, keychain, logs, and coding agents stay on your machine behind the local policy boundary.
security stack
phone control, local launch policy
agentnoise is the White Noise control plane. Agent execution can use direct raw agents for first setup, but the hardened path runs through bondage profiles, with optional envchain-xtra secret release and nono sandboxing. The practical setup notes live at learntoprompt.org.
native, small, no js bridge