Getting started

You run Agency. Deploy the acceptor and workers from the product repo, then include the CI template in a child project and point webhooks at your host.

What you need

• A GitLab you control. Self-hosted or gitlab.com both work.
• A cluster that can apply the product's Push apps. Acceptor plus workers.
• An API key for whichever model provider you use.
• A GitLab token that can comment and set labels.
• For named agent users, group CI/CD variables KIT_TOKEN_SCAFFOLDER through KIT_TOKEN_DOCUMENTER. Leave them unprotected so workers receive them.

Need a GitLab project

Create a GitLab project first. Then follow the same steps. The merge request is the office.

Deploy the runtime

1. Clone dev-agency/gitlab-agency.
2. Deploy the acceptor from deploy.nix. Push app name is kit-relay.
3. Deploy the workers from deploy-worker.nix. Push app name is kit-agent-worker. Give it a 50Gi PVC.
4. Set GITLAB_HOST to your GitLab. Secrets stay in relay/README.md.

The acceptor only enqueues. Model keys and per-agent PATs belong on the worker.

Wire a child project

Add .slopkit/config.ts. Agency wraps Flue.

export default {
  agents: {
    scaffolder: true,
    planner: true,
    developer: true,
    reviewer: true,
    tester: true,
    documenter: true,
  },
  previewEnvironments: false,
  sync: {
    onPush: true,
    onWebhook: true,
  },
};

Optional model in that file, or FLUE_MODEL in CI, selects any Flue-supported model. Bring the matching provider key.

Include the template:

include:
  - project: "dev-agency/gitlab-agency"
    ref: "main"
    file: "/templates/gitlab-ci/agentic.yml"
    inputs:
      node_image: "node:26"
      agency_ref: "main"
      agency_project: "dev-agency/gitlab-agency"

Set CI/CD variables on the child or its group:

• Your provider key.
• Optional FLUE_MODEL.
• GITLAB_TOKEN or a group access token.
• KIT_WEBHOOK_URL=https://<your-relay-host>/hooks/gitlab

First spec

1. Push. kit:sync-push writes issues and merge requests from .slopkit/ and registers the webhook on your acceptor.
2. Add a spec under .slopkit/specs/ or mention @kit-scaffolder on a merge request.

Webhook checklist