Integrations

An integration is a connection between your organization and a provider — GitHub, Azure DevOps, or Linear. Integrations are what let CodeLantern skills work with your real project data: reading and writing issues, opening and updating pull requests, and touching your source. You set them up once, in the portal, and every member of your organization works through them.

CodeLantern draws a line between two jobs a provider can do:

• Project manager (PM) is where your work items live: issues, backlog, and the board you plan against.
• Source control (SCM) is where your code lives: branches, commits, and pull requests.

GitHub and Azure DevOps can each do both. Linear does PM only, paired with a provider that handles your source. You connect at least one provider that covers both jobs — GitHub or Azure DevOps — and can add others per repository.

Connect GitHub

GitHub connects through the CodeLantern GitHub App. Installing the app grants CodeLantern scoped access to the repositories you choose, so skills can act on your behalf without you handing over personal credentials.

Once GitHub is connected, it can serve as both your project manager and your source control. This is the simplest setup, and a good default if all your work already lives in GitHub Issues and pull requests.

Connect Azure DevOps

If your team works in Azure DevOps Services, connect it to run the full workflow against Azure Boards (PM) and Azure Repos (SCM). Like GitHub, Azure DevOps can act as both your project manager and your source control, or as just one side — configured per repository.

Azure DevOps connects through Microsoft Entra delegated OAuth:

• An organization admin connects an Azure DevOps organization from the portal's Integrations page and authorizes CodeLantern through Microsoft Entra. One integration represents one Azure DevOps organization and is reused across its projects.
• Each member who runs Azure DevOps operations connects their own Microsoft identity the same way — actions are attributed to the person who ran them, and a member who hasn't connected is told to authorize before any change is made.

Required permission. To keep issue metadata in sync, CodeLantern registers a project-scoped Service Hook on your Azure Boards project. Registering it requires the connecting account to be a Project Administrator on that project (the permission Azure requires to manage Service Hook subscriptions). Without it, repositories still work and metadata still enriches on first use — only the continuous background sync is skipped, with a notice on the repository.

Azure DevOps parity notes

Azure DevOps maps cleanly onto CodeLantern's provider-neutral model, with two label differences worth knowing:

• Tags stand in for labels, without color or description. Azure work-item tags carry a name only, so the GitHub-style label color and description are ignored.
• A tag name can't contain ; or ,. Azure reserves those characters as tag delimiters, so CodeLantern rejects a label containing them (with an actionable note) rather than letting one label silently split into several. Every other name applies as-is and materializes the first time it's used — no pre-registration.

Connect Linear (optional)

If your team plans and tracks work in Linear, connect it as your project manager. Linear connects via OAuth: you authorize CodeLantern from the portal, and the connection is scoped to your Linear workspace.

Linear is PM-only. Your issues and planning live in Linear, but source control stays on a full SCM provider (GitHub or Azure Repos), so a Linear setup always keeps one of those connected too. Skills read and write your Linear issues while opening and updating pull requests in your SCM provider.

Next steps