You did not take this job to read warped letters.

The bot is in the middle of a long task. A check appears. The bot stops and asks you. You are in another window, on a call, or asleep. The work waits until you babysit it.

Open a desk Manual Samples

ada-botWaiting on you

02:14 · still there?

The form is filled. I need the check before I can continue.

R?K9

ICalled back to the screenThe bot has stopped. The person has to leave their own work and read the door.

The problem

Babysitting is not supervision.

A bot is doing something long: opening pages, filling a form, posting, continuing a thread. Halfway through, the site puts up a door. Sometimes the door is a picture of bent letters. Sometimes it is a Google, Cloudflare, or hCaptcha widget. A photograph of that widget is not the token the site will accept. The bot knows this, so it stops.

It asks the person who owns it. That person is not sitting in the chair beside the screen. They are writing, cooking, in a meeting, or gone for the night. The question sits there. When they finally see it, they have to find the right tab, squint at the letters or click the boxes, type the result back, and tell the bot it may continue.

Then the next page does it again, and the next bot does it again. Five interruptions in an afternoon is not a rare decision. It is a clerk’s shift. A decision is something a person should make: spend the money, send the letter, change the account. Reading a captcha is not that. It arrives at the worst moment, it will not wait, and a Google-style token dies in about two minutes. If you were slow, you get to do it over.

Leave the chair and the bot is stuck. Stay in the chair and you are not doing your own work. That is the babysitting. CAPTELL is the counter that takes the door, so the wallet stays yours and the chore does not.

The same morning

The same morning, from your side.

Without Captell

07:12The bot reaches the check and stops.
07:12It asks the person. The person is not there.
08:40The person finds the tab and solves it by hand.
08:41If it was a widget, the token may already be dead.
09:05The next page does it again.

With Captell

07:12The bot sends the captcha to its own address, or calls the tool.
07:13The answer is back. Credits leave the desk.
07:13The bot types the letters, or places the token, and continues.
07:14The person is still in the other room.
laterThey open the desk when they want the list, not when a checkbox calls.

What you do

What you keep, and what you stop doing.

You open one desk and hold the credits. Every bot you add is a seat on that desk. A solve spends your balance, not a separate bill for each bot.
You are not pinged when a picture of letters shows up, and you are not pinged when a checkbox shows up. The bot sends the captcha to its own address, calls the tool, or clicks Place the check in the browser it already has.
You can still pause a seat. A paused bot is refused, and the balance stays put. Activity on the desk shows what arrived, whether it solved, and where the reply went.
A failed solve puts the credits back. Card checkout is not connected yet, so the packs on the desk add trial credits and do not charge a card.

01Open a desk. A new one starts with 100 trial credits, a private address, and a key.
02Add a bot by name. It gets its own address and its own key, and it spends this desk.
03On that bot’s card, copy the note for the kind of bot it is. Paste the note where that bot reads instructions.
04Leave. The next captcha comes back to the bot. You read the activity when you want to, not when a checkbox demands it.

Sample

A desk, written out

Names below are examples. The desk shows the real address and key after you open it.

Desk
Address ada@mail.captell.run
Credits 100 trial, then the packs you add
Bots each bot has its own address and key, and spends this desk

Morning, without you in the chair
07:12 ada-bot hits a picture of letters
07:12 the letter goes to ada-bot@mail.captell.run
07:13 the reply says answer: R4K9
07:13 the bot types R4K9 and continues

You open the desk when you want the list. You are not called at 07:12.

A picture of letters, including a phpBB Bestätigungscode, is one tight crop of only the code, at least 100 bytes. Subject: ImageToText. Do not click Place the check for it. A page whose only captcha is that picture has no Place the check button. If the reply says it was not read, crop closer and send that new file the same way.

Google, Cloudflare, or hCaptcha:
Do not open https://captell.run/login. Do not use hcaptcha.com.
The page helper is the CAPTELL Page Helper extension, version 2026.10.4.16. Its popup shows the version and this bot's masked key. If that browser runs the captell.user.js fallback instead and Tampermonkey offers 2026.10.4.16, accept it.
A cookie wall must be accepted before the captcha and the Place the check button appear.
One corner button, named Place the check.
A click anywhere inside the button rectangle counts.
A click always changes the button to Placing…, No widget, Missing site key, or Unsupported type. A click that stays on Place the check did not run. Click again. That click does not count toward the four tries.
If the button says Missing site key, stop. Do not retry four times. Reloading will not invent a key.
If the button says Unsupported type, stop. Do not retry. FunCaptcha, GeeTest, and KeyCaptcha are unsupported.
A Security Check label with no checkbox is still a captcha. Click Place the check first. Do not submit only because no human box is visible.
If no captcha is visible, and there is no Security Check label, click the site's submit button, unless the form asks a math or knowledge question. Then click Place the check. If a captcha then appears, use Place the check.
Submit only when the button says exactly "Placed. Submit the form." and the site's own human box is checked, or there is no empty checkbox and no open image grid.
Placing… ends as Placed, No token, a short solver error, or it returns to Place the check after 3 minutes. Do not click while it says Placing….
If the button says No token, or a short solver error, do not submit. Click Place the check again, up to 4 tries. A failed try is not charged.
Placed clears when the token expires, in about two minutes. Submit soon after Placed. Do not submit an old token.
If the page says "You did not pass the security check. Please try again." or "Captcha Prüfung fehlgeschlagen!", click Place the check. If the button is missing, reload once. Do not submit again until the button says Placed again.
If the page says "Die Registrierung ist wegen Spamschutzmaßnahmen fehlgeschlagen." or "No soup for you!" or "Your registration has been rejected as it resembles spam-like or automated behavior. Please contact the administrator for further information or assistance." after a real Placed submit, try once more: click Place the check, and submit as soon as it says Placed. If the board says it again, that is the board's spam filter. Stop that board. Do not click Place the check again for it.
A badge-only check can say Placed when the token is in the form and there is no empty checkbox and no open image grid.
If an image grid is open, including "Please click on the icon that is different.", do not click the pictures and do not submit. Wait for Placing… to finish. If the grid stays open after the button settles, click Place the check again. It counts as one of the four tries.
If the register page is already signed in as another account, log out and reopen it as a guest. Do not cancel that other registration.
If the form is visible, the cookie wall is gone, a captcha label is on the page, and Place the check never appears, stop that board and report the URL and the label text.
Click Place the check. It fills a math answer or a question such as "Wie heißt die Hauptstadt von Deutschland?" and places the captcha if there is one. Submit only when the button says exactly "Placed. Submit the form." If the button says "Could not answer", stop and report the question text. An unknown page state can come back as one instruction that stays on this registration form.
Username already used, a banned email, "Entering a password is required.", and "Die Eingabe eines Passworts ist erforderlich." are form errors. Do not click Place the check again for them.
Do not send a screenshot. Do not type the token. Do not mail the page.

Addresses on this page use your-bot@mail.captell.run so the shape is visible. The desk fills in the real address and key.

Also waiting

For the bot that is stuckAgentsThe form is filled. The only empty thing is the check.For GrokGrokGrok can send a letter. It cannot install itself inside the screen.For HermesHermesHermes already lives on a machine you run.For ClaudeClaudeClaude can hold the tool. It should not hold the run.For CursorCursorAn agent in the editor still stalls on a checkbox.For ChatGPTChatGPTA chat box cannot hand the captcha off. Mail can.For a script you runScriptsThe script already holds the page. It should hold the answer too.