Roadmap | Proposals

Big ideas, shown first.

Before a big idea gets built, Yui draws it as a working mockup and writes it up the same way every time. You weigh in. Chris decides.

Open for votesPROP-11

Receipts

Every action a tap starts leaves one receipt, what the agent meant, what it actually did and what came back, so you can see what happened, not what was intended.

Cost MBy ChrisCounting
Open for votesPROP-10

Not sure is an answer

When a step times out after it may have acted, Yui says "not sure, checking" and finds out, instead of retrying and doing it twice.

Cost SBy ChrisCounting
Open for votesPROP-9

Checked when it's saved

Stop, a revoked share and a withdrawn yes are checked at the moment work is saved, not when it started, so nothing lands after you said no.

Cost MBy ChrisCounting
Open for votesPROP-8

Fresh asks

An ask that has waited shows its age and what changed before you tap, so an old yes is never mistaken for a new one.

Cost MBy ChrisCounting
Open for votesPROP-7

Yui: The GUI for You

An ad campaign on one line. Every spot shows a wall of text turning into the one screen you needed, and ends on "Yui. The GUI for you."

Cost MBy ChrisCounting
Open for votesPROP-6

Yui says I

The site and the app speak as Yui, in the first person, where it fits. Sparing with the word I, never a sentence pile-up of it.

Cost SBy ChrisCounting
ExploringPROP-5

Earn $U by using Yui

$U trickles in as you use Yui, a little with every message, tap and finished job, faster on a streak, and much faster when you help build it. One day you might spend it in Yui, own part of Yui with it, or both. Today it is a number you watch go up.

Cost MBy ChrisCounting
ExploringPROP-4

A first plan in every agent

The first time you open an agent, it asks a few taps and builds your first plan. Arnold is the worked example.

Cost MBy ChrisCounting
Open for votesPROP-3

What Stop stops

When you tap Stop, does it stop everything the agent queued, or only the reply you are watching?

Cost MBy ChrisCounting
Open for votesPROP-2

The Jev layer

One fast Jev call on every turn picks the shape of the reply, so the agent writes into it.

Cost LBy ChrisCounting
ExploringPROP-1

Pick your crew

A new user picks which agents join, instead of getting all six at once.

Cost MBy ChrisCounting

How proposals work

A proposal is a big idea for Yui, shown before any app code. Yui draws it as a working web mockup, writes it up the same way every time, and people weigh in. Chris decides. Votes inform.

The life of a proposal

  1. Exploring. Yui writes it up and builds the mockup. Nothing is promised yet.
  2. Open for votes. The page is done and anyone can say Yes, build it or Not yet.
  3. Accepted. Chris said yes. It becomes a card or an epic on the roadmap.
  4. Building. The card is in a lane on the board.
  5. Shipped. It is in a TestFlight build. The page links the release.
  6. Not now. Chris said no, or not yet. The page stays up with the reason.

Every proposal has

  • An id, PROP-1, PROP-2 and on. It never changes.
  • A title and one line that says what it is.
  • A status, one of the six above, and a date.
  • What it would become: the card or epic it turns into once accepted.
  • A mockup at the top of its page: the idea working in a phone, tappable.

Credits and trail

Optional lines in the file's header. Empty ones don't show. The page prints them as "Credits and trail"; the index shows "by" and "taken by".

  • by: who proposed it (Chris, Yui, a visitor, an agent). by_url links them when they are public.
  • sources: the posts or threads that sparked it, name | url ; name | url. The url is optional.
  • taken_by: who picked it up once accepted (a person, a Yui worker, an outside agent).
  • card, branch, pr: filled when it moves to Building. branch and pr are GitHub urls. release is filled when it ships.

The board sync fills taken_by, card, branch and pr on its own: a card or a pull request titled with [PROP-N] links itself, the same way claims work on /contribute. A line already in the file is never overwritten.

Credit is opt-in for people outside the team. A public Moltbook or GitHub handle can be named as a source; a private person never is. An unknown field or a bad url stops the sync, and the public guard still runs.

Every assessment asks the same things

The same fields, in the same order, so two ideas are easy to weigh side by side.

  • The problem. What is wrong or missing today.
  • Who it is for. The person it helps, in one line.
  • How it works. The idea, step by step, short.
  • Pros. What gets better.
  • Cons. What gets worse or harder.
  • Cost. S (a day or two), M (about a week), L (more than a week, or a platform bet).
  • Risks. What could go wrong, and what we would watch.
  • Open questions. What is not decided yet.
  • Yui's call. Recommend or not, and one line why.

Where they live

One file per proposal in docs/proposals/, synced to yuigui.com/proposals on every deploy. A file missing a field stops the deploy, so every page reads the same.

Try Yui, or help build it

Get the alpha

The MVP is done and Yui is in alpha, open to anyone with an iPhone on iOS 26. Download it on TestFlight, then connect the agent you already run: Hermes, OpenClaw, Claude Code, a model you run, or anything behind a webhook.

Star it on GitHub

Yui is open source under Apache 2.0. Star the repo, open an issue, or send a pull request.

Lend your agent

Spare tokens on Claude or ChatGPT Codex? Your agent can pick a card off our backlog and open a pull request. Yui@home, like SETI@home.

Want a hand getting in?

You don't need this to try Yui: the alpha on TestFlight is open to anyone with an iPhone on iOS 26. Leave your details if you have no agent yet, want help connecting one, or would rather Apple email you the invite.

  1. Yui emails you a link to confirm your address.
  2. We read your request, and reach out if you asked for help.
  3. Apple emails you a TestFlight invite.
  4. Open it on your iPhone, install Yui, and sign in with Apple.

We use this only to get you into Yui. Privacy.