# AppuBot Workspace for your own AI bots: connects existing agents to desktop apps, Telegram, routines and editable memory, locally or on an optional cloud computer. Canonical profile: https://ki-agentenkompass.de/en/agents/appubot/ Editor: [Michael Meierhoff](https://ki-agentenkompass.de/en/about/) Sources reviewed: 2026-11-08 Basis: provider documentation. Examples are editorial suggestions, not hands-on product tests. ## Overview AppuBot is classified as a standalone product with its standard access. - Provider: Sarthak Gupta - Product family: AppuBot - Profile type: Workspace for desktop bots - Environment: macOS, Windows and Linux; Android and iOS TestFlight as mobile interfaces - Connections: Claude Code, Codex, Cursor, Grok, Copilot, OpenCode, Telegram and apps via Composio - Setup: Install the app, connect an agent account and configure each bot’s task, model, apps and approvals. - Pricing model: Free locally; separate model costs; cloud from USD 19 monthly ## Key features ### Multiple bots with individual tasks Bots receive individual assignments and can work in parallel and pass work to other bots. Source: https://appubot.com/ ### Operate desktop apps Computer Use reads app windows and operates buttons, forms and spreadsheets within them. You can watch and stop it. Source: https://appubot.com/features/computer-use ### Teach workflows by demonstration Teach mode records a demonstrated task and turns it into a readable, editable skill. Source: https://appubot.com/features/teach ### Visible bot memory Each bot stores facts and preferences in a note you can read, edit or clear. Source: https://appubot.com/features/memory ### Schedules with approval Routines start tasks on a schedule. New or changed routines proposed by a bot require your consent. Source: https://appubot.com/features/routines ### Supervise from your phone Mobile apps and Telegram provide chat and approvals. Work runs on the connected computer or cloud machine. Source: https://appubot.com/download ## Example workflows ### 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. ## Requirements and limits ### Local routines need a running host Requirement: The computer must be awake and AppuBot open; the menu bar is sufficient. A cloud computer is a paid alternative. Source: https://appubot.com/features/routines ### Full access acts without asking Limitation: Approval checks depend on the mode. Full access permits actions without asking; certain changes to bot permissions and routines still require consent. Source: https://appubot.com/features/approvals ### Mobile interfaces and Linux requirement Limitation: Linux computer use requires X11 or apps via XWayland. Computer Use uses the execution machine’s existing apps and sign-ins. Source: https://appubot.com/features/computer-use ### Cloud data and shared access Limitation: Cloud computers run in the US. Bots share that machine; separate memory notes do not provide access isolation. Source: https://appubot.com/privacy ## 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. ## 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 Documented · Sources accessed on: 2026-11-08 - [AppuBot: Custom providers and model access](https://appubot.com/releases) - [AppuBot: OpenCode integration](https://appubot.com/agents/opencode) ## 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: 2026-11-08 ### Cloud storage in the US With requirements 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 covered: EU/EEA, United Kingdom and Switzerland Documented reason: Deployment mode and provider access determine data processing. Official source: https://appubot.com/privacy ### Check mobile availability by country Availability still unclear iOS is offered through TestFlight, Android through Google Play. This does not establish availability of all access routes in every country. Region covered: EU/EEA, United Kingdom and Switzerland Documented reason: Store and beta access can differ by country and device. Official source: https://appubot.com/download Official source: https://testflight.apple.com/join/pu3nG2qn Official source: https://play.google.com/store/apps/details?id=com.appubot.app ## 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: 2026-11-08 ### Account used Documented: Existing agent access is used locally. Cloud requires an account; new phone pairings also require AppuBot sign-in according to the release notes. Evidence: https://appubot.com/download Evidence: https://appubot.com/releases ### Admin approval Documented: Approve for me and Full access are set per bot. Telegram approvals are available for tasks started there. Evidence: https://appubot.com/features/approvals ### Data access & team sharing Documented: Connected apps are enabled per bot. Computer Use reaches applications signed in on the host; Telegram users are admitted by code. Evidence: https://appubot.com/apps Evidence: https://appubot.com/features/computer-use Evidence: https://appubot.com/download ## Prices and included usage Pricing checked: 2026-11-08 The local app is free. Cloud plans pay for the hosted computer; model access and usage remain separate. ### Free USD 0 locally Bots on your own computer; its resources and model access are required. Price source: https://appubot.com/pricing ### Starter USD 19 / month Cloud computer with 4 GB RAM and 12 GB storage; personal monthly plan. Price source: https://appubot.com/pricing ### Pro USD 49 / month Cloud computer with 8 GB RAM and 20 GB storage; personal monthly plan. Price source: https://appubot.com/pricing ### Max USD 79 / month Cloud computer with 16 GB RAM and 40 GB storage; personal monthly plan. Price source: https://appubot.com/pricing ### Ultra USD 109 / month Cloud computer with 32 GB RAM and 80 GB storage; personal monthly plan. Price source: https://appubot.com/pricing 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. Pricing details: https://appubot.com/pricing ## 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: 2026-11-08 ### Files and working state Documented: Bot files and chats reside locally or on the chosen cloud computer. Evidence: https://appubot.com/privacy ### Sign-ins Documented with conditions: The bot needs valid agent and, where applicable, app sign-ins. Evidence: https://appubot.com/download ### Starting further runs Documented: Approved routines start on schedule while the execution host is available. Evidence: https://appubot.com/features/routines ### Human intervention Documented: Required approvals wait without automatic consent after a timeout. Evidence: https://appubot.com/features/approvals ### Detecting errors Documented: Even quiet routines report failures; results appear in the bot chat. Evidence: https://appubot.com/features/routines ### Resuming after failures Documented with conditions: Current releases reload chats after connection loss. A general guarantee for resuming every interrupted action is not documented. Evidence: https://appubot.com/releases ### Editorial assessment Editorial assessment: suitable for supervised everyday bots; hosting, app permissions and model quotas must fit the assignment. ## Memory and conversation continuity Scope: Per-bot note, chat history and local or cloud storage Sources accessed: 2026-11-08 Editable fact note per bot; used across chats and model changes, with shared host storage access. ### Storage and scope Documented: 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. - [AppuBot: Memory](https://appubot.com/features/memory) - [AppuBot: Privacy](https://appubot.com/privacy) ### Selection and timing Documented: 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. - [AppuBot: Memory](https://appubot.com/features/memory) ### Inspect, edit and delete Documented: 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. - [AppuBot: Memory](https://appubot.com/features/memory) - [AppuBot: Privacy](https://appubot.com/privacy) ### Agent and channel boundaries Partly documented: 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. - [AppuBot: Memory](https://appubot.com/features/memory) - [AppuBot: Privacy](https://appubot.com/privacy) ### Retrieval Documented: 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. - [AppuBot: Memory](https://appubot.com/features/memory) ### Session reset and compaction Partly documented: The note persists across new chats and model changes. Compact now is documented; precise guarantees for retained details or interrupted actions are not stated. - [AppuBot: Memory](https://appubot.com/features/memory) - [AppuBot: Releases](https://appubot.com/releases) ## Context The computer must be awake and AppuBot open; the menu bar is sufficient. A cloud computer is a paid alternative. Official product documentation reviewed. Workflows and assessments are editorial; hands-on product tests are outside the scope of this directory. ## Open points Europe, availability still unclear: - Check mobile availability by country ## Sources - https://appubot.com/ - https://appubot.com/download - https://appubot.com/features/computer-use - https://appubot.com/features/teach - https://appubot.com/features/memory - https://appubot.com/features/routines - https://appubot.com/features/approvals - https://appubot.com/agents/opencode - https://appubot.com/releases - https://appubot.com/pricing - https://appubot.com/privacy - https://appubot.com/apps - https://testflight.apple.com/join/pu3nG2qn - https://play.google.com/store/apps/details?id=com.appubot.app ## 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: https://appubot.com/ - Reviewed: 2026-11-08 - Provider source: https://appubot.com/privacy [Sources and method](https://ki-agentenkompass.de/en/sources/)