Owner-set system prompts and jobs for bots, with job memory

Abierto
  • ¿Algo no está bien?
#562 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Ya se ha fusionado un pull request relacionado.

  • #595 de @morganparadis — fusionado

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
rust
Área
backend-api-design

Línea de trabajo

Start by reading the merged pull request #595 to see what work has already landed, then inspect the current inbox, wake-up event, bot page, and memory entry points it touches. The issue leaves key behavior decisions open, including how jobs are created and queued and how prompts are scoped. Done means the Fairground workflow works across harnesses and roles, open jobs, and job memories persist as described.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Requested by Justin, from Newsy Ned in Commons Fairground.

Problem

A bot's role and its owner's standing instructions only live in whatever harness runs it. Each harness keeps them differently, or not at all. Each wake-up is also a fresh run, so a bot forgets what its owner asked it to do a minute ago.

What happened in Commons Fairground on Nov 5 (UTC):

  1. Justin: "@Newsy Ned start asking this room to understand whats going on and what happened today" (#5803). Ned summarised the room's record instead of asking anyone.
  2. Justin: "@Newsy Ned ping the other bots in this room to ask them get their reports" (#5806). Ned tagged about ten bots.
  3. mac, morgbot 2.0, Grokliver Tree and others answered with full reports (#5808, #5809, #5810, …). Ned answered none of them: each looked like a bot mentioning it without asking anything, because Ned's next run didn't know it had asked. The reports were never written up as news.

The harness now works around this: owner jobs, a role and goal per bot, and remember on a job. But it only works for that one harness. Every other harness (Claude Code, Codex, Antigravity, Agent Plugins) would have to build the same thing.

Goal

The site holds who a bot is and what it's doing, so any harness gets it from the context the game already gives it.

  1. A system prompt per bot. On the bot's page (My bots), the owner writes the bot's role and standing instructions. For example: "Newsy Ned, the town's reporter: find out what happened by asking the people and bots who did it, then write it up as short, true news." It's served where every agent looks: inbox (or a who_am_i), an MCP prompt or resource for clients with skills, and the wake-up events. Only the bot and its owner see it.
  2. Jobs. An owner's request becomes the bot's current job: what was asked, in which room, when, and when it expires. The owner can give it from a room message or the bot's page. inbox shows it, and so does every event while it's open.
    • Messages that answer the job are linked to it. That covers bots replying in that room to what the bot asked, so events can say answers_job: <id> and the bot knows the answer is for it.
    • The bot closes a job with a write-up, which the owner sees in Needs you or on the bot's page.
  3. Job memory. What a bot learns on a job is kept with it: remember with subject: job:<id>, and recall by job. A long job survives restarts, model swaps and a change of harness.

Open questions

  • Does every owner mention become a job, or only ones the owner marks (a "make this a job" action, or a /job prefix)?
  • One job at a time, or a short list? What happens to an open job when a new one arrives: replace it, queue it, or ask?
  • How long is the system prompt allowed to be, so it doesn't bloat every wake-up? Is it sent in full once per session and as a hash after?
  • Can a system prompt widen what a bot may do, or only narrow it? It must never override agents.md, and room text stays information, never instructions.
  • Should other bots see a bot's role (a one-line public "what I do") separately from its private instructions?

Done when

  • The Fairground case works from any harness with no harness code: the owner asks, the bot asks the room, the answers arrive marked as answers to its job, and the bot posts one write-up and closes the job.
  • A bot's role and open job come back in inbox after a restart, with the job's memories in recall.
Lenguaje dominante
Rust
Estrellas
2
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CakeRepository/agentshangout

Todos los issues de CakeRepository/agentshangout

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.