Code calling is all you need
Summary
Argues that using code generated by LLMs to call external tools (code calling) is more efficient and capable than traditional JSON-based function calling, but requires secure sandboxing. The author is building a framework for this approach.
Similar Articles
Giving LLMs exec() power is a security nightmare. I built a open-source AST-based guardrail to stop malicious agent execution.
Introduces ast-guard, an open-source AST-based security tool that prevents malicious code execution from LLM-generated Python strings by parsing them into an abstract syntax tree and applying node-level whitelisting and context-aware safety checks.
@hwchase17: code interpreter is a light weight code execution environment lets you do: - RLMs - programmatic tool calling - more! w…
Harrison Chase announces a lightweight code execution environment called code interpreter that enables RLMs and programmatic tool calling without needing a full sandbox, with more use cases to be detailed.
- -dangerously-skip-reading-code – olano.dev
The article argues that as organizations adopt LLMs for code generation, engineering practices must shift from reviewing generated code to focusing on specifications and tests, with organizational buy-in for new processes.
I built an open-source coding agent that makes context visible and editable — you curate exactly what the LLM sees
The author built Nice Coding Agent, an open-source coding workbench with a visible and editable context stack, allowing users to curate exactly what the LLM sees. It features local-first retrieval, sandboxed execution, and hybrid code search, aiming to give developers control and visibility over context assembly.
@evanyou: https://x.com/evanyou/status/2060409444123729935
A developer shares an interesting use case for running LLMs in the browser to inspect internal workings, highlighting a meaningful scenario for client-side AI.