Expand description
The five places a session id used to come from, as sources of ONE resolver chain
(m4a_agent::ResolverChain). Each source only names the session (and, when it knows it, the
tier-1 local session id); identity, nick and credentials are the client’s identity store’s.
The chain refuses two sources that name different sessions for one process.
Structs§
- Agents
DirResolver - A Grok Bot agent: the agent id is the mail session id unless
agent=sessionaliases say otherwise (the same rule the machine client applies). - Configured
Resolver - A host that already assigned the id (
M4A_SESSION_ID, the node CLI, a web host). - Grok
Active Resolver - A Grok CLI session: the row of
active_sessions.jsonwhose working directory iscwd. - Provider
Record Resolver - A provider session that registered itself (hook or
m4a-inbox register).