Hooman - Own your AI agent stack — local, open source and extensible

by
Hooman is an open-source, local-first AI agent runtime that works across the terminal, VS Code, ACP-compatible editors and event-driven workflows. Use your preferred models and inference endpoints, including local llama.cpp and MLX, or bring your own API keys. Hooman includes agent, plan, ask and design modes, MCP integrations, reusable skills, subagents, approval controls and persistent project-scoped sessions.

Add a comment

Replies

Best
Hey Product Hunt 👋 I built Hooman because I wanted an AI agent stack I could actually own. Most agent tools are either tied to a hosted platform, limited to one interface, or difficult to adapt to private and local infrastructure. Hooman is an MIT-licensed, local-first agent runtime that works across the terminal, VS Code, ACP-compatible editors, and event-driven daemon workflows—all sharing the same configuration, sessions, skills, MCP tools, and approval model. You can use hosted providers, bring your own keys, point it at private inference endpoints, or run locally with llama.cpp and MLX. There’s no account requirement and no telemetry; your keys, sessions, and configuration stay on your machine. It also includes Agent, Plan, Ask, and Design modes, reusable skills, subagents, human-in-the-loop approvals, MCP integrations, background tasks, and design exports to formats such as PDF and PowerPoint. I’d especially love feedback on: • What would make you switch from your current coding agent? • Which model or provider integrations should I prioritize next? • Where does the setup or documentation still feel unclear? Thanks for checking it out. Hooman is open source, so issues, stars, feedback, and contributions are all genuinely appreciated 🙌

Would love to see a built-in TUI dashboard for monitoring active sessions, token usage, and subagent status at a glance. Something like a tmux-style interface where I can attach to a session, see what the agent is currently thinking, intervene mid-run, and pause or kill it without dropping context. Would make managing long-running local workflows way less opaque.

Local-first is a great call, would love to see a built-in cost and token usage dashboard per session and provider so I can keep tabs on API spend without wiring up my own logging.