Skip to content
pixelscortexPublic

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

538 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Tokamak

Tokamak is a Rust server with TypeScript plugins and a Solid 2 web client in Tauri 2. The client skeleton lists and creates Chat threads. /kit holds ui-sdk controls. Compiler-built plugin views load through the server; the product shell is next.

Run

Install proto, rustup, and your platform's Tauri prerequisites. .prototools pins Bun, Moon, and Rust. From this repository:

proto run bun -- install --frozen-lockfile

Launch the desktop app:

proto run bun -- run app

The host builds Chat and the server, starts or reuses the local server and connects automatically. New thread creates a Chat thread. No external agent is started. See app/README.md for browser development and checks.

Packages

packages/server owns storage and plugin execution. packages/engine keeps QuickJS for server plugins. packages/runtime keeps a server-only Rust facade, server process tooling, and reusable TypeScript catalog/reload logic. packages/sdk supplies the portable protocol and Solid 2 DOM integrations. packages/build builds server plugin artifacts. packages/ui is a placeholder for web primitives and tokens. wiki contains the docs and design rules.

Chat's plugins/chat/src/client stays untouched as rewrite reference. Its root tsconfig includes only plugin.ts and src/server; lint ignores the client. The compiler emits DOM ESM plugin UI and the web host loads it through revision-pinned server URLs. Chat's client remains excluded until ported. No Solid 1 runtime remains in workspace dependencies.

Checks

proto run bun -- run check
proto run bun -- run typecheck
proto run bun -- run test
proto run bun -- run e2e
moon run app:web-build
proto run bun -- run --cwd app tauri build --no-sign

The check pipeline runs Oxfmt, rustfmt, Oxlint, and advisory Clippy. Type-checking covers the remaining packages, including the wiki. Server/engine tests and SDK/build/app tests cover the runtime. Run proto run bun -- x playwright install --no-shell chromium webkit once, then proto run bun -- run e2e:browser for production browser tests against a real disposable server. See e2e/README.md for adding tests.

Every PR runs Linux TypeScript/native/browser checks and an unsigned macOS Tauri build. bash .ci/release-macos.sh on macOS arm64 creates the unsigned .app, zip and standalone server archive under .ci-results/macos-arm64. The release workflow is manual and uploads artifacts only. See .ci/README.md for reserved signing inputs; signing, notarization and publishing are absent.

Plugin workers

A plugin opts its actions into Bun with runtime: "worker" in definePlugin. Queries and mutations continue to run in QuickJS. Each opted-in plugin has one lazy, long-lived worker, preserving module state between actions. Bun must be installed on the machine; a missing executable produces Plugin <id> needs Bun: install from https://bun.sh.

The build emits a separate Bun action bundle and a generic SDK worker entry. The server and worker exchange newline-delimited JSON with a 1 MiB message cap: server → worker: invoke {id, fn, args}, opResult {id, value|error}, cancel {id}, and shutdown; worker → server: result {id, value|error}, op {id, call, name, payload}, and log {level, text}. Messages have a type field. Invocation and operation IDs correlate concurrent calls. Host operations reuse the existing action bridge and permission checks; workers get no database handle. Each invocation receives an AbortSignal through ctx.signal.

Workers run in per-plugin data folders under the server data directory, with a cleared environment containing PATH, HOME, USER, LANG and manifest env:<name> grants. Worker code has ordinary local process access; this is not an OS sandbox. Reload, disable, and server shutdown kill the worker's whole process group. Crashes fail pending actions and restart on the next call with a short backoff. Actions have a one-hour wall deadline; cancellation allows 500 ms to settle before the worker and its children are killed. Plugins without the field keep running actions in QuickJS.

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages