Help, with the boundary visible.
Local agent work should be inspectable before, during, and after the run.
Does Coil upload prompts, files, previews, memory, or audits?
Not unless you turn on Bring Your Own Key. By default, prompts, routing, embeddings, memories, workspace previews, graph results, and route-audit data stay on your Mac. Bring Your Own Key is off until you turn it on and confirm it. While it is on, the provider you configure generates replies, memory updates, and wiki drafts, so what they need goes directly from your Mac to that provider, using your own key where it requires one, and never to Silo Systems: your message, your room brief, the last few messages of the conversation (each shortened), relevant memories, and for a wiki draft its topic and your existing page names. Coil never uploads embeddings, workspace previews, graph results, trace receipts, or route-audit exports; it writes receipts and exports only to the destination you choose. There is no Silo account, no analytics, and no telemetry. Coil also downloads model weights from Hugging Face: the chat models you choose, after you consent at first run or when you pull one in the Models pane, and an on-device embedding model the first time Coil starts after setup, whichever engine you use. It runs the optional model-catalog check described in the next answer only if you turn it on.
What is the optional “check for new models” setting?
It is off by default. If you turn it on, Coil periodically downloads a small signed model-catalog file from ohmslaw.net, a site operated by Silo Systems and hosted on Vercel, so it can tell you when a newer local model build exists. It is a one-way download of metadata: no prompt, file, workspace path, transcript, memory, or account identifier is sent, and there is no account to identify you with. The request exposes only what any HTTPS request exposes: your IP address and a user-agent string. Coil logs nothing about it, though the hosting infrastructure may keep standard web access logs. Turning the setting off stops the checks, and if the catalog is missing, expired, or fails signature verification, Coil just keeps using the model list it already knows.
What does it mean when a model is marked unvalidated or experimental?
It means the model has not been tested on Silo Systems hardware. Some models the catalog offers are marked this way so that large builds can reach machines we do not own. Their memory and disk requirements are estimated, not measured, calculated from the model's published size and format rather than from a real run, and Coil shows you the basis for the estimate before anything downloads. An unvalidated model is never picked for you: it is never a default at any memory tier, and installing one takes an explicit extra confirmation on top of the normal model-download consent. It may need more memory than estimated, or run poorly, on your Mac. If a real evaluation is done later, the same model is republished as a tested one with measured requirements.
Can the current App Store build edit my workspace?
Yes, after review and approval. The current App Store build scopes Read, Write, Edit, read-only bounded shell, and graph queries to one folder you choose, under a policy selected for that run. Write and Edit show a bounded preview or diff, where relevant, before execution; full-content hashes force re-review if the file changes.
What will I review before a tool runs?
The current build shows the tool, bounded arguments, workspace-relative path, policy, and a file preview or diff where relevant. Full-content hashes protect a reviewed file from changing underneath the approval. Read-only bounded shell never becomes an unrestricted terminal.
How do I map a folder's code?
Open the Workspace pane and choose a folder. Coil reads the Swift files inside it and maps their types, protocols, and functions into a local graph, with each symbol sized by how connected it is. Hover a symbol to see its file, or click it to see its kind and file. Mapping only reads the folder; the map itself is kept with Coil's data on your Mac.
Does the wiki write pages on its own?
No. Name a topic in the Wiki pane and the worker model drafts a Markdown page as a proposal. Review it, then approve or discard it; nothing is written until you approve, and a new draft waits until the pending one is settled. Approved pages are kept with Coil's data on your Mac.
What does route preview show before a turn is dispatched?
Coil can show a side-effect-free route preview with the proposed recipient and role, resident model, bounded context counts, bounded route reason, and a static list of seven available workspace-tool capabilities, not the tools this turn will run. Preview does not start generation, load a model, change transcript or memory, or run a tool.
Can I accept, cancel, or change the proposed route?
Yes. Set route preview to Always, Ambiguous (only close model choices), or Never. When a preview is shown, accept it, cancel without dispatch, or choose another eligible model already resident on your Mac. Coil revalidates and reserves the exact selection before changing transcript or memory.
What does a route-audit export contain?
Coil can export a deterministic local route-audit JSON file. Depending on what was logged, the file may include turn text alongside the proposed route, user selection, and result. Coil writes an export only to the destination you choose and does not transmit it automatically. Review it before sharing.
Please do not attach private workspace files, prompts, trace receipts, or route-audit exports. Describe the visible state and we can help without receiving your content.