Choose an agent
Use Claude from Android with FireCursor
FireCursor supports Claude through an eligible-plan Channel or a separately billed API fallback, depending on the configured desktop path. The app makes that readiness explicit before you commit a task.
Quick answer
The shortest useful version.
Configure one supported Claude path on the computer, confirm its authentication state in FireCursor, choose Claude for the task, and keep approvals and review inside the paired project session.
Step by step
Do this with confidence.
- 01
Choose the Claude path
Use the eligible-plan Channel when available or configure the separately billed API fallback. These are different access paths.
- 02
Verify provider health
Check authentication and setup state before launching. Resolve provider-side errors on the computer when the runtime requires it.
- 03
Load project guidance
Keep CLAUDE.md and other project rules accurate so the agent receives durable repository-specific instructions.
- 04
Control the run
Use Android to steer, answer, approve supported decisions, and review the resulting changes.
Plan and API access are not interchangeable
A consumer subscription, an eligible provider channel, and separately billed API usage can have different entitlements. FireCursor’s job is to show the configured path and its readiness, not flatten those distinctions into one green button.
If the provider reports an authentication or billing issue, correct it at the provider layer and then refresh readiness.
Where Claude can fit well
- Repository explanation with explicit evidence
- A bounded refactor guided by CLAUDE.md
- Reviewing a plan before implementation
- Writing or tightening tests around an existing contract
- Cross-provider handoff when a second approach is valuable