One singulacomp.yaml. One Git repo.
Your entire AI workforce, as code.
hardcodedUi.autoAppPublicMarketingDevelopersPageJsxTextAgentsSkillsTools813c489d
singulacomp_version: 2
project:
name: acme-ops
sandbox:
image: .singulacomp/Dockerfile
agents:
support-triage:
connectors: [slack, linear]
skills: [ticket-triage, singulacomp-memory]
triggers:
- type: cron
schedule: "0 8 * * *"
agent: support-triage
The coding-agent loop, for real work
Describe intent, an agent edits files, you review the diff. SingulaComp runs that same loop for support, ops, and research.
Agents are sandboxes
Every agent runs in its own disposable cloud VM, on its own git branch. Spin up thousands in parallel — nothing is shared between runs.
Work is code
Agents, skills, triggers, connectors and policies are plain files in one repo. Diff them, review them in a change request, roll them back.
You own the stack
Open source. Self-host the exact same stack, bring your own runtime and model keys. No black box, no lock-in.
From curl to production
One repo, one config, one command. The whole path, top to bottom.
Install & scaffold
One line installs the CLI. singulacomp init scaffolds singulacomp.yaml and .singulacomp/, wired to your coding agent.
Build it locally, like code
hardcodedUi.autoAppPublicMarketingDevelopersPageJsxAttrBodyAnAgentd3ac5ad4
---
description: Acme's support agent. Resolves tickets end to end.
mode: primary
model: anthropic/claude-opus-4-8
tools:
lookup_order: true
---
You are Acme's support agent. Resolve customer tickets
end to end, with full product and order context.
Issue refunds under $500 on your own. Anything higher
goes to a human for approval.
Declare the project in one manifest
singulacomp.yaml holds secrets, sandbox images, triggers, connectors, and channels. Versioned from the first commit.
singulacomp_version: 2
project:
name: acme
# the OpenCode runtime config dir
opencode:
config_dir: .singulacomp/opencode
# a trigger runs itself, on a schedule
triggers:
- slug: daily-digest
type: cron
agent: research
cron: "0 0 9 * * 1-5"
prompt: Summarize yesterday across Slack & Linear
# connect a tool's API as agent tools
connectors:
- slug: stripe
provider: http
base_url: https://api.stripe.com
# answer where your team works
channels:
- platform: slack
agent: support
Ship it
hardcodedUi.autoAppPublicMarketingDevelopersPageJsxAttrBodySingulaCompShipef9c33ee
It runs as a fleet of sandboxes
hardcodedUi.autoAppPublicMarketingDevelopersPageJsxAttrBodyEverySession6d5c7d97
Bring your own runtime & model
hardcodedUi.autoAppPublicMarketingDevelopersPageJsxAttrBodySessionsRund6d02c3d
The whole lifecycle, one CLI
hardcodedUi.autoAppPublicMarketingDevelopersPageJsxTextScaffoldShipRunb35564e3
Scaffold & ship
$ singulacomp initScaffold singulacomp.yaml + .singulacomp/
$ singulacomp shipCommit, push, link & go live
$ singulacomp validateType-check your manifest
Run & talk
$ singulacomp sessionsSpawn & manage sandbox sessions
$ singulacomp chatTalk to a session's agent
$ singulacomp filesBrowse the repo, diffs & branches
Automate
$ singulacomp triggersCron & webhook automations
$ singulacomp channelsConnect Slack & chat surfaces
Connect
$ singulacomp connectorsWire up 3,000+ tools
$ singulacomp secretsManage encrypted secrets
$ singulacomp envPull / push as dotenv
Review
$ singulacomp crOpen, review & merge change requests
$ singulacomp accessInvite, grant & revoke access
Operate
$ singulacomp self-hostRun your own SingulaComp cloud
$ singulacomp hosts useSwitch cloud ↔ local
$ singulacomp providersBring your own model keys
1 session = 1 sandbox = 1 branch
hardcodedUi.autoAppPublicMarketingDevelopersPageJsxTextEverySessionRuns6dd000d3
- Anything worth keeping comes back as a change request — and merges into main
- Main is always the source of truth: every agent action is auditable Git history
- It’s all Git under the hood — branch, diff, review, merge
- The same SingulaComp CLI runs inside every sandbox — so running locally and in the cloud is identical
- Isolated compute per session; one runaway agent can’t touch another
Every tool, behind one interface
hardcodedUi.autoAppPublicMarketingDevelopersPageJsxTextSingulaCompConnectorsPut612736c1
- 3,000+ one-click apps via Pipedream — OAuth handled for you
- Or bring any MCP, OpenAPI, GraphQL or HTTP endpoint — same interface
- Credentials live server-side and never reach the sandbox
- Agents hold one scoped SingulaComp token; connect once, shared org-wide, self-healing
+ 3,000 more via Pipedream
A platform that improves itself
hardcodedUi.autoAppPublicMarketingDevelopersPageJsxTextBecauseEverythingIsd6715079
Everything is files
Agents, skills, tools, connectors and schedules live in the repo. Edit in your IDE, in the web UI, or let an agent edit them.
Agents edit themselves
Describe a change and an agent ships it — referencing what already exists, reusing patterns, opening a PR you review.
Skills, git-backed and invisible
Non-devs publish skills as markdown; SingulaComp handles the branch, PR and merge behind the scenes. Versioned, reviewable, auditable.
Self-healing connections
When a token expires or a service blips, SingulaComp refreshes it or asks you to reconnect in plain language — never a cryptic error.
Quality gates built in
Type checks, lint, docs validation and dedup run before anything merges, so a fast-moving, agent-written codebase stays coherent.
Every feature is a conversation
The UI is a reference, not a requirement. Anything you can do in a menu, you can do with a message.