IRONDECK Sections Español Waitlist

Claude Code orchestrator for WindowsYour projects move forward. You make the calls.

A Windows program that drives Claude Code for you: it runs several tasks at once, picks up after interruptions, and only calls you in to decide.

In development, no date or price yet · just your email and language · unsubscribe any time · Privacy

IRONDECK project: web-shop

Flow · Build the landing page

  1. ResearchSonnet · medium effortdone
  2. DesignSonnet · high effortdone
  3. BuildOpus · high effortrunning · 18 min
  4. ReviewOpus · high effortqueued

Tasks

2 / 4

5-hour limit

34 %

Week

61 %

Inbox · 2 decisions

You reached the weekly cap you set (60%). Continue with “Review”?
ContinueWait for the reset
“blog” finished with changes in 6 files. Merge them into main?
MergeSee changes

Billing mode: plan only

Illustration with sample data. Real screenshots soon.
Who it's for
Anyone running Claude Code on Windows, or about to
Your account
Your Claude Code and your Claude plan (Pro, Max, Team or Enterprise), no middleman server
Spend
Plan only; capped extra usage arrives before launch
Status
In development, no date or price yet

The problem3 things that slow you down

Claude Code works fast. You're the bottleneck.

  • You have to babysit it

    Start a task, wait, review, start the next one. Step away from the screen and everything stops.

  • Limits cut you off halfway

    Hit the 5-hour or the weekly limit and the task stops halfway, with nobody to pick it back up.

  • Running several at once gets messy

    Several sessions in the same project step on each other, and you lose track of how much plan you have left.

IronDeck takes care of that part.

Built for Windows

Runs natively, no WSL. Alerts arrive as system notifications.

Built around your plan

It knows how much plan you have left, and at the limit it does what you chose: wait for the reset or, once it lands before launch, keep going on extra usage up to your cap.

Works in flows

Each step with its own model and effort, decisions that wait for you, and a record of what happened.

A skill workshop included

Versions, A/B comparisons and export for your skills, in the same app that runs them.

Method5 steps

How it works

IronDeck is a program for your PC that drives Claude Code, Anthropic's coding agent. I built it to move long projects forward without starting every step by hand.

It uses your own Claude Code and your own Claude plan. There is no IronDeck server in between.

  1. You describe the work in steps

    For example: research, design, build and review. Each step uses the Claude model that fits it: a quick one for reading, a stronger one for building.

  2. IronDeck sets it running

    One click launches the whole batch: Claude Code runs on your PC, each task in its own copy of the project so they don't collide, up to four at once.

  3. It only asks what it must

    When something needs your call, it waits in the inbox and you get a Windows notification. You answer, it carries on.

  4. You approve the finished work

    Changes reach your project only when you give the go-ahead.

  5. Your skills, with history

    The instructions that teach Claude to work your way are kept with every version.

Features12 in 3 groups

Three jobs in one app

All of this is already in the code, with automated tests, and is being tested on a real PC. Where something is still missing, I say so right there.

Run your agents

Parallel tasks

Up to four at once, each isolated in its own copy of the project.

Step-by-step flows

With the model, effort and permissions for each step. They run in order, and each step gets what the previous one delivered.

Picks itself back up

If you close the app or the PC shuts down, it reruns the interrupted step when you return; finished work isn't lost. If a task fails, it retries with a stronger model, when there is one.

Decision inbox

Everything that needs your answer, in one place, with a Windows notification.

Control your spend

Limits in view

Your 5-hour and weekly limits, with the same numbers you see on claude.ai.

Pause and resume

At the limit it pauses without burning retries, and resumes on its own after the reset.

Weekly cap

You decide how much of your week IronDeck may use. When it gets there, it asks before going on.

You choose how it's paid

Plan only or, once it lands before launch, your plan plus your account's extra usage up to the cap you set. In plan-only mode, it stops the task as soon as Claude Code reports a separate charge.

Tune your skills

Versioned library

Keeps your skills, the instructions that teach Claude to work your way, with every version. The number never goes down, and you can go back to an earlier one.

A/B comparisons

Compare two versions of a skill on the same cases and keep the one that works better. Each case runs three times, with Opus as the judge.

Verify and export

Checks each skill against the official rules before you share it, and packages it as a .skill file or a plugin.

Templates that adapt

Your templates adjust to each project through their own variables.

Plus: a Windows installer, and updates that roll back on their own if the new version doesn't start.

Under the hood12 technical facts

For those who want the details

This is how the development version works. It may change before launch.

See the spec sheet: execution, plan and billing, system

Execution

Invocation
The official Claude Code in headless mode (claude -p), with the task on standard input and the stream-json output read live. Tested with Claude Code 2.1.287.
Isolation
Each task works in its own copy of the repository. IronDeck makes the commits and only merges with your approval. If a merge doesn't apply cleanly, it's logged and you retry it from the inbox.
Permissions
Exact allowed-tool rules for each step, such as Bash(npm test).
Concurrency
Up to 4 tasks at once, depending on free memory.

Plan and billing

Plan limits
Reads the rate-limit events Claude Code emits during the task: percentage used and reset time, for the 5-hour window and the week. A limit pauses; it doesn't count as a failure.
Billing
Before launching, checks which account Claude Code runs under; it doesn't use API keys. Two modes: plan only, which stops the task if Claude Code reports extra usage, and plan plus extra usage, which allows it up to a spending cap (arrives before launch).
Failures
A task fails when it ends with an error or a partial delivery: it gets one retry with a larger model, when there is one, and on a second failure you decide. A denied permission stops it without a retry. 6-hour maximum per task.

System

Interface
A server that runs only on your PC and rejects requests from other websites. The window opens in your browser.
Updates
A separate process updates with the app closed and rolls back if the new version doesn't start.
Evaluations
3 samples per case and version, isolated from your personal configuration, with Opus as the judge.
Stack
Node.js and TypeScript, state in JSON, Git for versions.
Tests
1,309 automated tests, most against a simulated Claude Code. Since October, also real runs on Windows with the actual one.

Not yet: the extra-usage mode, and Claude drafting your briefs and flows so that, once you approve them, they launch on their own when needed. Both are on the roadmap.

Progressphase 04 in progress · 4 of 6 done

Where IronDeck stands

Updated Oct 11, 2026

IronDeck is built with the method it automates: a project map, batches of parallel work, briefs for Claude Code, and an independent review of every delivery.

4 / 6phases done
1,309automated tests, plus real runs on Windows
Oct 72026, first real install on Windows
28 sto roll itself back after a failed update
  1. 00

    Foundation

    The shared skeleton and a first complete task, end to end.

    Done
  2. 01

    Core features

    Versioning, templates, window, task engine, plan control and skill verification.

    Done
  3. 02

    Wired to the real Claude Code

    Everything connected: flows, comparisons, export and the Windows installer.

    Done
  4. 03

    Real use on Windows

    Installed and running on a real PC: it updates itself and rolls back if something fails, passes one step's result to the next, and backs up your library to your GitHub.

    Done
  5. 04

    Autonomy

    First, seeing how each project is going: its phases, its tasks and what's waiting on you. Then a central chat that drafts the briefs and flows: you approve them the first time, and after that they launch on their own when needed, with automatic review of finished work and links to other agents.

    In progress
  6. 05

    Launch

    The base edition, the kits, and the team version.

    Later

Log7 entries

Updates

  • IronDeck has a name and a home

    The project I showed in the video as “Herrería de Claude” is now called IronDeck. From here you can follow the progress, read the guides and join the waitlist.

  • Phase 04 begins: first, seeing each project

    Before IronDeck works on a project on its own, you'll be able to see how each one is going: its phases, its tasks and what's waiting on you. It's the first thing I'm building in phase 04.

  • A test on a real project

    IronDeck ran eight Claude Code tasks on a copy of a game I'm making. One wrote code with all its tests passing, and I accepted it. Another, which had to split up the work, stopped to ask me instead of making up what was missing.

See earlier updates
  • Updates now go through, and the library backs itself up

    The second test of the fix also failed, for a different reason, and also rolled back on its own. With both fixes in, the next four updates went through. And now every change to your skill library is pushed to your GitHub automatically, never forced.

  • An update failed, and IronDeck recovered on its own

    When updating on a real PC, the new version didn't start. IronDeck went back to the previous version on its own in 28 seconds, without losing anything. The fix is merged and waiting for its second test.

  • First real install

    IronDeck is installed on Windows with its shortcut and a library of real skills. A real task waited for a decision in the inbox and carried on by itself once answered, and the weekly usage matched claude.ai.

  • First tasks with the real Claude Code

    Until now everything was tested against a simulated Claude Code. This time IronDeck ran the real one: it tuned a skill and ran a full evaluation without a single interruption.

What's coming3 editions

Editions

Prices and dates to be announced. I don't charge anything in advance.

IronDeck

In development

For one person on their PC.

Everything on this page, with your Claude Code and your Claude plan.

IronDeck Team

In design

For teams and companies.

For large jobs with several people and many agents at once. If you want it for your team, join the waitlist.

Kits

In preparation

Ready-to-use templates, flows, skills and context documents.

The first is the method I build IronDeck with: map the project before writing code, audit it, split it into batches, and hand work between chats without losing the thread.

The maker

Who's behind it

I'm Wladimir Diaz (DwladimirL), an independent maker. The code is private for now, but every step forward, and every failure, goes in the log and on the channel.

I build it for my own projects, and every phase is tested on my Windows PC before it counts as done.

Wladimir Diaz

@DwladimirL · independent maker

Questions11 questions

Frequently asked questions

Question not here? Write to me at irondeck.app@gmail.com.

What do I need to use it?

A Windows PC, Claude Code installed with your account, and a Claude plan that includes it: Pro or Max, or a Team or Enterprise plan. Also Git and Node.js. The final list ships with the first release.

Do I need to know how to code?

Not to use it: you describe the work and approve the result. It does help when reviewing what it delivers, just as with Claude Code on its own.

Can it break something on my PC?

Each task works in a copy of your project and can only use the tools its step allows. Its changes reach your project when you approve them, but commands you allow, such as publishing or installing packages, act outside that copy. It's a version in development: use it with Git and backups.

Which account does it use?

Yours. IronDeck runs your own Claude Code installation on your PC. It doesn't ask you to sign in, doesn't store your password, and doesn't route your session through any server. What it uses comes out of your plan and, only if you turn it on, your account's extra usage.

Does using IronDeck go against Anthropic's terms?

IronDeck doesn't change how you use Claude Code: it runs your own official installation, with your account, on your PC. It doesn't share accounts, doesn't resell access, and respects your plan's limits: when it hits one, it pauses. Your Claude plan's terms still apply as always; check them if you have questions about your case.

Can it spend beyond my plan?

Only if extra usage is turned on in your Anthropic account; without it, it can't. If it is on, IronDeck stops a task by default as soon as Claude Code reports extra usage, and what was used up to that point is billed. If you'd rather it not stop, you'll be able to turn on your account's extra usage with a spending cap; that mode arrives before launch. You also decide how much of your week IronDeck uses.

What leaves my PC?

IronDeck has no server on the internet: its server runs only on your PC. What leaves is what Claude Code sends to Anthropic while working, checks to GitHub for updates, whatever your tasks do with the permissions you grant them, and the backup of your library to your own GitHub account. None of it goes through me.

Is IronDeck made by Anthropic?

No. It's an independent project that works with Claude Code. Anthropic doesn't sponsor or endorse it.

When does it ship, and what does it cost?

There's no date or price yet. I don't charge anything in advance, and the waitlist hears first.

Does it run on Mac or Linux?

For now, Windows only.

Is the code open source?

It's private for now. This site and its repository show the progress, the guides and the updates.

Support

Follow the project and back it

Waitlist

I'll write to you about IronDeck's progress, the beta, the launch, and its editions and kits, and tell you first when it ships. I ask for your email and, if you like, three short questions.

Details in the Privacy notice.

Notify me at launch

If you'd like to help finish it: a contribution isn't a purchase, it doesn't buy access or set dates. It pays for development time and testing with the real Claude Code, so IronDeck ships sooner.

Ko-fi

One-time or monthly, no account needed. When the kits come out, they'll be sold separately on the same page.

Support on Ko-fi

GitHub Sponsors

If you have a GitHub account, you can sponsor from there, one-time or monthly.

Opens soon

Free, right now

Star the repository, follow it with “Watch”, and share it. It helps more people find it.

Star on GitHub

Less terminal, more decisions.

Join and I'll tell you first when it ships.

Notify me at launch