kuzychat
XMPP-native chat for agents and people. OMEMO encrypted, MUC-aware, daemon-managed presence and dispatch.
Explore kuzychat// all tools
Three primary tools — chat, mail, scheduling — plus the adjacent pieces a long-lived agent runtime actually needs: directory lookup, identity reception, calendar, diagnostics, mounting, signing.
XMPP-native chat for agents and people. OMEMO encrypted, MUC-aware, daemon-managed presence and dispatch.
Explore kuzychatnotmuch-backed mail with per-profile workflows. Managed-attention mode coalesces incoming mail.
Explore kuzymailPersistent triggers for agent runtimes. Daily, weekly, guarded, one-off — with delivery audit.
Explore kuzytrigDirectory client with pluggable backends.
kuzydir resolves identities — email, XMPP, agent metadata — through pluggable backends: CardDAV addressbooks, LLDAP directories, the kuzys reception API (Portier), or WebFinger. A single profile can have multiple accounts, each pointing at a different backend, and the client merges results into a coherent identity view.
Configuration is minimal: pick a backend, set the URL, set the secret reference. The doctor subcommand verifies the wiring; cache manages a local copy for offline work; lookup resolves a specific identity by slug or alias.
Public HTTP layer for identity and service requests.
Portier is the reception side of the kuzys infrastructure: an HTTP API exposing identity-update requests, service requests, and lookup endpoints over standard auth. Agents and humans submit requests via the public API; operators review and approve them through the administrative path; downstream tools (kuzydir, etc.) consume the resulting state.
Built as a small, inspectable HTTP service with a documented OpenAPI schema. Authentication uses standard HTTP Basic against the configured identity store. Requests are queryable by ID; identity updates apply atomically on approval.
CalDAV calendar client and event primitives.
kuzycal handles calendar state for agent and human profiles via standard CalDAV. Events, recurrences, and free/busy lookups work through the same per-profile/per-account model as the rest of the suite, with a CLI for inspection and a daemon for keeping local state in sync.
Structured diagnostics across the suite.
kuzydoctor is the "what's wrong with this setup" tool. It walks per-profile configuration, credential availability, local daemon state, backend reachability where probeable, and cross-tool consistency, then emits structured diagnostics with stable codes — machine-readable enough for automation, separating offline checks from active probes. Used during install, after a config change, and when a kuzychat / kuzymail / kuzytrig operation fails in an opaque way.
Profile-based SSHFS automount manager for personal shares.
kuzymount is a JSON-first mount manager brokered by kuzymountd, a root daemon that receives profile requests from the CLI over a Unix socket and creates validated systemd .automount/.mount units. It does per-profile / path / identity validation and uses peer credentials, so each agent profile sees only its own SSHFS share — no ad-hoc fstab edits, no shared mount surface.
Local PDF signing and verification for Kuzys acceptance workflows.
kuzysign is a local PDF signature rail for agent acceptance workflows. Each profile holds a local signing key; the tool uses it to add and verify cryptographically-checkable PDF signatures via a local certificate. The signatures are real signatures in the cryptographic sense, but they are local Kuzys signatures — not qualified electronic signatures, and not equivalent to externally-recognized e-sign workflows.