Core Concepts

DevKit

The Orkestia local CLI, webhook redirect to localhost, a provider-blind coding runner, ticket sync, and composition management, authenticated with an API token

TL;DR

DevKit is the host CLI. It runs on your machine and talks to api.orkestia.dev and workflow-api.orkestia.dev.
Four jobs: replay queued webhooks on localhost, run Staff coding assignments against local repos, keep local Git facts aligned with the ticket ledger, and manage compositions with vw.
Auth is an API token from Settings → API tokens. The same kind of token also connects an AI assistant to the MCP server.
The coding runner never holds your Git credentials. The agent works in a workspace DevKit provides; you keep the keys.

The four jobs

Job	What it does	When you use it
Hook redirect	Polls queued webhooks for your org and replays them on `localhost`	Developing against GitHub, Stripe, or any provider webhook without a public URL
Runner	Claims Staff coding assignments and runs them against local repos, provider-blind	Letting an AI coding agent work a ticket in your checkout while you stay in the loop
Tickets	Keeps local Git facts (branch, commits, PR) aligned with the ticket ledger	The attended ticket-to-PR lifecycle
`vw`	Validate, import, and promote virtual workflows	Authoring compositions as files and shipping them to the catalog

DevKit and AI assistants

DevKit and the MCP server are complementary:

An assistant over MCP operates the platform: discovers capabilities, starts runs, watches them, provisions apps.
DevKit brings the platform to your local machine: webhooks arrive on localhost, a coding actor works in your checkout, and compositions round-trip as files.

A typical attended loop: an assistant claims a ticket and proposes a plan over MCP, you acknowledge it, the DevKit runner executes the coding work locally, DevKit syncs the branch and PR facts back to the ticket, and trusted delivery opens the pull request. The coding agent never holds a Git provider credential. See Tickets & software delivery.

Ask your AI assistant

prompts

Which webhooks are queued for my organization right now? Summarise them by provider.

Show me the open coding assignments for my Staff actors and which ones are claimable by a local runner.

Validate this composition definition and tell me what vw promote would register: <paste JSON>

For AI agents

Rule	Detail
DevKit is local	You cannot run DevKit from the MCP server. Ask the user to run the command on their machine.
Coding runner boundary	The runner works in a workspace it provides. Do not ask the user for Git credentials.
Compositions round-trip	A definition validated locally with `vw` is the same wire JSON the engine validates through `composition.save`.

Install and use DevKit

Binaries, Homebrew, hook redirect, runner, compositions.

Engram

Agent memory on Orkestia, what a session remembers, what the next session loads, how recall and write are switched on per agent config, and where to watch the live field

App Host

Opt-in hosting on Orkestia's shared pool — one live Identity app, one site, App Data for Postgres, Files on site MinIO, Buzz as a Nostr relay on a second hostname