Google Analytics, Vercel Web Analytics, Leadsy and the TikTok Pixel stay off until you accept. The help chat starts once you have chosen. The scheduling button starts once you have chosen. Read our Privacy Policy.
An assistant's files stay between tasks. Send files, photos, screenshots, and voice notes, get files back as downloads, and see where repositories live.
Each assistant's workspace has a real folder of files. What the assistant creates there stays put: between one task and the next, and after the workspace goes to sleep and wakes again. You do not need to ask it to save anything.
Press the paperclip in the message box and pick what to add:
Upload files: documents, spreadsheets, slides, pictures, recordings, or a zip. You can also drag files onto the box or paste them.
Take a photo: a picture from your camera, for a receipt, a whiteboard, or a page.
Take a screenshot: a screen or a window. In the desktop app you pick it from a list with previews.
Record a voice note: talk for up to 30 minutes. The recording is kept and written down for your assistants.
The phone app has the same paperclip, with your photos and videos (screenshots are there too), the camera, and voice notes.
Each file goes to the assistant's workspace and is read there: the text of a document, the text in a photo or screenshot (the assistant looks at the picture too), a transcript of a recording. A zip is unpacked next to itself and every file inside is read, so you can send a whole folder at once. The assistant can then work on the unpacked files directly.
Ask for a file and the assistant makes it in its workspace and shares it with you. Its answer ends with the file, ready to download. Several files, or a whole folder, come as one zip.
On the web the file downloads like any other.
In the desktop app you choose where to save it.
On your phone the share sheet opens, so you can keep it in your files or send it on.
Every file in a chat downloads the same way, including the ones you attached. Sharing a file only hands it to you, so it never waits for your Approve.
When you connect a source-control tool such as GitHub, the Coder clones your repository into its own workspace, before its first task. It never clones onto your computer and never works in a folder on your machine.
That has a few practical effects:
Your own copy of the repository is never touched while the Coder works.
Each Coder has its own copy, so several Coders never trip over each other's files.
Your login for the repository is passed to a single command at a time. It is never written into the repository settings or shown in the Files view.
If the clone fails, the job stops as Blocked before any coding, with a plain sentence saying what to fix, such as the token not being able to read that repository.
What happens to the work afterwards depends on your house rules. The Coder can open a pull request for review, and merge when your house rules allow it. Pushing waits for your Approve. See approvals and house rules.