By reboot-dev
Use Reboot to build AI Chat Apps (MCP Apps) for ChatGPT, Claude, VSCode, Goose, and others.
Build a Reboot application from a user description. Routes to the chat-app skill (MCP Chat Apps for ChatGPT, Claude, VSCode, Goose) or the web-app skill (standalone web apps with a browser frontend). Commits to a route only when the prompt verbatim names the front-door (MCP/Claude/ChatGPT for chat-app; a URL/SPA/"website" for web-app); otherwise asks the user. Does NOT infer the front-door from the app's domain (CRM, todo, dashboard, blog, …) — those describe what the app does, not where it lives.
Build complete Reboot AI Chat Apps (MCP Apps) for ChatGPT, Claude, VSCode, Goose, and other MCP hosts. Layers on top of the python skill for backend mechanics; covers what's specific to MCP Chat Apps — the User-type front door, MCP tool exposure, the UI() method type, and the full React/Vite scaffolding.
Reboot Python framework for building transactional microservices with durable actor state. APIs are defined in pydantic Python (`reboot.api`). Use this skill when writing Python code for a Reboot application, defining APIs with reader/writer/transaction/workflow methods, implementing Servicers, calling actor refs across services, scheduling work, building durable workflows with the right call primitive (`.per_workflow(alias)` / `.per_iteration(alias)` / `.always()` for Reboot calls; `at_least_once` / `at_most_once` for external calls; `until` / `until_changes` for reactive waiting on Reboot state), calling an LLM / building an AI agent in the backend via the durable `reboot.agents.pydantic_ai.Agent`, or testing Reboot applications with the `Reboot()` test harness.
Run an existing Reboot application locally. Detects whether the project is an MCP Chat App or a standalone Web App, makes sure dependencies and secrets are in place, then starts every process the app needs — the backend (`rbt dev run`) and the frontend dev server (for Chat Apps it also opens the setup wizard, from which the user can launch MCPJam on demand). Use this to bring an app back up, e.g. at the start of a new session.
Build complete Reboot Web Apps — a Reboot backend behind a standalone browser-facing React frontend, served at a normal URL (not embedded in an MCP host). Layers on top of the python skill for backend mechanics; covers what's specific to standalone Web Apps — no MCP front door, no UI() methods, normal React/Vite SPA scaffolding, and Reboot auth for browser users.
Executes bash commands
Hook triggers when Bash tool is used
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A plugin for building on Reboot from your coding agent. The same skills work in both Claude Code and Codex.
| Skill | Description |
|---|---|
app | Build a Reboot app from a description — routes to chat-app or web-app |
chat-app | Build AI Chat Apps (MCP Apps) for ChatGPT, Claude, VSCode, Goose, and others — layers on top of python |
web-app | Build standalone Reboot Web Apps — a Reboot backend behind a browser-facing React frontend — layers on top of python |
run | Run an existing Reboot app — detects MCP Chat App vs. Web App and starts every process it needs |
python | Reboot Python framework reference: proto- or pydantic-defined APIs, Servicers, contexts, refs, scheduling, and testing |
The skill files are tool-agnostic. Claude Code invokes skills by name
(e.g. /chat-app); Codex selects a skill automatically from its
description. Both read the same SKILL.md files and references/.
The quickest path installs for whichever of Claude Code / Codex you have — having only one is fine, the installer skips the other:
curl -fsSL https://reboot.dev/install.sh | bash
Restart your agent afterward so the new skills and configuration load.
If Codex is detected, the installer pauses to ask whether to disable
Codex's sandbox globally — a requirement to work around
openai/codex#24933.
Decline (n) and the Codex install is skipped entirely; accept (Y,
the default) and the installer writes the opt-out into
~/.codex/config.toml. See Differences in Codex vs. Claude Code
for the full rationale. For non-interactive installs (CI/CD), set
REBOOT_PLUGIN_DISABLE_CODEX_SANDBOX=yes (or no) to pre-answer
the prompt.
Add the Reboot skills marketplace and install the plugin:
# 1. Add the Reboot skills marketplace (one-time).
claude plugin marketplace add reboot-dev/reboot-plugin
# 2. Install the plugin.
claude plugin install reboot@reboot-plugin
To auto-enable for your team, add to your project's
.claude/settings.json:
{
"extraKnownMarketplaces": {
"reboot-plugin": {
"source": {
"source": "github",
"repo": "reboot-dev/reboot-plugin"
}
}
},
"enabledPlugins": {
"reboot@reboot-plugin": true
}
}
Or run from a checkout without installing:
git clone https://github.com/reboot-dev/reboot-plugin.git
claude --plugin-dir ./reboot-plugin
install.sh uses Codex's native plugin system. Equivalent to:
# Register the marketplace (a local checkout, or the GitHub repo).
codex plugin marketplace add ./reboot-plugin # or: reboot-dev/reboot-plugin
# Install the plugin (skills and hooks are picked up from the bundled
# .codex-plugin/plugin.json + .agents/plugins/marketplace.json).
codex plugin add reboot@reboot-plugin
install.sh then merges a small marked region into ~/.codex/config.toml
that:
features.hooks = true — off by default),uv, node, rbt, …) to
PATH for every subprocess via shell_environment_policy.set.PATH.
Codex SessionStart hooks can't modify PATH the way Claude Code's can,
so this is how the bin/ prepend is wired. set replaces PATH
wholesale, so the install-time PATH is baked in after the plugin's
bin/ — re-run install.sh to refresh it, andsandbox_mode = "danger-full-access")
to work around
openai/codex#24933;
see the Differences section
for context. install.sh asks for explicit consent before writing
this; if you install manually you must add it yourself.If you check out the plugin and work inside it, the bundled
.agents/skills directory makes Codex discover the skills with no
install at all (skills only — hooks and the PATH prepend still need the
full install).
The skills behave identically; three pieces of lifecycle automation differ because of Codex limitations:
npx claudepluginhub reboot-dev/reboot-plugin --plugin rebootUltra-compressed communication mode. Cuts ~75% of tokens while keeping full technical accuracy by speaking like a caveman.
Memory compression system for Claude Code - persist context across sessions
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Curate auto-memory, promote learnings to CLAUDE.md and rules, extract proven patterns into reusable skills.