[only21mil]

Problem

Pi, Muse Code, and fx ship in v0.1.6, each with its own adapter and setup guide, but the provider lists leave some of them out. The README names fx but not Pi or Muse Code. AGENTS.md names none of the three, so agents working on provider-shaped features skip them in the "Hit every surface" check. The FAQ names Pi and Muse Code but not fx.

Change

• README: add Pi and Muse Code to the two provider lists, plus one setup line each, in the same shape as the fx line from docs(readme): list fx as a supported provider #25974, linking to docs/user/providers-pi.md and docs/user/providers-muse.md.
• AGENTS.md: add Pi, Muse Code, and fx to the summary line and the "Providers" bullet.
• FAQ: add fx to the "Bring your own" list.

Names match the provider labels in packages/contracts/src/model.ts. The setup lines restate the install and login steps from each provider's guide and from docs/user/install.md. Like the existing Cursor, Grok Build, OpenCode, and fx lines, they leave the enable-in-Settings step to the linked guide.

Scope and approval

A factual docs correction for providers that already ship. It adds no capability and changes no model eligibility. It follows #25974, which added fx to the README the same way.

Verification

• Checked that the Pi, Muse Code, and fx guides were added in commits that are ancestors of v0.1.6, and that packages/provider-pi, packages/provider-muse, and packages/provider-fx each have a src/server/adapter.ts.
• Compared each new setup line with providers-pi.md § Set Up Pi, providers-muse.md, and the install.md § Providers table: the same URLs and login commands.
• vp run check:changed 1d626d02d95f9a2343553f6498037ee82290d304: format passes; knip and the unused-patch check are skipped because no code or manifest changed.

Not checked: no UI or runtime change, so no screenshots. I did not render the README on GitHub.

Prior PRs

#25974 by DarlingtonDeveloper added fx to the README provider lists. This PR finishes those lists the same way.

Generated with Claude Opus 5.5 and GPT-6.1 Terra and GPT-6.1 Sol in T3 Code Nightly

[macroscopeapp]

Approvability

Verdict: Approved at c169520

Macroscope's review found this PR approvable — Updates provider lists and adds Pi and Muse Code setup references. These documentation-only changes do not alter product defaults or runtime behavior.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: pingdotgg/t3code
• Branch: main
• File: .coderabbit.config.ts
• Commit: 71646e0
• Layers: Repository TS config
• Review profile: CHILL
• Plan: Advanced
• Run ID: 5909112c-d74f-4c21-8c76-9c9c000c273f

Commits

Reviewing files that changed from the base of the PR and between c169520 and b51229c.

Files selected for processing: 1

• AGENTS.md

Files skipped from review as they are similar to previous changes: 1

• AGENTS.md

Limit details: You’ve used all 10 included reviews currently available.

Walkthrough

Documentation now lists Pi, Muse Code, and fx as supported providers. The README adds installation and authentication instructions for Pi and Muse Code, with links to setup guides.

Changes: Provider support documentation

Layer / File(s)	Summary
Document provider support and setup README.md, AGENTS.md, docs/user/faq.md	Provider lists now include Pi, Muse Code, and fx. The README adds installation and authentication instructions for Pi and Muse Code, with links to setup guides.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Suggested reviewers: juliusmarminge, t3dotgg

Merge Risk: Minimal · up to b5122

The provider documentation update is ready to merge after normal checks.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title clearly and concisely describes the main documentation change: listing Pi, Muse Code, and fx as supported providers.
Description check		The description includes the required Problem, Change, Scope and approval, and Verification sections. It explains the documentation omissions, the exact changes, the rationale and prior PR context, an…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Description check

Explanation

The description includes the required Problem, Change, Scope and approval, and Verification sections. It explains the documentation omissions, the exact changes, the rationale and prior PR context, and the checks performed with limitations noted.

Finishing Touches

Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.

[maria-rcks]

Note

Written by gpt-6.1-sol on behalf of Maria

Verified in a real dev environment

verified as-is at c169520a1a4b8e75af847df367564a21890f6f46 on linux. this is a documentation correction, with no runtime code changes.

• reproduced the omission on github/main (e925dd681904f8a1ead0502ecca3f65f5bc28146) in a separate worktree: the readme leaves out pi and muse code, the faq leaves out fx, and the provider checklist leaves out all three.
• ran vp i and the real dev app on main, stopped that server, then installed and ran the exact pr head with isolated task state. used repo playwright and /usr/bin/google-chrome, without mocks or seeded data.
• rendered the before/after readme on github and clicked both added setup-guide links. they open the correct guides and match the documented host-side login commands. checked the faq and agent checklist corrections against the existing provider adapters.
• created a project for a real git repo through the web app. selected codex gpt-6.1-sol, sent a read request, then a follow-up reading the pr readme and linked guides. both real provider turns completed and the follow-up quoted the corrected provider list. reload restored both replies.
• neighboring behavior: settings still offers pi, muse code, and fx through add provider; codex model selection and follow-up conversation work.

blacksmith-check: installed dependencies on the task worker
vp run check:changed 1d626d02d95f9a2343553f6498037ee82290d304
check:changed: 3 files since 1d626d02d95f
pass format
unused patch check skipped: no dependency files changed
knip skipped: no code or manifest changed

the worker needed its shallow history deepened before the check could find the base. current github checks pass, with the expected docs-only skips. no source edits or pushes were needed.

Not verified

pi, muse code, and fx installation, authentication, and provider turns were not exercised; their credentials are not configured on this vm. their settings discovery and documentation links were exercised. native ios/android, electron shell, macos/windows, remote relay, and tunnel paths were not exercised on this linux web verification pass. no new runtime behavior is introduced by this pr.

merge follow-up

merged current main into the existing head at b51229c60bab4394931ce417e5c11315763482b8, preserving kiro alongside pi, muse code, and fx in both conflicted provider lists. the pr remains 3 files, 7 additions and 5 deletions against main.

blacksmith vp run check:changed 71646e031a6dc9db1309b3b9dff597f872cf2fd3 passes after fetching the worker's missing history. format passes; code checks, typecheck and tests are not selected for this documentation-only diff. two independent read-only reviews found no defects in this head. github reports it mergeable. no runtime code changed, and the earlier evidence above remains applicable.