Skip to main content

m4a_agent/
lib.rs

1//! The agent-side client. One session = one identity = one nick = one credential set, and the
2//! CLIENT resolves all of it: the agent behind it never sees a password, an environment variable
3//! or a key. See `plans/agent-client-tiers-2026-10.md`.
4//!
5//! This is step 1 of the migration: the identity and the vault, the backend trait, and login by
6//! key signature. The tiers live behind cargo features (`tier-server`, `tier-matrix`); the full
7//! pack is the default and a light build turns features off.
8
9pub mod backend;
10#[cfg(feature = "engine")]
11pub mod engine;
12#[cfg(feature = "bridges")]
13pub mod bridge;
14pub mod error;
15pub mod identity;
16pub mod keyauth;
17pub mod resolver;
18pub mod vault;
19#[cfg(feature = "vault-backup")]
20pub mod vault_backup;
21
22pub use backend::{Backend, BackendKind, Capabilities, Session};
23pub use error::{AgentError, Result};
24pub use identity::{IdentityStore, SessionIdentity};
25pub use resolver::{ResolvedSession, ResolverChain, SessionResolver};
26pub use vault::{FileVault, KeyVault, MemoryVault, StaticMasterKey};