Getting Started
The AI that already knows your business.
Soleur remembers every decision, customer, and context — so your next prompt starts where the last one ended. Ship faster because the AI already caught up.
Takes 30 seconds. We’ll email you Soleur updates, including when hosted access opens.
Soleur is the Company-as-a-Service platform: 60+ AI agents and 60+ skills across 8 departments — engineering, marketing, legal, finance, operations, product, sales, and support — source-available (BSL 1.1), built on the Model Context Protocol (MCP).
Soleur is a source-available platform that turns a solo founder into a full company: 67 AI agents and 104 workflow skills across 8 departments, all sharing one knowledge base. You delegate work in plain language; the agents execute and remember every decision.
Built on open standards:
- Source-available under the Business Source License 1.1 — free to use, modify, and self-host; converts to Apache-2.0 four years after each release.
- Runs on agentic coding harnesses — self-hosted today on Claude Code, Grok Build, Codex, Devin CLI, and OpenCode, each with its own setup guide below.
- Connects tools and context through the Model Context Protocol (MCP) open specification.
Source-available. Install in your own harness.
Run it yourself
Prefer to run it yourself? Soleur is source-available and runs self-hosted on Claude Code, Grok Build, Codex, Devin CLI, and OpenCode today — the same 67 agents and 104 skills on each. Keep your knowledge base as plain files on your own machine, and join the waitlist if you want the hosted version when it opens.
The blocks below install Soleur on each harness. The Claude Code path is the one with a published marketplace; the other four install from this repository and each has its own setup guide. Every harness needs its own session: nothing is shared between them.
Claude Code
Self-hosted in Claude Code: signed in with your Claude plan or an Anthropic API key. This is the path with the published marketplace, and two commands is all it takes.
claude plugin marketplace add jikig-ai/soleur-marketplace
claude plugin install soleur@soleur-marketplace
Grok Build
Soleur loads from this repository as a Grok Build plugin. Check it loaded first, then start a session:
grok inspect # the soleur plugin, skills, agents, and MCP servers must appear
grok # interactive session
Full setup — subagent spawning, trust, and the command names Grok Build uses instead of Claude Code’s — is in the Grok Build onboarding guide.
Codex
Codex installs from a marketplace defined in this repository:
codex plugin marketplace add jikig-ai/soleur --sparse .agents/plugins --sparse plugins/soleur
codex plugin add soleur@soleur
Then read the Codex setup guide for local development, updates, and compatibility details.
Devin CLI
devin plugins install jikig-ai/soleur#plugins/soleur -y
Use -y to skip the confirmation prompt. Devin Cloud sessions run under Soleur Cloud Mode — skills, rules, and MCP carry, but plugin subagents and session hooks do not. See the Devin compatibility instructions for the cloud-vs-local capability matrix.
OpenCode
Install Soleur into your OpenCode config directory via npm (this needs bun on PATH), then start a session. The installer vendors the payload into ~/.config/opencode/soleur/ (or run bun plugins/soleur/scripts/install-opencode-adapter.ts from a local checkout).
npx @soleur/opencode install
# or: bunx @soleur/opencode install
npx @soleur/opencode install --check # prints opencode-install ok when the tree matches
Commands are bare (/go, /sync, /help) and skills are invoked by bare id (plan, not soleur:plan), because OpenCode has no soleur: namespace. Two guards decide shell commands on OpenCode, and both run for real — a deny blocks the call, an ask opens a prompt — but they decide shell calls only: actions taken through OpenCode’s code-mode execute are not covered. Soleur’s operator-stage approval gate is not wired on OpenCode: those flows refuse rather than approve. OpenCode has no Stop hook, so the pipeline’s <promise>DONE</promise> completion marker is advisory: a finished gate sequence is reported rather than hard-stopped, and autonomous skills rely on their own structural checks. /version is installed but reports an unknown version, because the canonical command resolves the plugin through CLAUDE_PLUGIN_ROOT, which this harness does not set. Full routing rules and the remaining capability differences: OpenCode instructions.
Claude Code: /soleur:go. Grok Build: /go. Codex: $soleur:go. Devin CLI: /soleur:go. OpenCode: /go.
| Step | Claude Code | Grok Build | Codex | Devin CLI | OpenCode |
|---|---|---|---|---|---|
| Entry | /soleur:go |
/go |
$soleur:go |
/soleur:go |
/go |
| Sync | /soleur:sync |
/sync |
$soleur:sync |
/soleur:sync |
/sync |
| Help | /soleur:help |
/local:help |
$soleur:help |
/soleur:help |
/help |
| Next skill | Skill tool soleur:<skill> |
Read SKILL.md in this process (/<skill>) |
Load $soleur:<skill>, or read SKILL.md |
Slash /soleur:<skill> |
skill tool, bare id (plan) |
/soleur:sync. Grok Build and OpenCode: /sync. Codex: $soleur:sync. Analyze the codebase and populate the knowledge base.Starting fresh? Claude Code and Devin CLI:
/soleur:go. Grok Build and OpenCode: /go. Codex: $soleur:go. Describe what you need.
claude plugin marketplace update soleur-marketplace advances the marketplace checkout; claude plugin update soleur@soleur-marketplace updates the plugin you actually run. Name the marketplace in both halves — on current releases the bare plugin name can fail with Plugin not found, and if you added this repository directly the id is soleur, so run claude plugin list and use whatever it prints beside Soleur. Skipping the second command leaves you on the old version while the new one looks installed — and if a fix still isn’t taking effect, claude plugin uninstall soleur@soleur-marketplace && claude plugin install soleur@soleur-marketplace is the step guaranteed to converge them.
The Workflow
Soleur follows a structured 6-step workflow for software development:
The 6-step workflow (each harness invokes it with its own entry command — see the table above):
1. brainstorm
Explore what to build
2. plan
Create a structured implementation plan
3. work
Execute the plan with quality checks
4. review
Run multi-agent code review
5. compound
Document learnings for future reference
6. ship
Prepare the feature for production deployment
Commands
/soleur:go
Unified entry point — routes to the right workflow skill
/soleur:sync
Analyze and document your codebase
/soleur:help
List all available components
Example Workflows
Building a Feature
/soleur:go build [feature] → brainstorm → plan → work → review → compound → ship
Generating Legal Documents
/soleur:go generate legal documents → Terms, Privacy Policy, GDPR Policy, and more
Fixing a Bug
/soleur:go fix [bug] → autonomous fix from plan to PR
Defining Your Brand
/soleur:go define our brand identity → interactive workshop producing a brand guide
Reviewing a PR
/soleur:go review → multi-agent review on existing PR
Validating a Business Idea
/soleur:go validate our business idea → 6-gate validation workshop
Tracking Expenses
/soleur:go review our expenses → routed to ops-advisor agent
Learn More
Common Questions
Frequently Asked Questions
What do I need to run Soleur?
Nothing to install. The hosted version runs in your browser once your access opens -- bring a workspace and your team. Prefer to self-host? The self-hosted version runs inside your own agentic harness -- Claude Code, Grok Build, Codex, Devin CLI, or OpenCode. Setup is two commands on Claude Code; the other harnesses install from this repository and each has its own setup guide.
Why a waitlist?
We're onboarding a founding cohort of 10 teams by hand so every workflow lands right. Access opens in waves as the hosted infrastructure matures -- we ship weekly and move people off the list as capacity grows. Want to skip the line? Run the self-hosted version today.
Does Soleur work on Windows, Linux, and macOS?
The self-hosted version runs anywhere its harnesses run: Claude Code, Grok Build, Codex, and Devin CLI all support Linux, macOS, and Windows via WSL, and OpenCode follows its own platform support — install inside whichever one you already use. The hosted version will be accessible from any browser on any operating system.
How much does Soleur cost?
See the pricing page for hosted plans (coming soon; join the waitlist) -- founder pricing starts at $49/month. The self-hosted version is free; your costs depend entirely on the model provider you use through your harness.
What is the difference between /soleur:go and individual skills?
/soleur:go (Claude Code and Devin CLI), /go (Grok Build and OpenCode), or $soleur:go (Codex) is the unified entry point that classifies your intent and routes to the right workflow automatically. Individual skills like brainstorm, plan, work, and review can be invoked directly when you know exactly which stage you need — Skill tool soleur:<skill> on Claude Code; Read that skill’s SKILL.md in this process on Grok Build; the skill tool with the bare id on OpenCode.
Can I use Soleur with an existing project?
Yes. Claude Code and Devin CLI: /soleur:sync. Grok Build and OpenCode: /sync. Codex: $soleur:sync. Analyze the codebase and populate the knowledge base with your project's conventions, architecture, and patterns. Soleur adapts to your existing codebase rather than requiring a fresh start.
What is the difference between the hosted version and self-hosted?
Both versions ship the same agents and skills. The self-hosted version runs inside your own harness — Claude Code, Grok Build, Codex, Devin CLI, or OpenCode — with full access to your own files. The hosted version (coming soon) adds a web dashboard, managed infrastructure, real-time agent orchestration, team collaboration, and email support. Both access the same 67 agents and 104 skills.