Developers

Build on Genisys

Genisys runs on your PC. Developers extend it two ways: plugins that give agents new tools and skills, and API clients that start runs and call plugins through the local Developer API.

Plugins: tools and skills

A plugin is one .genisys-plugin.json file: a manifest and one ES module. Tools are async functions agents can call (asked for, or granted, like any other tool). Skills are Markdown instructions agents can follow. Plugin code runs in a sandbox with no network, files or storage; it reaches the outside only through ctx.fetch to the hosts its manifest names.

Plugin guide · Try the playground

API clients

The desktop app can serve a local HTTP API on 127.0.0.1 (off until you enable it in the Developer console). Scripts, editors and services on your PC use an API key to list projects, start agent runs, read usage and invoke plugins. Each key has scopes, optional project limits, a per-minute rate limit and optional token budgets.

Quickstart · API reference

Test, preview, production

A plugin has an editable draft and up to two frozen releases, a previewversion and a production version, served at the same time.

  1. Test: the draft. Write and run it in this playground or the desktop Developer console's test runner; gsk_test_ API keys can call it too.
  2. Preview: promoting the draft freezes its version (which must be new and higher than every frozen one) and serves it to agents in the preview projects you choose.
  3. Production: promoting preview copies that version to production, for agents in all other projects and gsk_live_ API keys. Production keeps serving the old version until you promote a new one; rollback points production at any earlier frozen version.

Disabling a plugin withdraws it from everyone but the console.