码模式的复杂性与工具整合不清
问题概述
帖子介绍了一个名为Codemode的概念，旨在通过语言（如JavaScript）在LLM内部进行工具调用。然而评论中多位用户指出其标题模糊、实现过于复杂、工具语言选择（JS vs bash）不清，且可能导致副作用如子代理能力退化。用户普遍对其必要性表示质疑，认为更简约的虚拟bash命令注入即可满足需求。
痛点标签
- 标题与内容不匹配，使用者需深入阅读才能理解概念
- 实现过于复杂，对于简单的工具调用带来不必要的架构负担
- 工具语言选择（JavaScript 对比 Bash）不清，导致用户难以上手
- 可能导致子代理能力退化，出现词语合并、关键词喷洒等问题
待验证问题
- 如果提供一个基于 Bash 的工具调用沙箱，是否会让你更愿意使用 Codemode？
- 你是否认为目前的工具语言选择（JS 对比 Bash）对你的工作流有实质影响？
- 你是否在实际项目中遇到了因使用类似 Codemode 导致的子代理能力下降问题？
证据
原话 · @anonymous
Between this and the Cloudflare post, this is a lot of words and no simple system level picture. Here's what I think is going on:1. Homoiconicity: Harness mechanics are kludgy and we need proper homoiconicity to uniformly handle code (tool calls) and data ("natural language") as token streams.2. Actor semantics: for isolation, encapsulation and concurrency.3. Object capabilities: injected references and no ambient authority. Capabability-based reflection/introspection is a clean way to discover interfaces and affordances."Code mode" or whatever is basically rediscovering this by hacking outward from LLM token streams, instead of from system design principles based on decades of computer science. It is the beginning of treating an LLM as a programming-language runtime participant (any ta
原话 · @anonymous
If you're like me and you're still wondering what "codemode" is after reading the article and comments: It's giving the harness a small js sandbox to compose tool calls and manipulate the data they return before reading it into context.
原话 · @anonymous
I'm not sure why almost all codemode implementations choose Javascript. I prototyped an agent[1] to use bash as the language for codemode, which in my opinion worked equally well and requires no teaching (there is literally 0 prompt to teach the LLM about codemode. A tool named "bash" is enough to have them know the usage).
原话 · @anonymous
Sadly this seems like introducing a very complex apparatus for little gain. I don't need MCP or many tool calls that the agent can program around - in fact the promise of pi was that you basically just need bash and no other tools. The minimally-invasive approach would have been to just "inject" tool calls as virtual bash commands. No code mode required, no hands vs. brains dichotomy. LLM can use language of its own choosing to interact with tools.
原话 · @anonymous
The headline is "What is codemode". As someone who did not know what codemode is, I had to read until the section "Orchestrating The Harness", where it says "If you are not familiar with Codemode, it’s basically just a way to issue tool calls from within some language, in our case JavaScript." I could then somehow get what is meant from the examples, but the contents of the article do not at all match the headline.
原话 · @anonymous
I've noticed that code mode seems to cause progressive lobotomisation in Sol 6.1 around subagents. The more it uses it, the worse it gets at giving prompts to subagents: URLs, datasourceproxy accesspathonlyallowed anddefault404. Do not set authbasic onprivate ports; perplanPodmannetwork trustedinfrastructure nottenant boundary. Publicroutes internal /tinyauth protected internal, proxyGETemptybody /api/auth/nginx toprivate tinyauth3000; proxy_pass_request_headersoff, CookieonlyTinyauthSession header extracted map name/value actual runtime pattern tinyauth-session-[0-9a-f]{8}, X-Original-URL constructed
免责声明：本卡片由 AI 从社区讨论中提炼，属于「痛点证据」，是需求分析与验证的起点，不等同于「已验证的市场需求」。AI 存在分析局限，关键决策前请打开上方原始讨论人工复核。