State the expected behaviour
Include what happens now, what should happen instead and a way to reproduce it. Name the files or user flow you already know about.
Getting started
Start with a small change in a project you know. Give the agent enough context, follow its work and verify the result with your project’s own checks.
Find the current installer availability, system details and release information. Use the same account on the website and in the application.
Explore project files, task plans, edits, diffs, terminal commands and saved conversations. Start with a focused question or change.
Understand the local and cloud boundary. Review permissions and network tools before sharing sensitive project context.
Open project records, run history, API keys, device access and workspace settings. These pages require sign-in.
Pro is $20/month. Supported local-model requests have no request-count cap. External-provider expense limits are separate; Team billing is planned.
Use workspaces, invitations and roles for shared projects. Company checkout, paid seats and proration are not yet available.
Review account data, cookies, model-provider context, data requests and your choices before connecting sensitive projects.
Send the page or app version, visible error and time of the problem. Never include passwords, API secrets or private project files.
Include what happens now, what should happen instead and a way to reproduce it. Name the files or user flow you already know about.
Say what may change and what must remain compatible. Ask for a short plan before a larger edit, and split unrelated work into separate tasks.
Use an existing test, build command or manual scenario that can show whether the task worked. Read the output and inspect the diff yourself.