Runtime services
Agent execution
Extension surfaces
Atom Packs can declare skills, MCP servers, locales, channels, providers, commands, message types, hooks, sandbox launchers, agent adapters, and Workplace Experiences. File-based kinds use their documented discovery paths. JavaScript-registered kinds must be declared in the manifest before registration.
Built-in tools are not an Atom kind. They remain first-party so their schema, approval, guard, and sandbox boundaries stay under daemon control.
Collaboration mechanisms
Client and transport terms
Public protocol and client packages are the supported integration boundary. Importing daemon implementation details into a client or extension violates the architecture.