zeron.exe and the engine have no console, so every gh and git run by the GitHub and Git plugins opened a window of its own. Plugin installs from git and the Codex voice helper did the same. They now start with CREATE_NO_WINDOW.
A plugin allowed any public host could update to name `rebind.example.com`,
pointed at 127.0.0.1. Nothing asked (it read as public) and the window didn't
flag it, yet a named host reaches a private address it resolves to. `127.1` and
`0x7f.1` went the same way through the app's transport.
- `net::risky`: a name ending in a number reads as local, so it's flagged and
asks.
- `capability::diff` (crates/engine): over an any-public grant, a newly named
exact host asks. `*.` names still don't: they never reach a private address.
This reverses "narrowing to named hosts doesn't ask" for exact names.
- The permission window, under exact names that don't read as local: "A named
host can be on this computer or your network." en and zh-Hans.
Names like `.ts.net` and split DNS keep working once named and allowed, with no
manifest change. A plugin allowed as it is isn't asked again. Nothing here
works out where a name points: DNS can change after consent, so the person's
yes is what allows it, and the new line is what makes that yes honest.
Engine change: ships in a stable release before a beta.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
A plugin that names `python3`, `node` or a shell in `commands` has full
control of the computer, and the window only listed the name. It now says so,
by name, each on its own line: "It can run python3, which gives it full
control of your computer." (zh-Hans too.)
Rated in plugin-guard, beside `risk`, which doesn't change, so the engine
behaves as it did: `full_control` (shells and interpreters, `python3.12`
too) and `held_to_its_own_rules` (git and gh, which the runner holds to the
rules R2 gave them). git and gh read as what they do: "Run git on this Mac as
you. It can do whatever git can do with your sign-ins." A program nobody knows
reads exactly as before ("some-tool: can do anything you can"). With a mix,
"These can do anything" would be untrue of git beside them, so the line under
the title says "They run as you, with your sign-ins." and each row says its
own. What grew since you allowed it reads the same way.
The risk of a program, whether it's asked about, and what it may do are all
unchanged: only the words.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
A plugin's `ui.fetch` and remote pictures could reach anywhere: this device,
the private network, a cloud's metadata address. `plugins/network.rs` is the
app's `ScriptHost::fetch_policy`, and its rule is plugin-guard's `net`, the
one the engine holds a plugin's service to: public addresses, or the hosts
its manifest names (by host and port); metadata and addresses no host has,
never. Redirects, every resolved address (`to_canonical` first) and headers
all go through it, before anything connects. Its rules come from the engine's
list, whose consent covers `network.hosts`; nothing a plugin runs reaches
them. The app's own requests (`caller` None) are unchanged.
A refusal says what to add: `"network": { "hosts": ["localhost:3000"] }`.
Shared code: `net::Policy::header_to`, for a transport that asks of a host
and not a port (`FetchPolicy::header`). `Policy::header` reads as before, so
the engine's behaviour doesn't change.
network_tests.rs goes through zgx's own transport: 127.0.0.1, localhost,
`::ffff:127.0.0.1`, `0x7f.1`, 169.254.169.254, 0.0.0.0; a redirect to this
device; a name resolving here; a named `localhost:<port>` allowed and another
port refused; a plugin's Host header. `ui.socket` has no connector in this
app today, so it has no test here: zgx's own tests hold that hook.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
* Plugins and templates: consent bound to capabilities, engine-held decisions, hardened runtime
- Consent binds a capability digest (programs, MCP servers, tools, network hosts, services, module replacement); it re-asks only when that grows. UI targets never ask.
- "You" is this device's key; code-running powers are never auto-granted; keys are revoked on sign-out and rotation, listed and revocable in Settings, and new keys are announced.
- Decisions and signing need a one-time review the consent window holds; agents get a scoped IPC token; agent-created chats can't exceed their creator's access; peers can't allow; relayed calls carry the edge-verified device.
- Runtime: text-only Luau, one command policy (env allow-list, hardened git/gh), plugin network blocks private ranges unless declared, safe path joins, verified snapshots, hardened built-in Git service.
- App: ui.change can't override modules, Settings sealed, decision controls protected, plugins get ids and resolve data through grants, consent sheet hardened, dev switches debug-only.
- Templates: unapproved templates run as previews with Keep/Revert, a host-owned way back on every platform, safe mode, no builtin-theme spoofing, increasing versions.
- Edge: step-up for key registration and account deletion, key list/revoke, reserved names, invitation/image/admin limits, relay device stamp.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
* Signing keys register on the first sign-in, revocations act at once, setup and layout fixes
- A sign-in registers this device's key with its fresh ticket, also on a local-mode engine; new keys are noticed at start; a revoked own key rotates at once (peers are told), drops code-running grants and shows a notice.
- Calls during unfinished account setup answer setup_incomplete; plugins and templates load once an organization is chosen.
- The host strip's wrapper fills the window.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
* Engine: only plugin and template calls answer setup_incomplete during onboarding; everything else waits as before
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: zeronsh[bot] <346184242+zeronsh[bot]@users.noreply.github.com>