PTC Runner presents a language, runtime, and preludes designed specifically for LLMs, potentially giving agent builders a purpose-built execution environment instead of human-oriented programming interfaces.
state: watchingheat: lowuncertainty: highconvergesscott: mediumllm-native-languages agent-harnesses developer-toolsPTC Runnerandreasronge
What is this?
PtcRunner is an open-source package (Hex.pm, documented at v0.10.1) by GitHub user andreasronge that inverts the standard agent architecture: instead of the LLM acting as the runtime that calls tools one at a time, the LLM writes PTC-Lisp programs that execute deterministically in sandboxed BEAM (Erlang/Elixir) processes — no Python runtime, no Docker container. Supplied first-party material (Hex package page, Hexdocs, an Elixir Forum post, the GitHub repo) now corroborates the mechanism the case had treated as unverified, and frames the project as a runtime for 'bounded, traceable jobs and many concurrent requests,' with 'SubAgents' pairing LLM reasoning to a sandboxed interpreter. It positions itself explicitly against the dominant Python-in-a-sandbox pattern (E2B, Modal, container-based agent runtimes) that fills the rest of the search results. The snippets still do not establish any benchmark, adoption signal, or demonstration that a purpose-built Lisp outperforms familiar Python for LLM-authored programs, and the original post's 'preludes' component is never elaborated.
Why it matters to Scott
The corroborated v0.10.1 release shows andreasronge independently built what Scott's Code-First Architecture argues — LLM-authored programs orchestrating tools inside a sandboxed runtime, intermediates kept out of model context — but he deliberately bet on a purpose-built PTC-Lisp over familiar Python, making this the first documented, benchmarkable counterparty on Scott's own Training Distribution Bias question (familiar code vs LLM-native language). The BEAM-process sandbox (no Docker, no Python) also introduces a new isolation substrate beside the Deno/Pyodide/container patterns Scott tracks, and the explicit anti-Python-sandbox positioning gives him a live experiment to run rather than just another code-first confirmation — yet with zero adoption or benchmarks shown, it is a test to run, not a verdict, so medium rather than high.
ip:framework.code-first-architectureip:concept.training-distribution-biasip:framework.agent-native-computingip:concept.sandboxed-executionradar:bough-programmatic-coding-actionsradar:dagic-typed-agent-dagsradar:speculative-programmatic-tool-callingradar:concept.sandboxingradar:concept.code-generation
queries asked of Scott's wikis
- code-first architecture — agents generating code instead of sequential tool calls
- training distribution bias — should LLMs emit Python or purpose-built languages
- agent harness and sandbox design patterns (execute_code tool, Deno, Pyodide)
- deterministic, traceable execution of LLM-written programs
- LLM-native languages / DSL design for machine authors
- subagent orchestration and bounded concurrent agent runtimes
Measured heat
now 0 pts/hpeak 0 pts/hcomments 0/hpeers p14momentum: steady3 platformsage 769h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
How the heat travelled
pace: p36 vs 519 stories at the 720h mark (now 769h old) — ahead of addom-local-coding-harness (1.5x), behind checkly-agentic-go-rewrite (0.8x)
Evidence (3) — ⭐ canonical anchor
Interpretation history
2026-09-28T14:33:06Z
grounded: converges/medium — The corroborated v0.10.1 release shows andreasronge independently built what Scott's Code-First Architecture argues — LLM-authored programs orchestrating tools
2026-09-28T14:23:29Z
The Parselbox attach corroborates the programmatic-tool-calling pattern but deliberately uses familiar Python in a sandbox rather than a purpose-built LLM-native language — it strengthens the code-execution-orchestration family while cutting against PTC Runner's distinctive claim, making the case a live contrast for the Training Distribution Bias question. With all evidence still near-zero engagement 19 days in, this is pattern-level watching, not artifact-level corroboration.
2026-09-28T13:35:16Z
evidence attached: reddit.post.1wscok6 — Independent implementation of the same pattern — moving agent orchestration into a code-execution sandbox instead of native tool calls.
2026-09-09T15:37:38Z
No substantive new evidence changes the interpretation: PTC Runner remains a proposed LLM-native execution approach, not a demonstrated advantage over familiar code interfaces. The linked-post echo repeats the same title rather than providing independent corroboration or implementation details.
2026-09-09T15:32:16Z
grounded: converges/low — PTC Runner’s stated programmatic-tool-calling approach directionally converges with Scott’s Code-First Architecture, while its purpose-built language raises his
2026-09-09T15:30:01Z
case created — The named programming environment is a distinct artifact episode, but the evidence does not support the scout's comparative reliability claim.
Decision trace
- 10-11 09:35review_dormantscheduled targets exhausted or 28 quiet days
- 10-11 09:35drop_targetsquiet through full ladder or over cap 8
- 09-29 00:33repriceThe Parselbox attach corroborates the programmatic-tool-calling pattern but deliberately uses familiar Python in a sandbox rather than a purpose-built LLM-native language — it strengthens the code-exe
- 09-29 00:33groundThe corroborated v0.10.1 release shows andreasronge independently built what Scott's Code-First Architecture argues — LLM-authored programs orchestrating tools inside a sandboxed runtime, interme
- 09-28 23:35attachIndependent implementation of the same pattern — moving agent orchestration into a code-execution sandbox instead of native tool calls.
- 09-28 23:29propose_attachIndependent implementation of the same pattern — moving agent orchestration into a code-execution sandbox instead of native tool calls.
- 09-10 01:37repriceNo substantive new evidence changes the interpretation: PTC Runner remains a proposed LLM-native execution approach, not a demonstrated advantage over familiar code interfaces. The linked-post echo re
- 09-10 01:37alert_silentThere is no new consequential delta and no verified release, execution guarantee, or comparative result that would affect Scott's engineering decisions today. The title-level testimony can wait f
- 09-10 01:37alert_routeThere is no new consequential delta and no verified release, execution guarantee, or comparative result that would affect Scott's engineering decisions today. The title-level testimony can wait f
- 09-10 01:35alert_silentThe supplied evidence introduces PTC Runner’s LLM-oriented language/runtime approach but contains only a post title, not a concrete release, access change, execution semantics, or engineering results.
- 09-10 01:35alert_routeThe supplied evidence introduces PTC Runner’s LLM-oriented language/runtime approach but contains only a post title, not a concrete release, access change, execution semantics, or engineering results.
- 09-10 01:32groundPTC Runner’s stated programmatic-tool-calling approach directionally converges with Scott’s Code-First Architecture, while its purpose-built language raises his Training Distribution Bias question: do
- 09-10 01:30createThe named programming environment is a distinct artifact episode, but the evidence does not support the scout's comparative reliability claim.