SpielOS
The operating system for AI-run companies.
spielos.xyz · one durable Goal loop, Agent-owned Departments, approvals, evidence, and memory — all local, all on disk.
GOAL → OBSERVE → DECIDE → ACT → EVALUATE
Turn business intent into measurable Goals. The Director Agent (in OpenCode or Codex) owns the conversation; SpielOS owns the durable loop behind it: every run, work order, approval, evidence record, and memory item is persisted in a local SQLite database — never lost when a chat session ends.
Install
One line with pipx (requires Python 3.11+):
pipx install spielos && spielos init --dir my-company -y
One line with Homebrew:
brew install shayanspiel/spielos/spielos && spielos init --dir my-company -y
One line with npm (thin launcher; needs the Python package too):
npm i -g spielos && pipx install spielos && spielos init --dir my-company -y
One line with curl:
curl -fsSL https://raw.githubusercontent.com/ShayanSpiel/SpielOS/main/install.sh | sh
The chosen folder becomes a self-contained SpielOS home: the runtime
spine, Director agent + host adapters for OpenCode and Codex, and empty
private state. The spielos command itself is a global CLI — your company
data always lives in the folder you chose.
Talk to your Director
cd my-company
opencode # or: codex
In OpenCode: run /agents, select the Director agent, and talk to
it — it already sees your company state.
In Codex: talk to the Director agent — it already sees your company state.
No manual probing, no status commands to start: the host injects a fresh,
read-only company projection into every model request.
Update
pipx upgrade spielos && spielos update --dir /path/to/your/home
update refreshes only the vendored spine and host adapters; your private
.spielos/ state, owner profile, memory, and user Departments are always
preserved. Stale files from older releases are pruned so the home matches a
fresh install exactly.
What's inside
| Concept | What it is |
|---|---|
| GoalRuntime | The one durable control loop: observe, decide, act, evaluate |
| Goal | A measurable outcome with an owner, metric, and target |
| Department | A declarative, Agent-owned capability package |
| Workflow | Ordered steps with declared evidence and approval keys |
| Agent | Performs claimed work orders through a Host |
| Evidence | Immutable proof attached to Goals and Runs |
| Memory | Three scopes: owner profile, workflow learning, strategy learning |
| Approval | Explicit owner keys — external actions always park first |
Fresh homes start with zero Departments — add clean declarative packages only when their Goal, Workflow, Agent, Evidence, and approval contracts are ready.
Executor identity is enforced: a WorkOrder executes only for its declared agent (exact string, no aliases), claims are claim-then-complete, and work for an agent that is neither installed, nor the goal owner, nor declared by the owning Department is refused upfront and escalated to the owner instead.
Memory retrieval is topology-aware: a Goal's relevant memory carries the
strategy claims of Goals it is structurally related to (same owner and
metric, parent, child, or supports edge), parked asks append the workflow
or goal-relevant learning they should build on, and every WorkOrder brief
carries that bounded memory list so the next execution differs from the
last — memory is causal, not decorative. Strategy memory stays selective —
completing a goal writes no new strategy claims; owners and evidence-backed
host distillation are the only strategy writers, operational lessons are
the only per-completion writes, and stale claims retire with
memory retire without losing their evidence. Approvals acknowledge
their answered asks, and unknown comparison operators raise instead of
silently failing closed.
Useful commands:
spielos status
spielos overview
spielos context
spielos memory summary
spielos memory retire <memory_id>
spielos profile list
spielos notifications list
spielos runner tick
Development
git clone https://github.com/ShayanSpiel/SpielOS.git
cd SpielOS
PYTHONDONTWRITEBYTECODE=1 python3 -B -m unittest company.tests.test_clean_core_acceptance
- Architecture — the clean-core contract
- Website · GitHub
- MIT licensed
Metadata
Release files for spielos 10.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| spielos-10.3.0.tar.gz | 181.3 kB | With provenance | Details for spielos-10.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| spielos-10.3.0-py3-none-any.whl | Python 3 | none | any | Details for spielos-10.3.0-py3-none-any.whl |
Total release size: 400.7 kB
Release files / spielos-10.3.0.tar.gz
| Download URL | spielos-10.3.0.tar.gz |
|---|---|
| Size | 181.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eb6f5e40cc490ba8858cceb898d25f10e376bf28d104e265edd1a6a7e74b7f8c
|
|
BLAKE2b-256 checksum How to use checksums |
f18a65cb0e23d4c2301c1ba0756d3396c72adb3e580e2e392385f791bde601c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency logRelease files / spielos-10.3.0-py3-none-any.whl
| Download URL | spielos-10.3.0-py3-none-any.whl |
|---|---|
| Size | 219.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
55b127e67e7778095f7a2f5932b6b48a479060d1bbb0b76e8b8353c564896c11
|
|
BLAKE2b-256 checksum How to use checksums |
458230c7963f01beb6d3a5db5f7bff0d7c07279f7583013bfca9290a1cc99a8f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency logSecurity for spielos 10.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for spielos-10.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.