# Runner, Claude Code and meeting commitments

> Runner, Claude Code and meeting commitments: review what was agreed, turn the right next action into a follow-up, and bring a clear brief to your codebase.

Canonical: https://www.runtheworld.ai/guides/runner-claude-code-meeting-commitments

Updated: 2026-11-16

## Start with the meeting record, not a memory of the meeting

A useful handoff begins with what the meeting actually said. Runner reads a meeting's transcript and notes and proposes the decisions, objections, risks, commitments and next actions it found. Each proposed item carries the evidence position it came from, so the next step starts with the conversation rather than a reconstructed summary.

That makes the meeting record the place to settle what was agreed. A decision can remain a decision, a commitment can become something to track, and a next action can move forward without turning every sentence from the call into a task.

## Review the commitment before it becomes work

Runner puts each proposed extraction in a review queue. Read the wording beside its transcript position or notes reference, then accept it, edit it into the work you mean, or reject it. A source that could not be anchored is visibly marked so it earns extra care instead of quietly becoming a fact.

This review is where a broad promise becomes a useful instruction. Keep the outcome small enough to own, name the decision that changes it, and preserve the evidence that explains why it matters.

- Accept wording that says what the meeting agreed.
- Edit a proposal until the next action is clear to the person doing it.
- Reject an item that does not belong in the record.

## Turn the reviewed next action into a follow-up

Once a commitment or next action is accepted or edited, Runner can set it as the linked opportunity's next action. It can also schedule a follow-up meeting from that reviewed item, keeping the commercial conversation and its next step together.

Choose the path that moves the promise forward. A customer conversation belongs on the follow-up meeting; a change to the product, a customer document or an integration belongs in the work brief the owner takes into the codebase.

## Add Runner to Claude Code when the next step belongs in code

Claude Code connects to Runner over MCP. Add Runner as an HTTP server, sign in through Runner and select the products the connection may see. The connection follows your Runner role, so it works inside the access you already have.

In Claude Code, the Runner connection can list a contact's meeting record: its state, meeting type and scheduled time. Use that record to orient the work around the right customer conversation while the reviewed commitment remains the source for the task itself.

## Give Claude Code a brief that carries the decision forward

A good code brief keeps the reviewed outcome in the first sentence: what was committed, which product or customer path it affects, and what a completed change looks like. Add the repository paths, the relevant constraints and the evidence you want the implementation to preserve. That gives Claude Code a bounded job instead of asking it to infer the meeting from a loose recap.

Keep the meeting record open while you work. It is the place to check the original wording, distinguish a promise from an idea, and decide whether a change needs a customer follow-up rather than another code change.

## Keep control as the meeting turns into progress

Runner keeps the commercial record under review while the repository work moves forward. Use the accepted meeting action for the task, return to the opportunity when the work changes its next step, and schedule the follow-up when the conversation needs to continue.

You can manage the Claude Code connection in Runner under Settings → MCP clients. Your connections are listed there, and revoking one stops the next request from using Runner.

