oppie
A project-management operations CLI with a plan/apply workflow. Propose changes from natural-language prompts, review them as structured operations, then apply.
Install
oppie is distributed on PyPI. Core install:
pip install oppie
Optional features ship as extras:
| Extra | Enables |
|---|---|
oppie[linear] |
Linear ticket provider |
oppie[openai] |
OpenAI-compatible LLM backend (works with Ollama, llama.cpp, LM Studio for local models) |
oppie[anthropic] |
Anthropic Claude backend |
oppie[all] |
All of the above |
An LLM backend is required for normal use. Most users want:
pip install 'oppie[openai,linear]'
For Anthropic Claude instead of local models:
pip install 'oppie[anthropic,linear]'
Quickstart
# 1. Initialize an instance in the current directory
oppie init
# 2. (optional) View or edit config
oppie config show
# 3. Ask a question or request a plan
oppie "what's the status of the migration work?"
oppie init walks through picking an instance type (local or Linear-backed),
configuring an LLM backend, and optionally seeding context docs.
Usage example
End-to-end: ask for a plan, review it, then apply it.
$ oppie "update the priority of the auth-rewrite ticket to high"
● Classifying intent…
● Generating plan…
Plan plan-01HX… (1 operation)
- update ticket TKT-42: priority = high
$ oppie apply plan-01HX…
✓ Applied 1 operation
Plans are content-addressed and stored under the instance home; re-running with the same prompt produces the same plan id when nothing has changed.
CLI flag reference
Root flags (apply to every subcommand):
| Flag | Description |
|---|---|
--home PATH |
Override instance home auto-detection |
--debug |
Enable debug logging (also via OPPIE_LOG_LEVEL) |
--no-sync |
Skip auto-sync; use cached ticket data |
Conversational CLI (oppie "<prompt>"):
| Flag | Description |
|---|---|
--force |
Skip drift prompts when the intent resolves to an apply |
Selected subcommand flags:
| Command | Flag | Description |
|---|---|---|
oppie apply <plan_id> |
--force |
Overwrite drift without prompting |
oppie sync |
--full |
Ignore checkpoint, re-sync everything |
oppie sync |
--no-flush |
Skip flushing the outbound queue |
Run oppie --help or oppie <command> --help for the full list.
Exit codes
General contract for all commands:
| Code | Meaning |
|---|---|
0 |
Success |
1 |
Error |
oppie sync returns a more granular code so CI scripts can distinguish
retryable failures:
| Code | Meaning |
|---|---|
0 |
Success |
1 |
Generic error |
2 |
Auth error |
3 |
Rate limited |
4 |
Network error |
5 |
Provider API error |
Development
# Install dev deps (all extras)
uv sync --all-extras
# Pre-commit
uv run pre-commit run --all-files
# Tests
uv run pytest
# Lint and format
uv run ruff check .
uv run ruff format .
Metadata
Release files for oppie 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| oppie-0.3.1.tar.gz | 189.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| oppie-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 284.2 kB
Release files / oppie-0.3.1.tar.gz
| Download URL | oppie-0.3.1.tar.gz |
|---|---|
| Size | 189.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e8fbcad9d12fb04a447bebba42e5a469ed0402e115d943cb1461437a4f3d0582
|
|
BLAKE2b-256 checksum How to use checksums |
346fdba5f61aac9b7385262ea90e72a93041826c5a87206db9fe418d4c04c0d6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 19, 2026.
Transparency logRelease files / oppie-0.3.1-py3-none-any.whl
| Download URL | oppie-0.3.1-py3-none-any.whl |
|---|---|
| Size | 95.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
44987ffdb6e32707f6814c65b62c5c89dd3720f9ff37dd92a8abb484b32893d3
|
|
BLAKE2b-256 checksum How to use checksums |
bc3fb5b221ac54000c4a9d5af694dc608ebe3d8d0a76f2fca42157d133791641
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 19, 2026.
Transparency log