Just applied to @HF0 W27 with @heyula_ai 🤞 Got this card at the end of the application and I can't stop looking at it 😅 "One bot journeys many roads" is pretty much what we want Ula to be for families planning trips together

Thanks for the interest. 1. Go to - heyula.ai 2. Just tap, message ula. 3. It will ask for your whatsapp number. And you can join immediately to the waitlist.

50+ signups on the @heyula_ai waitlist 🥳 Almost half of them came in the 2 days since our launch post. Honestly didn't expect this much love for a travel planner we started building for our own messy family trips. Thank you to everyone who commented ULA, reposted and shared it. It means a lot to us. Now back to building..

Launching my new product, @heyula_ai 🥳 - Ula is an AI travel companion right inside your messaging app. - Ula understands your travel preferences. - Helps plan personalised trips. - Remembers what you save. So that you don't have to start from scratch every time. Travelling with a toddler is messy enough. Planning it shouldn't be.

I planned our last family trip with 12 tabs open. Never again. If you travel with a toddler, you know. Trains that don't clash with nap time. Hotels that actually have a cot. "Is this place okay with a 2 year old?" Reviews, maps, prices, again and again. And at the end, one spreadsheet nobody else opens 😅 This year I was already deep into AI agents. Building them, breaking them, spending days just fixing memory. That's when it clicked. If an agent can remember how I work, why can't it remember how my family travels? So we're building Hey Ula. You message it like a friend on WhatsApp. Tell it where, when and who's coming. It comes back with a few options that actually fit, not 50 links. It remembers what you like for next time. Built with my co-founders, tested on our own messy family trips. Waitlist opens today. Comment "ULA" and I'll DM you the link 👇 (follow so I can DM you)

I hid almost all my bots yesterday. 😅 For the past few months, I've been building my bot team on Grok Bot. Every time I had a new job, I added a new bot. Support bot for each product, SEO bots, a research bot, a growth bot, a dev pair, a watchdog. I ended up with 30+ bots, all in one chat list. Everything was fine until last week. Every bot started asking me something at the same time. Questions, approval cards, "can you check this", one after another. Each bot thought its question was the urgent one. I was answering bots most of the day instead of building. My own bot team became my biggest distraction. --- The Fix: A Head Bot for Each Product Instead of talking to every bot, I've now set it up like a small company: 1. Chiti is my main bot I talk to Chiti and the head bots, nothing else. Everything else is hidden from my sidebar. 2. One head bot per product Each product has one head bot. Only the head bot talks to that product's support, dev and SEO bots. If they need me, it goes through the head bot. 3. One task at a time On Oct 16 I told Chiti this rule. Bots don't push questions at me anymore. Chiti collects them and brings me one at a time. 4. Separate everything Each product has its own Chrome profile and its own Claude account, so bots don't mix up logins. --- The Execution: The dev bots work as a pair. Claude Code writes the feature, Codex tests it and fixes the bugs. A watchdog bot checks my main service every 30 minutes and tells Chiti if something looks off. Support bots draft inbox replies and I read them before anything goes out. Feels weird seeing my chat list this empty. A few days in and I'm not jumping between chats all day anymore. Hoping this holds up when things get busy! I'll share more on how it works as I go. If you're running more than a few agents, I'd love to know how you keep them from all talking to you at once.

Grok bot has a computer inbuilt, when needed i just take over it. I use grok bot app.

Claude Code in one terminal, Codex in another, two Claude accounts, and no idea which session was logged in where. T3 Code put all of it in one window. → Claude Code, Codex, Cursor and Grok in one model picker → Multiple Claude accounts side by side. Tweetsmash account and personal account, one click apart → Every session gets its own git worktree, so parallel agents never touch each other's files → Diff, commit, push and open the PR without leaving the app → Phone app connects to the session on your Mac, so the agent keeps working when you step away Open source. It wraps the CLIs you already use, so no new subscription. If you're like me and recently got Claude startup credits on a new account, but still want to use your existing Claude plan, this is the easiest way to run both without logging in and out. The catch: it is still pre-1.0. Expect rough edges. The real upgrade is not a better model. It is one place to run all of them. t3.codes

Never deleting this app. 7 days stuck in Play Store review. 31 minutes to get a reply from Google's CEO. The fastest support ticket in tech is still a public post.

AI answers are too long to read. Stop asking for text. Karpathy's fix is a ladder of output formats, each one easier to absorb than the last: 1. Strict English. Ask for "80% of the way to ASD-STE100", the writing spec for aerospace maintenance manuals. About 900 approved words, max 20 words per instruction, active voice only. Dense answers become readable. 2. A diagram. Ask for a picture instead of paragraphs. You see what connects to what in seconds. 3. A web page. Ask for the answer "in HTML". You get something you can click, filter, copy from and share. 4. An explainer video. "Create a 3b1b style video explainer on X." Narrated, animated, made for an audience of one. 5. The real shift: as agents do more of the work, your job moves to reviewing and understanding it. Custom throwaway apps and videos are now cheap enough to build for a single question. Two of these already run my week with Chiti: -> Anything I paste into another tool arrives as an HTML page with a Copy button. Copying from the terminal once dropped characters into a live post. -> Analysis-sized answers come as a narrated video. macOS voice, headless Chrome, ffmpeg. $0 for audio, about 2.8k tokens to script 14 slides. Reading more was never the bottleneck. The format was.