Skip to content

docs(ai-transport): document interruption and steering#3471

Draft
zknill wants to merge 3 commits into
mainfrom
zak/docs-steering
Draft

docs(ai-transport): document interruption and steering#3471
zknill wants to merge 3 commits into
mainfrom
zak/docs-steering

Conversation

@zknill

@zknill zknill commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Documents the AI Transport interruption and steering feature, and verifies the affected agent-side docs against the SDK source (the ait-1017-steering-steps branch, the release target).

  • Replaces the old features/interruption.mdx with features/interruption-and-steering.mdx, covering the three change-direction patterns: steer the active Run with a follow-up prompt, cancel and re-prompt, or send alongside as a concurrent Run.
  • Adds a "Steer a Run" section to concepts/runs.mdx documenting the client-side steer() API ({ published, outcome }, consumed/runTerminalReason).
  • Repoints the nav entry ("Interruption" → "Interruption and steering") and cross-links in cancellation.mdx, concurrent-turns.mdx, double-texting.mdx, and why/index.mdx.
  • Fixes the agent loop in the steering page to match the SDK: createRun is synchronous (no await), drain run.view with loadOlder() before run.start(), feed run.view.getMessages() to the model (not run.messages, which is turn-only), and tear down with session.end(). Corrects a stray ActiveRun reference to ClientRun.
  • Fixes the cancellation page's server-side abort-signal snippet, which fed run.messages (this Run's own turn) straight to the model, losing all prior conversation context. It now drains run.view and feeds the full conversation.

zknill added 2 commits July 14, 2026 11:55
Replace the Interruption feature page with a combined Interruption and
steering page, and add a "Steer a Run" section to the Runs concept.
Repoint the nav entry and all cross-links from the old page, with a
redirect_from to preserve the old URL.

The page documents three ways a client changes direction mid-response:
steer the active Run with a follow-up prompt, cancel and re-prompt, or
send alongside as a concurrent Run.
The server-side abort-signal example fed run.messages straight to the
model. run.messages is only the current Run's own turn (its triggering
input plus its output), not the multi-turn conversation, so a model
called with it loses all prior context.

Drain run.view with loadOlder() before run.start() and feed
run.view.getMessages() through convertToModelMessages, matching the
agent hydration pattern used across the getting-started and
interruption-and-steering pages.
@zknill zknill added the review-app Create a Heroku review app label Jul 14, 2026
@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 9d4e68e2-cbe1-47ab-9024-dfaefd2b657b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch zak/docs-steering

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@ably-ci ably-ci temporarily deployed to ably-docs-zak-docs-stee-dhtkzh July 14, 2026 11:06 Inactive
Order the Features section entries by name so the nav is predictable
and new pages have an obvious insertion point.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

review-app Create a Heroku review app

Development

Successfully merging this pull request may close these issues.

2 participants