Coding agents
Coding agents
inline runs a server your coding agent can call, so you can get a review of your working changes without pushing anything. Connect it once and ask your coding agent to review with inline.
Anyone on the team can connect their own coding agent and run reviews with it. Turning the feature on for the workspace and setting its budgets is an admin task.
#What you get
A review before the pull request exists. You ask your coding agent to review the change it made, inline reads it, and the findings come back in the session you are already working in.
You can also pull the findings from a pull request that inline already reviewed back down into your editor, and work through them without switching to the browser.
#Connecting yours
Coding agents
Connect Claude Code, Codex, or any MCP-capable coding agent to inline. One connection powers both ad-hoc pre-PR reviews and visual plan submissions.
Connect your coding agent
claude mcp add inline --transport http https://inline.dev/api/mcp
Create a key on the API keys tab.
Copy the snippet for your coding agent from Connect.
There are snippets for Claude Code, the Codex CLI, and Cursor, Cline, Windsurf and Claude Desktop, plus the Server URL on its own for anything else.Paste your key in where the snippet says.
That is the whole setup. The connection gives your coding agent the review tools and the visual plan tools together.
#Getting a good review out of it
Say "review my changes with inline" before you open a pull request, and your coding agent sends the diff. How much inline can see decides how much it can find:
| What you give it | What inline can do with it |
|---|---|
| The diff alone | Read the change on its own terms. A shallow pass, and inline says so. |
| The changed files and what they import | Read the change in context. Ask your coding agent to attach them; the tool asks if it has yet to. |
| A pushed commit, reviewed at depth: "deep" | Explore the whole repository through the GitHub App. The deepest pass available. |
Every review reports which of the three it had, so you can tell a shallow answer from a thorough one.
#Visual plans before code
The visual plan tools arrive over the same connection, so one key turns both on. Ask your coding agent to "create a visual plan with inline" before it builds a feature, and it publishes wireframes, architecture and open questions to a link your team can comment on. See Visual plans.
#Turning it on for the workspace
Enable ad-hoc review on the Settings tab is the switch. It lets developers connect coding agents and run reviews before a pull request exists, and it is the same switch the visual plan tools arrive behind.
Two caps sit under it: a Monthly budget cap (USD) for the whole workspace, and a Per-developer monthly cap (USD) within it. Leave either blank for no cap. The Usage tab shows what has been spent and by whom.
Coding-agent reviews are included with Pro. See Plans and billing.