Tutorials
How-to
Sessions
Engines and modes
Writing a message
Tools and permissions
Scheduled jobs
Other machines
Remote access
CAD designs
Games
Updates
When something breaks
Sending elsewhere
Reference
Sessions and engines
Composing and shortcuts
Rules and settings
Machines and disk
Explanation
Turret help
Tutorials
Welcome screen Open the Welcome screen, take the guided tour, and find your way back to it later.
Your first session Install Turret, open a folder, send a first message, answer a permission ask and read the reply.
Your first design in CAD mode Open a repository of design packages in CAD mode, install what it needs, and get a design's shapes on screen.
Running a game Open a Game session, install its skill, build and load an effect, and step it once.
Two sessions working together Spawn a second session, send it a follow-up while it works, and read back what it did.
How-to
Sessions
Start a session on a folder Open a new session against a folder or a GitHub repository, picking its mode, engine and worktree.
Set the base folder Choose the folder Turret clones GitHub repositories into, and sign in to GitHub for the private ones.
Resume a session Restore an archived session or adopt a Claude Code CLI transcript from the New Session screen's Resume session view.
Archive a session Remove a session from the sidebar's active list, and choose what happens to a worktree it opened.
Open a session on a git worktree Give a new session its own git worktree instead of the folder's current checkout.
Queue a message while a turn runs Send a message while a session works on its current turn, and choose whether it queues or interrupts.
Read a subagent's conversation Open what a subagent was asked, everything it said and did, and how it ended, on the desktop or the phone.
Engines and modes
Pick an engine, a model and a reasoning effort Choose which engine, model and reasoning effort a new session starts with.
Choose a mode for a session Pick which mode a new session runs in, from the New Session screen's mode cards.
Turn on Coding v2 Make Coding v2 available as a mode choice on the New Session screen.
Choose an output style Set a session's own output style, or change the default every new session opens with.
Install the spreadsheet skill Write the spreadsheet, map, database and runbook skills into a folder and install the runtime that recalculates a workbook, draws a map and migrates a database.
Writing a message
Run a slash command Complete a slash command from the composer's menu, then send it to actually run it.
Mention a file in the composer Point a message at a specific file by picking it, rather than typing its path from memory.
Attach an image Send a picture with a message, from a file dialog, the clipboard or a drag onto the composer.
Attach a picture from Google Photos Connect a Google account with your own OAuth client, then pick pictures from Google Photos in the composer.
Tools and permissions
Switch an MCP server on for a session Turn an MCP server on or off for the session in front of you, without changing what every new session starts with.
Turn a built-in tool off Switch off one of Claude's built-in tools for every session in this app.
Turn on computer use Let sessions look at this computer's screen and click and type in other apps, and grant the permissions it needs.
Find out what a tool does Read what a built-in tool or an MCP tool actually does before deciding anything about it.
Answer a permission request Decide what happens when a session stops mid-turn to ask before it runs something.
Write a permission rule Add an Allow, ask or deny rule for a Claude tool without waiting for a session to ask first.
Stop being asked about a tool Turn off an always-asks entry so a Claude tool call it covers stops interrupting a session for an answer.
Put a tool on the never list Add a Claude tool or pattern to the Deny List so no rule, mode or session can run it.
Set a Codex sandbox Choose what every Codex session is allowed to read, write and reach on the network, before it starts.
Set Gemini's permissions Choose what every Gemini session is allowed to run, and which tools it always refuses.
Scheduled jobs
Write a scheduled job Create an automation job that opens a session and sends it a prompt, on a schedule or by hand.
Run a job by hand Fire a job's run right now, without waiting for its schedule.
Duplicate or delete a job Copy a job, or remove it along with its run history.
Have a job archive its own sessions Set a job so Turret archives each run's session once it has sat idle long enough.
Other machines
Pair two machines Switch two Turret installs on the same network so each can start a session on the other.
Open a session on another machine View a session already running on a paired machine, or start a new one there.
Change another machine's settings Reach a paired machine's own settings from this one, without walking over to it.
Unpair a machine Remove a pairing with another machine, in a single press with no confirmation.
Sync a folder with Google Drive Connect Google Drive, then keep any folder the same on every computer and phone, and share it with other people.
Remote access
Sign in to Tailscale Sign Turret in to your Tailscale account so your other machines and your browser reach it from any network.
CAD designs
Install the design skill Write the CAD design skill into a repository, and install the CAD runtime a session needs.
Pick which design is on screen Switch between open designs in a CAD session, or open one that is not open yet.
Draw a shape on a face Mark a spot on a design's face in the viewer, and give the session something concrete to act on.
Games
Install the game-setup skill Write the game-setup skill into a repository so a Game session is ready to load a binary.
Update the game engine Take a newer game engine that Turret has downloaded, or check for one now, without restarting Turret.
Run a local game engine build Point Turret at a game engine you built in a checkout, and reload it after every change without publishing.
Drive the VFX pane Turn an effect's parameters, step or loop it, and read the filmstrip it leaves behind.
Updates
Check for an update Ask Turret to look for a newer version right now, rather than waiting for its own background check.
Change the release channel Understand why there is no channel switch, and what actually decides a build's channel.
Install an update Finish installing an update Turret has already found and downloaded.
When something breaks
Fix a session that will not resume Read why a row in the New Session screen's Resume session view is blocked, or why picking one failed.
Fix an engine Turret cannot find Read why an engine's card is disabled on the New Session screen, and get it working.
Read main.log when the screen says nothing Find Turret's own log file when something broke and nothing on screen explains it.
Fix another machine that will not appear Work through why a paired or pairable Turret install is not showing up.
Fix a CAD session that sits waiting for its runtime Read what CAD mode's setup steps mean, and what to do when one fails.
Fix a design that will not open Recover when a design will not open, or a part in an open design will not load.
Sending elsewhere
Send a message to Telegram Give sessions a Telegram bot and a list of chats, so a session can send you a message, photo or file.
Talk to sessions from Telegram Set up a bot and a private group, then start sessions, answer their asks and add people from Telegram.
Talk to sessions from Slack Make a Slack app for Turret, set up channels, and start and steer sessions from Slack threads.
Reference
Sessions and engines
Modes What each of Turret's seven modes gives a session — its tools, its panes and its prompt.
Engines and their models What each engine is, which models and reasoning efforts it offers, and what a new session picks by default.
Built-in tools What each of Claude's built-in tools does, grouped the way the Tools screen groups them.
The MCP tool catalogue What the MCP tools page shows and what each of its fields means.
Composing and shortcuts
Keyboard shortcuts Every keyboard shortcut Turret answers to, on both platforms, and what each one does.
Slash commands How to run a slash command from the composer, and where the list of them comes from.
File mentions How to open the composer's file picker, which files it offers, and what a mention becomes once sent.
The widgets a model can put in a transcript What a diagram, an image gallery, a sound gallery and a download are, and how each behaves on screen.
Rules and settings
Settings Every field on every Settings tab, its values and its default.
Permission rule syntax What a stored Claude permission rule holds and what the add-rule form's fields accept.
Automation schedule fields Every field a scheduled job holds, what each schedule kind means, and what a run record shows.
Machines and disk
Another machine's settings What you can see and change on a paired machine's settings from this one, and what stays local to the other machine.
What pairing grants The requests a paired machine can make once paired, and the ones it cannot.
What a session leaves on disk The files a session writes, where they live, and how they differ from the engine's own transcript.
Environment variables Every environment variable Turret reads, and what setting it changes.
Explanation
What a mode is, and why a tool belongs to one Why Turret scopes a session's tools, panes and prompt together as a single mode, fixed for its life.
The agents' creed, and what Coding v2 changes Coding v2 is Coding with a single rule set placed ahead of everything else in the system prompt.
Why a session is a child process A session starts its subprocess only when a message needs answering, and stops it once nothing does.
Sessions that talk to each other, and how that differs from subagents A spawned session is an ordinary session; a subagent runs inside its parent's own subprocess instead.
Why Turret holds no credential Claude and Codex sessions run on the CLI's own login; Gemini is the one exception, held encrypted.
What pairing authorises, stated plainly A single PIN exchange is the whole of what a pairing authorises, checked once and trusted afterward.
What the phone can reach, and why The phone and the desktop reach sessions through separate routes, checked against each other at build time.
Why a CAD design lives in your repository CAD mode reads your repository's own Python and files, and keeps no copy of a design anywhere else.