Everything you need to get Knight running.
Go to knight.tech and click "Get Started". Sign in with Google or create an account with email and password. You'll be taken to the onboarding page where you pick a tier:
Solo ($99/mo): 1 concurrent agent. Team ($249/mo): 3 concurrent agents. Scale ($499/mo): 10 concurrent agents.
Select a tier, agree to the Terms of Service, and complete checkout with Stripe. Once payment is confirmed, you'll be redirected to the Settings page. This is where you'll do the rest of your setup.
Everything you need to configure is on the Settings page at knight.tech/settings. You'll see two tabs: "Connections" and "Account".
The "Connections" tab has a graph showing your integration status. Each node in the graph represents a service: your Anthropic API key at the top, git providers (GitHub, GitLab) on the left, and work sources (Jira, Linear, Slack) on the right.
Grey nodes are disconnected. Green nodes are connected. The graph shows "Operational" when you have all three requirements met: an API key, at least one git provider, and at least one work source.
To connect or disconnect a service, click its node in the graph. Clicking a grey node starts the connection flow. Clicking a green node lets you disconnect. The graph is your control panel.
Knight uses Claude to write code. You provide your own Anthropic API key. Knight charges only a platform fee, not AI usage.
Get a key at https://console.anthropic.com/settings/keys. Copy it.
On the Settings page, scroll down below the graph to the "Anthropic API Key" section. Paste your key (starts with sk-ant-) and click "Save Key". Knight validates the key with a test API call before saving. If the key is invalid, you'll see an error.
You can update or remove your key anytime from this same section.
Click the "GitHub" or "GitLab" node in the graph to connect. You need at least one.
Clicking the node takes you to GitHub to install the Knight Dev Agent app on your organization. Choose which repos Knight can access. You can grant all repos or select specific ones. A GitHub Organization owner or account owner must approve the installation. Once approved, you're redirected back to Settings and the node turns green. Knight creates commits and PRs as "Knight Dev Agent" (a bot identity, not a human account).
Clicking the node takes you to GitLab to authorize Knight via OAuth. Grant the requested permissions (api, read_user, read_repository, write_repository). Once authorized, you're redirected back and the node turns green. Knight creates Merge Requests under the GitLab account you authorized with. You can use a dedicated service account if you prefer.
You can connect both if your team uses both platforms. Knight detects which provider to use from the repository URL on each work item.
Click the "Jira", "Linear", or "Slack" node in the graph to connect. You need at least one. This is how Knight receives work.
Clicking the Jira node takes you to Atlassian to authorize Knight via OAuth. Sign in as the account you want Knight to act as. All comments and status transitions will appear under this account. You can use a dedicated Jira service account. After OAuth, you'll be prompted to install the Knight Forge app for event delivery. The Forge app uses Atlassian's internal event system for reliable delivery across all project types (team-managed and company-managed). The connecting account must have access to all projects where Knight will be used. No manual webhook setup required. You're redirected back and the node turns green.
Clicking the node takes you to Linear to install Knight as an agent in your workspace. A workspace admin must approve. Once installed, Knight appears as a delegatable agent in your Linear workspace. No webhooks to configure, no custom fields required.
Clicking the node takes you to Slack to install the Knight bot in your workspace. Once installed, you can open a DM with the Knight bot and click "Request Work" to submit tasks directly. Each Knight organization must use a dedicated Slack workspace.
You can connect multiple work sources. Many teams use Jira or Linear for planned work and Slack for quick ad-hoc requests.
Knight needs to know which repository to work in for each issue. This works differently depending on your work source.
Include "Repository: https://github.com/your-org/your-repo" or "Repo: https://github.com/your-org/your-repo" anywhere in the issue description. Knight parses the URL automatically. Alternatively, you can create a URL-type custom field called "Repository" in Jira — Knight checks the custom field first, then falls back to the description. Either approach works. Knight refuses to process issues without a repo URL.
Include "Repository: https://github.com/your-org/your-repo" or "Repo: https://github.com/your-org/your-repo" in the issue description. Knight parses it automatically. No custom fields or admin setup needed.
When you click "Request Work" in the Knight bot DM, a form pops up with a "Repository URL" field. Enter the repo URL there. No setup needed.
Your graph should now show "Operational" (green badge). You're ready to go.
Create a Jira issue. Include "Repository: https://github.com/your-org/your-repo" in the description (or use the custom field if configured). Assign the issue to the Jira account you connected Knight with. Knight picks it up automatically, clones the repo, writes the code, opens a PR, and polls CI. Watch the Jira comments for live progress updates.
Create a Linear issue. Include "Repository: https://github.com/your-org/your-repo" in the description. Assign the issue to a team member, then delegate it to Knight (Knight appears in the delegate dropdown). Knight picks it up, writes the code, opens a PR, and posts progress updates as Linear comments.
Open a DM with the Knight bot. Click "Request Work". Enter the repo URL and describe what you need. Knight enqueues the request and sends you DM updates as it works.
If Knight can't proceed without more information, it asks in the same channel the work came from: a Jira comment, a Linear comment, or a Slack DM. Update the issue with more detail and reassign or re-delegate.