#RockBot
Breathless by The Corrs is playing at the gym...

Because I added it to the RockBot
November 12, 2026 at 8:23 PM
The #rockbot ecosystem (at least how I use it) has changed and grown a lot over the past several months since I started the project. Here's a summary of how I use my personal #ai agent today.

blog.lhotka.net/2026/11/12/T...
The RockBot Ecosystem
VP, Open Source Creator, Author, Speaker
blog.lhotka.net
November 12, 2026 at 7:32 PM
The RockBot Ecosystem
We just added a “RockBot ecosystem” section to the RockBot readme, listing the related projects that work alongside the agent. Putting that list together made me realize that my RockBot Band post from March is pretty out of date. Some of the projects have been renamed, some are new, and quite a lot has changed in how I actually _use_ RockBot day to day. So I want to walk through how my RockBot is configured right now. I’m talking about my actual running instance this time, rather than the framework, and the MCP servers that let it help me manage email, calendar, meetings, files, GitHub, and a few other things. tl;dr - an agent is only as useful as what it can reach. RockBot itself mostly thinks and remembers. Everything it _does_ goes through MCP servers, each running in its own container and each holding only the secrets it needs. ## What RockBot Can Reach Here’s the list of MCP servers my RockBot agent is connected to as of today: 1. Adjutant - email, calendar, and contacts across all my accounts 2. Scheduler - finding meeting times with other people 3. Two OneDrive servers - one for my Marimer work files, one for personal 4. GitHub - repos, issues, PRs, file contents 5. Todo - a persistent to-do list with due dates and recurrence 6. OwnTracks - where I am (more on this later) 7. Research agent - deeper multi-source research, as an MCP server 8. Advisor council - several advisor personas that deliberate on a decision 9. OpenRouter, Azure Foundry, and Introspection - so the agent can see its own costs and usage Plus SocialAgent, which RockBot talks to over A2A rather than MCP, to keep an eye on my Mastodon and Bluesky accounts. That’s a lot of moving parts. But each one is a small, focused service, and that is very much on purpose. ## Email, Calendar, and Contacts The heart of the whole thing is Adjutant. If you’ve followed along, you might remember this as calendar-mcp. It got renamed (and hit 2.0) because it had grown well beyond calendars - I wrote about that, and everything it can connect to, in What Adjutant Can Connect To. Adjutant is an MCP server that gives an agent email, calendar, and contacts across multiple accounts: Microsoft 365, Outlook.com, Google Workspace, IMAP/SMTP, CalDAV/CardDAV, and read-only ICS feeds. The “multiple accounts” part is the whole point. Like a lot of consultants, my life isn’t in _one_ mailbox or _one_ calendar. There’s my Marimer work account, client accounts, personal accounts, family calendars. Any assistant that only sees one of those is going to tell me I’m free when I’m absolutely not. Adjutant lets RockBot see all of them at once, so “am I free Tuesday afternoon?” gets a real answer. Each account also has its own permissions. You can let an agent read one mailbox but never send from it, or work with a calendar but never touch the email on that account. I think that matters a lot as we hand more of our lives to these agents. Least privilege applies to “which mailbox” too, not just to which process. One detail I’m happy with is attachments. Passing file contents through an LLM as base64 is a terrible waste of context, and the models aren’t great at it anyway. So RockBot’s MCP bridge handles attachments itself. Files live on a shared volume, and the model just refers to them by path. Small files get inlined to Adjutant, large ones get uploaded out of band, and incoming attachments land on the shared volume where the agent (or a Python script it runs) can work with them. The bytes never go through the model. ## Scheduling Meetings Scheduler is one of the newest pieces. Scheduling a meeting with people outside your own organization is still a mess. The usual answer is either a lot of email back and forth, or some tool that wants to read everyone’s calendar. Most people (rightly) won’t share their calendar with a random service, and most companies won’t allow it anyway. Scheduler never reads anyone’s calendar. The organizer (or their agent) proposes a handful of times that already work for them. Everyone invited votes on each time - preferred, yes, if necessary, or no. They can vote from their own MCP-capable agent (Claude, Copilot, RockBot, whatever), or just from a web page linked in the invitation email. Each person’s own agent checks their own calendar. The server only ever learns the votes. This is where Adjutant and Scheduler really work together. When I ask RockBot to set up a meeting: 1. RockBot uses Adjutant to find times that are open across all my calendars 2. It proposes those times through Scheduler 3. People vote 4. Once a time is picked, RockBot creates the real meeting in my calendar via Adjutant, and tells Scheduler it is done And it works the other way around too. When someone invites _me_ through Scheduler, RockBot can find the invitation email with Adjutant, check each proposed time against my calendars, and vote for me. > Neither one needs the other. Scheduler works with any calendar MCP server, and people without an agent at all can just click the link in the email. But together they cover the whole loop. A couple of newer MCP features come into play here too. Scheduler can ask questions in the middle of a tool call (like “you didn’t give me a time zone”), and RockBot’s bridge hands those questions back to the agent, which can answer from what it knows or ask me, and then resume the call. And each Scheduler event is an MCP resource RockBot can watch, so it finds out when everyone has voted without having to poll. RockBot runs headless, so it connects to Scheduler with a personal access token rather than an interactive OAuth sign-in. I’ve scheduled a number of meetings this way now, and it saves me a lot of time and effort. I don’t have to manually look through all my calendars to find open times from work, family, etc. because Rockbot does that via Adjutant. And the login process for using Scheduler (via the web) for everyone else is _so_ much simpler than a lot of other tools, because I’m not trying to sell anything or collect their info - I just want them to login (via oauth) and vote. Or use their own agents to do the voting. ## Files and Code For files I’m using a community OneDrive MCP server, running as two separate instances - one signed into my Marimer account, one into my personal account. Two instances means two completely separate sets of credentials, and neither server knows the other exists. I did add a guard in the RockBot MCP bridge for this one. When RockBot downloads a file, the bridge only allows the target directory to be under the shared volume. The model doesn’t get to decide to write files just anywhere. For GitHub I use my own mcp-github server, which exposes the GitHub REST API as MCP tools. The GitHub App credentials live only inside that container. RockBot can read repos, work with issues and PRs, and pull file contents (which come back through the same attachment mechanism, so a big file doesn’t blow up the context window). ## Everything Else The rest of the list is smaller, but each one earns its place. The todo server is just a persistent to-do list with due dates and recurrence. Not glamorous. Really useful. OwnTracks is newer. I run an OwnTracks recorder in the cluster, and an MCP server in front of it, so RockBot knows roughly where I am. That helps with things like time zones when I travel, and whether “tomorrow morning” means home or a hotel. I went into the details in RockBot Can Know Where You Are (If You Want It To). Right now I’m just having Rockbot use my location data when I ask, but in the future I anticipate being able to use geo-fencing and other spatial capabilities to make Rockbot even more useful and proactive. The research agent and advisor council are both RockBot agents in their own right, but they are exposed to my main agent as MCP servers, each with one tool. They can take a while, so they run as long-running MCP tasks - RockBot kicks off the work, keeps chatting with me, and picks up the result when it is ready. The advisor council in particular tends to need more context (“how much risk are you willing to take here?”), so it uses the same question hand-back as Scheduler. And then OpenRouter, Azure Foundry, and an introspection server let RockBot look at itself: what models cost, how much credit is left, how its own memory is doing. Which is a little weird when you think about it too hard, but it is very handy for keeping an eye on spending. ## Least Privilege All the Way Down OK, so why all these separate services instead of one big agent with a bunch of plugins? Because of secrets. One of the core ideas behind RockBot is that the agent shouldn’t have access to any secrets other than its LLM keys. Everything else - the Microsoft and Google OAuth tokens, the GitHub App key, the OneDrive tokens, the Scheduler access token - lives in the MCP server that needs it, in its own container. Adjutant, Scheduler, and OwnTracks even get their own Kubernetes namespaces. If the agent gets confused, or gets prompt-injected by some email it is reading (and it _will_ read hostile email, that’s what email is these days), it can only do what the tools allow. It can’t go grab a token and use it some other way, because it never had the token. This is the same thinking we’ve been applying to n-tier apps for decades. You don’t put database credentials on the client PC. You put them on the app server. MCP servers are just the app servers for agents. > This is also why, when I looked at whether RockBot needs UTCP, I came down on the side of keeping a trusted server in the middle rather than having the agent call APIs directly. > All of this runs on my home Kubernetes cluster, with Rancher Fleet deploying from git, and Tailscale for the few things that need to be reachable from outside. That’s a whole other blog post. There’s a nice side effect too. Because these are just MCP servers, they aren’t RockBot-only. The same Adjutant, Scheduler, OneDrive, and todo servers are registered in my MCP Aggregator, so Claude Code, Claude Desktop, and Copilot can use them from any of my PCs. RockBot connects to them directly inside the cluster, my other tools go through the aggregator. Build the service once, use it from whatever agent I happen to be in. ## Summary When I wrote the RockBot Band post in March, a lot of this didn’t exist yet. Adjutant was still calendar-mcp, and Scheduler, OwnTracks, and the research and advisor MCP servers weren’t there at all. Today RockBot can read and triage my email, see what’s on all my calendars, set up meetings with people who don’t share my calendar (or my employer), find files in OneDrive, and poke at GitHub. All without ever holding a credential other than its LLM keys. At the start of this journey I had ideas about a useful agent, but honestly it wasn’t something I relied on. As these features and capabilities have expanded over time, I find that I rely on my personal agent more and more. Especially for managing my calendars and schedule, as well as finding lost emails and files. If you want to dig in, the RockBot readme now has the whole ecosystem list, and there’s a Discord server if you want to chat about it. _This post was authored with the assistance of AI._
blog.lhotka.net
November 12, 2026 at 8:30 PM
Very true! And since I'm the primary creator of #rockbot, when it doesn't do something (or do it well) I just see that as a new feature or capability to add
November 12, 2026 at 9:29 PM
Looking at #utcp and whether it fits with the #rockbot ecosystem for #ai #agentic systems.

blog.lhotka.net/2026/11/08/D...
Does RockBot Need UTCP?
VP, Open Source Creator, Author, Speaker
blog.lhotka.net
November 9, 2026 at 4:48 PM
Does RockBot Need UTCP?
One of the things I enjoy most about the agent tooling space right now is how many people are trying new ideas. The Model Context Protocol (MCP) has become the default way to connect agents to tools, but it’s far from the only idea out there. One project that has caught my attention is the Universal Tool Calling Protocol (UTCP). I build and run several things that live in this space: RockBot (my agent framework and agent), an MCP aggregator, and AgentRegistry (a registry where agents and tool servers can find each other). So I took a serious look at whether UTCP belongs in any of them. The short answer for my projects: not right now. But working through UTCP’s ideas did inspire an improvement to RockBot, and I came away with a lot of respect for what the UTCP team is doing. ## What UTCP is UTCP starts from a smart observation. Many tools an agent wants to use already have perfectly good interfaces: REST APIs, command line tools, WebSockets, gRPC services. MCP asks you to put a server in front of each one so the agent can talk MCP to it. UTCP asks: why not just describe the existing interface and let the agent call it directly? So instead of a server, a UTCP provider publishes a _manual_. The manual is a JSON document that lists tools, each with: * a name and description * input and output JSON schemas * a _call template_ that says how to call the tool over its own interface: HTTP, server-sent events, streamable HTTP, CLI, WebSocket, a text file, or even MCP The agent reads the manual and then calls the tool directly. A provider can serve its manual at a well-known `/utcp` endpoint. A UTCP client can also point at an existing OpenAPI document and convert it into a manual automatically, which is a really nice touch, because it means a huge number of existing APIs are usable right away. Credentials (API keys, basic auth, OAuth2 client credentials) appear in the manual as `${VARIABLE}` references. The client fills them in from its own configuration. The project has actively maintained SDKs for Python, TypeScript and Go. It also has an MCP bridge in both directions, so it works alongside MCP rather than against it, and a “code mode” library that I’ll come back to. The core spec is still a draft RFC, so it’s a young project that’s still evolving. ## How it compares to MCP UTCP’s own comparison frames it as “direct” versus MCP’s “middleman” model. I think the more useful way to see it is that the two make different trade-offs, and each fits different situations. **Where UTCP shines:** * No wrapper server to build, deploy and keep running for every API you want to expose. * No extra network hop. * You can describe an API you don’t own, as long as it has a usable interface (or an OpenAPI document). * It’s simple. Writing a manual is much less work than writing a server. **What MCP offers that UTCP doesn’t aim to:** * **More than tool calls.** MCP has prompts, resources, elicitation (the server asking the user a question mid-call), sampling, tasks and notifications. UTCP deliberately focuses on calling tools. My own MCP servers use prompts, OAuth sign-in and mid-call questions, so I need those features. * **A server-side place for secrets.** With UTCP, the client holds the credentials, and the manual says where they’re sent. That’s part of what makes it simple, and it also means you need to trust the manuals you load. The UTCP RFC is upfront about this and recommends loading only trusted manuals. * **A large ecosystem.** MCP has a big head start in servers and client support. **The middleman has value.** UTCP’s design removes the server in the middle, and for many scenarios that’s a real win. For my scenarios, though, I find the server in the middle worth keeping. It reminds me of an old lesson from n-tier architecture. Back when client/server apps talked straight to the database, every client machine needed a connection string, and often the credentials to go with it. Moving to n-tier, with an application server between the clients and the database, meant the keys to the database lived only on the app server. No client ever saw them, and the whole system was more secure as a result. An MCP server (or an aggregator in front of several) plays the same role for agents. The agent holds a credential for the MCP server, not the keys to every API behind it. A central server is also the natural place for logging and tracing. Every tool call passes through one spot, so you can record who called what, with which arguments and what result, and connect it all with distributed tracing. When agents call tools directly, that record is spread across every client and every API. **Both protocols keep improving.** One thing UTCP’s early comparisons pointed out was that MCP was heavy and stateful. The 2026-07-28 MCP specification made the protocol stateless: no sessions, no initialization handshake, each request stands on its own, and any request can land on any server instance behind a plain load balancer. I think having projects like UTCP asking “does it have to be this complicated?” is healthy pressure for the whole ecosystem. ## RockBot RockBot’s tool system isn’t tied to MCP. At the core there’s a tool registry: each tool is a name, a description, a JSON schema and an executor. MCP servers, A2A agents, web tools, scripts and wisps all register into it. Adding a UTCP tool source would be easy at the basic level. I’ve decided not to, for reasons that are about RockBot more than about UTCP. **RockBot already has its own answer for large tool sets.** Some of the motivation for UTCP is handling lots of tools: too many for a model to choose from, and too much context spent describing them. Over the past year I’ve built a lot of RockBot machinery for that problem: * the model searches for tools and activates them per session * each tool gets its own typed definition, not a generic “call some tool” shim * markdown guides for each subsystem * caps that keep each request under the provider’s tool limit UTCP has its own pluggable tool search, but bringing UTCP tools into RockBot’s existing machinery would be a fair amount of work for tools I can already reach another way. **Security model.** RockBot follows a “nothing trusts the LLM” design, and the model can manage some of its own server connections. Since a UTCP manual says where credentials are sent, I’d need to keep the model away from adding manuals, which takes away much of the convenience. **I tried something similar.** RockBot once had a REST API gateway, which was a similar idea, and I ended up removing it in favor of putting everything behind MCP. That experience shapes my thinking here. ## The MCP aggregator The aggregator is where UTCP’s ideas fit best for me. Its job is to sit in front of many backend servers and present them as one MCP server, with tool search, typed wrapper tools and skills. A UTCP or OpenAPI backend would fit there nicely: read the manual (or OpenAPI document), present those tools as MCP tools, and make the calls from the server side. That combines the best of both. UTCP’s manual format makes it easy to describe existing APIs, and the server in the middle keeps credentials on the server and logs and traces every call in one place. Every MCP client gets the tools without knowing UTCP is involved. If I do this, I’ll probably start with OpenAPI import, since that’s where most of the APIs I’d want to expose are described today, and add UTCP manuals alongside it. I’d also stick to HTTP-style call templates, registered by an operator. I’ll build it when I have a specific REST API I want to expose. ## AgentRegistry This is the most natural fit of the three. AgentRegistry is deliberately protocol agnostic. It already lists A2A agents, MCP servers and ACP agents. It stores each one’s native description as metadata, and it doesn’t speak any of those protocols itself. Adding UTCP would mean one more protocol type and a small adapter, about the size of the ACP one. There’s also a fun twist: the registry already publishes an OpenAPI document, and UTCP clients can convert OpenAPI on the fly. So a UTCP client should be able to use the registry’s discovery API today, with no changes at all. That’s a nice demonstration of UTCP’s “use what’s already there” approach. If I add UTCP support, I’d follow the UTCP RFC’s own trust guidance: require HTTPS and an admin key to register a manual, and leave out CLI templates, since discovery in the registry is public. The main reason I haven’t done it yet is simply demand. Right now nothing in my own world publishes or consumes UTCP manuals. As the UTCP ecosystem grows, this is the first place I’d add it. ## Inspired by code mode The most interesting thing I found in the UTCP project is code mode. Instead of the model making one tool call at a time, with a full round trip through the LLM for each, the model writes a short script that calls tools as ordinary functions. The script runs in a sandbox, and only the final result goes back into the model’s context. It’s a clever idea, and the UTCP team made it work over MCP tools as well as UTCP ones. It addresses the same problem as RockBot’s _wisps_ , from a different angle. A wisp is a lightweight pipeline the agent can spawn for a multi-step task when it knows the steps in advance. Steps either call a tool directly (no LLM involved at all), or hand a tightly-scoped prompt to a small, cheap model. A five-step task that might cost 60-80K tokens as a subagent costs about 2-12K as a wisp. Comparing the two was useful, because each does something the other doesn’t. **What wisps bring.** The harness runs a wisp’s steps, rather than code the model wrote, which fits RockBot’s “nothing trusts the LLM” principle. Because a wisp is _data_ , RockBot can: * validate it before running anything * limit which tools it can touch * recognize when the model retries the same wisp, and learn from failures over time * notice when a tool it depends on has changed **What code mode brings: control flow that depends on the data.** A wisp is a straight list of steps. It can pass results from one step to the next and skip ahead on failure, but it can’t loop or make decisions. Take “search my email, then fetch each of the N messages that came back”. In code mode that’s a simple `for` loop. In a wisp, today, it needs a step handled by the small model, so tokens are back on the meter for purely mechanical work. Code mode made that gap obvious to me, and it inspired a fix that fits how wisps already work. I’ve opened an issue to add a for_each step to wisps. A direct step names a list from a previous step’s result, and the harness runs it once per item, with limits on item count and concurrency and per-item failure handling. A simple `when` condition may follow. Both stay declarative, so wisps keep everything that comes from being data, and gain much of what makes code mode so appealing. ## Where I landed | Can it use UTCP? | Should it, today? ---|---|--- RockBot | Yes, easily | Not for now. Its existing tool machinery already covers my needs MCP aggregator | Yes, as a gateway | Likely, starting with OpenAPI import, when there’s a real API to expose AgentRegistry | Yes, most naturally | Yes, once UTCP manuals show up in my world Code mode | Partly covered by wisps | Inspired a `for_each` (and maybe `when`) step for wisps UTCP makes a great point: wrapping every existing API in a server just so an agent can call it is a lot of ceremony. For my own projects I prefer to keep a trusted server in the middle, so the place I’d use UTCP’s ideas is inside the aggregator rather than in every agent. And code mode gave me a concrete improvement to RockBot that I wouldn’t have thought of otherwise. Thank you to the UTCP team for pushing on these ideas and sharing them openly. If you build agents, I encourage you to take a look at UTCP and its code mode library. Even if you stick with MCP, as I am, it’s well worth seeing a different take on the problem. I’ll be following the project as it matures. _This post was authored with the assistance of AI._
blog.lhotka.net
November 9, 2026 at 6:27 PM
RockBot's new location awareness feature brings human-like context to your AI assistant. Timezone tracking, city awareness, location history—all hosted on your own infrastructure. Optional, secure, and privacy-focused from the ground up. www.isaacl.dev/hdh #RockBot #AI
RockBot Can Know Where You Are (If You Want It To)
VP, Open Source Creator, Author, Speaker
www.isaacl.dev
November 5, 2026 at 11:00 PM
🟠 Rockbot is reporting a Partial Outage since 16:49 UTC

"Server Issue"

Affects: Rockbot Player, Rockbot Dashboard, Rockbot Remote App, +2 more

Live timeline → https://pingoru.io/providers/rockbot/incidents/12471909

#Rockbot #RockbotDown
Rockbot: Server Issue · November 5, 2026 · Pingoru
Rockbot incident on November 5, 2026: We
pingoru.io
November 5, 2026 at 5:06 PM
🟢 Update: Rockbot marked this resolved at 17:14 UTC.

Duration: 24m.
November 5, 2026 at 5:41 PM
Rocky Lhotka joins Carl and Richard to unpack RockBot, a .NET and Kubernetes powered AI assistant focused on strong security and controlled service access. Covers practical patterns for wiring agents to calendar and email with auditable boundaries.

#dotnet #csharp #kubernetes
.NET Rocks! - RockBot with Rocky Lhotka
bbb.dev
November 2, 2026 at 5:05 PM
Having recently switched #rockbot to use #claude Haiku 5.5 and found it better than Terra, I can confirm that cheaper models can be better.
Is the cheap model good enough? How to test a new model in your agent. https://jimbobbennett.dev/blogs/test-new-model-in-agent/ #ai #agents #models #tokens #performance #testing
hachyderm.io
November 5, 2026 at 1:56 PM
If you like the shirt, come check out my Etsy shop.

www.etsy.com/shop/RockBot...
November 3, 2026 at 4:08 PM
I decided to try running Claude Haiku 5.5 as my Balanced tier #ai model in #rockbot (vs Terra which I was using). Haiku 5.5 seems to work really well for this purpose - which is nice, given its cost.
November 3, 2026 at 5:28 AM
#rockbot can now keep track of your location; super helpful for those of us who travel a lot!

#ai #agentic

blog.lhotka.net/2026/11/01/R...
RockBot Can Know Where You Are (If You Want It To)
VP, Open Source Creator, Author, Speaker
blog.lhotka.net
November 1, 2026 at 4:30 PM
RockBot Can Know Where You Are (If You Want It To)
A personal assistant that doesn’t know where you are is missing something basic. Ask a human assistant “what time is my next meeting?” while you’re traveling, and they’ll answer in your local time without being told. Ask “where was I when that call came in yesterday?” and they can probably tell you. Until now, RockBot couldn’t do either of those things. RockBot now has an **optional** location awareness feature. It’s off by default, and if you don’t configure it, nothing about the agent changes. Same prompts, same tools, same behavior. But if you want your agent to follow you around, it can. ## What it does There are two levels, and you can stop at the first one. **The built-in level** gives the agent a rough sense of where you are: * The agent’s clock follows your time zone as you travel, while still remembering your _home_ time zone. * Every turn, the agent knows your last known city and when it was reported. It never gets precise coordinates at this level: just the city, or a rough area if you haven’t set up geocoding. * Scheduled tasks can be marked `local` or `home`. A morning briefing marked `local` arrives at 7am wherever you are. A task tied to office hours stays on home time. **The optional history level** adds an MCP server that lets the agent answer questions about where you’ve _been_ : * “Where was I yesterday afternoon?” * “How long was I at the office today?” * “When did I get home?” * “How far did I drive this week?” This level returns much more detail (street addresses, exact coordinates, full history), so it’s a separate choice. ## How it works, at a high level I didn’t want RockBot to depend on a big tech company’s location service. Google doesn’t offer a usable API for your own location history anyway. So the whole thing runs on open source pieces you host yourself: 1. **OwnTracks on your phone.** This free, open source app for Android and iOS reports your location in the background. You set it to HTTP mode and point it at your own server. 2. **The OwnTracks Recorder on your own infrastructure.** This small server receives the reports, keeps them on disk, and serves them back through a simple REST API. It runs fine in Docker or Kubernetes. Add an optional (free tier) geocoding key, and it turns coordinates into city names and addresses. 3. **RockBot pointed at the Recorder.** A couple of configuration values (the Recorder URL and your user name) turn the built-in feature on. 4. **Optionally, a location MCP server.** For the history questions, I’m using OwnTracksHermes, an MIT-licensed, read-only MCP server that sits on top of the Recorder. RockBot connects to it like any other MCP server. One important note: the Recorder has no authentication of its own. It belongs on a private network. I run mine behind Tailscale, so only my own devices can reach it. ## Regions: naming the places that matter The piece that makes this feel natural is _regions_. In the OwnTracks app you can define named places, such as “Home”, “Work”, “Gym” or “Cabin”. Each has a center and a radius. (The Android app calls them _Waypoints_ ; iOS calls them _Regions_.) When you’re inside one of those circles, every location report carries its name. And when you enter or leave one, the phone reports it right away. So instead of the agent working out that you’re at some street address, it simply knows you’re “Home” or at “Work”. It can tell you exactly when you arrived and how long you stayed. This also handles the case where “home” isn’t a single place. If you split time between more than one house, you just define a region for each one. The place definitions stay on your phone, not in the agent’s configuration. ## Privacy is your call Location is personal data, so the design leans toward you being in control: * It’s entirely opt-in. Nothing happens unless you set it up. * Everything runs on infrastructure you own. Your location history never goes to a third-party service, other than the optional geocoding lookups. * The built-in level only gives the agent your city. * The history level gives full detail, and you decide whether to turn it on at all. ## Getting started The full setup guide, including phone settings, Recorder deployment, RockBot configuration, the MCP server, regions and troubleshooting, is in the RockBot documentation: **User location on rockbot.dev** If you’re new to RockBot, start at rockbot.dev. The source is on GitHub. _This post was authored with the assistance of AI._
blog.lhotka.net
November 1, 2026 at 6:06 PM
Yes, that was me who troll requested Not Like Us by Kendrick on Rockbot at Planet Fitness after seeing a Drake song get played.

Let this be a lesson to that thief of joy.
Thor: Because That's What Heroes Do
Alt: Thor: Because That's What Heroes Do
static.klipy.com
October 28, 2026 at 5:50 PM
🟠 Rockbot is reporting a Partial Outage since 21:58 UTC

"Server Issue"

Live timeline → https://pingoru.io/providers/rockbot/incidents/12439936

#Rockbot #RockbotDown
Rockbot: Server Issue · October 25, 2026 · Pingoru
Rockbot incident on October 25, 2026: We
pingoru.io
October 25, 2026 at 10:03 PM
🟢 Update: Rockbot marked this resolved at 22:05 UTC.

Duration: 7m.
October 25, 2026 at 10:13 PM
🚀 New Remote Job Alert!
💼 Position: Strategic Enterprise Sales Director
🏢 Company: Rockbot
🌍 Location: USA
📁 Category: Sales & Business
#RemoteJobs #RemoteWork #WorkFromHome #Hiring #JobOpportunity
Apply now: https://www.remote-work.app/job/rockbot-strategic-enterprise-sales-director-remote
October 13, 2026 at 1:15 PM
🚀 New Remote Job Alert!
💼 Position: Tier 2 Technical Support Specialist
🏢 Company: Rockbot
🌍 Location: USA
📁 Category: Customer Service
#RemoteJobs #RemoteWork #WorkFromHome #Hiring #JobOpportunity
Apply now: https://www.remote-work.app/job/rockbot-tier-2-technical-support-specialist-remote
October 13, 2026 at 1:10 PM
October 13, 2026 at 12:30 AM
🎯 Tier 2 Technical Support Specialist
🏢 Rockbot

Get matched to remote gigs the minute they post: gigsniper.net

#RemoteJobs #Hiring #RemoteWork #TechnicalSupport #FullTime
Tier 2 Technical Support Specialist
Rockbot · via Jobicy · Apply now — found by GigSniper
jobicy.com
October 13, 2026 at 4:31 AM
🎯 Strategic Enterprise Sales Director
🏢 Rockbot

We match remote jobs to your keywords in real time: gigsniper.net

#RemoteJobs #Hiring #RemoteWork #Sales #FullTime
Strategic Enterprise Sales Director
Rockbot · via Jobicy · Apply now — found by GigSniper
jobicy.com
October 13, 2026 at 12:01 AM