Set up Shed.
Two pieces, installed separately. The CLI deploys. The skill teaches your agent to drive it. Neither is open yet.
The pieces
The CLI is the only required one. Everything works without the skill; your agent just needs more hand-holding.
- The CLIsoonPackages your project, builds it on Shed, returns a live URL.
- The agent skillsoonTeaches Claude Code, Cursor, and Codex to write a SHED file and run the CLI.
- MCPA server your agent connects to instead of running the CLI.
By agent
The same two installs, written up for the agent you actually use: where its skill goes, what to ask it, and the command each ask ends up running.
- Claude CodeAnthropic's terminal agent. It reads the codebase, edits files, and runs commands in your shell.
- CursorAn editor with an agent in it, plus a CLI that runs the same agent headless in a terminal.
- Codex CLIOpenAI's coding agent for the terminal. It reads AGENTS.md, edits the repo, and runs commands.
- OpenCodeAn open-source terminal agent with a TUI, provider-agnostic, so the model behind it is your choice.
- Gemini CLIGoogle's open-source terminal agent. It reads GEMINI.md for context and runs commands in your shell.
- GitHub Copilot CLIGitHub's coding agent in the terminal, with its repositories and issues close at hand.
- AmpSourcegraph's coding agent, run from the terminal or from an editor extension.
- ClineAn open-source agent that runs as an IDE extension, a CLI, or a task board.
- AiderA pair-programming CLI that edits files and commits them, with git as the undo button.