... solo founder from Italy, I create tools to fight manual data entry. Everyone's trying to manage data, but who's actually entering it? Doing it manually is a destructive activity. I've been waging this little personal crusade, looking for environments where data collection and entry

... Kashika, a business student at Northeastern University studying marketing. I just launched Ledger & Lore , a free, sourced database documenting why 194 startups actually failed, spanning 22+ countries and industries from fintech to biotech to retail. Each entry includes funding history, investors, a sourced explanation of what actually went wrong, a timeline, and a plain-language lesson, built to be a genuine alternative

... myself. It didn't feel like a "product" until I picked my own graduation year and had that same "wait, seriously?" reaction about six times in a row. That's when it became worth building properly, hand-verifying entries, organizing by subject, letting people pick their own year instead of just mine. The hardest part honestly wasn't the build, it was the verification. Every entry

... Been tracking pricing across the major agents and the thing nobody puts on the landing page is what happens when you actually use the tool heavily . The advertised price and the real price diverge fast. The entry tiers look deceptively similar. Cursor Pro and Claude Code's entry

... When we first built Murror, we stored every journal entry forever. More data meant better emotional pattern detection, smarter insights, richer reflections. Our AI kept getting better. Our users kept getting quieter. We dug into the data. Users who'd been on the app for 3+ months were writing shorter entries

... active-state styles in split view, and command palette extension view design; - RTL layout : cleaner alignment for right-to-left languages; Bug Fixes: - Type-to-search : fixed quick search not activating on non-Latin keyboard layouts; - Directory loading : fixed entries reordering after a directory finishes loading; - Custom icons : fixed custom icons loading with a noticeable delay; - Grid cards : fixed grid layout cards changing size while loading; - Grid scrollbar : fixed the grid scrollbar hiding behind sticky headers; - Quick selection : fixed quick ... ... file selection sometimes opening the file; - Terminal shortcut : fixed `Alt+T` opening a terminal for the current directory instead of the selected entry

... Last month I pulled our engagement data expecting to celebrate. Daily active users up. Session length up. Entries per week up. Every growth chart pointed right and up. Then I read what our most active users were actually writing. One user was journaling 6 times a day. Not because they were building a healthy reflection habit they were spiraling. Writing the same anxious thought over and over, looking for the AI to say something that would make it stop ... ... question most product teams never face: what if our best engagement metrics are a sign that something is going wrong? So we made changes that would horrify a traditional growth team: We added gentle cooldown prompts after the third entry

... months ago we added a pause to Murror. After you finish a journal entry, the AI waits. No instant analysis. No immediate insight. Just a small animation and 8 seconds of silence. Our engineer thought it was a bug when he first saw the spec. "You want me to add... a delay?" Yes. On purpose. Here's why. We ran an experiment: instant AI response vs

... help the attention switch land on the right thing. But I quickly realized: what I can do is only the physical switch the pane, the click, the jump. The other thing you're pointing at the cognitive re-entry, actually getting your mind back into the previous context I haven't found a good answer for yet. And honestly, I think this vibe coding mode we're all in makes it worse. We're context-switching between tasks constantly ... ... this globally in CLAUDE.md one line there and every project inherits it, no per-project prompt editing needed. Still opt-in, but at least you only opt in once. That said, you're right that "agent leaves a re-entry

... When we first built Murror, our AI would automatically surface emotional patterns after every journal entry. "You've mentioned feeling anxious about work 4 times this week." "Your mood tends to dip on Sunday evenings." Users loved it in demos. They called it "impressive" and "insightful." Our internal metrics looked great -- pattern detection accuracy was 87%. But something was off. People were journaling less over time, not more. After two weeks, entries

... three months, the #1 feature request in Murror was "let me share my journal entries with my partner." It made perfect sense. Murror helps you understand your emotions and relationships. Sharing seemed like the obvious next step. Our roadmap was built around it. We designed the UI, built the sharing flow, even wrote the notification copy. Then we actually talked to the people requesting it. What we found: they didn't want to share what they'd written. They wanted ... ... their partner to start journaling too -- separately. The "sharing" they were asking for wasn't about showing their entries

... revoked token says so and points at the regenerate URL if it came from $GITHUB_TOKEN, or gh auth refresh if it came from the gh CLI. Under-scoped tokens name the exact scopes GitHub asked for. Watched entries never vanish silently. A watch_repos entry

... When we launched Murror's delete feature, we thought of it as housekeeping. Users write messy drafts, clean up later. Standard stuff. Then we looked at the data. About 15% of entries were being deleted within minutes of writing them. Not drafts. Not typos. Full, completed entries

... hates forms. As product builders, we spend countless hours obsessing over UI/UX, tweaking dropdowns, optimizing multi-step wizards, and adding helpful tooltips. But the reality in the B2B world especially for sales reps and field workers is that data entry is universally despised. No matter how "beautiful" your CRM interface is, your users will still take notes in their native notes app or send themselves a Slack message, only to begrudgingly do batch data entry

... hardest conversations we had at Murror was about a pattern we kept seeing in the data. Some users were journaling every single day. Multiple entries. Long, thoughtful, beautifully written reflections about the same thing over and over a breakup, a falling out with a friend, a decision they couldn't make. On paper, these were our best users. High engagement, long sessions, consistent retention. Every growth metric said: these people love the product. But when we actually read what they ... ... that felt deeply counterintuitive for a journaling app: a gentle nudge that appears after the AI notices repeated emotional patterns. It says something like: "You've been reflecting on this a lot. Sometimes the next step isn't another entry

... live on PH Aug 22, so this thread's been good practice at saying it in one paragraph.) Comment from Demetrio Koro(@aktivist): siOsi upload one selfie and it reads your 12-season color type, undertone, gold vs silver, and which hair colors suit you, then grades the actual makeup in the photo (flash cast, oxidation, coverage), which most tools skip. Free, no signup. Built it because every beauty sub has a queue of "what season am I" posts waiting ... ... Gemini, since more buying decisions now start there instead of traditional search. If you want to see how an AI agent currently reads your own site, we put out a free tool that shows what an AI fetches vs

... v1.6), we shipped two major releases: v1.7 added OAuth 2.0 on the MCP endpoint and importance-score-aware smart merging, so high-value memories resist being collapsed by near-duplicates. v1.8 added semantic compression: a nightly cron job synthesizes entries with 10+ tags into net-new memory digests. Source entries

... Setting IDEs aside for this one - Cursor, Windsurf, VS Code + Copilot live in a different conversation. I'm specifically curious about CLI-and-agent territory. A year ago the answer for most of us was straightforward: open Claude Code or Codex, talk to it, ship code. That CLI was the entry

... When we first built Murror's reflection AI, we optimized for insight. Every journal entry got a thoughtful, confident analysis. Pattern recognition, emotional connections, suggestions for growth. Users were impressed. But something felt off. We noticed that our most thoughtful journalers -- the ones writing about genuinely complex emotions -- were engaging less over time. They'd write a deep entry

... Cursor: coding Supabase: backend and auth Vercel: hosting GitHub: version control Google Search Console: SEO Campix: my own project, camp software, yes I'm biased Comment from Hans Desjarlais(@ismaelyws): Gmail Calendly Claude Code Google Docs & Sheets VS Code Comment from Bill Davis(@billspaced): @nolan_vu  Slack, not because I love it but because everything dies without it. YESSSSSSSSSSSSS Comment from Bill Davis(@billspaced): @riya_pariyar   @benfleming   @asapx  same question... never heard ... ... solo founder, these are the five tools I use almost every day: ChatGPT VS

... Last quarter, we built a feature at Murror that our engineering team jokingly called "the empty room." After a user finishes a journal entry, the AI doesn't immediately respond. It waits. For 30 seconds, the screen shows nothing but the user's own words and a gentle prompt: "Sit with what you just wrote." No analysis. No reframe. No pattern recognition. Just silence. We almost didn't ship it. Our product team argued it would feel broken. Our investors ... ... process. So we ran the experiment. Half our users got the immediate AI response. Half got "the empty room" first. The results were striking: Users in the silence group were 2.4x more likely to add to their journal entry

... months, we celebrated our power users at Murror the ones journaling every day, sometimes multiple times a day. They had the highest session times, the most entries, the best retention curves. On paper, they were our success story. Then we started reading what they were actually writing. Many of them weren't journaling out of growth or self-reflection. They were stuck in loops writing the same anxious thoughts over and over, looking for reassurance the app couldn't give ... ... nailed it. That's exactly the trap it feels like effort, so it feels like progress. One of our users told us "I journal every day, I'm doing the work" but when we looked at her entries

... your disk. No accounts, no cloud sync, no telemetry. If Folio disappears tomorrow, your manuscript is still just a folder of `.md` files. What v0.1.9 brings: - Panel-visibility settings (hide/show inspector, plan, AI panels per project) - Split IDE-wide vs. book-scoped settings (theme/font global, status flow per book) - Plan timeline + beats improvements for outliners - Smaller polish: status bar cleanup, settings gear moved out of the way The bigger picture (in case you're new to it): - Codex / world-bible ... ... characters, places, lore as Markdown entries

... coding assistant built for real engineering work: File reads Shell commands Sub-agents Full control over execution New Memory Commands: /memory Show memory status & commands /memory on|off Enable or disable workspace memory /memory list List all memory entries /memory view View full content of entry

... have full control over your entries, without losing what matters. What's new: Edit your entries