Getting started
Integrations
Connect GitHub, Linear, Sentry, and PostHog so agents can work with your issues, errors, and analytics from chat.
Raven connects external services to the work in your workspaces. GitHub and 1Password connect once for the app; Linear, Sentry, and PostHog connect separately for each Raven project, and each connection names the one team or project the agent can reach.
Settings › Integrations is the overview: GitHub’s and 1Password’s connections, and for each of the other three a row per project showing whether it’s connected, with a link straight to that project’s settings.
GitHub
Choose Connect beside GitHub, copy the code Raven shows, and approve it on GitHub’s device page in your browser. This enables pull-request status and merging for worktree workspaces with a GitHub remote. See Pull requests for opening a PR and the GitHub CLI requirement.
Linear
In Settings ›
Ask in plain language or use /linear:
/linear show open issues assigned to me/linear create an issue to fix the empty search state/linear move ADR-123 to In Progress
The agent can read and update issues, projects, cycles, documents, and initiatives. A Linear project groups issues; it is separate from the repository you added to Raven. Build or Plan mode can create or update work; Ask can only read.
Issue cards are live: change the status, priority, assignee, or title on the card and it’s written to Linear; Refresh from Linear pulls the latest. A single-issue card can also Start in new worktree workspace (or a local one) — a workspace briefed on that issue, whose pull request will close it with a Fixes line.
Sentry
In Settings ›
Ask the agent to investigate errors, inspect an issue’s events and stack trace, look at error volume over time, or compare releases. When it shows a result, the card keeps the evidence beside the discussion of a fix, and each issue row links to Sentry.
PostHog
In Settings ›
Ask questions such as “Which events arrived today?” or “How many people used search this week?” The agent can read the event schema, run trends, funnels, and HogQL queries, run saved insights, and check that an event arrived. Charts and tables show as cards.
1Password
The agent can sign in to web pages in Raven’s browser with logins from your 1Password vault, without ever seeing a password. Settings › Integrations › 1Password › Set up opens its own page: it installs the 1Password command-line tool (through Homebrew) and needs Integrate with 1Password CLI turned on in the 1Password app. Then Import from 1Password… picks the logins Raven may use, and New workspaces start with decides whether a new workspace gets All imported logins or No logins; each workspace’s browser can narrow its own list. Raven keeps login names only, and types the password itself when the agent signs in.
Your Claude MCP servers
MCP servers you’ve added to Claude Code in the terminal — with claude mcp add, at user scope or in the project — connect in Raven’s Claude chats too, in every workspace of the project, worktrees included. They’re read when a chat starts, so a server you add shows up in the next new chat. A malformed ~/.claude.json fails the turn with an error card rather than quietly dropping your servers.
Cards in the conversation
Results don’t become cards on their own. The agent answers in prose, and when a chart, a list, or a stack trace says more than a sentence would, it shows the result as a card — one or two per answer at most, each with a link to open it in the service. Ask for the data (“show me the trend”) and you’ll get the card. The same goes for settings: when the agent points you at a switch, it can show a Take me there card that opens Settings on that exact row; the same card opens the Browser or Simulator surface when the agent has something to show there, and its screenshots and clips sit in the reply as pictures.
Availability and scope
Raven is free, and every integration is included. Agent subscriptions are separate; see Agents, models and modes.
A connected section shows its binding — the team or project — with a Manage menu to change it, reconnect, or disconnect. Check the binding before asking about another product’s data. Disconnecting a service turns its tools off for that Raven project.