
Security News
TC39 Advances Temporal to Stage 4 Alongside Several ECMAScript Proposals
TC39’s March 2026 meeting advanced eight ECMAScript proposals, including Temporal reaching Stage 4 and securing its place in the ECMAScript 2026 specification.
openwork-server
Advanced tools
Filesystem-backed API for OpenWork remote clients. This package provides the OpenWork server layer described in packages/app/pr/openwork-server.md and is intentionally independent from the desktop app.
npm install -g openwork-server
openwork-server --workspace /path/to/workspace --approval auto
openwork-server ships as a compiled binary, so Bun is not required at runtime.
Or from source:
pnpm --filter openwork-server dev -- \
--workspace /path/to/workspace \
--approval auto
The server logs the client token and host token on boot when they are auto-generated.
Add --verbose to print resolved config details on startup. Use --version to print the server version and exit.
Defaults to ~/.config/openwork/server.json (override with OPENWORK_SERVER_CONFIG or --config).
{
"host": "127.0.0.1",
"port": 8787,
"approval": { "mode": "manual", "timeoutMs": 30000 },
"workspaces": [
{
"path": "/Users/susan/Finance",
"name": "Finance",
"workspaceType": "local",
"baseUrl": "http://127.0.0.1:4096",
"directory": "/Users/susan/Finance"
}
],
"corsOrigins": ["http://localhost:5173"]
}
OPENWORK_SERVER_CONFIG path to config JSONOPENWORK_HOST / OPENWORK_PORTOPENWORK_TOKEN client bearer tokenOPENWORK_HOST_TOKEN host approval tokenOPENWORK_APPROVAL_MODE (manual | auto)OPENWORK_APPROVAL_TIMEOUT_MSOPENWORK_WORKSPACES (JSON array or comma-separated list of paths)OPENWORK_CORS_ORIGINS (comma-separated list or *)OPENWORK_OPENCODE_BASE_URLOPENWORK_OPENCODE_DIRECTORYOPENWORK_OPENCODE_USERNAMEOPENWORK_OPENCODE_PASSWORDToken management (scoped tokens):
OPENWORK_TOKEN_STORE path to token store JSON (default: alongside server.json)File injection / artifacts:
OPENWORK_INBOX_ENABLED (1 | 0)OPENWORK_INBOX_MAX_BYTES (default: 50MB, capped)OPENWORK_OUTBOX_ENABLED (1 | 0)Sandbox advertisement (for capability discovery):
OPENWORK_SANDBOX_ENABLED (1 | 0)OPENWORK_SANDBOX_BACKEND (docker | container | none)GET /healthGET /statusGET /capabilitiesGET /whoamiGET /workspacesGET /workspace/:id/configPATCH /workspace/:id/configGET /workspace/:id/eventsPOST /workspace/:id/engine/reloadGET /workspace/:id/pluginsPOST /workspace/:id/pluginsDELETE /workspace/:id/plugins/:nameGET /workspace/:id/skillsPOST /workspace/:id/skillsGET /workspace/:id/mcpPOST /workspace/:id/mcpDELETE /workspace/:id/mcp/:nameGET /workspace/:id/commandsPOST /workspace/:id/commandsDELETE /workspace/:id/commands/:nameGET /workspace/:id/auditGET /workspace/:id/exportPOST /workspace/:id/importToken management (host/owner auth):
GET /tokensPOST /tokens (body: { "scope": "owner"|"collaborator"|"viewer", "label"?: string })DELETE /tokens/:idInbox/outbox:
POST /workspace/:id/inbox (multipart upload into .opencode/openwork/inbox/)GET /workspace/:id/artifactsGET /workspace/:id/artifacts/:artifactIdPOST /workspace/:id/files/sessionsPOST /files/sessions/:sessionId/renewDELETE /files/sessions/:sessionIdGET /files/sessions/:sessionId/catalog/snapshotGET /files/sessions/:sessionId/catalog/eventsPOST /files/sessions/:sessionId/read-batchPOST /files/sessions/:sessionId/write-batchPOST /files/sessions/:sessionId/opsToy UI (static assets served by the server):
GET /uiGET /w/:id/uiGET /ui/assets/*OpenCode proxy:
GET|POST|... /opencode/*GET|POST|... /w/:id/opencode/*OpenCode Router proxy:
GET|POST|... /opencode-router/*GET|POST|... /w/:id/opencode-router/*Auth policy:
GET /opencode-router/health requires client auth./opencode-router/* endpoints require host/owner auth.All writes are gated by host approval.
Host APIs accept either:
X-OpenWork-Host-Token: <token> (legacy host token), orAuthorization: Bearer <token> where the token scope is owner.Approvals endpoints:
GET /approvalsPOST /approvals/:id with { "reply": "allow" | "deny" }Set OPENWORK_APPROVAL_MODE=auto to auto-approve during local development.
FAQs
Filesystem-backed API for OpenWork remote clients
We found that openwork-server demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
TC39’s March 2026 meeting advanced eight ECMAScript proposals, including Temporal reaching Stage 4 and securing its place in the ECMAScript 2026 specification.

Research
/Security News
Since January 31, 2026, we identified at least 72 additional malicious Open VSX extensions, including transitive GlassWorm loader extensions targeting developers.

Research
Six malicious Packagist packages posing as OphimCMS themes contain trojanized jQuery that exfiltrates URLs, injects ads, and loads FUNNULL-linked redirects.