This release is a pre-release and may not be stable for production use.
CAIROS
CAIROS - Context-Aware Intelligent Runtime Operating Shell
CAIROS is a context-aware console assistant that lives inside your normal shell. It is useful offline through deterministic templates, and can use AI as a fallback when configured.
Package/distribution name: cairos-shell
Terminal command: cairos
GitHub repo: Saltybukket/cairos
Quickstart
Install from GitHub:
pipx install git+https://github.com/Saltybukket/cairos.git
cairos quicksetup
Use from any project:
cd ~/projects/my_repo
cairos doctor
cairos context
cairos check if repo is ready to commit
Optional AI quickstart:
export OPENROUTER_API_KEY="your-key"
cairos config ai use-openrouter-free
cairos config ai test
Windows users should run:
py -m pip install --user pipx
py -m pipx ensurepath
pipx install git+https://github.com/Saltybukket/cairos.git
cairos quicksetup
PyPI-Ready Install
There is no PyPI release yet. The repository is prepared for PyPI Trusted Publishing; after the first release is published, installation will be:
pipx install cairos-shell
Development Install
git clone https://github.com/Saltybukket/cairos.git
cd cairos
pipx install --editable .
cairos install-info
Everyday Use
cairos
cairos templates
cairos gui --check
cairos gui
cairos templates system
cairos plan create cpp mini project engine with class Player and main
cairos plan list wsl distros
cairos plan open project in vscode
cairos run create folder docs
Direct cairos <task> prints a plan. Use cairos run <task> to execute after
confirmation.
Optional Local Web GUI
Install the optional GUI dependencies, then launch a localhost-only dashboard:
pipx inject cairos-shell fastapi uvicorn jinja2 python-multipart
cairos gui --check
cairos gui
For editable development installs:
python -m pip install -e ".[gui,dev]"
The GUI shows config paths, AI profiles, provider setup, fallback settings, doctor output, and update/backup guidance. It binds locally, uses a temporary session token for state-changing POST requests, and hides raw API keys unless you explicitly use a reveal action.
Templates vs AI
Simple, clear commands use offline deterministic templates. Longer fuzzy requests are scored for confidence; low-confidence templates step back so AI fallback can handle the request when configured. Every template or AI plan is still safety-scanned before display or execution.
Debug routing decisions with:
cairos plan --debug-route <task>
CAIROS cannot permanently change the parent shell directory from a child
process. Use cairos find-dir <name> or a shell wrapper from
Shell Navigation for cd workflows.
Update
cairos update
cairos backup-config
GitHub installs are updated with the command printed by cairos update.
Config, history and AI profiles live outside the package install and are
preserved across package upgrades.
AI Profiles
Save multiple providers/models and switch quickly. Full provider setup lives in AI Providers.
cairos config ai use-openrouter-free
cairos config ai profiles
cairos config ai switch
Automatic profile fallback is enabled by default. If the active profile is rate-limited, out of credits, temporarily unavailable, missing a visible key, or points at an unavailable model, CAIROS tries another saved profile and prints a notice before the plan:
cairos config ai fallback status
cairos config ai fallback disable
cairos config ai fallback enable
cairos config ai fallback order openrouter-free gemini-flash groq-llama
CAIROS stores environment variable names, never raw API keys.
Generate shell-specific key setup commands:
cairos config ai key commands OPENROUTER_API_KEY --shell bash
cairos config ai key commands OPENROUTER_API_KEY --shell powershell
cairos config ai key status OPENROUTER_API_KEY
Reveal commands print secrets only when explicitly requested:
cairos config ai key reveal OPENROUTER_API_KEY
Key Locations
Global config lives in ~/.config/cairos/config.json on Linux/macOS/WSL and
%APPDATA%\cairos\config.json on Windows. History lives in
~/.local/state/cairos/history.jsonl or %LOCALAPPDATA%\cairos\history.jsonl.
Optional project-local rules live in .cairos/rules.json.
Documentation
Metadata
Release files for cairos-shell 0.5.0a4
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 | |
|---|---|---|---|---|
| cairos_shell-0.5.0a4.tar.gz | 112.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cairos_shell-0.5.0a4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 204.5 kB
Release files / cairos_shell-0.5.0a4.tar.gz
| Download URL | cairos_shell-0.5.0a4.tar.gz |
|---|---|
| Size | 112.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70c1dfbdf0c37dba5b9a94f9b05afd3776ab913a0606e02b2aca33b1c73c5283
|
|
BLAKE2b-256 checksum How to use checksums |
e6ae894c5be5838ae29b9ea52143fe6fd8a1d9d309039460d63850ee7a8050ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 8, 2026.
Transparency logRelease files / cairos_shell-0.5.0a4-py3-none-any.whl
| Download URL | cairos_shell-0.5.0a4-py3-none-any.whl |
|---|---|
| Size | 91.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
deef043fd0f8bdc05fd946a9f008c8dca4627ee89f463cc5874d0e962efcc07c
|
|
BLAKE2b-256 checksum How to use checksums |
c16f5b6b01e57275674c5b393c40b75e4860d2ef7f1100fd6341006fec82856f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 8, 2026.
Transparency logSecurity for cairos-shell 0.5.0a4
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 cairos_shell-0.5.0a4.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 Jul 8, 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.