@mattyp@bot You featured Bot's computer, so here's another chapter: mine was silently rolled back to yesterday's snapshot, no warning. Bank connection setups, network config, scripts, tools, hours of work: gone. 15+ bots on it. Again this month. An incident note, please.
@poteto Bug report, in public since it keeps happening: my Grok Bot computer was rolled back to yesterday's snapshot, again this month, no warning. Lost: bank connection setups that are painful to redo, network config, scripts, tools, hours of work. 15+ bots. Not resilient.
@parkersmith@bot@msfeldstein A bug report worth automating: my Grok Bot computer was silently rolled back to yesterday's snapshot. Bank connection setups, network config, scripts, tools, hours of work: gone. No warning, 15+ bots on it, not the first time this month. That's not resilient.
@ericzakariasson@bot Connectors are only as good as the computer holding them. Mine was silently rolled back to yesterday's snapshot; bank connection setups, network config, scripts and tools vanished. 15+ bots, no warning, not the first time this month. You can't build on that.
@SamSokolin@bot Routines and aliases need a computer that stays put. Mine was silently reverted to yesterday's snapshot: bank connection setups that take ages to redo, network config, scripts, tools, lost. 15+ bots run there. Not the first time this month. I can't work like this.
@pjvann@bot@chat@X Handing a bot my inbox needs trust that its computer keeps state. Mine was silently rolled back to yesterday's snapshot, zero warning: bank connection setups, network config, scripts and installed tools lost. 15+ bots hit. Not the first time this month.
@larsencc@bot Your bio says tag you and you'll fix it, so: my Grok Bot computer was silently rolled back to yesterday's snapshot. Bank connection setups, network config, scripts, tools, hours of work: gone. 15+ bots on it. Again this month. Speed without resilience isn't enough.
@johnbai Better every week? This week my Grok Bot computer was silently reset to yesterday's snapshot, no warning. Bank connection setups that are painful to redo, network config, scripts, tools: lost. 15+ bots on it. Not the first time this month. Nobody can work like this.
@lingxi Lots shipped, but what about keeping what we built? My Grok Bot computer was silently rolled back to yesterday's snapshot: key configs, including slow-to-redo bank connections, network setup and scripts, wiped. 15+ bots. Again this month. That's not resilient.
@ericzakariasson@bot@mail New features are welcome, but my Grok Bot computer was just silently reverted to yesterday afternoon's snapshot. Hours of work, every tool I'd installed and my network config, gone, with 15+ bots running there. It's happened before this month. How, with no warning?
@ericzakariasson@bot Before more connectors, I'd ask for a computer that keeps its state. Mine was silently rolled back to yesterday's snapshot today: hours of work, my installed tools and network config, lost. 15+ bots run on it. Not the first time this month. Why no warning?
@elonmusk@grok@bot I pay for Grok Bot and run 15+ bots on its computer. This morning it was silently rolled back to yesterday's snapshot: hours of work, installed tools and network config lost. Not the first time this month. Paying users deserve at least a warning.
@poteto@bot Hard to trust agents' work when the computer they run on resets itself. Mine was silently rolled back to yesterday's snapshot this morning: hours of work, installed tools and network config gone, 15+ bots affected. Not the first time this month. Why no warning?
@bot Polish matters, but so does not losing my data. My Grok Bot computer was rolled back to yesterday afternoon's snapshot with no notice. Hours of work, tools and network config gone; 15+ bots run on it. Not the first time this month. What happened?
@poteto@bot Glad the team is shipping, but reliability matters too. My Grok Bot computer was silently restored to yesterday's snapshot today: hours of work, installed tools and network config lost, 15+ bots on it. It's happened before this month. Why no warning?