Skip to main content

Module agent_access

Module agent_access 

Source
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§

Grant 🔒
Grants 🔒

Constants§

FILE_NAME 🔒

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_in under this instance’s config dir.
always_allowed_in
Whether the user said “always” for agent on connection.
path_in 🔒
read 🔒
remember
remember_in under this instance’s config dir.
remember_in
Remember “always” for agent on connection.
revoke
revoke_in under this instance’s config dir.
revoke_in
Forget “always” for agent on connection (Remotes’ Revoke, SPEC_REMOTES_PANE_2026_10_05.md §4.10): the agent is asked again on its next use of the host. false if there was no such grant.