## Description
Surface the **`#oss-contributors`** Slack channel
([link](https://warpcommunity.slack.com/archives/C0B0LM8N4DB)) as the
dedicated place for contributors to chat with each other and the Warp
team in the docs new contributors actually read.
- **`README.md`** — adds a `[!TIP]` callout under "Open Source &
Contributing", and updates the "Support and Questions" bullet to point
at `#oss-contributors`.
- **`CONTRIBUTING.md`** — adds a `[!TIP]` callout near the top so
contributors see it as soon as they land, and updates the "Getting Help"
bullet at the bottom.
- **`FAQ.md`** — updates the "Where do I get help?" bullet.
The existing
[`go.warp.dev/join-preview`](https://go.warp.dev/join-preview) link is
preserved as the workspace on-ramp for people who aren't yet in the Warp
Slack.
## Testing
Docs-only change — rendered the markdown locally to confirm the
GitHub-flavored `[!TIP]` callouts and Slack/`go.warp.dev` links render
correctly.
## Server API dependencies
N/A — docs only.
## Agent Mode
- [x] Warp Agent Mode - This PR was created via Warp's AI Agent Mode
## Changelog Entries for Stable
<!-- Docs-only change; no changelog entry. -->
---
[Conversation](https://staging.warp.dev/conversation/1011b077-6ef3-4516-857f-85043490d114)
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-authored-by: Oz <oz-agent@warp.dev>
## Description
Adds a FAQ entry for a common question about whether users can access
other models or subscriptions in Warp's agent.
The answer clarifies that Warp's built-in agent harness runs server-side
and is not open in this repo, so a personal subscription cannot be used
for Codex model access there. It also points users toward planned ACP
support for connecting Codex directly while using their own
subscription.
## Testing
Documentation-only change; not run.
## Server API dependencies
None.
## Agent Mode
- [x] Warp Agent Mode - This PR was created via Warp's AI Agent Mode
## Changelog Entries for Stable
Co-Authored-By: Oz <oz-agent@warp.dev>
## Description
Adds a top-level `FAQ.md` covering the questions most likely to come up
for someone landing on this repo for the first time, especially someone
planning to contribute or run an agent against it.
Sections:
- **Contributing** — how to contribute, filing good issues, readiness
labels, why feature work goes through a spec PR, building from source,
the Oz + SME review flow, what to do when a PR is stuck, becoming a
collaborator.
- **Using an agent on this repo** — bringing your own agent, how to get
Oz to implement an issue for you, cost, the quality bar for
agent-generated PRs, training data.
- **What's open source and what isn't** — straightforward answers about
which parts of Warp live in this repo (the client) and which don't (the
server, Drive backend, Oz), and what running locally without the cloud
looks like.
- **Licensing** — why we chose AGPL for the app and MIT for the UI
framework crates, enterprise use, the CLA, forking.
- **Help and security** — where to ask questions, how to report security
issues.
Most of the substance is already implied by `README.md`,
`CONTRIBUTING.md`, `SECURITY.md`, and the licenses; the FAQ pulls those
answers into one skimmable place and answers a few questions that aren't
covered elsewhere (e.g. "is Warp fully open source", "can I get Oz to
implement my issue", "why AGPL").
## Testing
Documentation-only change. Verified the rendered Markdown locally and
that all in-repo links resolve.
## Changelog Entries for Stable
<!-- Docs-only addition; no changelog entry. -->
---------
Co-authored-by: Oz <oz-agent@warp.dev>
