DevKit

Local CLI for Orkestia — webhook redirect, provider-blind coding runner, ticket sync, and composition (virtual workflow) management

DevKit (ltinteg-devkit) is the local companion CLI. It runs on your machine (or as a hosted broker), authenticates with a Bearer API token, and never does a browser login.

It is how you:

Pull webhooks to localhost without exposing a port (reverse of ngrok).
Run a provider-blind coding runner that claims Staff assignments and never sees GitHub/GitLab credentials.
Sync tickets with local Git facts.
Validate, plan, import, and promote virtual workflows (compositions) against the Workflow API.

Install & configure

GitHub Releases, Homebrew, go install, API token.

Hook redirect

Poll → forward to localhost → acknowledge.

Local coding runner

Claim assignments, map repository_uuid → a local path, no provider secrets in the child.

Compositions (`vw`)

Validate / plan / import / promote virtual workflows from a repo catalog.

Commands

ltinteg-devkit configure    # write ~/.config/ltinteg-devkit/config.json
ltinteg-devkit hook …       # webhook redirect
ltinteg-devkit runner …     # provider-blind local (or hosted) coding broker
ltinteg-devkit ticket …     # sync local Git facts with Orkestia tickets
ltinteg-devkit vw …         # virtual workflow definitions

Auth

Create an opaque API token in the Orkestia app: Settings → API tokens. That value is api_key / LTINTEG_API_KEY. It is not a Cognito JWT and not an @orkestia/auth end-user token.

Default API bases:

Config	Default
`api_base_url`	`https://api.orkestia.dev`
`workflow_api_base_url`	`https://workflow-api.orkestia.dev`

See Tickets & software delivery for the ticket → PR lifecycle DevKit participates in.

Field & feed

Live Engram feed — events, JSON fields, what the field draws

Install DevKit

Install ltinteg-devkit from GitHub Releases, Homebrew, or Go, then configure an API token