YOUR KNOWLEDGE
Select documents, decisions, and discussions. Add a goal. Start with the context that matters to your team.
sources → evidenceOPEN-SOURCE AGENT CONTEXT ENGINE
CONTEXT IN.
CAPABILITY
OUT.
Your agent can write code.
Give it your way of building.
Turn company knowledge into reviewed instructions, workflows, and checks. One harness. Your engineering DNA.
An animated dot matrix gathers knowledge into an italic O monogram and routes it to three coding agents.
~/olivium $
FIG. 01 — FROM KNOWLEDGE TO EXECUTION CONTEXT
NATIVE EXPORT TARGETS
⌘ Codex CLI✳ Claude Code>_ OpenCode
ONE CONTEXT LAYER. YOUR CHOICE OF AGENT.01 / THE ARCHITECTURE
TURN WHAT YOU KNOW
INTO HOW IT WORKS.
A harness is the context around your coding agent: instructions to follow, workflows to use, and checks to perform.
YOUR JUDGMENT
Inspect citations. Edit recommendations. Resolve conflicts. Approve the exact guidance and package plan.
proposal → approvalYOUR HARNESS
Build a versioned package for your agent’s native format. Keep the connection between the guidance and its source.
context → capabilityINPUT ADAPTERS /
Markdown & text · GitHub · GitHub Projects · Jira Cloud · Slack · Confluence Cloud
02 / INSIDE THE PIPELINE
TRACE THE INPUT.
OWN THE OUTPUT.
Step through an example. Two team documents. One goal. Guidance your team can review.
03 / OPEN BY DESIGN
YOUR CONTEXT.
YOUR MACHINE.
YOUR RULES.
Open source under Apache 2.0. A local-first application with human review at its core. Inspect how guidance is built, keep control of your inputs, and choose your model provider.
Cloud AI is optional. You decide when selected context leaves your machine, with consent and spending controls.
# Built for ownership. license Apache-2.0 runtime local-first decisions human-approved provenance preserved # Bring your preferred agent. exports ├── Codex CLI ├── Claude Code └── OpenCode # Your standards become the context. $
04 / THE DETAILS
READ THE MANUAL.
The things worth knowing before you build.
01 Is this another coding agent?
Olivium Harness builds the instructions, workflows, and checks around your agent. It exports native packages for Codex CLI, Claude Code, and OpenCode, so your team’s context can travel into the tools you use.
02 What can I use as context?
Selected Markdown or text documents; GitHub metadata, issues, pull-request descriptions and reviews; GitHub Projects; Jira Cloud issues; Slack threads; and Confluence Cloud pages. GitHub imports do not currently ingest repository source files. Current cross-source analysis uses two to four selected documents and one saved goal.
03 Who approves the instructions?
You do. Recommendations include supporting evidence for review. You can edit, reject, and resolve conflicts before approving an exact revision. The package plan requires a separate approval before the harness is built.
04 Does local-first mean no cloud AI?
Cloud AI is optional. If you choose a cloud model provider, selected context can leave your machine with your consent. Provider access and spending are controlled explicitly.
05 What is the project’s current status?
Olivium Harness is an open-source tool under Apache 2.0, in active development. The landing-page implementation is proprietary and its source repository is private. The application is a separate project with its own licensing and currently requires repository permission. A public product release is not yet available. The animations on this page are illustrative. Export support is separate from validation of an agent’s live runtime.
OLIVIUM / HARNESS
BACK TO TOP ↑YOUR CONTEXT.
YOUR CONTROL.
Make your engineering knowledge
part of the way your agents work.