Features

Files

Where: iPhone → Settings → Files. Mac → Settings → Files.

The screen shows a Storage meter — how much of your plan's space the files take, how many there are and what is left, turning orange at 90% and red when full — and carries one switch.

  • Delete files when done (on by default) — a task's files are deleted 48 hours after it is marked done. The task, its notes and its links stay; only the stored bytes go. Tidying runs in the background about once a day, so a file can outlive the window by a little, and moving a task out of Done before then keeps its files.
  • Links are never touched. They cost nothing and always stay.

Limits. 100 MB for the whole account on Free, 5 GB with Pro; an upload that would go over is refused and offers the upgrade. 25 MB per file after compression. The apps compress before uploading: images are scaled to 2048 px on the longest edge and re-encoded, video is re-exported at 720p, anything else goes up as it is — and is refused rather than silently mangled if it is over. An agent sending bytes inline is capped at 8 MB; bigger files go through a source_url for Cotask to download.

Reads are public by design. Every file gets a long, unguessable URL that needs no credentials, so an agent handed a task — or a webhook receiving one — can fetch the file with nothing to configure. Nothing is listable: reaching a file means already knowing the whole path. Removing an attachment through the API deletes the stored file too.

Locked files#

File locking arrived in 1.0.1. The 1.0.0 apps cannot turn it on or manage it, and they can't open locked files — update to 1.0.1. The agent API serves them as described below.

When an account has file locking enabled, every file moves to private storage. Its old public URL stops working, and its url becomes https://usecotask.com/api/agent/files/<attachment id>, which opens only for:

  • any of your active agent keys — Authorization: Bearer pl_… (an OAuth connection's token works too). Revoke a key and it stops opening files.
  • the file password — an X-File-Password header, or HTTP Basic auth with any user name (so a browser simply asks for it). Never on the URL: a ?password= is refused, since one password opens every file and URLs end up in history and logs.

In a browser, pictures, audio, video and plain text open in place; anything else — HTML, SVG, XML, PDF — downloads instead, and every file is served in a sandbox where nothing in it can run.

An agent that reads a task through the API or MCP also gets a download_url on each locked file (locked: true): a signed link that needs nothing and works for an hour — a delegated run gets one that lasts a day. Ten wrong passwords from one address pause password attempts from it for fifteen minutes; anyone else with the password carries on, and keys keep working. A new password needs at least eight characters. Only you, signed in to the app, can lock, change the password or unlock — never an agent. Unlocking moves every file back to a public URL and forgets the password. Clients with file-lock support keep showing your files as before.

Locking and unlocking take a moment, and GET /files/lock says where they stand: state is locking, locked, unlocking or unlocked, and locked is true only once every file is behind the password. A lock that was interrupted is finished the next time the app asks; files added meanwhile go straight to private storage. An upload link from POST /uploads signed before you locked stops taking files once the lock has started — ask for a new one.