Conversations
inline isn’t only a one-way reviewer. You can talk to it directly in a pull request by mentioning @inline in a comment. Every interaction is answered by the bot as the repo’s posting identity and logged in the portal for observability.
# Commands
| Comment | What it does |
|---|---|
@inline ask <question> |
Answer a question about the PR or codebase. |
@inline full review |
Re-review the entire PR from scratch (ignore the incremental base). |
@inline learn <rule> |
Record a learning — a convention to remember. |
@inline resolve |
Resolve the finding thread it’s posted in. |
@inline help |
List available commands. |
An ask runs a bounded agentic loop with the same read-only repo tools the reviewer uses (read_file, search_code, and — when configured — web research), so it can actually look at the code before answering rather than guessing.
# How it works
A comment mentioning @inline fires a webhook that enqueues the command. Handling is idempotent on the comment — the same comment is never answered twice. The bot answers with Claude, bounded by a step cap so a conversation always terminates cleanly.
# The Conversations page
Every command interaction is persisted and listed under Conversations in the portal, with:
- the repo, PR, and commenter,
- the command kind (ask / review / learn / resolve / help),
- the question and inline’s answer,
- the model used, cost, duration, and status.
Admins can filter by repo, kind, or status and search the text. It’s the audit trail for everything anyone asked inline and everything it answered — useful for spotting recurring questions (which often make good skills) and for tracking spend on interactive use.