Repository Automation
Three optional automations that run in or alongside your repository, what each one needs, and how to turn it on.
Most CodeLantern work happens in your coding agent, with you present. Three automations can also run without a session open. Each is independent. The cloud agent and board automation are optional choices, and knowledge base sync is on by default (on GitHub, you can turn it off).
| Automation | What it does | Providers | How you turn it on |
|---|---|---|---|
| Cloud agent | Runs skills unattended when someone mentions @codelantern-ai on an issue or pull request | GitHub | An optional cl-init choice |
| Knowledge base sync | Mirrors your repository's knowledge base to CodeLantern for your analytics | GitHub, Azure Repos | On by default: a workflow cl-init always adds on GitHub; automatic on Azure Repos |
| Project board automation | Moves issues across your project board as work progresses | GitHub Projects | An optional cl-init choice on GitHub Projects |
None of these is required to use the workflow. Every skill runs locally in your coding agent whether or not you enable them.
What cl-init does and what's left to you
/cl-dev:cl-init writes the files these automations need into your working tree and asks about the optional ones. It doesn't commit, push, or run anything. For any GitHub workflow it adds, you finish the setup by committing the files and merging them into your default branch, because GitHub runs these workflows from there. Each page below lists any other step that's yours, such as a permission an organization owner approves.
To turn on an automation you skipped, run /cl-dev:cl-init again in the repository. It asks before re-initializing, keeps your knowledge base and work items, and adds any workflow that's missing without overwriting ones you have. It also rewrites .codelantern/config.json and AGENTS.md, so review the changes before you commit them.