PUBLIC DOCUMENTATION

plugin-kit-ai

Build one plugin repo and ship it to many AI agents without learning the whole target model on day one.

Default Start

If you are new, start with the job-first path.

That keeps the first decision small, gets one working repo into your hands quickly, and leaves room to expand the same repo later.

Start By Job

• Connect an online service
• Connect a local tool
• Build custom plugin logic - Advanced

What To Know Right Away

• one repo remains the source of truth as you add more lanes
• choose the starting path that matches the job you need today
• expand later from the same repo when the product needs more outputs
• use generate and validate --strict as the shared readiness workflow

Supported Node And Python Paths

Node/TypeScript and Python remain supported when the language choice is already real for the team or the product.

• codex-runtime --runtime node --typescript stays the main supported non-Go path
• codex-runtime --runtime python stays the supported Python-first path
• both are repo-local interpreted runtime lanes, so the target machine still needs Node.js or Python installed
• Go remains the default when you want the strongest general production story

Choose What You Are Building

Start with the job first, then learn the deeper target model only when you need it.

Start Fast

Get a working repo fast from the new job-first entry path.

Advanced Custom Logic

Open the guided path for runtime code, hooks, and orchestration when wiring alone is not enough.

See The Product Shape

See how one repo grows into runtime, package, extension, and repo-owned integration setup.

Choose A Target

Match the target to how you want to ship the plugin instead of treating every output like the same thing.

Check The Exact Contract

Use the reference pages when you need the precise support boundary and compatibility terms.

Read In This Order

1. Choose What You Are Building

Pick online service, local tool, or custom logic before you go deeper.

2. Quickstart

Turn that choice into a working repo and a clean first validation loop.

3. Advanced Custom Logic

Use this when the plugin's value lives in your code, hooks, and runtime behavior.

4. What You Can Build

See the product shape across runtime, package, extension, and integration lanes.

5. Choose A Target

Use this later when you are ready for target-specific shipping decisions.

6. Support Boundary

Use the reference cluster when you need exact compatibility language and support details.

If you are new, stop after the starter pages. Everything else is deeper reference or implementation detail.

Current Repo Baseline

• The current public baseline in this docs set is v1.1.2.
• This patch line restored first-party install compatibility across legacy and current authored layouts, then fixed Gemini full multi-target installs for GitHub repo-path sources.
• Start there when you want the current recommended baseline.

What This Site Helps You Do

• start one plugin repo instead of splitting source of truth by ecosystem
• pick a recommended starting path without learning every target detail up front
• expand the same repo later into more shipping paths
• keep one review and validation story as the repo grows
• find the exact contract only when you need it