Skip to main content

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. Direct-work lessons are goal-keyed: a lesson learned completing a direct order (workflow_id NULL) reaches future direct orders of that same Goal. 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

Metadata

Release files for spielos 10.3.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for spielos 10.3.1
File Size Uploaded Provenance Actions
spielos-10.3.1.tar.gz 182.1 kB With provenance Details for spielos-10.3.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for spielos 10.3.1
File Interpreter ABI Platform Actions
spielos-10.3.1-py3-none-any.whl Python 3 none any Details for spielos-10.3.1-py3-none-any.whl

Total release size: 402.4 kB

Release files / spielos-10.3.1.tar.gz

Download URL spielos-10.3.1.tar.gz
Size 182.1 kB
Tags Source
SHA-256 checksum
How to use checksums
9aebd95573d10c16b3593807776c94bd9fe49f6b8f2d8c279fc4f00fc35b1142
BLAKE2b-256 checksum
How to use checksums
d18cb8b78595236f49f4d57e24a2ed4272c744ab9d6ecc679643a64093a5485e
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 log

Release files / spielos-10.3.1-py3-none-any.whl

Download URL spielos-10.3.1-py3-none-any.whl
Size 220.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
52ddd6912a11e19879ab5e9ceb4d3ab76403f17588cbfd38c7939f1752a94aac
BLAKE2b-256 checksum
How to use checksums
ee545e3f86a154b6cabc908e4f7afb1d3e1bd99a0af0d1a62aa4b558d4b091ce
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 log

Security for spielos 10.3.1

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.

Select from 2 files

Attestation for spielos-10.3.1.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 log

A 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.

Release history Release notifications | RSS feed

This release

10.3.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page