Closed beta · Waitlist open

Decide once.Every agent follows.

Stop maintaining separate docs for your agents.

Works with Claude Code, Codex and the Claude app

The problem

One stale doc.One wrong implementation.

Many teams build a knowledge base in Notion, Obsidian or a wiki, then wire it to their agents with CLAUDE.md rules, session hooks and skills that read and update it. Even so, the same decision ends up written in several docs across those tools, and if one of them isn't updated, the agent builds from that stale copy.

Features

How you work with UyooPack

See each feature in action in the real product.

01 · Docs

When a decision changes, no one has to update the doc by hand

An agent proposes the edit, and a teammate accepts it.

02 · Sharing

Every agent on your team works from the same requirements

Team rules are included too, so you don't have to copy CLAUDE.md into every repo and keep it in sync.

SamClaude Code
claude · ~/delivery-api
>Build the order cancellation API
uyoopack.what_applies
⎿Loaded 3 requirements to follow
Requirement2.1 An order can be canceled only until the restaurant accepts it
Linked2.2 Canceled orders are refunded right awayIncluded because it's linked to 2.1
Team ruleBlock · Never log card numbers
⏺Edit src/orders/refund.ts
⎿Blocked by a team rule · Never log card numbers
>
? for shortcuts
MayaCodex
codex · ~/delivery-app
›Build the order detail screen
uyoopack.what_applies
└Loaded 2 requirements to follow
Requirement2.1 An order can be canceled only until the restaurant accepts it
Requirement4.3 Order status is shown in five steps
I'll hide the cancel button once the restaurant accepts the order (2.1).
›
⏎ send

Neither repo has a copy of CLAUDE.md

03 · Progress

See what your team's agents are doing on one screen

Know right away when two agents are editing the same file or one is stuck waiting for an answer.

04 · Working solo

Even when you work alone, decisions don't get lost between sessions

If code changes after a task is reported done, the doc flags it.

What teams use today

Can't we just get betterat using Claude Code?

For one person in one repo, CLAUDE.md is enough.

CLAUDE.md · docs folder
What it does wellWorks well for a single repo.
Where it falls shortEvery person and every repo ends up with its own copy.
AGENTS.md
What it does wellClaude Code and Codex both read it.
Where it falls shortAnyone who doesn't work in the repo can't edit the file.
Skills · subagents
What it does wellYou can reuse the same steps to record each decision in a file, such as an ADR.
Where it falls shortThe file won't tell you if a decision was later replaced or has already been built.
Notion · Jira + MCP
What it does wellAgents read the product briefs and tickets directly.
Where it falls shortYou can't tell whether what the agent read is still current, or who changed it and when.
Autonomous agents like Devin
What it does wellYou hand over a whole job.
Where it falls shortThey don't share decisions with your teammates' Claude Code or Codex.
UyooPack
Everyone's agent reads and writes the same doc. Each decision records who made it, when, why, and whether it has been built.
FAQ

What people ask before trying it

Yes. Every time an agent gets an instruction, it first pulls the requirements and team rules for that work from UyooPack, and the first line of its reply tells you whose decision it's following and when that decision was made. Ask it to fix the order cancellation API, for example, and it receives the requirement “An order can be canceled only until the restaurant accepts it,” plus a note that Jordan made that call in the Claude app on Oct 2 and that it was implemented in PR #41. In Claude Code, a file edit that breaks a team rule is blocked before it runs. Codex and the Claude app receive the same information when they start work.

Closed beta · Waitlist

Join the waitlist

Tell us a bit about how you work today.We'll email invitations in the order people sign up.

1 / 7

How many people work on the product?

Count people, not agents.