Choose your first coding agent
Choose a project-editing workflow, then make one small change you can verify.
Choose by your starting point
Your first result is one reviewed change in the correct project, not three agent installations. Have a folder you can edit and know how to preserve its current state. A project folder contains files; a terminal runs commands; a preview shows the app those files produce.
Checked 2026-11-13: Claude Code provides a project-oriented coding workflow with its supported account routes. Codex CLI operates on a local project through its supported sign-in. OpenCode separates its client from the connected provider and selected model. Access, quotas, and billing depend on the route you choose; an installed executable does not prove account access.
1. Pick one starting path
- Already using Claude Code with working access? Follow Start with Claude Code.
- Already have a working Codex environment? Follow Start with Codex.
- Need OpenCode's provider selection and have a supported provider account? Follow Start with OpenCode.
If none is installed, choose the starter compatible with your operating system and account. Keep installation and authentication steps in that starter. The featured setup skills guide project orientation; they do not include provider subscriptions.
2. Orient before editing
Ask the agent to identify the repository root, instructions, current changes, app entry point, and run/check commands. Confirm it names the project you intended. If there is no app yet, go to Plan your app before requesting a large build.
Replace both bracketed fields:
Inspect [PROJECT FOLDER] and explain its structure and run/check commands.
Read repository instructions and preserve existing changes.
Change only the homepage heading to [EXACT TEXT]. Identify the file first.
Run the relevant checks, show the diff, and explain how to verify the visible result.Vibes for this guide
Use the materials that help with your next step.