agent-bridgelisted
Install: claude install-skill ZsoltSziklai/claude-code-agent-spawner
# agent-bridge
This session runs in an **isolated Linux VM**. The user's Mac is a separate
machine. There is no network out, no `launchctl`, no `rm`, and no
agent-to-agent messaging — but files written into a **mounted folder land on
the Mac's real disk**. That one channel is the whole bridge.
On the Mac, a launchd watcher picks up what you drop, validates it, asks the
user for approval **in Telegram**, and only then starts an agent. That agent
inherits the conversation of the parent you name, does the work with full
native access, and its answer comes back to you as a file in `bridge/results/`.
## Before anything else: is the folder mounted?
`~/ClaudeProjects/bridge/` must be visible to you. If it is not, the user has
not attached the folder to this session — say so and stop. Do not try to
create the folder somewhere else; a request outside the real mount reaches
nobody.
## Choosing the parent — this is the important decision
The spawned agent **inherits the named parent's conversation**. Pick the session
that already knows the topic; that is the entire point.
**Read `bridge/agents.json` first.** The Mac keeps it current — never work from a
list you remember, because the agents change:
```json
{
"updated_at": "2026-08-07T21:49:41Z",
"parents": [
{"name": "mac-main", "running": true, "about": "the agent system, the bridge, watchdogs"}
],
"spawned": [
{"name": "mac-main-dpelda-20260101", "running": true,
"request": "db-list-20260807", "since": "202