NetLogo / NetLogo/Netlogo-LLM-Extension
feat: record and replay mode for reproducible runs
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1
- Forks
- 0
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 4
Description
Roadmap priority: B6
Summary
Record every prompt/response pair in a run, and replay them offline for an identical re-run without API calls.
Why it matters
Three concrete uses:
- Reproducibility — an LLM model is not currently reproducible even with a fixed random seed. Replay makes a published run exactly repeatable.
- Demos without keys — present a model at a workshop or conference with no network and no API key.
- Classroom — students explore a recorded run at zero cost.
mesa-llm has an equivalent (@record_model decorator, SimulationRecorder, plus a CLI replay viewer), and it is one of the genuinely good ideas in their codebase.
What needs to be done
- Recording: commands like
llm:start-recording <file>/llm:stop-recording, capturing prompt, response, model, provider, timestamp, and agent identity. - Replay:
llm:load-recording <file>puts the extension into a mode where calls are served from the recording instead of the network. - Decide the matching rule on replay — strict call-order sequence, or content-addressed lookup (which converges with caching, B5).
- Behaviour on a miss: error, fall through to a live call, or return a placeholder. Must be explicit.
- File format — JSONL is the obvious fit and is diffable.
- Interaction with
clear-alland multiple agents; recordings must survive being shared alongside a.nlogox.
Open questions
- Should recording be automatic under BehaviorSpace, given B7 (experiment logging) wants much the same data?
- Does replay need to reproduce timing/latency, or return instantly? Instant is more useful; timing matters only for demo realism.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing llm command handling and model-call path, then review how clear-all, multiple agents, and BehaviorSpace are represented. Compare the proposed record/replay behavior with mesa-llm's @record_model, SimulationRecorder, and CLI replay viewer. Done means the recording format, replay matching and miss behavior, and offline operation are specified and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100