Plannix Bot sign-in
Overview
To enable Plannix Bot to act on behalf of your workspace, you must complete the one-time authentication and permission pairing flow.
Linking your Plannix account to Bot
Connecting your developer identity ensures that bot actions inherit your subscription’s fast compute queue and shared token pool:
Open Integrations
Navigate to Integrations > Bot Auth in the Plannix Console.
Link Plannix Identity
Click Link Plannix Identity and select your active billing workspace.
Authorize Application
Confirm requested OAuth scopes to enable automatic review webhooks.
Required OAuth scopes and permissions
Plannix Bot strictly requests the minimal permissions required to provide code insights:
| Scope | Classification | Rationale |
|---|---|---|
pull_requests:read | Read | Examine PR diffs and changed lines of code |
pull_requests:write | Write | Submit inline review comments and fix suggestions |
statuses:write | Write | Update commit check statuses (Pass / Warning / Fail) |
Service tokens for CI/CD runners
For automated pipelines without interactive user logins, create a headless Bot Service Token:
| Environment Variable | Description | Default Setting |
|---|---|---|
PLANNIX_BOT_TOKEN | Service authentication bearer token | Required |
PLANNIX_MODEL | Target reasoning model (e.g. plannix-coder-pro) | plannix-4.5-fast |
PLANNIX_STRICT_MODE | Fails PR checks on severe lint or security findings | true |
GitHub Actions workflow example
Add this configuration to .github/workflows/plannix.yml:
name: "Plannix Autonomous Code Review"
on: [pull_request]
jobs:
review:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Run Plannix Bot Review
uses: plannix-ai/bot-action@v2
with:
token: "${{ secrets.PLANNIX_BOT_TOKEN }}"
model: "plannix-coder-pro"Revoking and rotating bot tokens
If a token is inadvertently exposed or a team member leaves, admins can immediately invalidate the token under Security > Bot Credentials with zero downtime for other connected services.