General
What does 2501 actually do?
What does 2501 actually do?
2501 runs autonomous AI agents on your infrastructure. You point it at machines, give it a few rules about how your environment works, and it handles tickets from your ITSM - investigating, fixing, and reporting back in the ticket itself.
Does it work without a ServiceNow integration?
Does it work without a ServiceNow integration?
Yes. ServiceNow is the default gateway and what most deployments run, but custom-built gateways are available for other ticketing systems - contact your account team. You can also drive 2501 from the Command Center UI directly.
Is there a free tier?
Is there a free tier?
Yes - a built-in free tier caps your tenant at 50 lifetime tasks and 10 hosts (gateways are unlimited). Once you apply a license, those caps are replaced by your contract’s. See Licensing.
Agents and safety
How do I keep agents from running destructive commands?
How do I keep agents from running destructive commands?
Three layers, used together:
- Permissions - give agents the least-privileged credentials that still let them work.
- Blacklists - programmatic blocks for specific command patterns, always on.
- Read-Only Agents - put a specialty or an organization in Plan: its agents only read, and each change waits for a person to approve a plan.
What's the difference between Plan and Auto?
What's the difference between Plan and Auto?
An agent in Plan only reads: it diagnoses and reports, and each change waits in a plan until a person approves it with
@2501:approve-plan. An agent in Auto makes changes without approval. Each agent has the mode of its organization, unless its specialty overrides it. Force one mode on all the agents of a ticket’s job with @2501:plan or @2501:auto. @2501:auto works only when an Admin allows it. The old commands still work: @2501:investigate is @2501:plan, and @2501:remediate is @2501:auto. Only @2501:approve-plan approves a plan. See Agents: Execution Modes and Read-Only Agents.What's the difference between a Specialty and an Operational Rule?
What's the difference between a Specialty and an Operational Rule?
A Specialty shapes how the agent thinks about a domain - vocabulary, priorities, approach. An Operational Rule tells it what is true in your environment and what that implies. Specialty: “Kubernetes Operator”. Rule: “On this cluster, rollbacks go through
helm rollback, never re-applying manifests.”Rules outrank specialties in conflicts. See Prompting an Operational Rule.Why is there a 20-task limit per job?
Why is there a 20-task limit per job?
The results of every task go into the planning of the next turn and into the final answer, so a job’s prompts grow with each task. 20 tasks keep them within the model’s context, and a patch on 20 hosts still fits in one turn. If a job reaches the limit while the ticket still needs work on more hosts, the job ends as partial. See Agentic Flow.
Models and providers
What LLM providers does 2501 support?
What LLM providers does 2501 support?
Native: OpenAI, Anthropic, Mistral, DeepSeek, Cohere, OpenRouter, TogetherAI. Compatible: any OpenAI- or Anthropic-shaped API via
openai-compatible / anthropic-compatible, and Azure OpenAI (including APIM). Self-hosted endpoints (vLLM, Ollama) work through the compatible types. See Providers.Can I use different models for different agents?
Can I use different models for different agents?
Yes. Each agent picks its main and secondary engine from the tenant catalog. The tenant has its own defaults for gateway routing and the AI Assistant. See Engine & Agents.
Why two engines per agent?
Why two engines per agent?
The main engine does the work (commands, file edits). The secondary engine plans, watches, and judges every command for compliance and read-only enforcement. Separating execution from oversight improves both accuracy and safety. See Engine & Agents.
Deployment
Docker Swarm or Kubernetes?
Docker Swarm or Kubernetes?
Either. The same signed chart installs on Kubernetes (any distribution: vanilla, OpenShift, k3s, EKS, etc.), applied with Helm, ArgoCD or
kubectl, and on Docker Swarm, rendered into one compose.yaml for docker stack deploy. See Overview.How do I upgrade 2501?
How do I upgrade 2501?
Apply the chart of the newer build with the same
values.yaml, after reading the Upgrade actions of every release you cross and reviewing the diff. See Upgrade.Where do I configure secrets?
Where do I configure secrets?
The installation’s own keys, its database connection and the first LLM API key are secrets you create in your cluster or Swarm;
values.yaml only names them. Further LLM providers and their keys are configured in Command Center. Per-host credentials (SSH, WinRM, gMSA, vault paths, PAM accounts) live in Command Center → Credentials, encrypted at rest. Agents only access them programmatically - values are never displayed in the UI after creation. See Credentials.Knowledge and rules
What file types can I upload as knowledge?
What file types can I upload as knowledge?
PDF, DOCX, CSV, and Markdown. Max 200 MB per file. PDFs with diagrams need a multimodal model on the tenant to capture the visual content. See Knowledge.
What if my uploaded knowledge contradicts a rule I wrote by hand?
What if my uploaded knowledge contradicts a rule I wrote by hand?
Manual rules always win. The auto-extracted rule is replaced when you re-upload the same document, but your hand-written rules are untouched. See Working with Knowledge.
How do I know which rules reached a task?
How do I know which rules reached a task?
Each task’s detail page in Command Center shows a matching trace - which operational rules were applied, which were skipped, and why each skip happened. Use it to debug rules that are too broad or too narrow.