Skip to main content
You can configure 2501 three ways. Each has trade-offs.

Manual

Click through Command Center. Fastest for quick changes; tedious past a few dozen resources.

CSV import

Bulk-import hosts and their agents from a spreadsheet. Best for large infrastructures.

Git-managed

Manage every resource as MDX in a repo. Reviewable diffs, PRs, reproducible. Recommended at scale.

​
Manual

Create resources directly in Command Center on each resource’s page. Good for getting started, one-offs, and exploring how a feature behaves before automating it. Past a couple dozen specialties, rules, hosts, and agents the click-through cost adds up.

​
CSV import

The most time-consuming part of any setup is creating hosts and agents in bulk. The CSV importer reads a single file containing both, including credential references. Specialties and credentials must already exist (referenced by name). CSV does not cover specialties, operational rules, blacklists, knowledge, or gateways.

​
Git-managed (2501 resources)

The CLI synchronizes a directory of MDX files with your deployment. Each kind has its own subdirectory; each file declares one resource via YAML frontmatter, with the body holding any long-form text (specialty prompt, host knowledge, rule text).
KindSupported
Agents✅
Hosts✅
Specialties✅
Operational Rules✅
Blacklist✅
Credentials✅ (secret values from env vars at sync time)
Gateways✅
The workflow: 
# Snapshot the live platform into your repo
2501 resources pull -d ./config

# Apply the repo back to the platform; --prune deletes undeclared resources
2501 resources sync -d ./config
2501 resources sync -d ./config --prune
sync prints a plan (create / update / delete / unchanged) before applying. Deletes are opt-in via --prune and a delete that would orphan dependents is reported BLOCKED. For the full reference and worked examples, see Configuration as Code.

​
Which one when

ScenarioPick
First-time evaluation, demo, single tenantManual
Onboarding hundreds of hosts at onceCSV → then manual or git for the rest
Production at scale, multiple environmentsGit-managed
You already have it manual and want to adopt gitpull first, commit, then sync