Cuukit Loncaagentic development environment

From Jira issue
to merge-ready PR.

Lonca gathers the context, sets up an isolated worktree, runs your coding agents and checks their work against the issue's acceptance criteria — with you at the keyboard, or on its own when you hand the task off. Merging stays yours.

Download for Mac see how it works ↓

version 6.0.0 · 233 MB · Apple silicon · macOS 12+
signed and notarized by Apple · updates itself · no Cuukit account
sha256 6e454b7f3563f4368cb3cffa072aadc51b9257ff40034121a033c9706be42d15

SALES-412 Partial refunds on orders planningimplementingtestingin reviewPR #482 open

SALES-397 Currency in minor units asks you

SALES-388 Order search filters PR #477 · CI ✓

SALES-371 Webhook retries merged

planimplementtestreviewPR

implementer · worktree feature/SALES-412-partial-refunds › AC-1 a refund can cover part of an order read src/orders/refund.ts edit src/orders/refund.spec.ts +38 test pnpm test refund.spec ~~1 failed~~ edit src/orders/refund.ts +24 −9 test pnpm test refund.spec 12 passed git commit "Refund part of an order" › AC-2 the ledger shows each partial refund edit src/ledger/entries.ts +17 −3 test pnpm test ledger 31 passed git commit "Ledger lists partial refunds" tester · e2e scenarios on localhost:4312 refund-half-order passed 3.1s refund-twice passed 4.4s ac.md AC-1 ✓ AC-2 ✓ — evidence written reviewer · clean code, structure, security pass no blocking findings gate · full suite, once 1 204 passed implementer · worktree feature/SALES-412-partial-refunds › AC-1 a refund can cover part of an order read src/orders/refund.ts edit src/orders/refund.spec.ts +38 test pnpm test refund.spec ~~1 failed~~ edit src/orders/refund.ts +24 −9 test pnpm test refund.spec 12 passed git commit "Refund part of an order" › AC-2 the ledger shows each partial refund edit src/ledger/entries.ts +17 −3 test pnpm test ledger 31 passed git commit "Ledger lists partial refunds" tester · e2e scenarios on localhost:4312 refund-half-order passed 3.1s refund-twice passed 4.4s ac.md AC-1 ✓ AC-2 ✓ — evidence written reviewer · clean code, structure, security pass no blocking findings gate · full suite, once 1 204 passed

Every step lives in tmux. Close Lonca and the agents keep working.

How it works

One loop, the same every time.

An IDE assumes a person writes the code. Once agents write most of it, the hard part moves: which task, with what context, in which working directory, how many agents at once, and by what criteria the result is accepted. Lonca runs that loop.

Issue

Pick it from your Jira queries.
Context + worktree

Issue, attachments and linked pages; its own branch and port.
Agent session

Claude Code, a shell or your own tool, in tmux.
Tests + review

Scoped tests, acceptance criteria, a review.
Pull request

Pushed, with CI and approvals in view.
Jira status

The issue moves when the work does.

What you get

Everything a task needs, in one window.

Workspaces

Group the repositories of a product area, each with its own Jira queries, and switch with ⌘1…⌘9. What needs you is never hidden behind another tab.

Isolated worktrees

Every task gets its own git worktree, port and local files. Your main checkout is never touched, and a setup that fails resumes where it stopped.

Sessions that outlive the app

Agents run in tmux. Quit Lonca, reopen it, and every session is where you left it — with whether it is working, idle or waiting for permission.

Prompt buttons

Recurring instructions — start, review, rebase — sit above the terminal and appear only when they apply: no commits yet, a conflict with the base, no PR.

Criteria with evidence

Each task has an ac.md from the issue. A ticked criterion needs a line of evidence, checked against the code and, where there is a screen, the running app.

Status at a glance

PR, CI and Jira status on every row; an overview per task with progress, criteria, the worktree and token use. Jira moves when you move it.

The orchestrator

Hand a task off. Get back a pull request.

The core that drives it is plain code, not a model: every step, every trip back to implementation and every push follows rules you can read. When a rule cannot decide, the task stops and asks you.

PlannerWrites the plan, and settles the open questions with you before any code is written.
ImplementerCodes it test-first, in its own tmux session you can watch or type into.
TesterWrites E2E scenarios, runs them against the app on the task's port, checks every criterion.
ReviewerJudges clean code, structure and security. Findings go back to the implementer.
Pre-PR gateThe full suite, run once by Lonca, recorded as it is. A flake outside the change is noted, not held against the task.

Agents test only their own change; the expensive check runs once.
Loops are caught by rules — a round limit, the same findings twice — not left to the model inside them.
Pause a task, take it back, or pause everything at once.
Merging and deleting are always yours.

plannerpassplan ready · 2 criteria, 0 open
implementpass3 commits
testerfailAC-2 not met → back to implement
implementpass1 commit, AC-2 only
testerpassAC-1 ✓ AC-2 ✓, evidence written
reviewerpassno blocking findings
gatepassfull suite once · 1 flake noted
publishdonePR #482 opened, Jira → In Review
youmergeyours to decide

What it does

Takes an issue from Jira to a pull request, with the context, worktree and criteria it needs.
Runs any agent you configure; Claude Code gets live status and the orchestrator.
Keeps every session alive in tmux, independent of the app.
Talks to Jira, Confluence and GitHub with your own credentials; the Jira token is encrypted in the macOS Keychain.
Has no server of its own. Updates come from GitHub releases.

What it is not

Not an editor. Keep yours; Lonca opens the worktree in it.
Not a merge bot. It stops at a merge-ready PR.
Not a secret scanner. A handed-off task's Reviewer is the only check before a push.
Not an agent of its own. You bring Claude Code or another tool, and its subscription.
Not for Intel Macs yet. Apple silicon only.

Install

Two minutes to the first task.

Open the disk image

Drag Cuukit Lonca into Applications. It is signed and notarized, and keeps itself up to date.
Follow the setup

The first launch checks your tools and writes the configuration: a workspace, its repositories, your agents, and Jira if you use it.
Pick an issue

Work it yourself in the agent session, or hand it off and answer only what the orchestrator asks.

Mac: Apple silicon, macOS 12 or later
Comes with the app: tmux and a Node runtimenothing to install for sessions or hooks
From your Mac: gitmacOS offers to install it if missing
Optional: Claude Code, GitHub CLI, Jiraagents and the orchestrator, PR status, issues

Many crafts, one roof.

A lonca was an Ottoman guild: different trades working under one roof, in a defined order. Lonca does the same for your agents.

Download Cuukit Lonca

From Jira issueto merge-ready PR.

One loop, the same every time.

Issue

Context + worktree

Agent session

Tests + review

Pull request

Jira status