How to install Grum with an AI coding agent
Connect Grum to a coding agent in the repository you are working on. Copy one prompt, let your agent run setup, then approve sign-in and access in your browser.
To install Grum, open your repository in a local coding agent, copy the setup prompt from Grum's install page, and paste it into the agent chat. Grum supports Cursor, Codex, Claude Code, and other local agents that can run commands in the repository. Your agent handles the CLI setup. You use the browser for sign-in and approvals, so you do not need to open a terminal or type commands yourself.
Open the Grum agent setup page to copy the current prompt. The page is public and includes the exact steps for your agent to fetch and follow Grum's setup guide.
Before you start
- Open the repository you want to connect in Cursor, Codex, Claude Code, or another local coding agent.
- Make sure Node.js 22 or newer is available to the agent.
- Keep a browser available for Grum sign-in, device-code approval, and any editor or GitHub access the setup requests.
The agent needs to work in the repository so it can inspect the project and configure the right integration. A browser-only chat cannot do those local setup steps.
Set up Grum in three steps
- Open the setup page. Go to www.grum.so/setup and copy the prompt.
- Ask your agent to set up Grum. Paste the prompt into the chat for the repository you want to connect. The prompt directs the agent to fetch Grum's live instructions and use its command-line tool for setup.
- Approve the requested access. Follow the browser steps for sign-in and approvals. Let the agent know if it asks for an editor permission that you want to review before allowing.
The prompt points to Grum's agent setup guide, which the agent reads as plain Markdown. This keeps the instructions current and readable without relying on the visual page or client-side JavaScript.
What your agent does during setup
Grum's CLI checks the repository, connects it to a Grum workspace, and configures the integration for the agent you are using. Depending on the repository and your account, setup may also ask you to choose a project, scan the code, or connect the live site and browser extension.
Setup pauses when it needs your sign-in or an approval. Read each browser request and make the decision yourself. The agent should not ask you to paste a sign-in secret into the chat or to type a command in a terminal.
Use a local coding agent
Grum setup needs access to files and commands in the repository, so run it from a local agent session with that repository open. Cursor, Codex, and Claude Code are examples. A cloud-only agent without access to your local repository cannot complete this setup flow.
If your agent is not one of those named integrations, it may still use Grum's generic setup path. That path can connect the repository and run checks, but automatic enforcement depends on the agent integration.
What happens after setup
Once connected, Grum gives your coding workflow a shared design contract: approved tokens, components, and usage guidance from the repository and any sources your team connects. The agent can read that agreement while it works, and Grum can surface drift or changes that need review.
Start with the Grum agent setup page when you are ready. It provides the current prompt and the agent instructions in one place.
Set up Grum with your agent