Skip to main content

SpielOS — Agent-owned AI Company Operating System

SpielOS is an open-source local harness for running durable company work with AI: one Director owns the Goal loop, agents complete bounded workflows, and every approval, hand-off, and result is persisted on disk.

GOAL → OBSERVE → DECIDE → ACT → EVALUATE

Install

pipx install spielos && spielos init --dir /your/chosen/folder

The chosen folder becomes a self-contained SpielOS home. It receives the runtime, agent host adapters for Codex and OpenCode, empty private state, and no pre-installed departments.

Update

pipx upgrade spielos && spielos update --dir /your/chosen/folder

Update replaces only the harness spine and host adapters. It preserves the home’s strategy, assets, installed Departments, configuration, and private .spielos/ state. spielos refresh remains a compatibility alias.

To test unreleased source changes locally, install the built wheel explicitly; plain pipx install spielos installs the latest release published on PyPI:

pipx install --force /path/to/SpielOS/dist/spielos-VERSION-py3-none-any.whl
spielos update --dir /your/chosen/folder

Departments and agents

A Department is an installable, Agent-owned capability. Its agents own narrowly-scoped workflows and can only produce their declared evidence. The Director routes work through durable work orders; agents never own the company loop or approve external actions.

spielos department validate --file department.json
spielos department install --file department.json --dir /your/chosen/folder
spielos department list

Fresh homes deliberately start with no Departments. Install one package or all seven bundled capabilities only when they match a real company outcome:

spielos department install --all --dir /your/chosen/folder

The public architecture has one name per layer: Goal, Department, Workflow, Agent, Skill, Connection, and Artifact. Use one orientation command instead of probing several catalogs:

spielos overview

Open the live, read-only organism view with:

spielos observatory

The Observatory layers the Goal tree and support graph, current loop stage, Resolution work, Workflows, WorkOrders, Agents, Evidence, Memory, and source contracts on one navigable canvas. Its coherence view surfaces blocked, disconnected, redundant, unused, and compatibility-only state without mixing historical records into the clean-core authority.

Artifacts, friction, and migration

Generated work has one lifecycle under .spielos/artifacts/<goal>/<run>/<workflow?>/{work,final}. Agents prepare the workspace, finalize verified deliverables, clean declared intermediates, and automatically open the final folder only for owner-facing creative or content deliverables such as videos, images, audio, copy, documents, and decks:

spielos artifact prepare --goal GOAL_ID --run RUN_ID
spielos artifact finalize --goal GOAL_ID --run RUN_ID --file PATH --open

Code, packages, archives, tests, logs, manifests, migration plans, and internal evidence are reported with their paths but are not opened unless the owner asks.

Misleading tools, commands, instructions, contradictions, and fallbacks are durable friction rather than silent retries. Inspect them with spielos friction list.

Migrate into a fresh home, never by treating a foreign runtime as current code:

spielos migration inspect --from /old/home
spielos migration plan --from /old/home --out migration-plan.json

The plan archives foreign Goals by default, normalizes capability/executor aliases, quarantines unknowns, and converts one Department at a time.

State, context, and memory

Goals, runs, approvals, work orders, evidence, typed company-profile overlays, experiment learning, and reusable Workflow candidates are stored locally in .spielos/state/. Strategy Markdown is the reviewed base profile; owner-explicit profile overlays can supersede one typed claim without rewriting the source files.

Codex SessionStart and UserPromptSubmit hooks, plus OpenCode's model-request hook, load a small read-only projection automatically. Initial context contains the company profile, top Goal state, and urgent attention. Each user message adds only prompt-relevant profile claims, experiment results, and Workflow instructions. Chat history and tool traces remain host-owned and are not copied into SpielOS.

Memory writes have explicit triggers: the Goal loop records experiment learning only after valid cited evidence; an owner-explicit strategy correction writes a profile claim; and every user turn carries a typed memory-candidate contract. The host model interprets semantic intent while deterministic runtime code owns scope, authority, identity, deduplication, supersession, provenance, and retrieval. Explicit owner Workflow corrections apply immediately, task-only instructions stay temporary, and a canonical Workflow defect routes to a bounded source repair instead of contradictory memory. Other procedural candidates harden after two matching behavior keys in 14 days; stale one-offs expire during consolidation. Hooks remain read-only.

Development

PYTHONDONTWRITEBYTECODE=1 python3 -B -m company status
PYTHONDONTWRITEBYTECODE=1 python3 -B -m unittest discover -s company/tests -v

The shipped home is built from company/init_templates/; runtime spine files must remain identical between source and template.

See company/README.md for the operating contract.

Metadata

Release files for spielos 9.0.0

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 9.0.0
File Size Uploaded Provenance Actions
spielos-9.0.0.tar.gz 1.4 MB With provenance Details for spielos-9.0.0.tar.gz

Built distribution (wheel)

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

Total release size: 2.9 MB

Release files / spielos-9.0.0.tar.gz

Download URL spielos-9.0.0.tar.gz
Size 1.4 MB
Tags Source
SHA-256 checksum
How to use checksums
0b10fa1aa3449adf3f1f9bccc0dc18b84d20fba7d0f115ef00a3504610818371
BLAKE2b-256 checksum
How to use checksums
94966bd2ee5e757b540b9bb556da76d6613176b21f811b149fe85345beba385e
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 2, 2026.

Transparency log

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

Download URL spielos-9.0.0-py3-none-any.whl
Size 1.6 MB
Tags Python 3
SHA-256 checksum
How to use checksums
0d8ae3f3a642cf195233eec46100412c263ec703ef71904351cef691fe7d78dd
BLAKE2b-256 checksum
How to use checksums
89c42cddacc39b679a680e922b3cea3e966d84a90c99ec41fe6ccfdbcc406741
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 2, 2026.

Transparency log

Security for spielos 9.0.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.

Select from 2 files

Attestation for spielos-9.0.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 2, 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

9.0.0 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