Apothem v1.0.1 — launch release

Apothem v1.0.1 is the launch release of the host-agnostic configuration manager for AI assistant harnesses: one shared profile, seventeen harnesses, a single signed version, and supply-chain evidence attached to the release itself.

The thesis: one profile, seventeen harnessesCopy Anchor Link

Apothem reads a single shared profile at ~/.config/apothem/profile.yaml and materializes it into the native configuration each harness expects. You author your behavioral rules, skills, hooks, and conventions once. Apothem renders them into seventeen harness-native targets and keeps them in sync.

The seventeen adapters in this release:

• antigravity
• claude-code
• codebuddy
• codex
• cursor
• gemini-cli
• github-copilot
• glm
• hermes
• kimi-code
• kiro
• open-claw
• opencode
• qwen-code
• trae
• windsurf
• zed

Add a tool to your workflow, run one command, and your configuration is there. Remove a tool, and Apothem removes the files it wrote; the shared memory, contexts and learning stores go with the last harness, after a backup, and plans/ always stays.

InstallCopy Anchor Link

Several install paths, one CLI underneath:

1. Claude Code plugin — inside Claude Code:

   Copy Text

   /plugin marketplace add ahmed-g-gad/apothem
   /plugin install apothem@apothem

2. npx — run the CLI directly from the npm package @ahmed-g-gad/apothem, no install step:

   Copy Text

   npx @ahmed-g-gad/apothem profile init
   npx @ahmed-g-gad/apothem install --harness all --project .

3. One-shot script installer — places a self-contained runtime and an apothem launcher (~/.local/bin/apothem on POSIX, with a PATH hint when that directory is not on PATH; apothem.cmd in WindowsApps on Windows):

   Copy Text

   curl -fsSL https://apothem.ahmedgad.com/install.sh | sh    # POSIX

   The POSIX script verifies the release tag's GPG signature by default and aborts when the maintainer key is not in the local keyring. Until the maintainer publishes the key fingerprint (see SECURITY.md), set APOTHEM_VERIFY=checksum to check the archive against the release SHA256SUMS, or APOTHEM_ALLOW_UNVERIFIED=1 to proceed without tag verification.

   Copy Text

   irm https://apothem.ahmedgad.com/install.ps1 | iex         # Windows

4. Tool-native plugins and extensions — a Gemini CLI extension (gemini extensions install https://github.com/ahmed-g-gad/apothem), a Qwen Code extension (qwen extensions install ahmed-g-gad/apothem), and a Codex plugin (codex plugin marketplace add ahmed-g-gad/apothem). The source of a VS Code-family extension, covering VS Code and GitHub Copilot, is in the repository's vscode-extension/ folder. It is not listed on the Visual Studio Marketplace, and this release attaches no packaged .vsix.

Supply-chain postureCopy Anchor Link

The GitHub Release v1.0.1 carries the full evidence set alongside the code:

• sdist and wheel, validated before publish.
• A CycloneDX SBOM.
• Sigstore cosign keyless signature bundles for the sdist, the wheel, and the platform archives.
• SLSA-3 build provenance, verified inside the release workflow itself.
• Platform runtime archives (darwin / linux / windows) with a signed SHA256SUMS manifest.

The release commit is GPG-signed (v1.0.1 is a lightweight tag, with no signature of its own), and the npm package is published with Sigstore build provenance from GitHub Actions.

What's in the boxCopy Anchor Link

The apothem CLI exposes the operator commands you need for the full configuration lifecycle:

• apothem install — materialize the profile into one harness or all of them.
• apothem uninstall — remove a harness's materialized config, leaving the shared profile untouched.
• apothem update — re-materialize after you edit the profile.
• apothem verify — detect drift between the profile and a harness's on-disk config.
• apothem harnesses — list every registered adapter.
• apothem profile — inspect and manage the shared profile.
• apothem doctor — diagnose environment and configuration issues.

Each harness adapter implements a uniform HarnessAdapter protocol — install, update, uninstall, is_installed, verify — so every harness behaves predictably from the operator's seat regardless of the vendor format underneath. Read more about the design in the adapter architecture deep-dive and about format reconciliation in cross-harness convention convergence.

Where to go nextCopy Anchor Link

• Quickstart — install and materialize your first profile.
• Harnesses — per-adapter reference for all seventeen targets.
• Concepts — the profile model and materialization pipeline.

Apothem is MIT-licensed and developed in the open at github.com/ahmed-g-gad/apothem.