返回 2026-08-18 编辑版
发现与解读中文优先 · EN 原文AI 产品

Michael Zhou 发布:Codag 压缩 Agent 工具输出并追踪 token 去向

我们正在推出 Codag (@ycombinatorS26) - 代理工具的压缩和控制层。我们从日志开始。然后客户让我们进行搜索、测试、构建和 API 响应。模式总是相同的:代理在重复输出上燃烧上下文,而团队无法看到token去了哪里。 Codag 现在以答案对等的方式将输入令牌的使用量减少了约 3 倍,并为团队提供了整个代理堆栈的可见性。代理商正在成为软件的主要用户——公司正在增加代理商、模型、提供商和MCP服务器的速度快于其测量或控制的速度。大多数人无法回答他们的代理使用了哪些工具,这些工具的成本是多少,或者浪费在哪里。我们正在他们和他们阅读的所有内容之间建立一层。目前,90 多个工程组织已使用 Codag 来减少支出并查看跨提供商的代理工具使用情况。如需了解更多信息并预订演示,请访问 https://codag.ai/

查看英文原文

we’re launching Codag (@ycombinator S26) - the compression and control layer for agent tools. we started with logs. then customers pulled us into searches, tests, builds, and api responses. the pattern was always the same: agents burning context on repetitive output, with teams unable to see where the tokens went. Codag now cuts input-token usage ~3x at answer parity and gives teams visibility across their agent stack. agents are becoming the primary users of software - companies are adding agents, models, providers, and MCP servers faster than they can measure or control them. most cannot answer which tools their agents invoke, what those calls cost, or where the waste is. we’re building the layer between them and everything they read. 90+ engineering orgs already use Codag today to reduce that spend and see agent tool usage across provider. find out more and book a demo at https://codag.ai/

we’re launching Codag (@ycombinator S26) - the compression and control layer for agent tools. we started with logs. then customers pulled us into searches, tests, builds, and api responses. the pattern was always the same: agents burning context on repetitive output, with teams unable to see where the tokens went. Codag now cuts input-token usage ~3x at answer parity and gives teams visibility across their agent stack. agents are becoming the primary users of software - companies are adding agents, models, providers, and MCP servers faster than they can measure or control them. most cannot answer which tools their agents invoke, what those calls cost, or where the waste is. we’re building the layer between them and everything they read. 90+ engineering orgs already use Codag today to reduce that spend and see agent tool usage across provider. find out more and book a demo at https://codag.ai/

上下文不再只靠加长窗口:知识图、压缩层和结构化区域开始各自承重

为什么值得看

上下文工程正在从提示技巧变成独立基础设施。团队需要分别回答模型该看什么、重复输出怎样压缩、token 花在哪里,以及长期任务如何保持结构,而不是只购买更大的窗口。

最强反方

GitNexus 的任务通过率与成本改善、Codag 的约 3 倍 token 降幅和组织采用数均来自发布方;Leviath 是作者提交的项目页。现有材料证明产品方向活跃,不能形成统一效果排名。

原始出现与传播对照

1 条出现 · 本次 AIHOT 未精确命中

发现与解读

我们正在推出 Codag (@ycombinatorS26) - 代理工具的压缩和控制层。

我们正在推出 Codag (@ycombinatorS26) - 代理工具的压缩和控制层。我们从日志开始。然后客户让我们进行搜索、测试、构建和 API 响应。模式总是相同的:代理在重复输出上燃烧上下文,而团队无法看到token去了哪里。 Codag 现在以答案对等的方式将输入令牌的使用量减少了约 3 倍,并为团队提供了整个代理堆栈的可见性。代理商正在成为软件的主要用户——公司正在增加代理商、模型、提供商和MCP服务器的速度快于其测量或控制的速度。大多数人无法回答他们的代理使用了哪些工具,这些工具的成本是多少,或者浪费在哪里。我们正在他们和他们阅读的所有内容之间建立一层。目前,90 多个工程组织已使用 Codag 来减少支出并查看跨提供商的代理工具使用情况。

查看英文原文

we’re launching Codag (@ycombinator S26) - the compression and control layer for agent tools. we started with logs. then customers pulled us into searches, tests, builds, and api responses. the pattern was always the same: agents burning context on repetitive output, with teams unable to see where the tokens went. Codag now cuts input-token usage ~3x at answer parity and gives teams visibility across their agent stack. agents are becoming the primary users of software - companies are adding agents, models, providers, and MCP servers faster than they can measure or control them. most cannot answer which tools their agents invoke, what those calls cost, or where the waste is. we’re building the layer between them and everything they read. 90+ engineering orgs already use Codag today to reduce that spend and see agent tool usage across provider. find out more and book a demo at https://codag.ai/

we’re launching Codag (@ycombinator S26) - the compression and control layer for agent tools. we started with logs. then customers pulled us into searches, tests, builds, and api responses. the pattern was always the same: agents burning context on repetitive output, with teams unable to see where the tokens went. Codag now cuts input-token usage ~3x at answer parity and gives teams visibility across their agent stack. agents are becoming the primary users of software - companies are adding agents, models, providers, and MCP servers faster than they can measure or control them. most cannot answer which tools their agents invoke, what those calls cost, or where the waste is. we’re building the layer between them and everything they read. 90+ engineering orgs already use Codag today to reduce that spend and see agent tool usage across provider. find out more and book a demo at https://codag.ai/

直接发布标题Michael Zhou@michaelzixizhou打开该层出处 ↗

we’re launching Codag (@ycombinator S26) - the compression and control layer for agent tools. we started with logs. then customers pulled us into searches, tests, builds, and api responses. the pattern was always the same: agents burning context on repetitive output, with teams unable to see where the tokens went. Codag now cuts input-token usage ~3x at answer parity and gives teams visibility across their agent stack. agents are becoming the primary users of software - companies are adding agents, models, providers, and MCP servers faster than they can measure or control them. most cannot answer which tools their agents invoke, what those calls cost, or where the waste is. we’re building the layer between them and everything they read. 90+ engineering orgs already use Codag today to reduce that spend and see agent tool usage across provider. find out more and book a demo at https://codag.ai/

来源
X @ycombinator · x-ycombinator
证据角色
x_project_network
时间状态
known
用户判决
未判
查看该来源原文raw/x-ycombinator.json456f7ad15e343498ae9ba68155f36302654d2db5ffc7c9ab0dc22168995f2ead
Cluster IDevt_a6c51179e3b70ddd3822478a精确去重依据canonical_url事件状态未判