Ramya Chinnadurai 🚀

Want your web app on your phone? You may not need a separate mobile app. When a non-tech friend asks me for a mobile app for personal use, - I often suggest this instead of building a separate mobile app. - It opens like an app from the home screen. - It won't match a native app for every feature, but for a simple personal app it's often enough. Android (Chrome): 1. More > Install 2. Create shortcut, 3. then Install (or Create shortcut) iPhone (Safari): Share > Add to Home Screen > Add. To make your web app ready for both, copy-paste this prompt: "Make this web app installable on phones (PWA). Manifest with name, start_url, display standalone and the icon sizes Android needs, plus an apple-touch-icon for iPhone. Service worker that caches the main screens so they load offline. Optional: an Install button using before install prompt, only where the browser supports it iPhone has no install prompt, so show a small hint: tap Share, then Add to Home Screen, If you add push, on iPhone only ask after it's opened from the home screen and the user taps a button. Check the Manifest in Chrome DevTools (Application tab) and fix what it flags. Use Lighthouse for performance and best practices only."

Small milestone, big motivation! Our first flight booking went through @heyula_ai.. 2 flights, Germany to Asia, $1000+ and it worked on the first try. We also crossed 100+ public sign-ups, on top of 500+ friends and family who already tried Ula. From a temple ticket to real flights in few days 🥳 Still early and still waitlist only, but we're just getting started!

Try this prompt for a security audit: "Install Cloudflare's security-audit skill and run its full audit workflow on this project. Independently verify every finding before you report it. Read only, no fixes yet. Group what's confirmed by severity and stack layer, and clearly label anything you couldn't check." It walks the agent through 6 phases: - map the codebase, - hunt, - challenge each candidate, - record, - verify, - then report. So you get what's confirmed, rejected or still unverified, instead of a scary list of maybes. I ran it on @heyula_ai last night and as a result: ✓ 𝟬 critical ✓ 𝟬 high ✓ 𝟬 medium ✓ 𝟱 low + 𝟴 info, none confirmed exploitable Next: CSP in report-only, and the same bot check on every public form.

I tried to let @heyula_ai pay for an experience on its own. It got all the way to the payment page and died there 😅 Ula is our AI travel companion, it plans and books family trips. The planning part works. The booking part works, up to the moment money has to move. Then it needs a human. We tried a lot of routes over the last few weeks: 1. Plain cards. A card checkout expects a person. The OTP goes to your phone, not to the agent, and the bank's fraud checks are trained on human sessions. 2. Visa agent tokens. Live in the US and Europe, rolling out to Asia Pacific through partner banks. No bank in the market where we're launching first yet. 3. Mastercard agent tokens. There was one authenticated demo with local banks earlier this year, in a controlled setup. Nothing a small team can integrate today. 4. Some other payment APIs we looked at don't support agents at all yet. So the rails are too early for where we launch first. Agent payments on the local payment rails are being worked on, but still waiting on approval as far as I know. Here is how Ula works now: 1. Ula plans the trip and fills every form, [hotel, train, the kids' details], all of it. 2. It stops right before payment and shows the exact price. 3. You tap approve on your phone and pay with your usual method. 4. Ula confirms the booking and adds it to the itinerary. Every single payment gets one tap from a human. Honestly this started as plan B. Now I think it's the right default for family trips anyway, you want to see the final price before anyone pays for a hotel.. I'm watching the card networks and the local agent payment work closely. The day a bank here supports agent wallets with a limit per merchant, Ula will use them.

We applied to YC (@ycombinator) yesterday.. and a16z (@speedrun).. and PearX for @heyula_ai 😅 Honest confession.. I didn't write a single answer. My cofounders did all of it while I was busy building. Hey Ula is the AI travel companion we're building for families. It plans the trip, books it, and waits for your yes before it pays. A few weeks ago Ula booked its first real ticket, a temple visit for my own family. It logged in, found the open slots, filled the form from the details it had saved, showed me the exact price and waited. Then the ticket just showed up in our trip documents. That's the thing they had to explain in a few hundred words. I've rewritten "what does Ula do" so many times myself, so I know how hard that is! Now we wait. Speedrun says 4 to 6 weeks. Whatever the answer, we keep building. Families still plan trips with multiple tabs open and that's what we want to fix. Fingers crossed 🤞

How secure is @heyula_ai vault? We keep on getting this question. So thought to share a few things on how we built the vault.. An agent that books trips needs passports and IDs. That scared me too, because it's my own family's documents first. So the rule we started with: the agent can use your IDs, but it can never read them. 1. Lock before save. IDs get locked on your own phone before they're stored anywhere. 2. Only the user holds the key. It unlocks with your Face ID, fingerprint or phone PIN. Not even Ula can open it. 3. Nothing unlocks without a yes. The vault stays shut until you approve that booking. 4. Release only what's needed. Booking your dad's ticket? Only his ID comes out, the rest stay locked. 5. Copies expire. That one ID goes into the form for 15 minutes, then the copy is deleted. 6. Money needs its own tap. Ula shows the exact price and waits for you to approve. Still adding more as families start using it, like checks before anything gets shared with a new site.. will share those too! If you're building an agent that touches personal documents, bookmark this for later.6. Money needs its own tap. Ula shows the exact price and waits for you to approve. We tried all of this first on our own family's booking this week.. Ula filled the form, showed the price and just waited for my tap before paying. If you're building an agent that touches personal documents, bookmark this for later.

I created FREE directory for startup grants and investments. I kept looking for them while building @heyula_ai, and every time one had already expired or I found it too late. So I put them all in one place, and it keeps updating as new ones get posted. November deadlines still open: • a16z speedrun - nov 1, up to $1m + $10m+ in credits • yc w2027 - nov 2 at 8pm pt, $500k • era nyc - nov 2, $150k, 4 months in nyc • nsf america's seed fund - nov 4, full proposal (phase i up to $305k) • techstars spring 2027 - nov 18, $220k • thiel fellowship - rolling, $250k So I put them all in one place, and it keeps updating as new ones get posted. over 2 years, 22 and under • z fellows - rolling, $10k for one week

Wooh 1st success for @heyula_ai Ula successfully booked its first temple ticket for Tirupathi. - It triggered OTP, logged in and showed the open slots - Filled the form from my saved details ( vaults ) - Showed the exact price before doing anything. I tapped approve, paid inside Whatsapp using UPI, and ticket landed in my trip documents. Just converted the screenshots into video using claude for demo. Join our waitlist and will open spots quickly.

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