Skip to content

docs: Node req/res bridge, runTurn options, and what the CLI's API is - #470

Merged
anurag629 merged 1 commit into
devfrom
docs/advanced
Oct 30, 2026
Merged

anurag629 merged 1 commit into
devfrom
docs/advanced

Conversation

@anurag629

Copy link
Copy Markdown
Member

The last of F7's docs gaps from #440: the low-level APIs.

  • server/fetch-runtimes.mdx, new section "Node's http module, Fastify, Koa": turns Node's req into a Request and streams the Response back to chatcopsVercelHandler, with the session path routed and the client IP taken from the socket. I ran the same code against a scripted provider before writing it up. /session returned a token, the reply streamed, and a request without a token got 401 session_required.
  • packages/server/README.md, "Custom integrations": it showed handleChat, which streams the 0.5 format and sends no session token, so with feat(server)!: require session tokens by default, with allowAnonymous to opt out #462's default it gets session_required on every request. It now points to the Fetch handler and the bridge. It also says why bridging beats calling createChatHandler directly: the handler already does CORS, origins, body limits, pings, sessions and the 0.5 format.
  • core/providers.mdx: a table of every runTurn option and what the turn returns.
  • core/testing.mdx: the CLI's API is the command, its flags and defineConfig. Its other exports can change in a minor release until cli 1.0.

Tested: docs:check (147 blocks) and lint pass. The docs bot index gets rebuilt with the 1.0-rc release, since several docs PRs will land before then.

@anurag629
anurag629 merged commit 540822e into dev Oct 30, 2026
5 checks passed
@anurag629
anurag629 deleted the docs/advanced branch October 30, 2026 03:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant