dorfteich/packages/shared/i18n/en/apiTokens.json
Claude Fable 5 c4c84b33f9
Some checks failed
CI / Lint, typecheck, test (pull_request) Successful in 5m38s
CI / Build container images (pull_request) Successful in 4m11s
CI / Auth e2e pack (pull_request) Successful in 8m55s
CI / Import/export fidelity gate (pull_request) Successful in 1m9s
CI / Import/export fidelity gate (push) Blocked by required conditions
CD / Build and push images (push) Successful in 20s
CD / Deploy to Test (push) Failing after 51s
CD / Smoke tests against Test (push) Has been skipped
CD / Promote to Int (push) Has been skipped
CI / Lint, typecheck, test (push) Successful in 5m37s
CI / Build container images (push) Has been skipped
CI / Auth e2e pack (push) Has been cancelled
#200: hard instance-wide plugins.enabled kill switch
plugins.enabled (instance setting, default on — plugins predate the
switch; the VS-NfD reference configuration turns it off) makes every
plugin surface answer 404 via a shared guard: Site-Admin
install/list/mode, pond activation and plugin list, the sandbox frame
and asset routes. The dropzone watcher quarantines drops instead of
installing. Deliberately NOT guarded: the authenticated
fallback-metadata route — it serves no plugin code and existing
plugin_block nodes need it to render their declared fallback (an image
fallback degrades to the neutral placeholder while off, because its
bytes live on the disabled asset surface). The editor offers no plugin
blocks because the pond plugin list is one of the 404ing surfaces.
Admin settings panel gets the toggle (i18n de+en) with the documented
api-restart note (in-process settings cache).

Answers "code execution inside the zone?" with one verifiable
off-switch instead of per-plugin trust machinery (#232, ADR 0025).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0168Ph5uBmHm8X28CSVpbpnJ
2026-07-31 04:42:42 +02:00

70 lines
3.6 KiB
JSON

{
"section": {
"title": "API tokens",
"intro": "Personal access tokens let scripts and integrations use the public API as you. A token has your permissions, narrowed by its scope and an optional pond restriction.",
"instanceDisabled": "The public API is currently disabled on this instance — tokens can be created but will not work until a Site Admin enables it.",
"empty": "No API tokens yet."
},
"fields": {
"name": "Name",
"scope": "Scope",
"scopeRead": "Read only",
"scopeWrite": "Read and write",
"expiresAt": "Expires (optional)",
"ponds": "Restrict to ponds (optional)",
"pondsHint": "No selection = every pond you can access (that has the API enabled)."
},
"list": {
"created": "Created",
"lastUsed": "Last used",
"never": "never",
"expires": "Expires",
"status": "Status",
"active": "Active",
"revoked": "Revoked",
"expired": "Expired",
"allPonds": "all ponds",
"revoke": "Revoke",
"revokeConfirm": "Revoke this token? Clients using it stop working immediately."
},
"create": {
"button": "Create token",
"pending": "Creating…",
"createdTitle": "Token created",
"createdHint": "Copy it now — it is shown only this once.",
"copy": "Copy",
"copied": "Copied."
},
"pond": {
"title": "Public API",
"label": "Expose this pond through the public API",
"hint": "Off by default. When enabled, users can reach this pond with their API tokens — with exactly the permissions they have here anyway. The instance-wide API switch must also be on.",
"saved": "Saved.",
"mcpLabel": "Expose this pond to AI assistants (MCP)",
"mcpHint": "Off by default and independent of the REST toggle. When enabled, MCP clients such as Claude Code can reach this pond with an API token — again with exactly the user's permissions. The instance-wide MCP switch must also be on."
},
"admin": {
"title": "Public API",
"label": "Enable the public REST API",
"hint": "Master switch (default off). Users then create personal access tokens in their settings; each pond additionally opts in via its pond settings. Documentation: /api/public/v1/openapi.json",
"save": "Save",
"saved": "Saved.",
"mcpLabel": "Enable the built-in MCP endpoint",
"mcpHint": "Master switch (default off), independent of the REST API. MCP clients connect to /api/mcp with an API token; each pond additionally opts in via its pond settings. See docs/self-hosting/public-api.md.",
"feedsLabel": "Enable Atom feeds",
"feedsHint": "Master switch (default on). While off, every feed URL and the feed-token management answer 404 — for hardened environments where feed tokens must not appear in URLs as read credentials.",
"pluginsLabel": "Enable the plugin architecture",
"pluginsHint": "Master switch (default on). While off, every plugin surface answers 404 — install, pond activation, sandbox frames and assets — and existing plugin blocks show their declared fallback. For hardened environments that must answer \"no third-party code execution\" verifiably. Takes full effect after an api restart (settings are cached in-process)."
},
"feed": {
"title": "Feed tokens",
"intro": "Read-only tokens for Atom feeds: append ?token=… to a feed URL so your feed reader can subscribe to non-public ponds and pages. They never grant API access.",
"create": "Create feed token",
"revealHint": "Copy the token now — it is only shown once.",
"urlHint": "Example feed URL: {{url}}",
"pondPlaceholder": "pond",
"empty": "No feed tokens yet.",
"delete": "Delete"
}
}