@Janivcohen · X

keeps all your travel plans, bookings, and emergency info in one clean space. ✈️ ​👉

miketromba · HN

Cronloop, run Claude Code or Codex on a schedule

@SidathRashen · X

@nundinaapp · X

I dropped 😋

u/Hot_Spend_2860 · Reddit

Two of us built a group-scheduling tool over two months - the stack, what took longest, and the mistake that cost us our analytics Upfront so nobody wastes their time: free product, $0 revenue, no company formed. This isn't a revenue flex. I'm posting the build because the two things that went wrong were more interesting than the things that went right. here’s the link! What it is: Meetly, a group scheduling poll. The people you invite never make an account, calendars auto-import so nob

@troyaunderwood · X

@iHatePosting · X

@seb_klopfer · X

@GabrielBrangers · X

@harryjwang · X

I've used many of the major conference systems. Plenty still have docs as an unsearchable static site — or worse, as PDFs that stopped tracking the product three versions ago. Somehow, still true in 2026. We took an AI-first path with instead. Our docs are generated from the codebase itself. A custom Claude Code skill writes each page and retakes the screenshots whenever a feature changes — so the docs don't drift from the product. Every page still gets reviewed by a human before it ships. Now you can talk to them, too. We just shipped "Ask AI" over our docs: This feature also turned out to be a nice teaching case for agentic RAG vs. classic RAG: • Classic RAG: chunk → embed → vector DB → retrieve once, by fixed rules • Agentic RAG: hand the model a search tool and let it drive — write a query, read the results, rewrite, retry At more than 100 pages, still no vector database needed. And every answer cites the exact page it came from. #Age

bhagyeshsp · HN

First things first: On the landing page, click on the "demo" link below the Hero section to try it without jumping any hoops ** I'm a long-time Basecamp user and satisfied with its overall functionality. Of course, there are many things that can be improved but that is not the point of this post. *Background* Basecamp lets users create "Projects". These projects are isolated workspaces that contain: members, todos, chat, files, message board, and calendar, etc. My issue was with the scattered calendars. Because I (and every other Basecamp user) creates a dedicated project for different scope of work, even if it is for the same client. For example, at any given time, I may have 4 projects for client-X and 3 projects for client-Y. *My pain point* I have experienced that most clients (especially the decision-makers) do not use Basecamp as often as we--the agency folks use it. They just use it when some reviews or comments are required or some file access. The clients organize their

GrokTask — 基于 Grok AI 的智能任务自动化平台，支持定时任务、AI 自动执行、信息收集与分析