Cloud dev environments for Claude Code — run tasks, reviews, and CI in ephemeral sandboxes via SpaceCode
Use this agent when the user wants an independent code review from a cloud sandbox. Examples: <example> Context: User wants their code reviewed before a PR. user: "Can you review my code changes?" assistant: "I'll use the code-reviewer agent to dispatch a code review to a cloud sandbox." <commentary> User asks for code review — dispatch to cloud for independent analysis. </commentary> </example> <example> Context: User is about to create a pull request. user: "I'm ready to create a PR, but want a review first" assistant: "Let me use the code-reviewer agent to get an independent review of your changes." <commentary> Pre-PR review request triggers cloud code review. </commentary> </example> <example> Context: User wants a second opinion on their implementation. user: "Can you get a fresh pair of eyes on this branch?" assistant: "I'll dispatch a code review agent to analyze your branch independently." <commentary> Request for independent review triggers the cloud reviewer. </commentary> </example>
Use this agent when the user wants to run tests, linting, or type-checking in a cloud sandbox. Examples: <example> Context: User wants to run tests remotely. user: "Run the tests in the cloud" assistant: "I'll use the code-ci agent to run your test suite in a cloud sandbox." <commentary> User asks to run tests remotely — dispatch to cloud CI. </commentary> </example> <example> Context: User wants CI-like validation without local setup. user: "I don't have the test deps installed locally, can you run them remotely?" assistant: "I'll use the code-ci agent to run the tests in a cloud environment." <commentary> No local test setup — cloud CI is the right tool. </commentary> </example> <example> Context: User wants to validate before pushing. user: "Run lint and tests before I push" assistant: "I'll use the code-ci agent to run lint and tests in a cloud sandbox." <commentary> Pre-push validation request triggers cloud CI. </commentary> </example>
Use this agent when the user wants to explore or understand a codebase they don't have locally. Examples: <example> Context: User wants to understand an unfamiliar repo. user: "What does the owner/some-lib repo do? How is it structured?" assistant: "I'll use the code-explorer agent to analyze that repo in a cloud sandbox." <commentary> User wants to understand a repo they don't have — explore in cloud. </commentary> </example> <example> Context: User wants to evaluate a dependency. user: "Can you look at how org/framework handles authentication?" assistant: "I'll use the code-explorer agent to explore that repo's auth implementation." <commentary> Exploring a specific aspect of an external repo. </commentary> </example> <example> Context: User wants an architecture overview. user: "Give me an overview of the architecture of owner/big-project" assistant: "I'll use the code-explorer agent to analyze the project architecture in a cloud sandbox." <commentary> Architecture exploration of a remote repo. </commentary> </example>
Use this agent when the user wants to run tasks across multiple repositories. Examples: <example> Context: User wants to update a dependency across repos. user: "Update lodash to v5 in all my repos" assistant: "I'll use the multi-repo-runner agent to update lodash across your repositories." <commentary> Multi-repo update request triggers batch execution. </commentary> </example> <example> Context: User wants to apply a change to several projects. user: "Add the new lint rule to repo-a, repo-b, and repo-c" assistant: "I'll use the multi-repo-runner agent to apply the lint rule across all three repos." <commentary> Same change across multiple repos — batch execution. </commentary> </example> <example> Context: User mentions "across repos" or "all repos". user: "Run security audit across all our microservices" assistant: "I'll use the multi-repo-runner agent to dispatch security audits to all repos in parallel." <commentary> Cross-repo task triggers multi-repo orchestration. </commentary> </example>
Run the same task across multiple repos in parallel. Use when user says "batch", "multi-repo", "across repos", "all repos", or wants to apply changes to several repositories at once.
Run a task in a cloud sandbox. Use when user says "run in cloud", "remote exec", "cloud sandbox", or wants to execute code/commands in an ephemeral environment.
Dispatch a code review to a cloud sandbox. Use when user says "cloud review", "remote review", "review my code remotely", or wants an independent code review from a separate Claude instance.
Check status of cloud tasks. Use when user says "cloud status", "task status", "check tasks", "what's running", or wants to see active/recent cloud sandbox tasks.
Executes bash commands
Hook triggers when Bash tool is used
External network access
Connects to servers outside your machine
Uses power tools
Uses Bash, Write, or Edit tools
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.
Run tasks, code reviews, and CI in ephemeral cloud sandboxes — directly from Claude Code.
/plugin install github:s-p-a-c-e-code/spacecode-plugin
On first use, you'll be prompted to sign in with GitHub via OAuth. No API keys needed.
| Tool | Description |
|---|---|
remote_exec | Run a task in an ephemeral cloud sandbox |
remote_exec_batch | Run tasks across multiple repos in parallel |
remote_tasks | List active/recent tasks |
remote_task_status | Get task details |
remote_cancel | Cancel a running task |
remote_wait_all | Wait for tasks to complete |
agent_create | Create a service account |
agent_list | List agent accounts |
| Command | Description |
|---|---|
/cloud-exec | Guided cloud task execution |
/cloud-review | Remote code review |
/cloud-batch | Parallel multi-repo tasks |
/cloud-status | Task dashboard |
| Agent | Triggers |
|---|---|
cloud-reviewer | "review my code", "code review", pre-PR |
cloud-ci | "run tests", "lint", "type-check" remotely |
multi-repo-runner | "across repos", batch operations |
cloud-explorer | "explore repo", "how does X work" for external repos |
rm -rf /, git push --force, etc.This plugin connects to the SpaceCode MCP server at mcp.spacecode.app. Each task runs in an ephemeral Cloudflare container with:
Code changes are returned as git diffs but never auto-pushed.
Authentication uses OAuth 2.1 with PKCE via GitHub. Claude Code handles the flow automatically — just sign in with GitHub when prompted.
MIT
npx claudepluginhub g-a-l-a-c-t-i-c/spacecode-plugin --plugin spacecodeComprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Consult multiple AI coding agents (Gemini, OpenAI, Grok, Perplexity, plus codex, antigravity, and grok CLIs when installed) to get diverse perspectives on coding problems
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Production-grade engineering skills for AI coding agents — covering the full software development lifecycle from spec to ship.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review