Quickstart

This page walks through a first real session: starting tCode, signing in, and running a handful of representative prompts so you can see the shape of a normal turn before you dive into the rest of the documentation.

Starting and signing in

Open a terminal in the project you want to work on and run tcode.

Your first request

tCode reads checkout.py, makes the edit, writes a test alongside it, asks you to approve both the edit and the new file before saving them, then runs your test suite to confirm the fix actually holds.

A few more prompts to try

Each of these exercises a different part of what tCode can do:

What to notice in the first response

It is worth watching the very first response closely in your first session, specifically the order things happen in: a read before an edit, a search before a broader change, a test run after a fix rather than before it.

Correcting course mid-turn

If a prompt does not go the way you expected, the fastest way to correct course mid-turn is simply to say so once tCode responds, "that test is checking the wrong thing" or "use the existing logger instead of print statements" works exactly like it would talking to a person, and the next turn incorporates that correction.

Where to go from here

Once a prompt or two land the way you expect, Prompt examples goes further into how different kinds of prompts, direct, exploratory, outcome-based, tend to be phrased, and Use cases covers the broader categories of work people actually reach for tCode to do day to day.