Code on your Mac

Get to know a codebase you did not write

Point Torki Code at a folder on your Mac and ask where something lives — reading, listing and searching never stop to ask you.

Create a free accountAll walkthroughsDownload for Mac

Free covers this. The button on this page creates a Free account, and the Mac app signs in with that same account. You also need an Apple Silicon Mac — the download line reads "Apple Silicon (M1 or later) · macOS 11 or later · Signed and notarized by Apple", and there is no Windows or Linux build, both of which the downloads page lists as "Coming Soon". Torki Code spends your ordinary message allowance, which on Free is 25 messages in a rolling five-hour window shared with everything else in Torki: "Works with your Torki plan. A whole request counts as one message, not one per step." — though a very long request can run long enough that Torki asks you to send another message to carry on.

You have cloned a repo someone else wrote, and you want to know where one thing lives before you change anything. Torki Code is the Code half of the Torki AI Mac app: you point it at a folder, ask in plain words, and it opens files, lists directories and searches the project to build its answer. The four things this walkthrough does — open, read, list, search — do not change a file in your repo.

How it works, step by step

1

Get the app and sign in

Torki Code comes with Torki AI for Mac. The button on its page reads Download for Mac, and beside it, Included in Torki AI for Mac. Sign in with your Torki account. Open the app and it starts on Home, which is the sign-in screen when there is no session: Welcome to Torki AI, then Sign in with Torki, which opens Sign in to Torki offering Continue with Google, Continue with Microsoft, Continue with Apple and Sign in with Email. Sign in before anything else — pressing Code while signed out puts you straight back on Home.

2

Switch to Code

Press Code in the segmented control at the top of the sidebar. On a first signed-in run a short tour starts by itself: it opens on This is Torki, then Point Torki at a folder, and goes on through You decide what happens without asking, What “Guarded” means and What leaves this machine. Skip it whenever you like; Settings keeps Take the tour again / Start tour.

3

Open the repo

The Explorer reads No folder open over Open a folder to browse it, edit it, and let Torki work in it. Click Open folder… and choose the project — that folder becomes the only place Torki's file tools can reach. If the repo ships instructions of its own, a card comes first, This project wants to add its own instructions, and they stay off until you accept them.

4

Ask where something lives

The composer says Describe a task, or ask about this code. Type a plain question — where is login handled — and send it. The pill in the title bar, beside the model chip, reads Thinking.

5

Watch what it reads

Cards stack up as it goes: Read with the file's path, List with the directory, Search with the phrase it looked for, in quotes — the Search card carries the phrase, not a filename. The pill in the title bar now reads Working. Each card opens to show what came back, and when Torki is showing its reasoning, a panel labelled Thinking fills inside the answer, above the text.

6

Read the answer

The reasoning panel, where there is one, folds to Thought for as the answer starts, and the answer points at the files. Nothing in the repo changed: reading, listing and searching never ask for permission in Manual, Accept edits or Full auto, and none of them writes. The exchange costs one message however many steps it took.

Before you start

The things people hit on their first try, so you do not have to find them the hard way.

  • Reading never asks. A command can.

    Reading, listing and searching go through in every permission mode — Manual, Accept edits and Full auto. But Torki chooses its own tools, so if it decides it needs to run something such as git log, Manual, where you start, stops and raises a card whose eyebrow reads Run a command. Nothing runs until you answer it. The Guarded chip is about the file tools; a command you approve is a different thing, and the card tells you where it will run.

  • "No matches" means "not in what was scanned"

    Search skips files your .gitignore excludes, very large files, binaries, and credential-shaped files such as .env, and it says what it skipped in the result. Read that line before you conclude something is not in the repo.

  • What leaves this machine

    The tour card under that heading says it plainly, and Settings carries the same disclosure: "Torki runs on Torki’s servers. To answer you it sends what you typed and what it read: the files it opened, the output of the commands it ran, the pages and screenshots it looked at, anything you searched for. Files are opened inside the folder you chose; commands you approve run on your machine, and what they print is sent too. …"

  • Free starts you on Orbit

    Torki Code opens on Orbit, which Free includes and which is enough for reading a project you did not write. In the RESPONSE MODE menu, Stellar and Cosmos carry a Lite+ chip — they are Lite and above, and picking one on Free is refused with Stellar is available on Lite and above.

Next

Other walkthroughs worth watching.

Try it yourself.

Free to start, no credit card. Sign in once and the same account works on the web, on your Mac and on your phone.

Create a free accountSee plans