A few more prompts to try

Beyond the first fix, a handful of other prompts are worth trying specifically because each one exercises a different part of tCode. Orientation, "how does authentication work in this repo", shows how it traces real code paths with grep rather than guessing from names.

A pasted stack trace shows how it reads the surrounding code before proposing a fix, rather than pattern-matching on the error text alone. /plan before a larger, multi-file request shows how it can explore and reason about a whole change before anything is actually written, reviewed afterward with /exit-plan.

And /gmail or /linear followed by a few words shows the connector system pulling outside context, an email, a ticket, directly into the next message. See Prompt examples for a much longer set of worked examples once these first few land.

None of these need to be tried in any particular order, and none of them require setup beyond what a normal first session already has, aside from the connector example, which needs at least one provider linked first in tAI Settings, covered in Connectors.

Trying even two or three of these in a first session, rather than only the initial fix, gives a much more complete picture of what tCode is actually for than a single small fix does on its own, since each one exercises a genuinely different capability rather than a variation on the same one.