Tots: long-lived bots on mobile with a name, role and memory, plus teams (Grok Bot / Duet style)

[SamarpitSantoki]

The problem

T3 Code is great for coding sessions, but on my phone I mostly want something different: a few long-lived agents I talk to like teammates. For example "a PM for project X", "a reviewer" or "a T3 helper". Products like Grok Bot, OpenAI Dots and Claude Duet work this way, but they are closed and not tied to my own server and code.

Today on T3 Code mobile I can do this by hand: start a thread, paste a role prompt, and keep coming back to it. But the app treats it as one more coding thread. It has no name or face, no memory between threads, no way to group agents into a team, and the replies read like terminal reports.

The idea

A "bots" layer on the mobile app that uses only what the T3 Code server already has:

• A bot is a normal T3 Code thread. Its first message is a setup message with a name, a role, an emoji and a color. Because the setup message lives on the server, the server stays the source of truth. The app finds bot threads on the server, and agents can make new bots with t3_thread_launch.
• Main chat and fresh threads. Each bot has one continuous main chat. You can also start a new thread with the same bot.
• Memory. Each bot keeps a small memory file on the server, so all its threads share preferences and context.
• Teams. A lead bot hands out work to teammates with t3_thread_send. The team chat merges their threads, and bot-to-bot messages show as cards ("Lead → Reviewer").
• Chat-first UI. Bots talk like a teammate texting, not like a log. The Chats list has unread dots, pin, swipe to settle or hide, and search.
• Scheduled routines. These use the existing scheduled tasks (for example, a morning brief).

It needs no server or contract changes. All of it is in apps/mobile.

Working prototype

I built this as Tots, an unofficial fork, to try the idea, and I use it now with about 7 bots:

• Demo video: https://x.com/SamarpitSantoki/status/2115647812171952549
• Branch: https://github.com/SamarpitSantoki/t3code/tree/tots
• Code: apps/mobile/src/features/bots and apps/mobile/src/features/tots
• Build notes: README-TOTS.md

I know it is far too big for one PR, and that the UI choices are opinionated. I'm not asking you to merge the branch. I'd like to know if any part of this direction fits T3 Code. If it does, I'm happy to split the parts you want into small, focused PRs. Some examples:

1. Let a thread carry an optional "persona" (name, emoji, color) that clients can show.
2. Show agent-to-agent messages (t3_thread_send) as their own message type, not as user messages.
3. A mobile "agent view" for one continuous conversation (related: Agent-first view: one continuous conversation per project, sessions hidden #24351).

Feedback on the direction is welcome, including "not for T3 Code".

Built with Claude (Opus 5.5) in T3 Code.