Skip to content
stacks

OpenRouter web chat

A web chat app on OpenRouter: streaming replies, a model picker, tool calls, contact extraction, server-side history, usage and cost, Markdown export and a stub-backed Playwright flow.

Category: app

In your existing repository

Ask your agent to check compatibility, follow this fragment’s brief, and verify the resulting project. What happens next

Applies to:
react-router
Requires fragments:
openrouter-ai

Add to your project

Paste the prompt into the coding agent working on your project.

View prompt
Add the openrouter-chat fragment to this existing repository. 1. Run npx @steamfield/stacks show openrouter-chat --json and check that it fits the project. If it does not, explain why before changing files. 2. Run npx @steamfield/stacks add openrouter-chat and follow the brief it prints. 3. In this repository, run npx @steamfield/stacks verify. Fix failures without weakening or skipping verification steps. 4. Summarize what changed and the verification result. Quote published stats only when they are available, including their interval and sample size. The stacks docs, written for agents, are at https://stacks.steamfield.io/llms.txt.
Or use the terminal
npx @steamfield/stacks add openrouter-chat
Verify steps
StepPhaseLayerCommand
app-e2echecktestbun run e2e
app-acceptancechecktestbun run test tests/app-acceptance.test.ts
app-eval-dry-runchecktestbun scripts/check-eval-dry-run.ts
Use with a new stack

Starting fresh instead? These stacks support this fragment.

  • react-routeroptional
    npx @steamfield/stacks new react-router --with openrouter-chat

Files

  • DESIGN.md.tmpl
  • biome-plugins/styling.grit
  • docs/acceptance/openrouter-chat.md
  • docs/chat-turn.md
  • docs/guidance/openrouter-chat/ai-sdk.md
  • docs/guidance/openrouter-chat/index.md
  • docs/guidance/openrouter-chat/openrouter.md
  • docs/guidance/openrouter-chat/rate-limiting.md
  • docs/guidance/openrouter-chat/styling.md
  • docs/guidance/openrouter-chat/testing.md
  • docs/guidance/openrouter-chat/ui.md
  • docs/guidance/openrouter-chat/verification.md

Usage

Among stacks projects in the 28 days through 30 Oct 2026: Project count: not enough runs yet; Green rate: not enough runs yet.

Weekly projects by stack

Projects whose final fragment set included this fragment, grouped by stack.

Weekly projects including this fragment, by stack: time span

Not enough published observations yet.

Not enough published observations yet.

Stacks projects per UTC week through 30 Oct 2026. Published stack counts only.

Data table
Week endingStackProjects
5 Jul 2026react-router–
12 Jul 2026react-router–
19 Jul 2026react-router–
26 Jul 2026react-router–
2 Aug 2026react-router–
9 Aug 2026react-router–
16 Aug 2026react-router–
23 Aug 2026react-router–
30 Aug 2026react-router–
6 Sept 2026react-router–
13 Sept 2026react-router–
20 Sept 2026react-router–
27 Sept 2026react-router–
4 Oct 2026react-router–
11 Oct 2026react-router–
18 Oct 2026react-router–
25 Oct 2026react-router–

By stack

How often this fragment stays in a default composition, or gets attached as an option.

react-router
Optional · attachedhidden: too few projects

– projects including the fragment

Stacks projects · 28 days through 30 Oct 2026. Counts rounded to 5.

Data table
StackProjectsRoleShare
react-router–Optional · attached–

Green rate with and without it

This compares projects; it isn't an effect of the fragment.

Not enough runs in this breakdown yet.

Stacks projects · 28 days through 30 Oct 2026. Counts rounded to 5.

Often used with

Co-occurrence above the baseline, within a stack. Required fragment pairs are excluded.

Not enough runs in this breakdown yet.

Stacks projects · 28 days through 30 Oct 2026. Counts rounded to 5.

Computed 31 Oct 2026, through 30 Oct 2026. Numbers describe stacks projects, not the ecosystem.