Verified local apps
The store's second lane — server code from a verified publisher, read by a reviewer every version, signed by Chataway and always run isolated on macOS. What it may ship, what it may not, and what users see.
Most store apps are cloud apps: their code runs on your servers and the Mac only shows a sandboxed panel. Some apps genuinely need the Mac — transcoding a video with ffmpeg, reading a project's files, working offline. For those the store has a second lane: verified local apps.
A verified local app ships its server code in the bundle. Chataway reads that code, signs exactly that build, and every Mac runs it isolated — its own process, its own folders, only the hosts you declared. Users see it as Verified · Runs isolated.
#Who can publish one
- Your publisher must be verified (DNS TXT record, see Publishing). An unverified publisher's upload is refused with
publisher_unverified. - Every version is read by a person (
code-review), even one that changes no permission. Reviewers see every file, the diff against your last approved version, your skills' text and yourexecreason. - macOS only, for now. Isolation relies on the macOS sandbox; Windows and Linux get the lane when Chataway has an app sandbox there. Set
"platforms": ["darwin"]— the validator requires it.
#The manifest
{
"pluginApiVersion": 3,
"id": "com.acme.transcoder",
"name": "Acme Transcoder",
"version": "1.0.0",
"description": "Transcode videos on your Mac.",
"publisher": "acme",
"branding": { "icon": "assets/icon.png" },
"server": "server/index.mjs",
"platforms": ["darwin"],
"grants": ["storage", "network", "exec", "files:receive"],
"permissions": ["Transcode videos you hand it", "Download presets from api.acme.com"],
"network": { "domains": ["api.acme.com"] },
"exec": { "reason": "Runs ffmpeg to transcode the videos you hand it." },
"contributes": {
"tools": [{ "id": "transcode", "name": "Transcode", "description": "Transcode a video." }],
"secrets": [{ "name": "ACME_KEY", "label": "Acme API key" }],
"skills": [{ "id": "transcode", "dirName": "com.acme.transcoder-transcode", "source": "bundled", "sourcePath": ["skills", "transcode"] }]
}
}The store validates it at the store-local level — the lane comes from the bundle itself: server means this lane.
| Rule | |
|---|---|
server | Required: a .js, .mjs or .ts file in the bundle, written against the kernel API. No remote. |
| Bundle | plugin.json, ui/, assets/, server/, src/, lib/, skills/, your server entry, README, CHANGELOG, LICENSE. No node_modules — bundle your dependencies into readable JavaScript (minified is fine, obfuscated is flagged). No native code. |
| Grants | Any grant. network needs network.domains — the only hosts it can reach (no localhost). exec needs exec.reason. |
exec.reason | 10–300 characters, shown to users next to Full access to this Mac. Programs your app starts inherit Chataway's macOS permissions (Screen Recording, Accessibility) when the user granted them — the reason must say honestly what you start. |
| Secrets | Allowed: users enter API keys in the app's settings; your code reads only the names you declared. |
| Skills | Allowed as reviewed text: source: "bundled", under skills/, a dirName that starts with your app id (so it can never replace one of the user's skills), no permissionPatterns. |
| Not allowed | contributes.hooks, contributes.mcp (.mcp.json servers), adapters, a stdio mcpServer, activation: "always". They would run inside the user's agents, outside the sandbox. |
#Updates
An update that widens what the app can do — a new grant, a new host in network.domains, a new or reworded exec.reason, a new required app — is marked permissions-widened for the reviewer and asks every user to consent again before the new version runs. Narrowing never needs consent.
Withdrawn versions work as for every store app: a yank disables it on every Mac within the hour.