Start // Server Mode
The kernel daemon listens on a local Unix socket. Drive it from CI, a remote shell over SSH, or an external bot. Same audit chain, same capability bounds; just exposed across machine boundaries.
This walkthrough is in progress. The pieces below are real and shipped at v7.7.7; the connecting narrative for CI and remote workflows is being written. Follow up on the linked references for the current state.
If you've wired ostk into CI or a Discord bot already and have notes that would help others, send them to os-tack/ostk-site issues.
BUILDING_BLOCKS
The pieces that make server-mode real today.
ostk daemon canonical command
Starts the kernel daemon. Holds the socket at .ostk/ostk.sock, the process table, and the scheduler. Survives client disconnects. Run it on the host where the project lives. (ostk listen is a legacy alias.)
ostk mcp stdio bridge The MCP stdio bridge any external client can launch as a subprocess. Forwards to the running daemon. See /docs/mcp for the inbound protocol and configuration.
SSH socket-forward remote driving
Drive a remote daemon by forwarding its Unix socket over SSH. Pattern: run ostk daemon on the server, then on your laptop:
$ ssh -L /tmp/remote-ostk.sock:.ostk/ostk.sock user@server
Then point your local OSTK_SOCKET at /tmp/remote-ostk.sock. Audit lands on the server's .ostk/journal.jsonl; your laptop is just a thin client.
ostk.ai.discord pattern bot integration
The reference Discord-bot integration shows the bot-driving-daemon shape: bot connects to .ostk/ostk.sock over the MCP wire, dispatches user-typed commands as agents, posts back to the channel. Source: os-tack/ostk.ai.discord.
CI runner in-process
For CI, the simplest pattern is in-process: the runner clones a repo with a populated .ostk/, calls ostk init if needed, and dispatches an Agentfile via ostk run. The daemon is local to the CI job; audit lands in the workspace and gets uploaded as a build artifact.
WHAT_THIS_PAGE_NEEDS
- ·End-to-end CI walkthrough (GitHub Actions example).
- ·SSH socket-forward worked example with full env wiring.
- ·Multi-operator wiring (federation across machines, claim graph).
- ·Authentication / capability-pin model for remote callers.
- ·Discord-bot quickstart pulled out of the reference repo.