01 / Summarise
A summary, on a schedule.
Tickets, a dashboard, a changelog, a shared inbox. Read it, boil it down, have it waiting.
DeepShell Bots
Hire a bot for the job that keeps coming back.
Describe the job in plain words. Pick the site it’s allowed to work on. Choose when it runs. DeepShell does the rest inside your own Chrome, and tells you exactly what it did.
One site at a time · Runs while Chrome is open.
Your next hireExample setup
The morning support brief
- Job
- Summarise new tickets
- Allowed site
- Your support queue
- When
- Weekdays at 8
- Access
- Read-only
One quiet tab. A clear summary. You keep working in yours.
How it works
01
Say the job.
“Every weekday at 8, pull the new tickets from the support queue and summarise them.” That’s the whole setup. No flowchart, no scripting.
02
Grant one site.
A bot can only touch the sites you have allowed, one at a time. It never gets the whole web. If it ever lands somewhere else, it stops and the tab closes.
03
Let it run.
Each run opens one quiet tab in the background, does the job, and closes the tab. You keep working in yours.
04
Read the card.
Every run ends with a card: what happened, what it cost, and what it did not do.
Three things you can hire today
02 / Watch
A page watch.
“Tell me when the price drops below 40.” A watch only reads and notifies. It does not click, buy, submit, or send. When it triggers, the card says what changed and what it left alone.
03 / Repeat
A repeat read.
Anything you’d otherwise open every morning and skim. Hire it once.
Every ready-made bot ships read-only. Anything that would change a page asks you first.
Off until you say so
Bots are switched off when you install. Three switches in Settings turn them on, one job at a time.
All three start off. Turn on only what the job needs.
Let bots read pagesOff by default
Let bots act on pagesOff by default
Let bots download filesOff by default
When a bot reaches something it isn’t allowed to do on its own, it asks. If you don’t answer within five minutes, the answer is no. Some things can never be pre-approved at all: sending, paying, deleting, submitting.
It tells you what it did
Each run shows its real, settled cost. Not an estimate. The team view stays quiet until there are enough real runs to say something true.
When a page watch fires
“Nothing was bought, clicked, or submitted.”
The card for what didn’t happen is as important as the card for what did.
What it won’t do, said plainly
It runs only while Chrome is open.
Close Chrome and the bot waits. A missed window is shown as missed, not hidden.
It can’t see the page as a picture.
Bots read text. A job that needs eyes stops and says so.
It won’t take every website.
Access is granted one site at a time, when you say yes.
It doesn’t learn by watching you.
There is no record-and-replay. You describe the job; you don’t perform it.
Light on your browser
You should never notice a bot is installed until it has something to tell you. Idle, DeepShell uses about the memory of a single small tab and no processor time. A build that gets heavier fails our tests before it ships.
Questions about bots
Does a bot run when my laptop is closed?
No. Bots run inside your Chrome, while it is open. That’s what keeps them on your side of the fence.
Can a bot buy, send, or delete something?
Not on its own. Those actions can never be pre-approved. A bot that reaches one asks you, and silence means no.
What does the “read your browsing history” line at install mean?
That’s Chrome’s wording for one permission: reading tab titles and addresses, so DeepShell can name the site it’s about to ask you for. It never reads page text without a per-site grant.
Where do my bots show up?
In the Team tab in Chrome, and in your o10 console, marked as running in the extension. The console sees names, run status, and cost. It does not receive page content, steps, or permissions. For how selected content is used to answer a request, see the privacy policy.
What about jobs that need to see the screen?
Not in this release. A bot that needs it stops and tells you, rather than pretending.
The job that comes back every week shouldn’t come back to you.
One site at a time · Runs while Chrome is open.