What it does
6 features
AppuBot · Workspace for desktop bots
Product and access
AppuBot is classified as a standalone product with its standard access.
Core features
6 features from provider sources · reviewed on November 8, 2026. Availability and limitations are listed directly below.
Multiple bots with individual tasks
Bots receive individual assignments and can work in parallel and pass work to other bots.
Source 1Operate desktop apps
Computer Use reads app windows and operates buttons, forms and spreadsheets within them. You can watch and stop it.
Source 3Teach workflows by demonstration
Teach mode records a demonstrated task and turns it into a readable, editable skill.
Source 4Visible bot memory
Each bot stores facts and preferences in a note you can read, edit or clear.
Source 5Schedules with approval
Routines start tasks on a schedule. New or changed routines proposed by a bot require your consent.
Source 6Supervise from your phone
Mobile apps and Telegram provide chat and approvals. Work runs on the connected computer or cloud machine.
Source 2
Usable AI models
Open choice
Bots use existing agent access and a per-bot model choice. Since the November release, Ollama, LM Studio and custom OpenAI-compatible servers are directly documented. OpenCode additionally exposes its configured providers and API keys. Quotas and supported features depend on the chosen access route.
Model families named
- Anthropic (Claude)
- OpenAI (GPT)
- xAI (Grok)
- Google (Gemini)
- Other models can be connected freely
- Model choice
- You choose
- Your own API key
- Yes
- Router or custom endpoint
- Not stated
- Local models
- Yes
- Depends on
- Plan, Admin approval
The rating covers the generally available main access. Documented · Sources accessed on
AppuBot: Custom providers and model access · AppuBot: OpenCode integration
Does it fit my task?
2 practical tasks · 4 requirements and limits
A good fit if …
- you want to use existing AI access for tasks in your desktop apps
- you want to give several bots individual tasks and editable memories
- you want to demonstrate workflows and have them run repeatedly
Less suitable if …
- you want continuous operation without a running computer or cloud costs
- you require technical isolation of all data between bots
Editorial assessment based on provider documentation. Not a product test.
Practical tasks
Editorial examples based on documented features. No product tests performed.
Transfer invoices into a spreadsheet
- Your input
- Invoices, a target spreadsheet and a bot with limited app permissions.
- Possible result
- A spreadsheet draft for review and a PDF export.
- What to check
- Check amounts and recipients; approve sending separately.
Create a recurring briefing
- Your input
- Sources, desired format and an approved schedule.
- Possible result
- A regular report in the bot chat with relevant changes.
- What to check
- Review sources and new memory entries; check host availability.
Transfer invoices into a spreadsheet
Your possible prompt
Compare three providers for [task]. Use their official documentation. Show differences, sources, and open questions in a table.
Adjust the task, data and permissions.
Requirements and limits
Requirement
Local routines need a running host
The computer must be awake and AppuBot open; the menu bar is sufficient. A cloud computer is a paid alternative.
Source 6Limitation
Full access acts without asking
Approval checks depend on the mode. Full access permits actions without asking; certain changes to bot permissions and routines still require consent.
Source 7Limitation
Mobile interfaces and Linux requirement
Linux computer use requires X11 or apps via XWayland. Computer Use uses the execution machine’s existing apps and sign-ins.
Source 3Limitation
Cloud data and shared access
Cloud computers run in the US. Bots share that machine; separate memory notes do not provide access isolation.
Source 11
Can I use it?
With requirements
Europe & regional availability
Storage region and country access are assessed separately. A complete country availability list is not published.
Reviewed scope: Local operation, mobile access and AppuBot Cloud
Reviewed on:
With requirements
Cloud storage in the US
The privacy policy names Agent37 in the US for cloud computers and backups. Local operation does not automatically store data there; model providers and connected services receive data sent for tasks.
Region, reason and source
Region covered: EU/EEA, United Kingdom and Switzerland
Documented reason: Deployment mode and provider access determine data processing.
Availability still unclear
Check mobile availability by country
iOS is offered through TestFlight, Android through Google Play. This does not establish availability of all access routes in every country.
Region, reason and source
Region covered: EU/EEA, United Kingdom and Switzerland
Documented reason: Store and beta access can differ by country and device.
Official source · appubot.com · Official source · testflight.apple.com · Official source · play.google.com
Accounts & permissions
Based on provider documentation. Permissions depend on the account, integration and organization policies. Review the permissions actually requested before use.
Configuration covered: Local agent access, paired mobile devices and optional cloud account
Sources reviewed:
Show all 3 points
Documented
Admin approval
Approve for me and Full access are set per bot. Telegram approvals are available for tasks started there.
Evidence
Memory and conversation continuity
4 of 6 criteria documented
Editable fact note per bot; used across chats and model changes, with shared host storage access.
Per-bot note, chat history and local or cloud storage
Sources accessed:
Documentation by criterion
StorageDocumented
Storage and scope
Bot memories are notes in each bot’s folder. Locally they remain on your computer; cloud bots store them on their hosted computer in the US.
SelectionDocumented
Selection and timing
Bots save short dated facts, update changed information and remove content on request. On switching to a new chat, they are asked for facts worth retaining from the previous chat.
Edit & deleteDocumented
Inspect, edit and delete
The note can be read, edited and cleared entirely. Complete local deletion also requires removing app folders. Cloud account, computer and backups can be deleted from the account page; ordinary plan expiry has a seven-day retention period.
Access boundariesPartly documented
Agent and channel boundaries
Each bot has its own note shared by its chats and Telegram. This is logical separation: bots on the same cloud computer can read its shared data.
RetrievalDocumented
Retrieval
New chats start with the bot note, about 12 KB according to the documentation. Bots can read earlier chats; a semantic ranking mechanism is not described.
New conversationsPartly documented
Session reset and compaction
The note persists across new chats and model changes. Compact now is documented; precise guarantees for retained details or interrupted actions are not stated.
Cost and effort
5 plans · Prices as of 8 November 2026
Prices and included usage
Pricing checked
The local app is free. Cloud plans pay for the hosted computer; model access and usage remain separate.
| Plan | Price | Included |
|---|---|---|
| Free | USD 0 locally | Bots on your own computer; its resources and model access are required. |
| Starter | USD 19 / month | Cloud computer with 4 GB RAM and 12 GB storage; personal monthly plan. |
| Pro | USD 49 / month | Cloud computer with 8 GB RAM and 20 GB storage; personal monthly plan. |
| Max | USD 79 / month | Cloud computer with 16 GB RAM and 40 GB storage; personal monthly plan. |
| Ultra | USD 109 / month | Cloud computer with 32 GB RAM and 80 GB storage; personal monthly plan. |
- Prices exclude taxes. Work plans and annual billing are offered separately.
- A Claude allowance is currently a limited-time launch offer and is not a permanently guaranteed plan benefit.
Setup
Install the app, connect an agent account and configure each bot’s task, model, apps and approvals.
Operation & oversight
Based on public provider documentation. Assessments are editorial inferences from the stated properties. Actual time requirements and reliability have not been measured.
Deployment covered: Local AppuBot operation and optional cloud computer
Sources reviewed:
Editorial assessment
Editorial assessment: suitable for supervised everyday bots; hosting, app permissions and model quotas must fit the assignment.
Show all 6 points
Documented
Files and working state
Bot files and chats reside locally or on the chosen cloud computer.
EvidenceDocumented with conditions
Sign-ins
The bot needs valid agent and, where applicable, app sign-ins.
EvidenceDocumented
Starting further runs
Approved routines start on schedule while the execution host is available.
EvidenceDocumented
Human intervention
Required approvals wait without automatic consent after a timeout.
EvidenceDocumented
Detecting errors
Even quiet routines report failures; results appear in the bot chat.
EvidenceDocumented with conditions
Resuming after failures
Current releases reload chats after connection loss. A general guarantee for resuming every interrupted action is not documented.
Evidence
Evidence and open questions
14 sources · 1 open point
Open points
The reviewed sources contain no reliable information on these points. A gap says nothing about the product.
Europe: Availability still unclear
Sources and evidence
Official product documentation reviewed. Workflows and assessments are editorial; hands-on product tests are outside the scope of this directory.
Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.
Provider
AppuBot is developed by Sarthak Gupta in India. The local app and optional cloud service are separate deployment modes.
- Operator
- Sarthak Gupta
- Organization
- Independent developer
- Website
- appubot.com
Changes to this profile 1
Dedicated profile with computer use, editable memory, open model access and separate details for local and cloud operation.
These notes describe editorial changes. Source and pricing review dates appear in their respective sections.