Neutron joins agent execution, operational controls, durable memory, automation, and integrations in one self-hosted product. The chapters below separate shipped mechanisms from provider, adapter, and deployment boundaries.
Each named agent keeps an explicit persona, provider, capability set, workspace grants, safety posture, and visibility. Change the operating identity without forking the core image.
The provider control plane manages subscriptions, named API-key credentials, catalog providers, and custom endpoints without redeploying. The Neutron Core agent engine normalizes output and usage from its Claude Agent SDK adapter and OpenCode SDK adapter while retaining their different governance boundaries.
Turns using the Claude Agent SDK adapter resolve safety mode and per-tool policy before an operation runs. A gated action carries the exact request into a persisted decision and activity trace; the OpenCode SDK adapter remains a separately stated enforcement boundary.
readonly, approval-gated, and
readwrite set the default posture. Per-tool rules refine it,
and optional role or named-user routing supports two-person approval where policy requires it.
Neutron keeps per-agent, per-user memory alongside the agent's own working memory. A user can inspect, edit, or clear what an agent remembers about them.
Agent memory carries reusable context for one operating identity rather than silently merging every agent's history.
Each user gets a bounded memory slice per agent, with visible controls to review or remove it.
Saved web, repository, and linked-message threads retain their own activity and usage context.
The capability registry stores MCP servers, CLI tools, and skills once, then grants only the selected capabilities to each agent.
Agents can submit skill proposals after difficult work. Every proposal remains inert
until an admin reviews the full SKILL.md and approves it.
.mcpb bundles import as reviewable draftssecret:// references
Create recurring schedules from Settings → Schedules, then inspect recent runs, status, and errors. Execution and operator attention remain separate policy decisions.
A schedule stores cron, timezone, agent, and prompt in the bundled assay-engine. Each fire creates a durable headless turn, then records the result in its schedule thread.
Repository, messaging, computer, secret, and peer-core connections keep their acting identity and deployment boundary visible.
Link a Telegram chat, Discord DM, or Slack DM or channel to a selected agent. Messages run as the link owner with channel-specific thread and memory. A linked Slack channel has one link owner; it does not assign each participant a separate principal. Approve or deny gated actions inline in chat. Slack uses Socket Mode with admin-configured app and bot tokens, so it needs no public webhook.
On Kubernetes deployments with computer provisioning enabled and the required RBAC, admins can create a browser desktop from Settings → Computers. Provisioned desktops use Neutron's authenticated proxy without per-computer ingress; existing external noVNC URLs remain supported.
The optional computers connector lets operators allow,
gate, or deny agent requests to provision and remove desktops. Driving one still requires
a separately granted computer-use capability.
Constellation is a network of cores: a control core registers scoped peer tokens,
checks health, delegates chat, or invokes peer administration. The retained
fleet configuration identifier keeps existing deployments compatible.
GitHub and GitLab workspaces combine scoped connections with persistent per-agent worktrees. The encrypted vault, OpenBao backend, self-hosted search, REST API, and admin MCP remain opt-in services.
