Ϙ qor harness
Strap In!
Version 0.1.0 · 2026-11-15
qor harness (pronounced “core harness”) is a keyboard-first agent harness for working with projects from your terminal. It connects to an OpenAI-compatible model endpoint and gives the model tools to read and edit files and run commands.
Use the interactive terminal interface for a conversation, or run a single prompt from the command line. qor can also work in chat-only mode without workspace tools.
Requirements
- Python 3.12 or newer.
- An accessible OpenAI-compatible streaming chat endpoint and a model available on that endpoint. qor does not download models or install a model server.
- A terminal for interactive setup and the terminal interface.
Install
From an unpacked source distribution, use uv or pipx:
uv tool install .
# or: pipx install .
You can also install into an active virtual environment with pip install ..
The PyPI distribution is not yet published.
To install a built wheel directly, run pipx install /path/to/qor_harness-0.1.0-py3-none-any.whl.
Get started
Start in the project directory:
qor
If no model is configured, qor guides you through registering models from an endpoint and choosing a default. To use an already installed Ollama model without guided setup, for example:
qor --model gpt-oss:20b
Replace the model name with one available on your server. The default API root
is http://127.0.0.1:11434/v1; use --base-url to choose another endpoint.
Run qor models to list registered models, or qor models add to discover
models from an endpoint. qor does not automatically import another tool's
settings or credentials.
By default, the workspace is the directory where you start qor. Use
--workspace /path/to/project to choose another directory. In coding mode,
qor loads the workspace-root AGENTS.md, if present, as project guidance.
Tools and safety
Trusted mode is the default. The model can read and edit files and run shell commands without routine approval. Commands run with your OS permissions; Bash is not sandboxed. Run qor only with models, endpoints and projects you trust.
- Start with
qor --reviewto review edits and commands before they run in the terminal interface. - Start with
qor --chatfor chat-only mode without workspace tools. - Use
/chatand/codingwhile idle to switch modes without losing the conversation.
Review mode does not approve operations in headless runs: operations that need approval are denied instead.
In the terminal
Type a message and press Enter. Use Alt+Enter or Ctrl+J for a newline. Type /
to see local commands. A few useful ones:
| Command | Action |
|---|---|
/help |
Show keys and commands. |
/model |
Choose a registered model. |
/providers |
Manage providers and discover models. |
/new |
Start a new session. |
/resume |
Continue a saved session for this workspace. |
/compact |
Summarise older conversation history. |
/quit |
Exit qor. |
Use Ctrl+C to cancel a run. During a run, you can send another message to steer the next response after the current tool batch.
Run one prompt
Configure a model first using the terminal interface or qor models add. Then:
qor --chat run "Explain this project"
qor --workspace /path/to/project run --jsonl "Inspect the failing test"
Without --jsonl, a headless run prints the final reply. With it, qor streams
runtime events as JSON lines. Put shared options such as --chat, --review
and --workspace before run; put --jsonl after it. Run qor --help and
qor run --help for the available options.
The source distribution also includes model setup and headless guides in release/docs/.
Sessions and context
qor stores settings and model registrations under
${XDG_CONFIG_HOME:-$HOME/.config}/qor/ and session journals under
${XDG_STATE_HOME:-$HOME/.local/state}/qor/sessions/. Original journal entries
remain when older conversation history is compacted. Set an accurate model
context window with /model edit to use automatic compaction effectively.
A resumed session restores completed runs; an interrupted run does not rerun its tools. Chat or coding mode is not saved with a session.
License
Apache License 2.0.
Copyright © 2026 Gunnar Leffler.
Metadata
Release files for qor-harness 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| qor_harness-0.1.0.tar.gz | 102.8 kB | Without provenance | Details for qor_harness-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qor_harness-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for qor_harness-0.1.0-py3-none-any.whl |
Total release size: 223.1 kB
Release files / qor_harness-0.1.0.tar.gz
| Download URL | qor_harness-0.1.0.tar.gz |
|---|---|
| Size | 102.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7e3f6f0837d9696aa2bf6ca37734d67161008231c948b4eb9698122752d865fc
|
|
BLAKE2b-256 checksum How to use checksums |
8f0488cd9ffea840130d2b897e2235f924a0d1abd822172ef08705bfaf49ad69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.10
|
Release files / qor_harness-0.1.0-py3-none-any.whl
| Download URL | qor_harness-0.1.0-py3-none-any.whl |
|---|---|
| Size | 120.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9ace3f7a70513a9681a428a5809c426448617c227adcb5a1b347fc9b11b08f2b
|
|
BLAKE2b-256 checksum How to use checksums |
0e68ec2ea29cddc26151d3b22fe7a3efd2d80e456a741cf4991e01f0ead41597
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.10
|
Security for qor-harness 0.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.