Build agents once. Deploy them everywhere.

No. Open the builder and start creating — no signup, no email, nothing. You only need an account if you want to save your work or collaborate with teammates.

Claude Code (CLAUDE.md), Cursor (.cursor/rules), and GitHub Copilot (.github/copilot-instructions.md). More platforms are on the roadmap based on what the community asks for.

The builder is free with no limits on agents or exports. Paid plans exist for teams that need shared libraries, collaboration, and admin controls.

Yes. Team plans let you share agent configs, maintain a shared skill library, and make sure everyone's AI assistants follow the same standards.

A skill is a reusable block of instructions for a specific task — like writing commit messages in conventional commits format, reviewing PRs against your team's checklist, or following a particular framework's conventions. You can build your own or grab them from the community library.

Yes. Exported configs are plain text files (Markdown, YAML, etc.) that live in your repo. Version them, diff them, review them in PRs — they're just files.

Your agent configurations are stored locally in your browser until you create an account. We don't train on your data, and we don't sell it. Paid team plans store configs server-side with encryption at rest.

You can absolutely write config files by hand. spaget helps when you want to reuse skills across projects, export to multiple platforms at once, or share configurations with your team. Think of it as the difference between writing HTML by hand and using a design tool — both work, one is faster for most people.

Not yet, but it's coming. We're building an importer that will parse your existing config files and bring them into the visual builder so you don't have to start over.

The core builder is not open source, but the skill library is community-driven and all exported configs are plain text files you fully own. We're considering open-sourcing parts of the platform in the future.