A desktop coding agent with free access to frontier models.
TypeScript
docs(archive): project upload is on by default, opt-out is by email, 100 GiB caps
ogsamratbea9029aefa5
diff --git a/docs/project-archive.md b/docs/project-archive.mdindex c797c0e3..b363684f 100644--- a/docs/project-archive.md+++ b/docs/project-archive.md@@ -1,25 +1,26 @@# Project archive-When a chat runs in a folder that is a git project, OmniRush.ai can keep an+When a chat runs in a folder that is a git project, OmniRush.ai keeps anencrypted copy of the whole project folder on omnirush.ai. With that copy,the project can be restored as it was after any turn of the chat. This page-describes what the desktop app uploads, when it uploads it, and how to turn-it off.+describes what the desktop app uploads, when it uploads it, the size limits,+and how to opt out.The project archive is separate from the workspace collector described in[workspace-collector-privacy.md](workspace-collector-privacy.md). Thecollector keeps running for every chat and sends scrubbed snapshots, each-capped in size (a chat has no total storage limit). The archive is a raw copy of the folder: file contents are not-scrubbed and there is no size cap.+capped in size (a chat has no total storage limit). The archive is a raw+copy of the folder: file contents are not scrubbed. omnirush.ai accepts up+to 100 GiB per upload and 100 GiB per chat (see [Size limits](#size-limits)).## When it runsAll of these must be true:- You are signed in to omnirush.ai in the app.-- You have turned on the **project archive** opt-in in your omnirush.ai- consent settings. It is a separate choice, off by default. Agreeing to the- general data collection does not turn it on.+- Project upload is on for your account. It is on by default for every+ account, and there is no switch for it in the omnirush.ai console. To opt+ out, email [email protected] (see [Turning it off](#turning-it-off)).- The folder the chat started in contains `.git` (a git repository, aworktree or a submodule). Nothing is archived for other folders.- The folder is not your home folder, the root of a disk, or one of the@@ -47,6 +48,14 @@ archived.Each upload records the chat and its turn number, so the folder can berebuilt as it was after any turn.+## Size limits++omnirush.ai accepts up to 100 GiB in a single upload, and up to 100 GiB of+uploads in total for one chat. The app does not check the size itself. If+an upload is over either limit, omnirush.ai refuses it and the app stops+archiving that chat. The chat itself carries on as usual, and other chats+are still archived.+## What is left out- **Credential files.** The archive applies the same filename rules as the@@ -98,13 +107,16 @@ as chat errors.## Turning it off-- **Withdraw the project archive opt-in on omnirush.ai.** omnirush.ai then+- **Opt out by email.** Write to [email protected] and ask for project+ upload to be turned off for your account. There is no switch for it in+ the omnirush.ai console. Once your opt-out is recorded, omnirush.aideletes the archives it holds for you. The app stops archiving the nexttime it contacts omnirush.ai (at the next upload, or when a new chatstarts), and archives waiting on your computer are deleted, not- uploaded. While the opt-in is off, the app asks again when a new chat- starts, at most once every 10 minutes. If you turn the opt-in back on,- chats started after that are archived without restarting the app.+ uploaded. While project upload is off, the app checks again when a new+ chat starts, at most once every 10 minutes. If you later ask for it to+ be turned back on, chats started after that are archived without+ restarting the app.- **Sign out.** Uploads in progress are cancelled, and every archivewaiting on this computer is deleted, along with the app's records ofwhat it already archived. Nothing is uploaded later, even if you sign indiff --git a/docs/workspace-collector-privacy.md b/docs/workspace-collector-privacy.mdindex 81dbf31f..0374722a 100644--- a/docs/workspace-collector-privacy.md+++ b/docs/workspace-collector-privacy.md@@ -1,6 +1,6 @@# Workspace collector privacy rails-The project archive, a separate opt-in that uploads an encrypted, unscrubbed copy of git project folders, is described in [project-archive.md](project-archive.md).+The project archive, which uploads an encrypted, unscrubbed copy of git project folders (on by default, up to 100 GiB per upload and per chat; opt out by emailing [email protected]), is described in [project-archive.md](project-archive.md).The desktop server's workspace collector (`apps/server/src/workspace-collector.ts`) snapshots consented workspace files, git metadata and session traces for omnirush.ai; the backend applies the same denylist and scrubber server-side, so a rule changed on one side must land on the other, and the desktop side may only ever be the stricter of the two. Before anything leaves the machine, credential-named paths are dropped and counted in the envelope's `privacy.denied_file_count`: any path component whose words (split on space, `_`, `-`, `.`) include key(s), secret(s), token(s), password(s), passwd, credential(s), id_rsa, id_ed25519, netrc, npmrc, pypirc, kubeconfig, wallet, seed or mnemonic, plus `.aws`, `.ssh`, `.gnupg` and `.docker/config.json`, on top of the older `.env*`, `credentials*`, `secrets*`, `keys/`, `*.pem`/`*.key` rules. A file with a source-code or docs extension (`.ts`, `.py`, `.md`, `.json`, `.yml`, ...) is kept instead and scrubbed: a secret-named assignment (`password:`, `api_key =`, `"token":`, `export CLIENT_SECRET=`, in INI/YAML/JSON/dotenv/shell/source spelling; the key is split into segments on `_`, `-`, `.`, `:`, camelCase and letter/digit boundaries, and qualifies only when a whole segment or adjacent pair is a listed family word, so `author`, `keywords` and `tokenizer_class` never do) loses its value under value rule v2: in SOURCE mode (files with a programming-language extension: js, cjs, mjs, ts, tsx, jsx, py, go, rs, java, kt, c, cc, cpp, h, hpp, rb, php, swift, cs, scala, sh, bash, zsh, ps1, lua, dart, vue, svelte, map, patch, diff) a value is redacted only when it is 8+ non-space characters, not a code expression, `<placeholder>` or filesystem path, not an unquoted identifier or member expression (`config.token`, `tokenFile`), and carries a digit or is 20+ mixed-case characters, while CONFIG mode (every other extension, none, the envelope's git diff and the trace) keeps the permissive rule of 8+ characters with a letter, skipping only filesystem paths and unquoted dotted identifiers, and a key whose last segment is a structural word (`length`, `ttl`, `url`, `path`, `name`, `id`, `header`, `file`, `filename`, `dir`, `mode`, `method`, `role`, `owner`, `type`, `kind`, `enabled`, `estimate`, `hash`, `digest`, `at`, `config`, `client`, `prefix`, `suffix`, `format`, `scheme`, `provider`, `status`, `state`, `label`, `description`, `title`, `class`, `field`, `fields`, `list`, `names`, `version`, `timeout`, `limit`, `max`, `min`, `interval`, `retries`, `port`) never names a secret. A `Bearer` value is redacted only when its token carries a digit or is 20+ mixed-case characters that are not a bare identifier, the AWS 40-character proximity pass runs only on documents of three or more lines (a single-line JSON document relies on its key, or on a sibling naming AWS), and provider token shapes (AWS access key ids and, near them, secret access keys; GitHub, Slack, Google, Stripe, OpenAI, Anthropic, JWTs, Discord, `Bearer` values, private key blocks, URL userinfo) become `[REDACTED]`, and personal identifiers become `[REDACTED_PII]`. `.json` files and the trace document are scrubbed as JSON (every string, keys included) so a redaction can never break an escape sequence; git diffs stay text. As on the backend, a `.json` file first gets the AWS proximity pass over its raw text, an object or array whose keys or string values name aws/secret makes all its values AWS context (the container rail, which also covers the trace), every pair of a repeated key is kept and scrubbed (JSON.parse alone would drop the earlier value unscrubbed), and a document nested deeper than 512 levels gets the text scrub instead. The same denylist filters the manifest, touched paths, git status and diff sections.