Your desk is clear.
Open Install Camicus to keep reading.
Install Camicus 0.1.0
Use two local workflows through Codex or Claude Code. No account with Camicus, background service or remote collector is required.
Requirements: macOS 14+ and Python 3.11–3.14. This is an experimental alpha. Inspect the source and package; a checksum confirms matching bytes, not authorship or device safety.
1. Download and inspect
Download the plugin ZIP · Download the Codex marketplace ZIP · SHA-256 sums
Extract into a new folder you choose. Compare the downloaded archive’s SHA-256 with the published sums, inspect INSTALL.md and the two workflow skills, then follow the native setup below. Keep existing files and results; never overwrite them to retry an installation.
shasum -a 256 /absolute/path/to/camicus-plugin-0.1.0.zip2. Choose your assistant
Claude Code: load for one session
Use the extracted camicus directory. Validation checks the package format; the next command loads it into the selected Claude Code session.
claude plugin validate /absolute/path/to/camicus --strict
claude --plugin-dir /absolute/path/to/camicusInvoke /camicus:weekly-brief or /camicus:mac-audit with an explicitly authorized workspace. This package targets local Claude Code, not claude.ai or Cowork.
Codex: local marketplace
Extract the marketplace bundle into a new directory, or clone the tagged release below. Use its physical absolute root path in the commands. Adding the marketplace and plugin persists configuration; choose the Codex profile and project deliberately.
git clone --branch v0.1.0 --depth 1 https://github.com/modernlabyrinth/camicus.git camicus-0.1.0
codex plugin marketplace add /absolute/path/to/camicus-0.1.0
codex plugin add camicus@camicus
codex plugin listRestart the session if discovery requires it, then ask Codex to use the Camicus weekly-brief or mac-audit skill. The website does not install anything or grant extra tool permissions.
Read the complete native installation guide →
3. Run one authorized workflow
Example request: weekly brief
“Use the Camicus weekly-brief skill with the project folder I authorize. Help prepare project.json and tasks.json, let me review the snapshots, then check into a new JSON result. Show counts, blockers and failures. Do not send the update.”
Example request: read-only Mac audit
“Use the Camicus mac-audit skill with the workspace I authorize. Run the read-only audit into a new JSON file. Explain observed settings, unobserved checks and visible TCP listeners. Do not change settings or attempt repairs.”
A weekly brief needs two reviewed local snapshots. A Mac audit needs an authorized absolute workspace for its new result, not weekly input files. Neither workflow discovers accounts, asks for passwords or connects to your task app.
The engine refuses unsafe workspace paths, extended ACLs and existing output names. Choose a new authorized folder rather than changing broad permissions to make it run. Keep private results out of public issues.
Inspect, rerun, remove
Read the JSON and fixed diagnostic. Weekly verify checks a saved result against the current files; Mac audits must be rerun into a new file. Unsigned historical receipts can be edited and are not authenticated execution records.
Remove a persistent installation
codex plugin remove camicus@camicus
codex plugin marketplace remove camicus
claude plugin uninstall camicus@camicus
claude plugin marketplace remove camicusRun only the commands for the assistant you installed into, then restart it. A session loaded with --plugin-dir stops loading when that session closes.
Remove only the plugin/marketplace installation and folders you selected, following native assistant instructions. There are no Camicus background services to stop. Preserve results according to your retention needs.
Inspect fictional weekly examples · Troubleshooting and support · Where data goes