Capabilities

What Clootee actually does

The zero-setup install is the part people notice first. These are the parts they keep it for.

The two things everyone gets stuck on

Both of them fail quietly in a bare terminal. Both are handled up front here.

🌐

“It just doesn't respond.”

Clootee checks connectivity before you hit that wall, and gives two concrete ways out: turn on your VPN and re-check, or switch to a reachable provider in one click. Only providers that actually respond right now are offered — a list you can trust beats a list that is merely complete.

🔑

“It says nothing at all.”

Stock Claude Code must be signed in, or your messages get no reply and no error. Clootee moves sign-in into the UI: click the button, open the link, authorize, paste the code back. It works even when the server is remote, because the link opens in your browser.

Multi-session task queues

A coding agent is not a chat window — a real task takes minutes, sometimes an hour. Clootee treats that as the normal case.

  • One queue per session. Line up several tasks and let them run in order; each session keeps its own workspace, its own engine and its own history.
  • Interject without losing the run. Pause, reorder, or drop a message into a running task.
  • Several sessions at once. Different projects, different engines, side by side — switching sessions does not stop anything.
  • Progress you can read. Every step surfaces as it happens, so a long run is legible rather than a spinner you are asked to trust.

Full transparency, not a summary

When an agent edits your files, “it worked” is not enough information. Clootee shows the whole trace:

  • Reasoning, streamed as it is produced and collapsible once you have read it.
  • Every tool call with its complete input and output — the exact command, the exact diff, the exact file path. Nothing is truncated into a friendly sentence.
  • Timings and token counts per step, so you can see which part of a task is actually expensive.
  • A per-workspace file manager to browse, edit, search and bookmark the files being changed, right next to the session changing them.

Failures are never silent

The worst state a long-running agent can be in is “looks fine, is dead”. Clootee makes each of those states explicit, with a reason and a next step:

  • The engine process crashed.
  • The engine produced zero output.
  • Unusual silence — nothing has happened for far longer than this task should take.

Each one is reported as what happened plus what to do about it, rather than a frozen screen you have to interpret.

How it is built

projects/claude_hub/
├── backend/src/
│   ├── logic_struct/    # Orchestration — who is called, in what order
│   ├── logic_realize/   # Implementation — how each step actually works
│   ├── helper/          # Pure, business-free utilities
│   └── server/          # HTTP + WebSocket routes
├── frontend/            # Static, no build step
└── out_end/             # Portable runtimes, downloaded on demand

“What it does” and “how it does it” live in separate files. The orchestration reads top to bottom in one pass, and changing a detail cannot damage the architecture. The frontend has no build step at all — what you read in the repo is what runs in your browser.

Install paths branch per operating system from one codebase, which is why the same zip serves Windows, macOS and Linux.

Run it on your own machine

One zip, three platforms, Apache 2.0. No account, no telemetry.

Download Clootee v2.1.1
Open sourceApache 2.0 · GitHub