Ignacio Borrell

Really cool niche product. The automatic furigana annotation alone would save so much time for anyone reading Japanese content above their level. Being able to go from a raw PDF to an audiobook in one step is a killer feature for commuters studying Japanese. Do you plan to expand this to other CJK languages like Chinese or Korean in the future?

The hydration battery concept is such a clever way to gamify something as simple as drinking water. And the fact that it adapts to activity levels and weather without sending anything to the cloud is impressive. I always forget to drink during long work sessions so the ADHD friendly design resonates. Is there Apple Watch support for quick logging without pulling out the phone?

The pay per minute model is really smart, way better than yet another subscription for something you might only use when traveling. Preserving the actual voice tone is what makes this feel like a real conversation instead of talking through a robot. Curious, does it work well in noisy environments like airports or crowded streets?

Splitting planning, review, and shipping into separate slash commands is a great design choice. We've seen the same pattern in our own agent workflows: a single generic session trying to hold architecture context while also line-editing code always degrades quality on both fronts. How does GStack handle state handoff between skills? For example, if /plan produces a spec, does /ship...

The no-edit Friday report is a brilliant forcing function. Most accountability tools fail because founders can reframe their own narrative before sharing — removing that ability to spin is what makes this actually work. As a 3x YC founder, what's the most common pattern you've seen where founders set goals that feel productive but actually don't move their North Star? Would love to hear what...

The shift from "inbox zero" to "inbox clarity" really resonates. As someone who gets buried in a mix of transactional emails, newsletters, and actual conversations, the automatic signal-from-noise separation is exactly what's missing in most email clients. How does the AI categorization handle edge cases like transactional emails that are actually important, such as a Stripe payment failure...

The separation of planning, review, and shipping into distinct slash commands is a smart design choice. We've seen the same pattern in our own agent workflows — a single generic session trying to hold architecture context while line-editing code always degrades quality. How does GStack handle state handoff between skills? For example, if /plan produces a spec, does /ship automatically pick up...

This is exactly what on-call engineers need. The gap between "alert fires" and "understanding what actually broke" is where most incident response time gets wasted, and automating that correlation across logs, metrics, and traces is a huge win. How does Struct handle alert deduplication when multiple monitors fire for the same underlying issue? Does it group them into a single investigation...

Love the idea of removing all the DevOps friction from running AI agents. The $3.99/mo price point is impressive for a dedicated container with full terminal access. Curious about data persistence — if I'm running a background workflow that builds up state over time (like a market scanner), does the container's storage persist across restarts, and is there a storage limit?

Congratulations on the launch! Really love the minimalist approach, it's refreshing to see a dev tool that just works without all the bloat. Quick question: does it support custom card decks beyond the standard Fibonacci sequence? Some teams prefer T-shirt sizes or custom scales for different types of estimation.