For teams already running an AI-agent operating system
The board your AI agent was already keeping.
kenovislabs turns the company-os/ files your coding agent writes as it works — roadmap, decisions, findings — into a real, structured board. Not a JIRA sync. Not a wiki nobody opens. The same source of truth, finally legible to the human running the product.
Paid from day one — no free tier, no bait-and-switch.
## DECISION-090 Promote development → preproduction → main. Critical Next.js RCE fix, founder-authorized in-session. Status: Executed Owner: founder
Decision 090 — Promote to production
Executed · founder
Decision 089 — Subscription exemption
Executed · founder
Two views of the same files
kenovislabs is not a second tool bolted onto your AI agent. It is a second, human-shaped view of the exact files the agent already maintains.
Already in your repo
The framework layer your agent reads from — commands, workflows, agent definitions, policies — is served at runtime to your account. Only your own company-os/ lives in your repository: roadmap, decisions, domain rules, findings. Nothing about how your agent works today changes.
Now visible at kenovislabs.com
Connect a repo and its roadmap, decisions and findings render as a real board immediately — read straight from GitHub, not re-typed. From there, one CLI command (kenovislabs sync) keeps it caught up. No export step, no dashboard data entry.
How it works
Your agent already writes it
As Claude Code (or your agent of choice) works your repo, it records roadmap items, decisions and findings as plain markdown under company-os/. Nothing new to adopt — this already happens today.
Connect the repo
Sign in with GitHub and install the kenovislabs app on the repository that already has a company-os/ directory. Nothing is copied out of your repo to do it.
Get a board, not a copy
The moment the repo connects, kenovislabs reads company-os/ straight from GitHub and the board is already populated — no manual entry. Run kenovislabs sync (already part of the CLI) whenever you want the board caught up to your latest commit.
Not a JIRA integration. A replacement.
A JIRA sync is still a second source of truth to keep honest. kenovislabs has one source of truth — the files your agent already writes — and two ways to read it: the agent's, and yours.
See your own roadmap rendered.
Paid from day one — no free tier, no bait-and-switch.