Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/onenot8/issueLoop/llms.txt

Use this file to discover all available pages before exploring further.

IssueLoop is distributed on PyPI and requires Python 3.10 or later. The core package has no mandatory external services — it runs entirely on your local machine with a SQLite database and a local Ollama instance. The only optional dependency that requires network setup is the Supabase backend, which is gated behind a separate install extra.
Python 3.10, 3.11, 3.12, and 3.13 are all supported and tested in CI.

​
Install options

pip install issueloop
The standard install is all you need for the local SQLite backend and Ollama-based LLM triage. Install issueloop[supabase] only if you intend to use a hosted Supabase database as the ticket store.

​
Dependencies

​
Core dependencies

These are installed automatically with every pip install issueloop.
PackageWhy it’s needed
requestsMakes HTTP calls to Ollama, Anthropic, OpenAI, and the optional notification webhook.
pyyamlReads config/permission.yaml and config/provider_config.yaml for the fix-apply permission system.
pathspecApplies .gitignore-style patterns when scanning a repository’s file inventory.

​
Optional dependencies

These are only installed when you request the [supabase] extra.
PackageWhy it’s needed
supabasePython client for the Supabase REST API, used when database="supabase" is set in issueloop.use().
python-dotenvLoads SUPABASE_URL and SUPABASE_KEY from a .env file when the Supabase backend is active.
If you call issueloop.use(database="supabase") without having installed the [supabase] extra, IssueLoop will raise an import error at runtime. Install issueloop[supabase] first.

​
Environment setup for Supabase

When using the Supabase backend, IssueLoop needs two environment variables to connect to your project.
VariableDescription
SUPABASE_URLThe base URL of your Supabase project, e.g. https://your-project.supabase.co.
SUPABASE_KEYYour project’s service-role or anon key.
Create a .env file in your project root (or export these variables in your shell / CI environment):
.env
SUPABASE_URL=https://your-project.supabase.co
SUPABASE_KEY=your-service-role-or-anon-key
python-dotenv (included in the [supabase] extra) will load this file automatically when the Supabase backend initialises.
The .env file is only read when the Supabase backend is active. The local SQLite backend requires no environment variables at all.

​
Verify installation

After installing, run the built-in environment check to confirm that Ollama is reachable, the required models are present, and any configured environment variables are set correctly: 
issueloop check-env
This command reports the status of:
  • The Ollama server and whether the default model (qwen2.5-coder:7b) is available
  • Any configured cloud LLM providers and their API key presence
  • SUPABASE_URL and SUPABASE_KEY, if database="supabase" is set in your issueloop.use() call
A clean output looks like: 
[PASS] ollama binary on PATH
[PASS] ollama server responding
[PASS] model pulled: qwen2.5-coder:7b

ALL BLOCKING CHECKS PASSED
If check-env reports that Ollama is not reachable, make sure the Ollama application is running. You can download it from ollama.com and pull the default model with ollama pull qwen2.5-coder:7b.

Build docs developers (and LLMs) love

Get started for freeTalk to us