Shared workflows and project knowledge
By CodeLantern Team ·
The cloud agent runs in GitHub Actions without personal access tokens, and finalized pull requests show what the work added to the knowledge base and what it left uncaptured.
Run the cloud agent without personal access tokens
Mention @codelantern-ai with a command on a GitHub issue or pull request, and the run happens in your repository’s own GitHub Actions. It no longer needs personal access tokens. Copilot inference uses your organization’s GitHub Copilot access in Actions, and the plugin arrives through CodeLantern’s authenticated distribution, so there are no tokens or secrets to create or rotate.
The cloud agent works with GitHub repositories that track their issues in GitHub. It also needs the CodeLantern GitHub App on the repository, an active repository configuration, Copilot allowed in GitHub Actions, and the dispatch workflow on your default branch. The cloud agent guide covers each prerequisite and how to turn it on.
See what each pull request added to the knowledge base
When /cl-dev:finalize marks a pull request ready for review, its description lists the knowledge-base entries the work captured, each linked. It also lists suggestions skills surfaced along the way that were not captured, with the reason recorded at the time where there is one.
Reviewers see what was proposed and what landed before they merge. The finalize reference describes the section.
Retry failed webhook deliveries#142
Pull request description · GitHub
Knowledge base updates
Captured
| Type | Summary |
|---|---|
| learning | Retry webhook deliveries with backoff: space out retries when a service is unavailable. |
| convention | Name queues by domain: keep billing and notification work easy to identify. |
Surfaced but not captured
| Type | Summary | Reason |
|---|---|---|
| adr | Split the billing worker | Deferred to a follow-up issue. |
Improvements (6)
- PortalAzure DevOps. Knowledge-base sync for Azure Repos completes Azure DevOps support. Each push to the default branch syncs the repository’s knowledge base through a Service Hook that CodeLantern registers when an admin adds the repository, with no pipeline to maintain. Sync is one-way and leaves work-item files in your repository. The admin needs an active Azure DevOps connection and permission to manage Service Hooks. See Knowledge Base Sync.
- Plugincl-init. Workflow and script files are copied from the plugin’s bundled templates, so scaffolding is fast and identical on Windows, macOS, and Linux.
- Plugincl-init. Existing files are never overwritten. Each one is reported as created, skipped, or conflicting, and cl-init stops with a clear message when it can’t finish.
- PortalConnected accounts. The portal and provider authorization errors tell members when they still need to connect their own provider accounts.
- DocsOnboarding. The Admin Setup and Developer Setup guides cover the public CLI, preparing the knowledge base, and repository automation.
- PluginADRs. Decision records are referenced by number and title, and doctor lists any duplicate ADR numbers.
Fixes (2)
- PluginHandoff. Comments posted by /cl-dev:handoff start the cloud agent. They were previously ignored because CodeLantern posted them on your behalf.
- Plugincl-init. The init skill is now cl-init, so GitHub Copilot’s built-in /init no longer hides it. Doctor flags old references in AGENTS.md.
Availability
Live for CodeLantern customer organizations. The cloud agent needs a GitHub repository with GitHub issues, the CodeLantern GitHub App, Copilot allowed in GitHub Actions, and the dispatch workflow on the default branch.