Original Summary

Hey everyone, We’ve been building Sulcus, a control layer for AI agents. The idea came from a pretty simple problem: once you have multiple agents running, using tools, making LLM calls, editing files, failing, retrying, etc., it gets surprisingly difficult to understand what they’re actually doing. Sulcus gives you one place to see agent runs, tool calls, LLM activity, errors, resource usage and the relationships between agents. We’re also building runtime controls like permissions, approvals and limits. We currently support integrations with LangGraph, CrewAI, OpenAI Agents SDK, Codex and Claude Code. That also means we're exploring workflows where you might have different coding agents working at the same time — for example, Claude Code working on one part of a project while Codex handles another — while Sulcus gives you visibility and control over what's happening. It’s still early, and that’s exactly why I’m posting. We’re looking for developers actually building with agents who are willing to try it and tell us: - What’s confusing? - What’s missing? - What would make you actually use this? - What is completely unnecessary? - And, most importantly, what breaks? You can try it here: sulcus.dev I’m one of the co-founders and the CTO, so happy to answer technical questions here too. Would genuinely appreciate brutal feedback rather than compliments :)   submitted by   /u/MathematicianStill22 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/23 02:44:31