# The Wall

My review screen as a service, and the one project behind it. A single MCP server on the Fedora laptop turns any diagram, report or dashboard into a fullscreen page in front of me in about a second — cursor hidden, no tabs, newest page wins — while the same laptop keeps the tmux rooms where agents work and runs the ambient board. It now also listens: a wake word, local whisper, a fast router, a tool-only cloud brain and Piper, with the listening state drawn on the wall and the audio never leaving the laptop.

**Status:** Live · Agents · 2026

- **Local checkout:** `/Users/simon/Developer/wall` (branch `main`, last commit e23d084, 2026-11-07 — MCP rolodex diagram: agents → one gateway index → search, load, call (and idle expiry))
- **Uncommitted changes:** 35 file(s) at brief generation time
- **Repository:** https://github.com/ShimonNavon/wall
- **On another machine:** `git clone https://github.com/ShimonNavon/wall` — the paths below are Simon's Mac
- **GitHub:** https://projects.navonsimon.com/repo/wall
- **Voice CLI & MCP:** https://projects.navonsimon.com/wall-voice-tools.html
- **Voice architecture:** https://projects.navonsimon.com/wall-voice.html
- **Note:** Live on the Fedora laptop · voice assistant

## Stack

Python stdlib MCP server (Streamable HTTP), systemd user units on Fedora, Chromium kiosk + DevTools protocol, Python voice service: openWakeWord, faster-whisper int8, Piper, PipeWire (pw-record, pw-play, wpctl), OpenRouter with a closed tool schema, Voice CLI + fedora__voice_* MCP tools (status, ask, say, mute, timers, logs), tmux sessions as rooms, Tailscale

## Start here

- `server.py` — the MCP server: status, exec, tmux_*, show, screen, and the voice_* tools (status, health, ask, say, listen, mute, cancel, timers, logs)
- `install.sh` — installs fedora-mcp.service and fedora-tmux.service on the laptop (idempotent, --local flag)
- `README.md` — tools, units, registry entry and the gotchas
- `wall-plan.html` — the M0-M4 build plan shown on the wall
- `fedora-screen.html, fedora-plumbing.html, diagram.html` — the definition, the Archify plumbing diagram, the first connection diagram
- `agent-link.html` — the Agent Link bus diagram: every agent and person on the wire, presence and unread counts, and the send → queued on the hub → acknowledged flow
- `voice/` — wake word, local whisper, fast router, skills, Piper, HTTP API, wall overlay client and tests
- `install-voice.sh` — venv, models and fedora-voice.service on the laptop (idempotent, --local)
- `docs/VOICE.md` — voice design, config, privacy, skills, API, licensing and troubleshooting
- `docs/VOICE-HARDWARE.md` — measured laptop audio, RAM, disk and Python facts; no credentials
- `voice-assistant.html` — the one-turn architecture page shown on the wall
- `voice/cli.py` — the `voice` CLI: status, ask, say, listen, mute, cancel, timers, devices, logs, watch, test

## Commands

- **Install or update on the laptop:** `./install.sh`
- **Smoke test the laptop side:** `ssh home 'python3 ~/.local/share/fedora-mcp/server.py --check'`
- **Show a page on the wall:** `registry_fedora__show (url or html)`
- **Laptop health:** `curl -s http://100.82.194.118:30120/healthz`
- **Install or update the voice service:** `./install-voice.sh`
- **Voice health:** `ssh home 'curl -s http://127.0.0.1:30212/health | python3 -m json.tool'`
- **Run the voice tests:** `python3 -m unittest discover -s voice/tests -t .`
- **What the overlay is showing:** `ssh home 'curl -s http://127.0.0.1:30210/api/voice'`
- **Voice status (one screen):** `voice status`
- **Ask the assistant from a shell:** `voice ask "what time is it"`
- **Voice timers:** `voice timers`
- **Follow the voice journal:** `voice logs -f`
- **Voice tools through the MCP gateway:** `registry_fedora__voice_status`

## Deploy and where it runs

- Runs as user units on the Fedora laptop (tailnet host home, 100.82.194.118): fedora-mcp.service on port 30120, fedora-tmux.service keeping a session called habitat, and the transient fedora-review unit that holds the fullscreen page.
- fedora-wall.service owns the screen on 127.0.0.1:30210 with fedora-wall-screen.service as the only kiosk. fedora-voice.service runs beside it on 127.0.0.1:30212 with its own venv, models and a 1 GiB memory cap; stopping voice leaves the wall rotating.
- Shared with every agent through the tailnet MCP registry (ubuntu03:30105) as fedora__*; registry entry name 'fedora'.

## Current state

Live and in daily use. show puts any page fullscreen on the Fedora monitor in about a second; the wall agent owns the queue, rotation, expiry, history and a watchdog that keeps one kiosk on top. Since 2026-11-06 the same screen has a hands-free assistant: “hey jarvis” wakes it, faster-whisper base.en transcribes locally, a deterministic router handles timers, lists, weather, news, the wall and music, and OpenRouter answers the rest with a closed tool list. Piper speaks, the shell draws a listening/speaking bar, and all audio stays on the laptop. Weather and ai-dj music are the two things still waiting on coordinates and a Mac bridge. It is trackable from a shell and from every agent: `voice status` / `voice watch` / `voice logs` on the laptop, and `fedora__voice_status`, `voice_ask`, `voice_timers`, `voice_logs` and the rest through the existing MCP server.

## Watch out

- Serve pages from the laptop: show writes agent-supplied html into ~/.local/share/fedora-mcp/pages and restarts the review Chrome, so a page sent from the Mac must be scp'd over first or sent as an html body.
- The wall's HDMI monitor sleeps after long idle and GNOME refuses remote captures, so a page can be on the wall while the display is dark; only local input wakes it.
- Through the registry gateway each call is capped at 60 s, so tmux_wait timeouts must stay under 50 s.
- tmux targets: session commands use -t =name, pane commands need -t =name:.
- The laptop is a screen and a set of rooms, not a deploy target; no secrets in rooms.
- ai-dj binds 127.0.0.1:8765 on the Mac, so the laptop cannot reach it. Run voice/music_bridge.py on the tailnet (or set AIDJ_HOST) and set music.dj_url; until then the assistant says music is not configured.
- The laptop has Python 3.14: pin openwakeword==0.4.0 (0.6 pulls tflite with no cp314 wheel) and av<16 (PyAV 16 breaks faster-whisper decode).
- Without echo cancellation the assistant is half-duplex; the on-screen Stop and the “stop”/“mute” commands are the interruption. The installer tries PipeWire echo cancel and /health reports the result.
- Weather has no safe default: set weather.latitude and weather.longitude or it says it is not configured.

## Secrets — locations only, never print values

- None stored on the wall. The MCP listens on the tailnet address only and refuses peers outside it.
- The registry URL and tailnet address live in ~/Developer/mcp-registry/registry.json.
- The OpenRouter key is in ~/.config/fedora-voice/openrouter.key (0600) or OPENROUTER_API_KEY; never in the repo or logs.
- Voice models live under ~/.local/share/fedora-voice/models and are not committed.

## Tags

MCP, Chromium kiosk, Voice, whisper, Piper, openWakeWord, Tailscale

---

Brief generated 2026-11-08 from `~/Developer/my-projects/context/`. Canonical URL: https://projects.navonsimon.com/context/wall.md
