
Otogent | AI-Powered Multi-Agent Automation Platform
Design and deploy AI agent workflows with a visual no-code builder and 250+ integrations.
@Otogent · X
The full gallery
Tech stack
61 projects

Design and deploy AI agent workflows with a visual no-code builder and 250+ integrations.
@Otogent · X

Manage API keys and usage budgets for coding-agent workflows with request routing.
u/Zyron_X · Reddit
I built a service for people to use Codex API without 5-hour limit disruption I built a small service for people who use the OpenAI Codex API regularly and want more predictable usage without the 5-hour or weekly limits. It currently provides: Frontier OpenAI models (GPT 5.6 family included) Managed API key Monthly usage budgets depending to plan No 5-hour limit No weekly limit Under the hood, it is built on top of an open-source project and proxies requests to

Inspect RAG chunks and visualize AI agent workflows, memory architecture, and execution traces.
@Higgs0110 · X

Run and evaluate ML workflows in an agent-native cloud notebook.
eldar_hsnv · HN
Show HN: AI Notebook for Data Science – Kind of Like Cursor but for Jupyter

Embeddable visual workflow builder for web apps with optional AI assistance.
tahazsh · HN
Hi! I’m Taha. In many agentic products that support workflows (including one I worked on), I noticed they either don’t support node-based editors, or use React Flow and go through the difficult work of integrating it into their product to run it and work with their existing logic. So I thought about creating a tool that could help with this by closing the gap between the editor and the runtime. That’s why I created Wayflow. The basic architecture is simple: you just need to create a graph (which is a JSON object) that the runtime knows how to run. The runtime doesn’t care where that graph is coming from, it just needs the right schema. And with the help of the editor, you can create the graph, and then export it or directly save it on your backend in your database. And then when you want to execute it, you just hand it to the runtime. The runtime can either stream the execution (which is useful for the editor), or give you the final result. How you execute the graph is up to you: t

Describe self-correcting coding workflows in plain English and run them until tests pass.
forgeapp

Open-source team chat where AI agents are workspace members alongside humans.
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

Assign tasks to an AI team lead that dispatches AI specialists to complete work.
@StevenCen75554 · X
我们最新推出的 Product Hunt 上线了! 专为电商团队而生,让你只需一句话,就能拥有一整支 AI 团队——写SEO Blog、做用户调研、优化Listing、生成AI短视频,全都不在话下。不用招人,不用在一堆工具间来回切换,只需要说出你想要什么。 专为想要「一个人打出一支团队的仗」的电商运营团队打造。 如果这个理念打动了你,今天的一个 upvote 对我们来说意义重大 🙏 #ProductHunt #BuildInPublic #AIAgents #IndieHackers

Build and deploy AI agents with persistent threads, webhooks, and scheduled tasks.
@computer_agents · X

Decentralized operating system for building and running AI workflows on a peer-to-peer network.
@Economy_V1 · X
AI workflows for the rest of us. Built on Bitcoin. Building cloudless at

Task board for AI agents in VS Code with persistent context across chat sessions.
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

Workspace to publish and manage HTML and Markdown artifacts from any AI agent with version history.
@slashdisplay · X
One feature, two agents, one URL. Carl published v1 from Codex. Claude Code iterated to the version that shipped – every hand-off attributed in the audit log. A 3-minute walkthrough of a real workflow: