jinion
Download
0.11.963Builder

The coding agent you steer

Your call. Its craft.

Download for macOS
~/code/api
----------------------------------------------------------------------------
Ask jinion anything · / commands · $ skills · @ files
--- Accept edits · shift+tab ----------------------------------------------
jinion · Opus 5.5 · high · code/api · ctx: 23K/200K · $0.09

  • Your project

    It writes like your team

    Jinion maps how your project is built, then reuses what’s there instead of writing it again.

    • It maps your components, hooks, tokens and habits, and keeps the map current.
    • Before it writes something new, it looks for the one you already have.
    • When a turn ends, it checks what it wrote against the map and fixes what drifted.
    How the project map works
  • ~/code/shop
    > add a pricing card to the plans page
    [x] Look in the project map: card
    '-- Card src/ui/card.tsx · used in 14 files
    [x] Look in the project map: badge
    '-- Badge src/ui/badge.tsx · used in 9 files
    [x] Write: src/plans/pricing-card.tsx +38
    Built from your Card, Badge and Button, on your tokens.
    Nothing new added to the project.
    ------------------------------------------------------------
    Ask jinion anything · / commands · $ skills · @ files
    --- Accept edits · shift+tab ------------------------------
    jinion · Opus 5.5 · high · code/api · ctx: 23K/200K · $0.09

Interface

It checks the pixels too

A passing build doesn’t mean the screen is right. Jinion opens the page, looks, and fixes what’s off.

  • First look

    It finds what’s off

    It opens the page at phone width and in the dark scheme, and looks.
    ~/code/shop
    [x] Write: src/plans/pricing-card.tsx +38
    [x] Look at the result: localhost:3000/plans
    [x] Look at the result: localhost:3000/plans
    Two things are off. At phone width the price wraps under
    the badge, and in the dark scheme the card loses its
    border.

  • Second look

    It checks again

    It fixes both, then looks once more before it calls it done.
    ~/code/shop
    [x] Edit: src/plans/pricing-card.tsx +2 -2
    [x] Look at the result: localhost:3000/plans
    [x] Look at the result: localhost:3000/plans
    Fixed both. The price stays beside the badge at 390px,
    and the border shows in dark. Checked at both widths.

Preview

Point, don’t describe

Your app beside the thread. One click, and it knows the code behind it.

shop
Search threads and files⌘K

Pricing cards

add pricing cards to the plans page

Worked for 18s 2 searches, 1 file written

The plans page now has a card per plan, built from your Card, Badge and Button. Nothing new was added to src/ui.

Price pmake this the yearly price, $260

AgentOpus 5.5
localhost:5173/plans
NorthboundShopPlansRoastery

Fresh coffee, roasted the week it ships

Change, skip or stop any time.

Taster

$14/ month

One bag a month

Choose

Regular

p Price

$26/ month

Two bags a month

Choose

Office

$79/ month

For the whole team

Choose

  • Control

    Agree on the plan first

    Think it through together. Then it builds, the way you agreed.

    • Plan mode reads and thinks. Nothing changes until you approve.
    • The plan is a document. Edit it, and it builds what you wrote.
    • Modes set how far it goes alone. Rewind takes back anything.
    Plan a big change
  • shop
    Search threads and files⌘K
    PlanWaiting for youKeep planningBuild

    Yearly pricing

    Let people pay for a year at a discount, from the plans page.

    Toggle→PlansPage→PricingCard→Price

    Steps

    1. Add a monthly and yearly toggle to PlansPage.
    2. Pass the period down to PricingCard and Price.
    3. Show yearly as ten months: two months free

    Files

    • src/plans/plans-page.jsx
    • src/plans/pricing-card.jsx
    • src/plans/price.jsx

  • Debug

    The cause before the fix

    It doesn’t guess. It gathers evidence, finds the cause, then asks before it fixes.

    • It adds diagnostics, makes the bug happen, and reads what they logged.
    • You see the cause and the proof before a line changes.
    • Type /debug and the problem. On Claude and Codex.
    Debug a problem
  • ~/code/shop
    > /debug yearly shows $312, it should be $260
    [x] Open the evidence log
    [x] Edit: src/plans/price.jsx +1 diagnostic
    [x] Look at the result: localhost:5173/plans
    [x] Read the evidence
    Cause Price takes the monthly price and multiplies it
    by 12, so the two free months never come off. The yearly
    amount PlansPage passes down is never used.
    Evidence period yearly, amount 26, shown 26 × 12 = 312.
    Shall I use the yearly amount instead?

Attachments

Give it anything

A recording, a spreadsheet, a PDF or a video. Jinion turns each into something the agent can read.

pricing-call.m4a

What was said, line by line

00:42 Let’s give two months free on yearly.

q3-orders.xlsx

Every sheet as CSV

plan,orders,revenue Regular,412,10712

supplier-terms.pdf

The text of every page

p. 3 Prices hold until 31 December.

checkout-bug.mp4

A frame each time the picture changes

0:07 The total jumps from $26 to $312.

Two ways to work

Wherever you write code

One agent, two places to work with it.

  • jinion

    For the keyboard

    Stay in your flow. One command, and it’s in your project.
    ~/code/shop
    +- jinion v0.9.907 ----------------------------------------+
    | model Opus 5.5 /model to change |
    | cwd ~/code/shop |
    | try add a yearly price, fix the checkout |
    +----------------------------------------------------------+
    > add a monthly and yearly toggle
    The toggle is in PlansPage. Yearly shows $260 with two
    months free, and I checked it at 390px.
    ------------------------------------------------------------
    Ask jinion anything · / commands · $ skills · @ files
    --- Accept edits · shift+tab ------------------------------
    jinion · Opus 5.5 · high · code/api · ctx: 23K/200K · $0.09

  • Jinion.app

    For the big picture

    Thread, plan and preview, side by side.
    shop
    Search threads and files⌘K

    Threads

    Yearly pricing

    Pricing cards

    Checkout total

    Yearly pricing

    add a monthly and yearly toggle

    Worked for 24s 3 files edited

    The toggle is in PlansPage. Yearly shows $260 with two months free.

    Ask Jinion anything

    AgentOpus 5.5

  • Teams

    One memory for the team

    Every agent on your team keeps to what was decided, and says whose call it was.

    • Agents record what was decided as they work, with why and what was turned down.
    • A decision binds once its commit is in your branch, so nobody follows half-merged work.
    • Squash and rebase merges keep them, through the GitHub App.
    • Teammates in Codex, Claude Code or Cursor read them too, through jinion mcp.
    How Jinion works for teams
  • ~/code/shop
    > make sessions expire when nobody used them
    [x] Kept to Ayşe's decision Keep sessions in Redis · Oct 3
    [x] Recorded decision Expire after 30 idle days · you asked
    [!] Also on another branch Mehmet's "Move to Postgres"
    '-- feat/sessions-pg · #42 open, touches session.ts too
    Idle sessions now end after 30 days. I kept them in Redis,
    as Ayşe decided. Mehmet’s #42 moves them to Postgres, so
    whoever merges second carries the idle check across.
    ------------------------------------------------------------
    Ask jinion anything · / commands · $ skills · @ files
    --- Accept edits · shift+tab ------------------------------
    jinion · Opus 5.5 · high · code/api · ctx: 23K/200K · $0.09

jinion mcp

Your team’s memory, in any agent

Not everyone switches at once. Teammates in Codex, Claude Code or Cursor read the same decisions with one command.

  • Codex

    Keeps to what was decided

    It reads the decisions in your branch before it changes anything, and names whose they were.
    codex
    > move sessions to sqlite
    jinion · find_decisions
    Ayşe decided on Oct 3 to keep sessions
    in Redis, so every instance reads them.
    Keep that, or replace it?

  • Claude Code

    Finds what you already have

    The project map shows what your files offer, so a second date helper never gets written.
    claude-code
    > format the dates on the invoice
    jinion · find_existing
    formatDate in lib/format.ts does this,
    and 14 files use it. Using it here too.

  • Cursor

    Records it when you ask

    Say what to keep, and it reaches the team once a commit carries it.
    cursor
    > record that we retry payments twice
    jinion · record_decision
    [x] Recorded Retry payments twice
    Teammates get it once it’s committed.

Models

Claude or Codex.
Your call.

Use the plan you already have.

  • Switch any time

    Change the model mid-conversation. The new one picks up where the last left off.
    ~/code/shop
    +- Model ------------------------------------------------------+
    | effort default low medium high xhigh max |
    +--------------------------------------------------------------+
    | Claude |
    | > 1. Opus 5.5 current |
    | Most capable, for complex work |
    | 2. Sonnet 5 |
    | Fast and capable, for everyday work |
    | Codex |
    | 3. GPT-6.1-Sol |
    | Latest workhorse model for coding and everyday work. |
    +--------------------------------------------------------------+

  • Know what’s left

    /usage shows what’s left of your plan, and what used it up.
    ~/code/shop
    +- Usage Claude -----------------------------------------------+
    | Plan limits Max |
    | 5-hour window [=---------------] 8% resets 08:11 PM |
    | Week, all models [===-------------] 20% resets Wed |
    | |
    | This session $0.42 · 3m 10s waiting on the model |
    | Opus 5.5 182K in · 9K out $0.38 |
    | Sonnet 5 21K in · 2K out $0.04 |
    | |
    | What adds to your limits last 7 days |
    | Long context [=====-----] 48% requests past 150k tokens |
    | Subagent-heavy [==--------] 21% subagents ask on their own |
    +--------------------------------------------------------------+

Questions

Before you start

The ones we hear most.

  • It maps your project so new code fits in, looks at the screens it builds, and debugs with evidence. It runs on Claude or Codex, in your terminal or as a Mac app.

Steer your next change

In private beta. Bring your plan and your invite.

Download for macOS
Read the installation guide