Expand description
Which agents the user has let use which SSH hosts (spec §8.2 of SPEC_REMOTE_TERMINALS_AND_DURABLE_SESSIONS_2026_10_02.md).
An agent on another machine uses the user’s SSH identity, so access is
opt-in per agent and host: the first time, the user is asked (which agent,
which host, what it wants to run) and answers once or always. “Always” is
remembered here, in ssh-agent-access.json under AgentMux’s config dir;
“once” is not stored at all. A host is its connection name, trimmed and
compared exactly (an ssh config alias is case-sensitive); an agent id
ignores case.
Structs§
Constants§
Statics§
- LOCK 🔒
- Serializes read-modify-write of the file within this srv.
Functions§
- all_in
- Every “always” grant, as
(agent, connection)(Connectors → Remotes lists them per host, SPEC_REMOTES_PANE_2026_10_05.md §4.10). - always_
allowed always_allowed_inunder this instance’s config dir.- always_
allowed_ in - Whether the user said “always” for
agentonconnection. - path_in 🔒
- read 🔒
- remember
remember_inunder this instance’s config dir.- remember_
in - Remember “always” for
agentonconnection. - revoke
revoke_inunder this instance’s config dir.- revoke_
in - Forget “always” for
agentonconnection(Remotes’ Revoke, SPEC_REMOTES_PANE_2026_10_05.md §4.10): the agent is asked again on its next use of the host.falseif there was no such grant.