@manu_jsx · X

Built a coding agent for my repo in under a minute. No prompt engineering. No made-up skill names. Just answered 4 questions and exported to Claude Code.

Olscore · HN

Pullboard – a work queue for agents, built to run a quant desk

@AiShivam · X

AgentStacKPro is an OS for AI agents designed to make them production-ready, and it holds incredible potential. You can also check out the project I currently developed

u/OGMYT · Reddit

Validating a micro-SaaS for checking AI-built software before it ships I am building **Flows**, a system that turns an AI software goal into ordered implementation steps, checks, repair prompts, and a build report. The business thesis is not “better prompts.” It is reducing the cost of getting from an AI-generated first draft to a checked, shippable result. Metrics I want to measure: - prompts per completed project - tokens or credits per checked step - first-pass check rate - repair atte

@matebenyovszky · X

I use multiple providers Claude Code, Cursor, Codex, Hermes, Antigravity etc. and multiple machines. Over time, each one ended up with its own slightly different skills and tools 😰 So I started where a playbook is a portable bundle containing my MCP/OpenAPI servers, skills, prompts, personas and memory, which I can take with me into whichever environment I’m using. I’m still trying to figure out whether this is useful beyond my own workflow. Ideas? 🤔 🍎 Source / open source on Github: matebenyovszky/agentplaybooks I also built an npm CLI that audits a project and syncs the same skills and MCP definitions across harnesses.

u/Outside_Change_1692 · Reddit

I built an open source Slack where your AI agent is an actual member of the workspace Every dev I know has an agents doing real work now, but it lives in a terminal where nobody else on the team can see it. So I built FreeFlow completely free and open source. It's team chat where your coding agent is a member of the workspace, not a bot integration. You invite it in, @ it like any teammate, and it works in the thread where everyone can watch it happen. Same channel, same c

u/george_owen123 · Reddit

What I learned building an AI chatbot: the ecom tools are everywhere, but service businesses are completely underserved Spent the last few months building Chirpy, an AI receptionist for websites, with my co-founder. The biggest thing I've learned is a positioning one, and I think it applies well beyond my niche. When we started, we assumed we'd compete in the ecommerce chatbot space, because that's where all the money and attention is. But it's extremely saturated. Gorgias, Tidio, Intercom,

clapptastic · HN

GreatArrow.ai – Shared memory for Claude, ChatGPT, Gemini and Cursor

ns90001 · HN

Oasis - Giving Agents Situational Awareness

oomol-lab · GitHub

open-connector Open-source auth gateway connecting 1000+ SaaS providers to AI agents through SDK, CLI, MCP, HTTP, and OpenAPI.

dariusmonsef · HN

OzBrain, a shared brain for knowledge between agents and your team

gb2d_hn · HN

It was with the transience of valuable agent session dialogue in mind that I built https://www.agentkanban.io - A key feature is context capture in the tasks which you create on the board and then progress in agent sessions. Supported agents are currently Claude and Github CoPilot in VS Code. All of your context is captured in the task and can be reloaded into new agent sessions at any point in the future. Tool use is intentionally discarded because it is proprietary in nature and therefore brea