Most problems are one of six things, and the troubleshooting page lists them in the order they happen. What follows is everything else.
Install to first reply.
Six fixes, in order.
What a seat is, and what each plan unlocks.
No. Keys live in vscode.SecretStorage on your machine and go straight to the provider. No request is proxied through us, which is also why we cannot meter your tokens.
Only to the providers you seated, as part of the prompts you trigger. /context prints exactly what would be sent before it is sent.
Two seats have no tiebreaker and one seat is an ordinary chat. Three lets a read-only seat object to the writer while a third holds the whole repo.
It works, but you lose most of the value. Different training distributions are what produce objections worth admitting.
1.91 and newer. Older builds lack the chat participant APIs the panel relies on.
Anywhere the VS Code extension host runs and your provider endpoints are reachable. Remote and Codespaces work; keys are stored per-machine, so you re-enter them there.
They are files in your repo. PLAN.md, EXECUTION.md and memory/ stay exactly where they are, and the extension keeps working at Basic limits.
Support is answered by hand, usually within a working day. Include the Console output and your /context dump if something is broken — it saves a round trip.
Email support@tcredex.com. For privacy questions use privacy@tcredex.com; for anything contractual, legal@tcredex.com.