Autonomous AI Agents for Everyday Work — Your Agents. Your Machine. Your Control.
$ quark space run Loading Quarkfile ... Initializing plugins: medical-terminology, hipaa-compliance Starting inboxes: patient-forms, insurance-claims Main Agent ready Channels active: web:3000, telegram [main-agent] ORIENT reading inbox 'patient-forms' ... [main-agent] PLAN spawning sub-agent: triage-bot [triage-bot] EXECUTE processing intake form [triage-bot] SESSION user sess_abc123 asking for status [triage-bot] COMPLETE exit code 0Why Quark
The architecture that makes Quark different from opaque, cloud-hosted agent platforms.
Agents run on your machine. Every action is auditable and reversible. No cloud dependency, no data leaving your infrastructure.
Three execution modes: Autonomous, Assistive (human-in-the-loop), and Workflow (deterministic DAG).
One Quarkfile defines your entire Space: agents, plugins, inboxes, channels. Version it, share it, reproduce it anywhere.
Like a Dockerfile for AI agents. Space = built environment. Runtime = execution engine.
Channels connect users to agents through Web, Telegram, WhatsApp. Sessions maintain isolated conversational context.
Session Context never pollutes Work Context. Human queries don't disrupt agent processing.
Inboxes are async message buses for external data. Sub-agents consume messages as they arrive. No polling, no bottlenecks.
Main Agent creates Inboxes. Sub-agents subscribe and process at scale.
How it works
From zero to a running multi-agent Space in under a minute.
$ quark space init healthcare-ops Created Quarkfile Created plugins/ Created prompts/
A Space is your workspace + execution environment. Like a Docker image for agents — define once, run anywhere.
$ quark space run Loading Quarkfile ... Initializing plugins: medical-terminology Starting inboxes: patient-forms Main Agent ready Channels active: web:3000
The Runtime launches your Space. Plugins load, Inboxes open, Channels connect. The Main Agent begins orchestrating.
$ quark activity [main-agent] ORIENT reading inbox ... [main-agent] PLAN spawning triage-bot [triage-bot] SESSION user asking for status [triage-bot] COMPLETE exit code 0
The Main Agent orchestrates. Sub-agents handle specific tasks. Sessions maintain conversational context.
Under the hood
An OODA-inspired continuous cycle. The Main Agent orients on Inbox state, plans next steps, spawns Sub-agents, monitors execution, then assesses outcomes — and repeats.
Configuration
Define your agents, tools, and model in a Quarkfile.
Run quark run to start.
quark: "2026.04" meta: name: healthcare-intake version: 1.0.0 space: type: healthcare execution_mode: assistive model: provider: anthropic name: claude-sonnet-4-20250514 plugins: skills: - ref: quark/medical-terminology - ref: quark/hipaa-compliance binaries: - ref: quark/pdf-parser main_agent: prompt: ./prompts/main-agent.md sub_agents: - name: triage-bot prompt: ./prompts/triage.md consumes: [patient-forms] - name: billing-reconciler prompt: ./prompts/billing.md plugins: [erp_integration] inboxes: - name: patient-forms type: queue retention: 7d - name: insurance-claims type: queue channels: - type: web port: 3000 - type: telegram token: $TELEGRAM_BOT_TOKEN memory: episodic: ./state/work-context.db semantic: ./state/vector-store.db env: - ANTHROPIC_API_KEY - TELEGRAM_BOT_TOKEN$ quark space init healthcare-intake Created Quarkfile Created prompts/ Created plugins/ $ quark space run Loading Quarkfile ... Initializing plugins: medical-terminology, hipaa-compliance Starting inboxes: patient-forms, insurance-claims Main Agent ready Channels active: web:3000, telegram $ quark activity [main-agent] ORIENT reading inbox 'patient-forms' ... [main-agent] PLAN spawning sub-agent: triage-bot [triage-bot] EXECUTE processing intake form [triage-bot] SESSION user sess_abc123 asking for status [triage-bot] COMPLETE exit code 0Comparison
Local execution vs opaque cloud platforms. Your agents, your machine, your control.
Open source core
The best infrastructure is transparent. Quark's open-source core gives you full visibility and control — no vendor lock-in, no surprises.
Use, modify, and distribute. Supervisor, Runtime, CLI, and Web Channel — all open source. No feature gating.
Modular Golang architecture. Four core components, each independently maintainable and extensible.
Agent context, session history, and semantic memory stay on your infrastructure. Fully auditable execution.
Quark Enterprise adds SSO, audit logs, and compliance features on the same open core you trust.
Quark Enterprise
Quark Enterprise adds the features teams need to run autonomous agents in production — without changing how the runtime works.
Learn about EnterpriseConnect Quark to your identity provider. Authenticate users and control agent Space access through your existing SSO or LDAP directory.
Guaranteed response times with a dedicated support channel. Direct access to the engineering team. Escalation paths for production incidents.
Deploy Quark in air-gapped networks with custom infrastructure. We help you run Spaces securely in your environment.
Get started
Start with open-source Quark. Define Spaces, configure Inboxes, connect Channels. When you need compliance and enterprise support — we're one conversation away.