Skip to main content
Changelog
Live

The CodeLantern platform portal is now live

By CodeLantern Team ·

The CodeLantern portal's welcome screen in a browser window: the CodeLantern wordmark over a deep blue field, the heading Welcome to CodeLantern, a line describing the managed platform, and Sign in and Learn more buttons.portal.codelantern.aiCodeLanternWelcome toCodeLanternThe CodeLantern portal is a managed platform that brings astructured, agent-driven workflow — spec, plan, implement,and review — to your GitHub project.Sign inLearn more at codelantern.ai →AGENTIC DEVELOPMENT PLATFORMCODELANTERN.AI

One destination for running CodeLantern across an organization: invite and manage the team, connect GitHub and Linear, configure the repositories and projects CodeLantern works in, and see how the work is going.

Everything an organization needs to run CodeLantern now lives at portal.codelantern.ai. Sign in with GitHub or an email address, redeem the provisioning code your CodeLantern contact issued you, and your organization exists.

You configure it once and then mostly forget it. The day-to-day work happens in your coding agent; the portal is where you go to add a teammate, connect a new repository, change how one is wired up, or check how the work is going.

What you manage there

Organization
The account everything else belongs to: its name, brand colour, and the ID support asks you for. It always keeps at least one admin.
Team
Invite teammates by email and give each one admin or member. Change a role or revoke access from the same screen.
Integrations
GitHub through the CodeLantern GitHub App, and Linear through OAuth if you plan there. GitHub can be both your project manager and your source control; Linear is project management only.
Repositories
Register each repo and point it at the provider its issues live in. Connecting a provider says it's available; this says where the work actually is.
Analytics
How the knowledge base is growing, how fast issues move through the workflow, and how the MCP tools get used, across every repository you've connected.
The CodeLantern portal's Team screen: a left navigation of Dashboard, Team, Integrations, Repositories, Analytics and Organization Settings, beside a table of six members with their role, GitHub handle, and join date.portal.codelantern.aiCCodeLanternDashboardTeamIntegrationsRepositoriesAnalyticsOrganization SettingsTeam6 membersInviteNAMEROLEGITHUBJOINEDAna Beltránana@northwind.devAdminanabeltranJun 13Marcus Chenmarcus@northwind.devAdminmchenJun 17Priya Ramanpriya@northwind.devMemberpramanJul 10Tom Okafortom@northwind.devMembertokaforJul 21Sofia Marchettisofia@northwind.devMembersmarchettiJul 28Wes Iwuwes@northwind.devMemberwiwuAug 1
The Team screen. The rail on the left is the whole account surface.

Why it’s gated

Organization signup isn’t self-service, and that’s deliberate. Provisioning codes are single-use and issued by us, so a workspace only ever appears for a team we’ve actually onboarded. Installing the GitHub App doesn’t grant CodeLantern access on its own either: the two steps are separate on purpose, and both have to happen.

Getting in

If you’re being onboarded, use the provisioning code from your CodeLantern contact to create the workspace, then connect your organization’s GitHub App installation and register the repositories you want CodeLantern working in. If you need a code, or you’re stuck partway, get in touch.

Availability

Live for CodeLantern customer organizations. Portal access and single-use provisioning codes are issued by the CodeLantern team; organization signup is not self-service.