Help

How Red0 works

Red0 is one chat with your corp's orchestrator. You say what you want done; it answers, and for bigger pieces it proposes a team that works on your PC once you approve it. This page is the whole manual.

Your first corp, in six steps

Install Red0 from the download page (Windows or Linux) and open it. It updates itself.
Sign in with Sucia (top right). Your corps, teams and approvals live in your Sucia account, so this website and your phone can follow them.
Open the Sign in tab: sign in to Claude Code or Codex there (its own sign-in opens in a terminal window; choose Google there if that is how you signed up), or use your Sucia credits. A program's row turns green by itself; Red0 never sees your password or keys. No program? Its row says Get, and the tab can install Claude Code for you. You can also download a model under Local models and run a corp fully on your PC.
Make a corp. Click + New corp. It starts on the program that is signed in, with its own folder under Documents\Red0; choose another folder in the box above the chat or later in Set up.
Say what you want done, in plain words, and press Enter. The orchestrator answers in the chat and asks when it needs a yes or no.
Approve the team. For bigger work the orchestrator proposes a team: who is on it, the task and an estimate. Approve starts it, Change says in plain words what to change (it proposes again), Decline drops it. The team's card shows its progress, its current step and a box to tell it something for its next step.

What the words mean

Queued: Sent; your PC picks it up in a moment (here: Waiting for your PC, because the PC does the work).
Starting · Running: The program is working. The card says its current step, the steps so far and a clock.
Waiting for you: A card needs your answer: a team to approve, a command to allow, a question. Answer in the app, here or on your phone; the age on the chip says how long it has waited.
Awake: A finished team kept available for follow-ups until you close it.
Done · Failed · Stopped: The end of a turn or team. A done team shows what it changed, what it checked and what it left undone. A failed turn says why in plain words, with Send it again.
To review: Teams that finished and cards waiting for you, in every corp, until you close or archive them.
Trash: A corp or team you remove stays there for 30 days, and you can restore it.

Where a corp runs

Under Set up, Where this corp runs: Claude Code and Codex (everything on the programs you signed in to), Local first (the chat on a model downloaded to your PC, teams that edit on a program) or Only here (every model call on your PC; the chat and team logs are still kept in your Sucia account, which is how this website and your phone show them). Set up also holds the corp's folder, colour, how many teams may work at once, how long a team may be quiet before Red0 asks, and the corp's memory file RED0.md.

Approvals

Every team waits for your go, and a team on Ask asks before each edit or command. There is no "always allow": the card you approve is the whole permission. Closing the Red0 window while a team works asks first; closing stops the work in flight.

Sucia credits

No Claude account needed. Choose Use Sucia credits in the Sign in tab: Claude Code runs on your PC and talks to Claude through Sucia, and each answer is paid from your Sucia balance at Red0's rates (see Pricing); one credit is one US cent. The first message of a corp costs about 40 credits, because Claude Code's whole prompt is written to the cache; later ones cost a few credits. Agents run on Sonnet unless an agent names another model.

Set a cap per team under Set up (Credits cap per team); a team stops when it reaches it. Usage this week shows what your credits went on, by model and by run. Switch back to your own sign-in in the same tab at any time. Your balance is at the top right of the app.

What Red0 sends where

Model calls: With your own sign-in, Claude Code or Codex sends your instructions and the parts of your files it reads from your PC to its maker (Anthropic or OpenAI), under your own account. On a local model, nowhere: they run on your PC. With Sucia credits, those calls go through Sucia on the way to Anthropic, and Sucia counts their tokens.
Chats and team logs: Kept in your Sucia account: your messages and the replies, each team's log, the names of the files it changed and how many lines, and your answers to its cards. That is how this website and your phone show them.
Files: Stay in the corp's folder on your PC. Their contents and the line-by-line changes are not kept in your Sucia account.

This website and your phone

Sign in here to see every corp's chat and its teams from any browser, message the orchestrator and answer its cards. Red0 for Android shows the same and tells you when something waits. Hosting a corp needs the Red0 app on Windows or Linux: that PC does the work, and what you send from here reaches it when it is on.

When something fails

"The program is not signed in": open the Sign in tab, click the program's row and finish the sign-in in the terminal window, then Send it again.
"Your Sucia credits ran out": add credits from the balance at the top right, or switch to your own sign-in in the Sign in tab, then Send it again.
"This team reached its credits cap": raise Credits cap per team under Set up, then Send it again.
A team sits at Queued: the PC that hosts the corp is off or signed out; start Red0 there.
"Quiet for N minutes, still going?": the team said and did nothing for a while. Continue keeps it working, Stop ends it; open its Log tab to see its last steps.
The provider's limit: the team stops on your Claude Code or Codex limit, not on its work; its card says which limit and when it resets, and Resume when it resets picks it up where it was.
Anything else: the Activity fold at the bottom of the window keeps the plain-words log of what Red0 did; the program's own words are one fold away on a failed card.

Red0 is made by Sucia. Account, credits and sign-in questions: Sucia help.