@moxypixy15683 · X

Are you vibe coding and want to understand the argent language better? understands .ag files. You can pay with kaspa to use it :)

晨笙阅读 — 书籍解读平台，AI 辅助+人工校审，提炼经典书籍的核心问题、论证框架与实践洞见，支持分类浏览、全文搜索和主题阅读

@alexander_roese · X

1. Building a platform to help companies capture and preserve critical employee knowledge before it leaves the business. 2. For SMEs that want to reduce knowledge loss, improve onboarding, and make internal expertise easier to access. 3.

u/Glittering_Stage4118 · Reddit

Building a company brain that can host any interface I’ve always felt like company knowledge is way too fragmented. Docs live in one place, support answers in another, marketing content somewhere else, and internal know-how is usually buried across tools, Slack threads, and old pages. Even when companies have the knowledge, turning it into the right interface for the right audience is still way too hard. I’ve been building Sophic to solve exactly that. At its core, Sophic

@Asym_Alwali · X

@MyCrystalSite · X

@generalizingai · X

@vhm205 · X

Too many news articles, too many bookmarks, too many notes, but I never open them again because I don't know where to find them

@khagankarimi · X

simple markdown notebook with version history

aiobe · HN

I built Commonplace because I wanted to learn more about Google's Open Knowledge Format for knowledge sharing with human and agents. At the same time, Atlassian announced it will start using customer cloud data to train its AI models (opt-out is Enterprise-only), which made a self-hosted Confluence alternative feel timely. The idea: - Use a Git repository that follows Open Knowledge Format with plain Markdown - Commonplace is just a stateless frontend on top (nice UI, but no database, no backups

@Canvasowl · X

Building the best way to audit your landing page and find leads:

u/LeonHelloWorld · Reddit

Build update: testing whether visual AI maps are actually clearer than chat This week I finished a public beta of BranchAI, a web app that turns a complex question into a visual tree instead of a single long AI conversation. The hypothesis is simple: people lose useful context once a chat has several follow-ups. Keeping those follow-ups visible as branches should make research and complicated topics easier to revisit. What is working now: - Generate a starting map from a question - Op