morioka · HN

GlossaryPage – Turn customer questions into knowledge pages

@TheWhiz351 · X

I built two versions of the same responsible AI app using different vibe-coding platforms. Perplexity Computer: Base44: Try both. Which has the better design and user experience? #VibeCoding #ResponsibleAI

@gonelf · X

So many things - dead simple way to share projects within your team - dead simple base - no backend forms - ez directory submissions - a Lego event

g418572664 · V2EX

做了一个文档解析与记忆工具，专门辅助给传统行业做 AI 落地的老哥 现在 AI+的工作还挺常见的，就像大佬们说的，“所有行业的产品可能都会用 AI 重新做一遍”。最常见的就是各种 agent ，说要用 AI 赋能传统行业啥的，代替人类专家去处理海量的复杂资料、进行深度分析并做出决策。 举个例子，金融行业的“智能审计与尽调 Agent”。 过去，银行或投资机构想要给一家企业贷款或投资，需要人类审计师去读几十份、每份几百页的招股书和财务报表。现在虽然有了 AI ，但把文件一股脑全丢给它是不现实的，且不说烧 token 的问题，这些文档里有无数的跨行、跨列单元格表格，普通工具一拉，表格数据全串行了。如果 AI 把“第一季度利润”和“第二季度支出”的信息碎在一块，那得出的财务分析就完蛋了。 所以，现在要真想开发出一个能干活，还确保正确率的 agent ，就需要一个专业的、AI-native 的解析工具，把复杂的表结构和章节层级完整还原出来。我做的工具 Knowhere 就是干这个的： https://knowhereto.ai/?utm_source=v2ex 它能把复

@gravibase · X

Discover how AI agents can turn ideas into content. Try GraviBase today:

@hkbonur · X

that digitalise paper forms and make everything multi language, so businesses can get better conversion. One form any language.

@nav_ux · X

BaseThread here. We're building the shared context layer so a team's AI tools, Claude, ChatGPT, Cursor, all read and write the same thing instead of starting cold every session.

@GuidedBase · X

@Scyloq · X

Currently building SentrAI. The merge-time control plane for AI-assisted software development. Enforce policy, audit every AI-generated change. Just finished an interactive demo and would love your honest feedback. Built with @Lovable

@BotbaseAi · X

We just shipped 🚀 BotbaseAI — build & deploy an AI customer support agent in minutes. No code. Looking for early testers to break it and tell us what sucks. Try it → 🙏 RTs appreciated #buildinpublic #AI #SaaS

@kashyap_ai · X

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