soleur

The Company-as-a-Service platform. Collapse the friction between a startup idea and a billion-dollar outcome.

67 agents across engineering, finance, legal, marketing, operations, product, sales, and support – compounding your company knowledge with every session.

What is Soleur?

Soleur gives a single founder the leverage of a full organization. 67 agents, 4 commands, and 105 skills that compound your company knowledge over time – every problem you solve makes the next one easier.

Installation

Devin CLI:

devin plugins install jikig-ai/soleur#plugins/soleur -y

Start a Devin session and use /soleur:go . Use -y to skip the confirmation prompt. If the install hangs or fails, clone the repository and run bash scripts/setup-devin.sh to install from the local checkout.

Update to the latest version with devin plugins update soleur, or devin plugins update to refresh all installed plugins. If you see a transient “content could not be fetched” warning, Devin will retry automatically; run the update command again if it persists.

The plugin also loads in Devin Cloud sessions (/handoff or web app). Cloud sessions run under Soleur Cloud Mode — plugin subagents and SessionStart/SessionEnd hooks are absent, so fan-out runs sequentially inline with Reviewed-Coverage: sequential-fallback disclosure and secrets/production steps require an explicit session-scoped acknowledgement. See the capability matrix.

Codex:

codex plugin marketplace add jikig-ai/soleur --sparse .agents/plugins --sparse plugins/soleur
codex plugin add soleur@soleur

Start a new Codex session, review the bundled hooks in /hooks, and use $soleur:go . See the Codex setup guide for local development, updates, and compatibility details.

Grok Build:

Soleur loads the same in-repo plugin under Grok Build. From the repository root, confirm the plugin is discovered and start a session:

grok inspect    # the soleur plugin, skills, agents, and MCP servers must appear
grok            # interactive session

Use /go (Grok’s bare entry name), not /soleur:go. If grok inspect does not list Soleur, stop — there is no grok plugin install command to fall back on today, so install is done by pointing Grok at this repository (.grok/config.toml, merged via the project plugin loader) rather than a marketplace command. Full setup — subagent spawning, trust, and command naming — is in the Grok Build onboarding guide.

OpenCode:

Install Soleur into your OpenCode config directory via npm (this needs bun on PATH), then start a session:

npx @soleur/opencode install
# or: bunx @soleur/opencode install

Verify the install with npx @soleur/opencode install --check — it prints opencode-install ok when the vendored payload in ~/.config/opencode/soleur/ matches. (From a local checkout of this repository, you can also run bun plugins/soleur/scripts/install-opencode-adapter.ts and keep the checkout in place.) Use /go . 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 DONE 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.

Google Antigravity CLI (agy):

Soleur loads as an Antigravity plugin via .antigravity-plugin/plugin.json. From a repository root containing the plugin:

agy

Start an Antigravity session and use /soleur:go . Tool calls are translated natively to Antigravity primitives (view_file, write_to_file, replace_file_content, run_command, invoke_subagent), with background polling handled reactively through schedule rather than foreground sleep loops. See the Antigravity instructions for full mapping and dynamic domain subagent delegation.

Claude Code (recommended, via the published marketplace):

claude plugin marketplace add jikig-ai/soleur-marketplace
claude plugin install soleur@soleur-marketplace

This installs the plugin subtree only — about 10 MiB in well under a minute.

For existing codebases: Run /soleur:sync first to populate your knowledge-base with conventions and patterns.

Updating

Updating is two steps, and the first one looks sufficient on its own:

claude plugin marketplace update soleur-marketplace       # advances the marketplace checkout ONLY
claude plugin update soleur@soleur-marketplace            # updates the installed plugin (restart to apply)

Both halves name the marketplace. On current releases the bare plugin name can fail with Plugin not found — an Anthropic collaborator confirmed the @ form as the reliable one on anthropics/claude-code#76882 (2026-08-17). soleur-marketplace is the marketplace id on the path above; if you added this repository directly the id is soleur instead, so run claude plugin list and use whatever it prints beside soleur.

marketplace update moves the marketplace checkout to the new HEAD. It does not touch the plugin install, which keeps its own gitCommitSha in installed_plugins.json. Soleur’s commands resolve ${CLAUDE_PLUGIN_ROOT} to the install, never the marketplace checkout — so after step 1 alone you can read a fix as shipped while every run still executes the old payload.

If the fix still isn’t taking effect after both steps, reinstall outright:

claude plugin uninstall soleur@soleur-marketplace && claude plugin install soleur@soleur-marketplace

That used to be the only step that worked, and the reason no longer holds. The manifests are keyless as of 2026-08-12, so the CLI now records a compound version whose leading half is the delivered commit — measured across two installs on the same day as 43c7d3d79542-31fddb37 then 0d6443960662-31fddb37. The string therefore changes with every commit, the install directory name changes with it, and plugin update has something to compare. The old frozen 0.0.0-dev sentinel is what made an install sit months stale while every command reported success; that is the defect the keyless manifests removed.

Two consequences worth knowing:

• A full reinstall is still the surest way to converge a stubborn install, but it is a fallback now rather than the only mechanism.
• Because the directory name is derived from that changing version, each update leaves the previous cache directory behind. There is no CLI verb to reclaim them. See the reclaim section of knowledge-base/engineering/operations/runbooks/plugin-delivery-recovery.md.

The Workflow

The recommended way to use Soleur:

/soleur:go 

This classifies your intent and routes to the right workflow. For the full step-by-step:

brainstorm  -->  plan  -->  work  -->  review  -->  compound

Commands

Claude Code: /soleur:go. Grok Build: /go. Codex: $soleur:go. Devin CLI: /soleur:go. OpenCode: /go.

Per-harness setup guides: Claude Code · Grok Build · Codex · Devin · OpenCode.

Workflow Skills

See full component reference for all agents, commands, and skills.

Your AI Organization

Learn More

• Getting Started – Installation, first steps, and workflow overview
• Vision – Where Soleur is headed
• Changelog – Release history
• Community – Discord, contributing, and support

Contributing

We welcome contributions! See CONTRIBUTING.md for how to get started, file issues, and submit pull requests.

Community

Join the conversation on Discord.

Credits

This work builds on ideas and patterns from these excellent projects:

• Compound Engineering Plugin - The original Claude Code plugin that inspired this work
• OpenSpec - Spec-driven development (SDD) for AI coding assistants
• Spec-Kit - GitHub’s toolkit for spec-driven development

License

BSL 1.1 (Business Source License). See LICENSE for details.

Source-available for all individual and internal company use. The only restriction is offering Soleur as a competing hosted service. Each version converts to Apache-2.0 after 4 years. Versions v3.0.10 and earlier remain Apache-2.0.