Configuration

This page covers the settings available under Configuration in the IssuePit UI.

API Keys

API Keys configuration page

API keys let IssuePit authenticate with external services such as GitHub, AI providers, and cloud platforms.

  1. Go to Configuration → API Keys.
  2. Click Add Key.

  3. Select the Provider:

    Provider Used for
    GitHub Importing issues, creating branches/PRs
    GitLab Same as GitHub, but for GitLab
    Jira Importing issues from a Jira project (see Jira Sync)
    OpenAI AI agent completions (GPT-4, o3, etc.)
    Anthropic AI agent completions (Claude models)
    Azure OpenAI Azure-hosted OpenAI models
    Google Gemini models
    Hetzner Provisioning cloud VMs for agent runtimes
  4. Enter the Key Value (the secret token from the provider).
  5. Click Save.

Tip: GitHub tokens need at minimum repo scope to import issues and create branches.

Agent Runtimes

Agent runtimes define where and how agent containers are executed.

  1. Go to Configuration → Agent Runtimes.
  2. Click New Runtime.
  3. Choose the Type:
    • Docker / Podman — local container runtime
    • SSH — remote machine via SSH
    • Hetzner — auto-provisioned Hetzner VM
    • OpenSandbox — sandbox environment
  4. Fill in the connection details (host, credentials, image registry, etc.).
  5. Click Save.

MCP Servers

MCP (Model Context Protocol) servers extend agents with external tools and data sources.

  1. Go to Configuration → MCP Servers.
  2. Click Add Server.
  3. Fill in:
    • Name — display name (e.g. GitHub MCP)
    • URL — the MCP server endpoint (e.g. https://mcp.example.com)
    • Configuration — optional JSON configuration passed to the server
  4. Click Save.

After adding a server, you can link it to specific agents in the agent settings.

Telegram Bots

IssuePit can send notifications about issue events and agent run results to Telegram.

  1. Go to Configuration → Telegram Bots.
  2. Click Add Bot.
  3. Fill in:
    • Name — display name for this bot configuration
    • Bot Token — the token obtained from @BotFather
    • Chat ID — the Telegram chat or channel ID where notifications are sent
  4. Optionally select which notification events to receive (issue assigned, agent failed, CI/CD failed, etc.) and set rate limiting or silent mode to reduce notification noise.
  5. Click Save.

Once configured, IssuePit dispatches notifications whenever the selected events occur.

Telegram Setup (Pairing)

The Telegram Setup wizard lets you link a Telegram chat or group directly to an IssuePit org or project. Paired chats support interactive bot commands (/newissue, /newtodo, voice messages) in addition to notifications.

Pairing flow

  1. Open Telegram, find your bot, and send /start or /pair.
  2. The bot replies with a 6-character pairing code (e.g. ABCD34), valid for 15 minutes.
  3. Go to Configuration → Telegram Setup in IssuePit.
  4. Enter the code in the Link a Chat form. Select a scope:
    • Personal — linked to your user account
    • Organization — linked to a specific org
    • Project — linked to a specific project (enables /newissue commands)
  5. Paste your Bot Token and click Link Chat.

Bot commands (in paired chats)

Command Description
/start or /pair Generate a new pairing code
/newissue <title> Create an issue in the paired project
/newtodo <title> Create a to-do item
Voice message Transcribe and create an issue (requires Vosk model)

Managing paired chats

Go to Configuration → Telegram Setup to see all paired chats. Click Unpair to remove a chat from IssuePit.

Voice Input

IssuePit supports creating issues via voice using Vosk for offline speech recognition.

When voice input is enabled, a microphone icon appears on the issue creation form. Click it to start recording — spoken text is transcribed and inserted into the issue title and description fields automatically.

To enable voice recognition, the Vosk model must be available to the API service. Set the path via the Vosk__ModelPath environment variable in your docker-compose.yml:

environment:
  Vosk__ModelPath: /models/vosk-model-small-en-us-0.15
volumes:
  - ./models:/models:ro

Download a Vosk model from alphacephei.com/vosk/models and place it at the configured path.

Settings

The Settings page (gear icon at the bottom of the sidebar) shows:

  • Backend API URL — the URL the frontend uses to reach the API. Set via the NUXT_PUBLIC_API_BASE environment variable.
  • Appearance — theme picker (see below).

Themes

IssuePit ships with five built-in themes that can be selected on the Settings → Appearance page.

Theme Description
Dark Classic dark theme (default)
Dim Softer, cooler dark theme inspired by GitHub’s dim mode
Dark Accent Dark background with a vibrant purple accent colour
Dark Square Same dark palette but with sharp, square edges throughout the UI
Light Light theme for bright environments

Priority chain

The active theme is resolved in this order (highest priority first):

  1. ?theme= query-string parameter — e.g. https://app.example.com/?theme=light. Useful for screenshot automation and shareable links.
  2. Browser-local override — stored in localStorage under the key issuepit-theme. Applies only to the current device/browser without touching your profile.
  3. Profile preference — saved to your account in the database. Applied on all devices where you log in.
  4. OS / system default — prefers-color-scheme media query (light or dark).

Changing your theme

  1. Open Settings (gear icon in the sidebar).
  2. Under Appearance, click any theme card to preview and activate it.
  3. Toggle Save to profile to decide whether the choice is persisted to your account or kept as a browser-only override.
  4. To clear a browser override, click Clear override below the theme cards.

IssuePit — Agent Orchestration Platform

This site uses Just the Docs, a documentation theme for Jekyll.