kageos · Developer toolkit

Start, contribute to, and deliver kageos with Codex or Claude

Clone and open kageos locally, verify dependencies, start both ends, and then explore the source, contribute changes, or continue through directory verification and Hub publishing.

Download 0.3.0 View source Chinese changelog

The release includes manifests for both Codex and Claude Code.SHA-256

01 · Install for Codex

Prepare the personal plugin with one command

The installer downloads a fixed release, verifies SHA-256, backs up the previous version, and adds kageos to the Personal marketplace.

$ curl -fsSL https://kageos.ai/install-kageos-plugin.sh | bash

For managed environments, download and review the installer before running it. It does not read or write kageos, Hub, or model credentials.

02 · Use with Claude Code

Load the same package directly

After running the installer, Claude Code can load the same local plugin directory under its own namespace.

$ claude --plugin-dir ~/plugins/kageos

/kageos:kageos take this directory from design through publishing

03 · Open kageos locally

Let the toolkit handle first run

kageos-contributor checks Git, Go, Node.js, Podman or Docker, protects existing container data, clones the source, starts the backend through kagectl, then starts and verifies the frontend.

$ git clone https://github.com/kageos/kageos.git

$ cd kageos

$ ./scripts/dev.sh

Check prerequisites

Start and verify

Explore or contribute

Closed loop

Eight stages with explicit exit gates

01
Directory design
02
Local build
03
Platform build
04
Live verification
05
Bundle export
06
Publish preparation
07
Hub submission
08
Status confirmation

Start using it

After installation, use one entrypoint. Five skills route platform startup, source contribution, and directory delivery.

$kageos take /user/app/package from design and development through verified Hub submission.