Skip to content

Open source Grok Bot alternative, Bring your own agent and subscription: message Claude Code, Codex, Gemini CLI, Cursor, Copilot and 40+ AI agents as bots on your own computer, from iPhone, Mac, Windows, Linux or terminal. Agent-agnostic and free. Also a Muse and Dots alternative. Built in Rust.

docs: who reaches this computer's bots on the network

leepokaif8d411ed2b65
diff --git a/docs/design/codync-network.md b/docs/design/codync-network.md
index 07d7fea4..7c3324ce 100644
--- a/docs/design/codync-network.md
+++ b/docs/design/codync-network.md
@@ -146,11 +146,13 @@ A VPS can be a member (the host or the standalone daemon, with its own bots or a
The build plan, with what each step touches and when it's done: [what's left](../plans/codync-network-next.md).
Done: the network screens and the cloud assistants switch in every client (2.29.0): the desktop app and the
-terminal UI manage the network, phones show it, and a `network` event keeps them current.
-
-1. Per-bot offering and inbound rules (needed before networks shared with other people).
-2. Codync-run iroh relays as the default connector.
-3. A local MCP server for agents that aren't Codync bots.
-4. Hellos that carry only what changed, lifting the roster's per-computer cap.
-5. Account networks; several networks per computer.
-6. A control channel for the standalone daemon on Windows (named pipe).
+terminal UI manage the network, phones show it, and a `network` event keeps them current. Per-bot offering, the
+cloud assistant scope and inbound rules, checked by the receiving computer. A computer that moves re-signs where it
+is. Cloud assistants and agents that aren't Codync bots (`codync-host mcp network`) reach the bots across the
+network.
+
+1. Codync-run iroh relays as the default connector.
+2. Several networks per computer.
+3. Hellos that carry only what changed, lifting the roster's per-computer cap.
+4. Account networks.
+5. A control channel for the standalone daemon on Windows (named pipe).
diff --git a/docs/features/codync-network.md b/docs/features/codync-network.md
index 257697f3..f4c49560 100644
--- a/docs/features/codync-network.md
+++ b/docs/features/codync-network.md
@@ -103,12 +103,34 @@ that was off learns of a removal.
sessions (their inbox socket) and Codex threads (`codex queue`), see the crate README. It keeps its own key in
`~/.codync-network` (the host's is `~/.codync/network`), so beside a host it is a computer of its own.
+## Who reaches this computer's bots
+
+Every check is the **receiving** computer's, like the message budgets: no rule depends on the sender's goodwill,
+and nothing new crosses the wire beyond a refusal's reason.
+
+- **Offered to the network**, per bot (`offeredToNetwork` on the bot, on by default): a bot that's off isn't
+ published (`network::publish` filters it), so other computers don't list it, and a letter to it is refused like
+ one to an unknown agent. It's a bot setting, so any paired device may change it.
+- **Reachable by cloud assistants**, per bot (`reachableByAssistants`, on by default): `list_bots` from the cloud
+ assistant leaves it out and `message_bot` refuses it (`chat/team/assistant.rs`).
+- **Rules**, per computer: an ordered list of `{fromComputer, fromAgent, toAgent, access}` (`allow`/`deny`, `*`
+ for any). The first rule that matches decides; with none, everyone may write (`codync_network::rules`). The crate
+ checks them in `node/inbound.rs` before it takes a letter, so the standalone daemon has them too (`rules.json`
+ beside `agents.json`, `codync-network rules allow|deny <agent@computer> <agent> [--first]`, `rules remove <n>`).
+ A refused letter's sender gets the reason as its tool error, for example "desk refused it: reviewer doesn't take
+ messages from lead@laptop", and its exchange notice ends failed. Answers to this computer's own letters always
+ pass (the crate keeps the ids it sent), so a rule added while a request runs doesn't strand it. The host keeps
+ its rules in kv `network_rules`, applies them when the node starts, and changes them with `setNetworkRules`
+ (loopback only, like membership); `networkView` shows them, so phones list them read-only.
+- The master switches stay at the computer: being in a network, and cloud assistants on or off.
+
## Not yet
Planned in order, with what each step touches: [what's left](../plans/codync-network-next.md).
- One network per computer; the `.network` address suffix comes with several.
-- Shared networks (other people's computers) need the per-network list of offered bots and inbound rules first.
+- Shared networks (other people's computers): the offered switch and the rules exist, but per network (with
+ several networks per computer) they don't yet.
- Bots can't reach Claude Code or Codex sessions on another computer through the host (the standalone daemon can).
- Each computer's share of the roster is capped (256 entries) and keeps its oldest: an owner or admin that has
made 256 admissions, promotions and removals can't make more. Hellos sending changes since the last one, instead
diff --git a/docs/plans/codync-network-next.md b/docs/plans/codync-network-next.md
index 4d38b611..68b470a0 100644
--- a/docs/plans/codync-network-next.md
+++ b/docs/plans/codync-network-next.md
@@ -113,7 +113,10 @@ Phones list the computers. The live event updates every client. Analytics: `sett
switch is already there, and `network_joined` exists; add events for the screens the way
`docs/features/analytics.md` describes.
-## 2. Access rules (ACL)
+## 2. Access rules (ACL) (built)
+
+Built as the recommended model below. What it does now: [feature](../features/codync-network.md#who-reaches-this-computers-bots).
+
**Goal**: choose which bots each computer offers, and which agents may message them, before a network is ever
shared with other people.