AtSys
Installable supervision for general coding work: features, bug fixes, refactors, tests, builds, migrations and scripts.
pip install atsys
cd /path/to/your/project
atsys init
Then open a Codex session in that repository and ask:
$atsys Implement my feature, with tests, under automatic supervision.
The bundled skill teaches Codex to inspect the repository, prepare the task objective/plan and acceptance checks, configure bounded supervision/recovery, submit the task, and report a verified handoff. atsys init installs the repository skill, attaches the project, installs the macOS watchdog service, and starts the local dashboard. Existing source, AGENTS.md, Git hooks and provider credentials are preserved. Codex CLI and its native login must already be available for model-backed work.
atsys ui
atsys task list
atsys task show TASK_ID
atsys task stop TASK_ID
atsys service status
atsys task template --objective "My coding objective" --output .atsys/tasks/task.json
atsys task submit --config .atsys/tasks/task.json
The wheel contains the compiled backend and web assets. A Python dependency supplies Node 24; no npm install, development server, or source checkout is needed. State defaults to ~/.local/share/atsys, overridable with ATSYS_DATA_DIR. Runtime state is never written into the installed package.
Tasks run independently of the terminal and dashboard. Codex diagnosis is read-only; separately authorized repair uses workspace-write. Completion requires the configured validator. Telegram is opt-in through the dashboard. Local sleep/power loss suspends work; generic commands run as the local user. Built-in OS service installation currently targets macOS; Linux requires a separately configured service manager. Windows process supervision is unsupported.
Use atsys init --no-service --no-dashboard for integration-only setup, atsys integrate to install just the Codex skill, and atsys integrate --remove to remove the unmodified managed skill. Reopen the Codex session if it was started before the skill was installed.
1 maintainer
Metadata
1 maintainer
Release files for atsys 0.2.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 | |
|---|---|---|---|---|
| atsys-0.2.0.tar.gz | 1.0 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| atsys-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.0 MB
Release files / atsys-0.2.0.tar.gz
| Download URL | atsys-0.2.0.tar.gz |
|---|---|
| Size | 1.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f2bbbfd76fc2a91aa7d0e8323e03ad9825d55ee96c45accf0cd029ae1b20cfbc
|
|
BLAKE2b-256 checksum How to use checksums |
1b034fb1625d9cfe563498cfcc2f79c07c40925ee948ebd33c051db00e73a1f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 23, 2026.
Transparency logRelease files / atsys-0.2.0-py3-none-any.whl
| Download URL | atsys-0.2.0-py3-none-any.whl |
|---|---|
| Size | 1.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4f73abb653a86541290768af1534db9aa1f3481b5622e598ec543f8d086f6d46
|
|
BLAKE2b-256 checksum How to use checksums |
6ad27e42517f8e1ea78012fbf729737d0a140d86a8ddd434382f6d5b8db054bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 23, 2026.
Transparency logSecurity for atsys 0.2.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 atsys-0.2.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 Oct 23, 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.
