fkst-hosted turns GitHub issues into autonomous coding sessions. Install the GitHub App on a repository, describe work as issues, and receive a pull request for each task without operating the session infrastructure yourself.
- Run coding sessions for your repositories. Declare each session with a GitHub trigger issue and configure the workflows and environment it should use.
- Queue work with issues. Add focused work items, follow their status, and review the pull requests the session creates.
- Work from GitHub or the dashboard. Use issues as the durable source of truth, or sign in with GitHub for a visual view of repositories and sessions.
- Inspect and control sessions. Start or stop sessions, manage environments and GitHub App installations, and review live state, logs, and outcomes.
- Review your own activity and sandboxes. The Operations view shows the API calls you made and the live sandboxes you own or were explicitly given access to. It is scoped to you: sharing a session never exposes another person's API activity, and a deployment administrator is the only role that can see across users.
- Automate through REST. Use the dashboard's machine-readable API for supported session, work-item, environment, log, and outcome operations.
- Install the fkst-hosted GitHub App on the repositories where sessions should run.
- Start a session from the dashboard or the installed fkst substrate session issue template.
- Queue a task from the dashboard or the fkst work item issue template, then follow its issue status and review the resulting pull request.
See the fkst-hosted user manual for session configuration, work labels, environments, permissions, and lifecycle details.
The control plane serves its runtime-generated OpenAPI 3.1 contract at
GET /openapi.json. Use that contract as the authority for available routes,
request and response shapes, and each operation's authentication requirements.
For self-hosting, follow the FKST Local Deployment Guide.
The activity trace behind the Operations view is optional and operator-owned: AUDIT-TRACE.md documents its architecture, data boundaries, authorization model, and retention; AUDIT-RUNBOOK.md documents provisioning, rollout, and incident response.