Code on your Mac
Fix a bug and approve every change
Torki Code reads the repo, proposes a diff, waits for you to approve it, runs the tests and commits.
A Free account is enough, and you sign in inside the app on the Home half: Free gives you 25 messages every 5 hours, and a whole request counts as one message, not one per step, so a fix that takes twenty steps costs one — though a very long request can run long enough that Torki asks you to send another message to carry on. Torki Code needs an Apple Silicon Mac (M1 or later) on macOS 11 or later, and there is no Windows, Linux or Intel build; the response mode used here, "Orbit", is the default and works on Free, while "Stellar" and "Cosmos" carry a "Lite+" chip and need a paid plan.
Torki Code is one half of the Torki AI app for Mac — the other half is Home, where you sign in. You point it at a git repository, describe what is broken, and it opens and reads the files it needs on its own; every file it writes and every command it runs stops and asks you first. What follows is that default setting, "Manual", end to end: one diff you approve, one test run you approve, one commit.
How it works, step by step
Get the app, sign in, then open Code
Torki Code comes with Torki AI for Mac — the button on the Torki Code page reads Download for Mac
, and beside it, Included in Torki AI for Mac. Sign in with your Torki account.
Open the app and the window starts on the Home half, and that is where signing in happens — switching to Code while signed out puts you straight back on Home. Once you are signed in, click Code
in the segment at the top of the sidebar.
Open the repository
The Explorer reads No folder open
, and under it Open a folder to browse it, edit it, and let Torki work in it.
Click Open folder…
and pick the repository; the folder chip in the composer stops reading no folder
and shows the folder's name.
Check what Torki may do without asking
Beside the folder chip sits the permission chip, a shield glyph reading Manual
— the default. Open it: the menu is headed WHAT TORKI MAY DO
, and the line under Manual says what that means — Every file write and every command asks you first.
Describe the fix
Type what is broken into the composer, whose placeholder reads Describe a task, or ask about this code
. Torki opens and reads the files it needs without asking — reading is never gated — and then stops at the first thing it wants to change.
Approve the diff
A dialog opens over the app, headed Write to a file
: the file on a monospace line, then the change itself — a summary such as 6 lines added · 2 lines removed
, the changed lines with a little context, and gap rows reading 12 unchanged lines
where it skipped ahead. Under the diff are two scope rows, Runs inside
with the folder, and Cannot reach anything outside it — including through symlinks
. Leave the checkbox Always allow writes for this session
unticked so it keeps asking, then press Approve ⏎
— and the file picks up an M
badge in the Explorer.
Approve the test run
Ask Torki to run the tests, and a second dialog comes up headed Run a command
, with the command it found printed verbatim — a test script is an arbitrary command, so it is asked for like any other. Its second scope row is not the write dialog's, and says what is actually true of a shell: Writes are confined to this folder. The command can still READ files elsewhere.
Its checkbox reads Always allow this exact command for this session
; approve, and the output comes back into the conversation.
Stage the change and commit
Click the branch icon in the left rail — it is icon-only, with the tooltip Source Control
— and the panel opens under the header Source Control
with your file listed under Changes
. Click Stage all
: the file moves to Staged
and the Commit
button, disabled until something is staged, comes alive. Type into the message box, whose placeholder reads Message (⌘⏎ to commit)
, and click Commit
or press ⌘⏎; a toast reads Committed
.
Before you start
The things people hit on their first try, so you do not have to find them the hard way.
The two dialogs do not promise the same thing
On the
Write to a file
dialog the second scope row readsCannot reach anything outside it — including through symlinks
. On theRun a command
dialog that row readsWrites are confined to this folder. The command can still READ files elsewhere.
A command is a real shell, so read each sentence as belonging to its own dialog — the first one does not cover the second."Always allow writes for this session" is wider than the file in front of you
Ticking it does not cover only this file: it allows every write for the rest of the session. It is genuinely session-scoped and is cleared when you open a different folder. The command checkbox is narrower —
Always allow this exact command for this session
means that one command.What leaves your Mac
The app says it on the first run and again in Settings under Privacy: "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." Your files stay where they are and the commands you approve run on your machine — but what it read, and what those commands printed, are sent.
Sometimes the request is not from your own turn
Torki can hand part of a job to a specialist. When one of them is the one asking to write a file, the dialog's heading says so —
Write to a file — asked for by
and the name. Most of the time you will see the plain heading.The last step needs a git repository
If the folder is not tracked by git, the Source Control panel reads
Not a git repository
, with the lineTrack this folder with git to review and commit changes here.
and a buttonInitialise a repository
. Until you use it there is no message box and noStage all
to click.
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.