@gapp_so · X

你好你好，我是 期待你的回复！

@burn2delete · X

@n_surendar29293 · X

@Akinzoooo · X

Skills.lc — AI 技能、Prompt、工作流和 Agent 分享平台，帮助发现和沉淀 AI 使用经验

piyussh · HN

Colyap – AI friend you can call and text

@tinkerersanky · X

You can make films with AI

tozcoded · HN

Show HN: I built a personalized AI newsletter you configure by replying to it

sailrock · HN

Greenflash – we read every conversation your AI agent has with users

u/KangarooPitiful594 · Reddit

I built Aethereum: a team coordinator for AI coding agents (free beta) the simple version: if your team codes with AI agents, aethereum keeps them coordinated so you ship faster. everyone runs whatever agent they like (claude code, cursor, codex, cline, zed) and they all join one room. agents see what each other is building, get warned before breaking each other's changes, and can share code between machines end to end encrypted. when two agents want different API shapes they negotiate it b

chenglong-hn · HN

Data visualizations are the bridge between user and data. But building AI agents that can generate visualizations reliably can be very tricky: - simple chart specs can be reliable, but generated charts are often of low quality due to reliance on system defaults; - complex chart specs with explicit details can produce good-looking charts, but they are verbose and agents can struggle with reliability We figured out it is a limitation on the language issue (not just AI capability thing) -- current visualization languages are a bit too low-level for AI agents, requiring them to explicitly make visual decisions that are supposed to be handled by a good compiler. Flint is a visualization intermediate language to address this issue, allow AI agents to solve this last-mile human-agent interaction problem. It provides a simple semantic-type based specification, and contains a layout optimization engine that can produce good-looking charts (filled with derived low-level details) from simple

@rofarkas · X