u/Fine_Factor_456

i made these changes on nanobot’s codebase today and this came from a very simple frustration

chat works great… until it doesn’t

you ask something → you get an answer → conversation ends

and then what?

there’s no sense of:

• what the agent has been doing
• what changed over time
• what’s running in the background
• what’s coming next

everything just lives and dies inside messages , i kept hitting this again and again

so instead of trying to be more consistent or check more often, i decided to change the system itself

what i wanted was simple: something that keeps running even when i don’t
something that shows me what’s happening without me asking

so today i built a web UI that acts like a second brain for the agent

not replacing telegram that’s still the main interface
this just sits alongside it

here’s what’s in place now:

• shared workspace → tasks live here, i add things, agent picks them up and executes
• recent activity → shows what the agent is actually doing over time (not just replies, actual work like tasks, reports, notes)
• cron job viewer → finally visible what’s scheduled, running, paused (this used to be completely hidden)
• auth + channel config → setting things up from UI instead of doing everything manually
• pixel 3D office (first person view) → experimental, but you can literally walk inside the workspace (models are still very basic)

so now it feels more like:

telegram → input
agent → runs in background
web UI → shows state (second brain)

today was only frontend

nothing is wired to the backend yet, so everything you see is just structure for now

i’ll be integrating this with nanobot tonight so it actually starts reflecting real activity

more like something that keeps running alongside me whether i’m there or not

take a look if you want : agent-desk

i made these changes on nanobot today and this is one of those days where nothing looks different from outside, but internally everything shifted. until now, everything was happening through telegram and that’s still the main interface, but i kept hitting this gap once the conversation ends, everything kind of disappears. there’s no persistent layer where you can actually see what the agent is doing over time. so instead of trying to fix my behavior again, i built something around it.

what i wanted was simple: a second brain that keeps track of everything without me needing to constantly ask.

so now there’s a web UI that sits alongside telegram, not replacing it, just making everything visible and structured.

here’s what’s in place right now:

• dashboard → shared workspace where tasks live, i can add things and the agent can pick them up and execute
• recent activity → probably the most important part, shows what the agent is actually doing (completed tasks, generated docs, notes, assignments) and you can open anything to see full details
• cron job viewer → all scheduled jobs in one place, what’s active, paused, when it runs next (this used to be completely invisible)
• channel/auth layer → users can connect and configure things from the web instead of doing everything manually
• pixel 3D office (first person view) → yeah this is experimental, but you can actually walk inside a workspace with agents, desks, screens… models are still basic but structure is there

telegram is still where everything starts commands, quick checks, fast interaction. the web UI is just the layer where everything lands and stays. so now it’s more like:
telegram → input
agent → runs / executes
web UI → shows state (second brain)

today was just frontend. nothing is wired to the actual backend yet, so it’s all static for now. later tonight i’ll start integrating this with nanobot’s codebase so the activity, tasks, cron, everything becomes real.

this is starting to feel less like a bot and more like a system that just keeps running in the background whether i’m there or not. still rough, still early, but yeah… day 2.

curious what you guys think about this direction

if you guys wanna take a look at UI only here it is : second-brain