NetLogo / NetLogo/Netlogo-LLM-Extension

feat: observer-level / unbound LLM primitive for narrators and judges

Open
#57 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Scala
Stars
1
Forks
0
Avg merge
3d 1h
Merged PRs (30d)
4

Description

Roadmap priority: B8

Summary

An LLM call that is not bound to a turtle's conversation history — for narrators, judges, referees, and environment generators.

Why it matters

Every chat primitive binds to context.getAgent and commits into that agent's history (LLMExtension.scala:57, commitExchange). When called from the observer, the observer becomes the history owner, which works but conflates two different uses: an agent having a conversation, versus the model asking the LLM a one-off question.

Concrete cases from existing demos: a judge scoring a round in social-deduction, a narrator summarising what happened this tick, generating an environment or scenario at setup.

Was raised in discussion with Can Gurkan (Apr 2026) as an observer-level primitive.

What needs to be done

  1. Decide the semantics: stateless one-shot (no history at all), or a named history channel the modeler controls.
  2. Named channels are the more general design — llm:chat-in "judge" "..." with its own history, independent of any agent. Would also cover shared/group memory (B9).
  3. Primitives for clearing and inspecting a named channel, mirroring llm:history / llm:clear-history.
  4. Ensure it works when called from within ask (i.e. does not silently pick up the calling turtle's history).

Open questions

  • Is a named-channel API a superset of both this and B9 (shared memory)? If so these should probably be one design.
  • Does the observer's current history behaviour need to stay for backward compatibility?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading LLMExtension.scala:57 and the existing llm:history and llm:clear-history primitives, then inspect how observer calls and ask invoke the current context. Compare the proposed one-shot and named-channel semantics, including backward compatibility for observer history. Done means the API design is decided and its behavior inside ask is specified.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
ai
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.