Skip to content
clanksDownload

clank(n.) short for clanker, slang for an AI

Put the clankers
to work.

A whole crew of AI helpers that lives on your computer. Tell them what you want in your own words. They plan it, make it, check each other's work, and ask you before anything important.

Free and open source · Also for Windows and Linux

  • Runs on your computer
  • No account, no cloud
  • Nothing ships without you
Coffee cart site

Needs you: CLK-101 Home page with hero and hours is signed off and ready to approve

To do 2

  • CLK-105Code Contact form with opening hours Waiting on CLK-103
  • CLK-106Copy Launch email to regulars For Quill

In progress 2

  • CLK-103Code Order ahead for pickup Running npm test3/5
  • CLK-104Copy About us, in our voice Writing the second draft

Being checked 1

  • CLK-102↩1Code Menu with prices and photos Clicking through on a phone

Ready for you 1

  • CLK-101Code Home page with hero and hours Signed off by Atlas

The board in the app. Every card shows its clank and what it's doing this second.

How it works

From one sentence to done.

No setup wizard and no prompt writing. Say what you want and the crew takes it from there. You approve the plan, and you approve what comes back.

  1. 01 · Say it
    A simple website for my coffee cart, with our menu and opening hours
    A landing pageA launch planA researched report

    The project, its folder and its crew are made from that one line. Atlas asks what it needs to know.

  2. 02 · Approve the plan
    Spec v1 · 4 storiesAC-1 The menu shows every drink with its priceAC-2 Opening hours read right on any phoneAC-3 Order ahead, pay at pickup

    Scribe writes down what will be made, story by story. Nothing is built until you say yes.

  3. 03 · Watch them work
    CLK-103Order ahead for pickup Forge · Running npm test

    Tickets land on the board. Several clanks work at once, each on its own copy of the project.

  4. 04 · You approve
    CLK-101 · Home pageChecked by Gauge · Signed off by AtlasApprove and merge

    Approving merges the work, on GitHub if that's where the project lives. Nothing ships on a drag or a guess.

Meet the crew

Eight clankers. One for every job.

Pick who's on each project. Every clank has its own model, its own tools and its own memory of the project, so you can ask any of them why they made a call.

  • Atlas

    Leads the crew · Lead

    Tell Atlas what you want. It plans the work, hands it to the right clanks and checks it before it comes back to you.

  • Scribe

    Writes up the plan · Business Analyst

    Turns a rough idea into a clear, written list of what will be made, for you to approve.

  • Prism

    Designs it · Designer

    Designs how things look: pages, logos, colours and graphics, in the built-in Studio.

  • Forge

    Builds it · Engineer

    Builds websites, apps and anything made of code, with tests, each ticket on its own branch.

  • Gauge

    Checks it works · QA

    Tries out what was built the way a person would, and says what's broken.

  • Scoutoptional

    Does the research · Researcher

    Looks things up, and comes back with what it found and where it found it.

  • Quilloptional

    Writes the words · Writer

    Writes documents, emails, the words on a website, and posts.

  • Buzzoptional

    Spreads the word · Marketing

    Plans how to tell people: campaigns, posts, and when they go out.

Need someone else?

Make your own clank with a name, a job description, a model and the tools it may use, then give it a place in the line. Keep it in your library, or share it free on the marketplace.

Sentinel

Security · between Gauge and Atlas

A real team

Not a swarm. A crew that pushes back.

Work moves in order: spec, design, build, check, sign-off. Only the stages a ticket needs, so a quick fix goes straight to Forge. When something's wrong, it goes back to whoever can fix it, with a reason. If a ticket keeps looping, it comes to you.

  1. Spec
  2. Design
  3. Build
  4. Check
  5. Sign-off
  • ↩ Gauge › Forge AC-4 failed: prices cut off on small screens
  • ↩ Forge › Scribe The spec doesn't say what happens when the cart is closed
  • ↩ Atlas › Prism The banner doesn't use the brand colours
  • ✓ Atlas › You CLK-101 signed off, ready for you

The workbench

Watch every change as it happens.

Open any ticket: the chat on the left, the work on the right. Step in whenever you want.

Forge · CLK-102

Gauge found the prices cut off on narrow phones. I'm switching the menu to one column under 420px and adding a test for it.

edit_file src/Menu.tsx +2−1

shell npm test 14 passed

Ask Forge anything…

src/Menu.tsx

12 export function Menu({ items }: Props) {

13 return (

14- <ul className="grid grid-cols-2 gap-4">

14+ <ul className="grid grid-cols-1 gap-4 min-[420px]:grid-cols-2">

15 {items.map((item) => (

16+ // Prices never wrap under the name.

17 <MenuItem key={item.id} {...item} />

18 ))}

19 </ul>

KeepRejectComment on line
  • Changes

    Every edit, live. Keep or reject each one.

  • Terminal

    Every command and its output, with a stop button.

  • Browser

    A real browser in the app. Take over any time.

  • Studio

    A design tool, built in. Prism designs while you watch.

  • Activity

    Every step on a timeline. Go back to any moment.

Local models

The brains run on your machine.

clanks downloads an open model that fits your computer and runs it itself, with llama.cpp built in. No Ollama, no server, no command line. Your work stays private and keeps going with no internet.

  • Picks a model for your graphics card and memory, before you download
  • A model per clank: plan with a big one, build with a fast one
  • Serve your models to other apps on localhost, if you like
  • Optional: Anthropic, OpenAI, Google or OpenRouter with your own key

This computer · Apple M3 Pro · 36 GB

Gemma 4 26B A4BBest for this computer

16.8 GB to download · Runs fast on this computer

Download and set up
  • Qwen3.5 9BRuns fast
  • gpt-oss 20BRuns fast
  • Qwen3.6 35B A3BRuns, a little slower
  • gpt-oss 120BToo big for this computer

Routines

Put the crew on a schedule.

Ask in plain words. The crew does the work ahead of time, and you see exactly what will go out, where and when. Approve it, and clanks sends exactly that at exactly then. Unapproved, it never goes out, and if your laptop was asleep, it isn't posted late.

“Every Friday, have Prism make a promo banner for the weekend special and post it on X at 5pm.”

Goes out Fri 5:00 pm · @bluecart on XNeeds you

B

Blue Cart Coffee @bluecart

Weekend special: iced oat lattes, two for $9. Find us at the market, Saturday and Sunday from 7.

2 for $9 · this weekend
Approve for 5:00 pmSend back

Integrations and the marketplace

Plugs into what you already use.

Connect a service with a key or a sign-in that stays in your keychain, then choose which projects and which clanks may use it.

  • GitHub
  • GitLab
  • Stripe
  • Notion
  • Slack
  • Vercel
  • Google Analytics
  • X
  • Your email
  • + any MCP server
  • Reads run.Clanks look things up freely.
  • Changes ask first.You okay each one.
  • Money, posts and messages ask every time.With test or live mode shown.

A free marketplace

Install clanks, integrations, routines and whole crews that others have shared. No account and no paid listings. You see every tool, permission and host before anything installs.

  • Shopify storecrew
  • Podcast launchcrew
  • Sentinelclank
  • No account. No cloud.

    Projects, chats and models live in a folder on your computer.

  • Keys in your keychain

    Never in a file, never shown to a model, and sent only to the provider you chose.

  • Risky things ask first

    Pushing, deleting, deploying: a clank asks, and says why.

  • Never without you

    No merge, email, post or purchase happens until you approve it.

Your crew is waiting.

One download, one model, and they're ready. Free, open source, and yours.

Every release is on GitHub. New to it? Start with Getting started.