FEATURES
Work in ProgressBuilt for how developers actually work. Choose your perspective.
"Solo dev? Small team? Ship like you have 10 engineers."
Parallel Agents
Run 5 features at once across isolated workspaces. Each agent gets its own git worktree — no conflicts, no waiting.
Plan-Execute-Verify
AI proposes a plan, you approve with one click, tests run automatically. No more hoping it works.
Checkpoints
One-click rollback to any point. Never lose work. Experiment freely knowing you can always go back.
Structured Handoffs
Leave for lunch. Agent tells you exactly what it did and what it needs. No more "where was I?"
CORE CAPABILITIES
Git Worktrees
Each workspace is a real git worktree. Branches stay isolated. Merge when ready. No accidental conflicts.
Real-time Status
See agent status as it changes. Planning, executing, waiting, done. Never wonder what's happening.
AGENTS.md
Define your project's conventions in one file. Agents read it, follow it, and produce consistent code.
Session History
Every conversation, every decision, every change — logged and searchable. Context that persists.
Multi-Model Support
Claude, GPT-4, and more. Choose the right model for each task. Switch freely between them.
Native Performance
Built with Tauri. Fast startup, low memory. Works offline for code navigation and planning.
FREQUENTLY ASKED QUESTIONS
How is Antimaterial different from Cursor or Windsurf?
Antimaterial isn't an editor — it's an orchestration layer. Cursor and Windsurf are AI-enhanced editors limited to single conversations on single branches. Antimaterial works with your existing editor (VS Code, Cursor, Zed, JetBrains) and adds what they lack: parallel agents across isolated workspaces, a global activity feed, structured handoffs, and policy-based autonomy.
What does "agents as co-workers" actually mean?
Current AI tools treat agents as disposable command-line utilities. Antimaterial gives agents persistent identities with per-session memory, preferences, and clear status. When an agent blocks, it tells you exactly what it did and what it needs — like a colleague handing off work before leaving for the day.
How do parallel agents work without causing conflicts?
Each task runs in an isolated git worktree — a real, separate working directory with its own branch. Five agents can work on five features simultaneously without stepping on each other. When ready, you review and merge like any normal git workflow.
What happens when an agent gets stuck?
Instead of silently halting or making assumptions that require rework, agents reach out to you in a natural way — WhatsApp, Telegram, Slack — just like a regular coworker. They generate structured handoff cards explaining what they accomplished, where they blocked, and what decision they need. Reply inline; the agent resumes with full context. Async collaboration that actually works.
Can I control which actions agents can take autonomously?
Yes — policy-based autonomy lets you define trust levels per operation type. "Tests can run automatically. Database migrations require approval. Production config is read-only." You get a visual slider from manual to supervised to autonomous, per agent and per directory.
Do I need to switch editors to use Antimaterial?
No. Antimaterial is editor-agnostic by design. Keep using VS Code, Cursor, Zed, Neovim, or JetBrains. We integrate via "Open In" — you orchestrate agents in Antimaterial, and your preferred editor opens when you need to review or edit code directly.