Product target: S15 — Conversational autonomy with protected approvals was confirmed on 2026-11-02. It is not implemented by the documentation update. The capabilities and instructions below describe the existing S14 runtime.

S14 is the default for new source runs and installations. It uses fresh Bot-first state beside retained legacy data. --s14 remains an alias; --legacy selects the project-centric pilot explicitly. Existing service configs without runtime remain legacy. The owner-Pi first reply, complete legacy-byte preservation through post-reply R4, and actual prior-release rollback are recorded in the cutover evidence. See the cutover runbook.

Just in time. Just for you.

A self-hosted assistant with persistent Bots and private local computers.
Chat with one assistant, bring in specialists when needed, and pick up where you left off the next day.

English · ไทย

Historical legacy pilot screenshot; see the S14 experience for the current design.

Jit is a personal assistant that runs on a machine you control: a mini PC, a home server, a VPS or a Raspberry Pi. The service runs on 64-bit Linux (x64 or arm64) with systemd. For development, any OS with Bun works. You talk to Jit, the main bot. Jit keeps persistent Bots, conversations, work, decisions and sourced memory across days. A conversation needs no Project. Research can use bounded parallel Bots and publish reports with citations and downloadable artifacts.

Jit uses Schway as its execution engine. Schway runs the agent loop and the provider sessions. Jit owns Bots, work grants, conversations, memory, computers, artifacts and durable jobs.

Schway owns execution loops, provider protocols, native sessions, compaction and model retries. Jit consumes its pinned public host contract. A configured route or healthy login page does not prove a working subscription or computer.

• Authority comes from you. Model output and retrieved content can never create permanent Bots, grants or owner decisions, and they cannot widen access.
• Proposed, accepted and done stay separate. Every change has a revision and a receipt you can inspect.
• Your data stays on your host. Jit sends no telemetry. Relevant data goes to the selected inference provider, authorized Parallel reads and explicitly enabled brokers; local execution does not imply local inference.
• Credentials stay out of the box. No Jit credential, database or backup ever enters the execution box.

Jit is a single-owner pilot. #256 closed after PR #304 merged at 143ca067e3728af94badfc2eb677b4f04a5cdb59; its Linux x64/arm64 evidence remains attributed to the exact builds and routes in the evidence record. Owner-unread reports and deferred assistive-technology/mobile permutations remain disclosed limits. The default change does not certify another host, route, browser or website. The separate owner-Pi record supplies actual installation, one tool-free first reply, full byte-preservation windows and prior-release rollback evidence. Complete post-reply R4 equality also passed.

Use Bun 1.4.2 or later for development. The installed service uses pinned Bun 1.4.2.

bun install --frozen-lockfile
bun start            # S14, http://localhost:3001

Run foreground bun start from an interactive terminal. Open the one-time owner link displayed there, set the password in Web and follow the existing provider device sign-in and setup flow. Redirected/non-TTY output receives no capability. No JIT_S14_ROUTES is required. Live replies use the selected Schway route; there is no default scripted or billing fallback. Optional local provisioning remains bun run setup (hidden terminal password).

For a reviewed, published release on Linux x64/arm64 with systemd, run its extracted ./install.sh. Bare installation selects the independent jit-s14 service at loopback port 3001. ./install.sh --uninstall removes only its service units and retains data; legacy repair/uninstall requires --legacy. Follow service installation and the cutover procedure. A moving latest URL is not proof of a reviewed build.

Source S14 uses independent environment variables:

JIT_DATABASE never maps to S14. An unselected source command with that legacy variable refuses; select --legacy or explicitly acknowledge separate S14 settings with --s14. Unknown/duplicate/conflicting selectors and mismatched service configs refuse before writable application state. See selection and compatibility.

bun src/main.ts setup --legacy
bun src/main.ts serve --legacy          # http://localhost:3000
bun run owner:reset                     # legacy only; no S14 reset command
./install.sh --legacy                   # independent retained jit layout
./install.sh --legacy --uninstall       # retains both installations' data

Project access levels, scripted replies, jit ask/pending, signed webhooks, Telegram and the legacy schedule feed describe this retained runtime. They are not S14 capabilities. Legacy still uses JIT_DATABASE (.local/jit.sqlite), JIT_ORIGIN/JIT_PORT (3000) and JIT_RUN_PORT (scripted by default); see src/config.ts. Existing canonical serve --service-config <legacy-config> and upgrade descriptors remain supported without adding flags to old builds. Service operator commands select the exact installation via config; S14 uses --config /etc/jit-s14/service-config.json, with no auto-discovery or switch to another installation.

bun test             # deterministic: scripted models, protocol fixtures, fake clocks
bun run typecheck

Work is tracked in GitHub Issues. Before you change behavior, read AGENTS.md, the workflow, the relevant spec and its ADRs.

MIT © Jit contributors. See NOTICE for Schway attribution.