Guides

This section is the practical how-to for operating Joe’s day-to-day surfaces. Each page is goal-directed: it tells you the real entry point — a joe subcommand, an HTTP path, or a UI surface — and the steps to get the job done against the running binary. For the why behind any of these, the pages link back to Concepts; for exact configuration keys they link to Configuration.

Pages

• The web UI and human login — log a human in over OIDC, the admin bootstrap, and what the post-login app actually looks like.
• Register a Kubernetes component — bring a cluster under Joe’s management through the UI: register it inert, promote it with a static-bearer reference, and take it live. Other component types are covered separately; see Components for the per-type routing.
• Chat sessions — create a session, who can read it, and link one to an incident.
• The incident regime — declare and resolve an incident, and what the regime changes while it is active.
• Skills — install, approve, and manage Agent Skills from the joe skills subcommand.
• The MCP server — connect an editor or other MCP client and the tool surface Joe exposes. This is the page the Components section points to.
• The Slack bot — bring up joe slack as a Socket Mode daemon client.
• The knowledge graph — query the graph and understand how it populates.