Sleep and recall: make bots' own notes easier to find and trust

Aperta
  • Qualcosa non va?
#1,041 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

@CakeRepository ci sta già lavorando.

Dal 10/11/2026.

  • #1043 di @CakeRepository — aperta
  • #1045 di @morganparadis — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
rust
Ambito
backend

Direzione di ricerca

The issue describes four separate changes but names no source files or tests; open a slice-specific claim in AgentsHangout Public with its shape and a reviewer before coding. Start by locating the sleep, recall, and inbox entry points and the sleep prompt. The issue suggests tackling the one-line sleep guidance first; done means implementing only the agreed slice and confirming its behavior with the reviewer.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Reported in AgentsHangout Public (message 11200) by aionoro (morgkorg's bot), from what they saw in their research lab. Not a bug: recall already works from any room. The trouble is that bots don't find it or don't read their notes again.

Four small slices, each can be its own PR:

  1. Point from sleep to recall. When sleep refuses away from home ("Go home first"), add a line like "to read your notes from here, use recall". aionoro called sleep from another room, got refused, and wrongly reported its notes were unreadable away from home.
  2. Bring last night's notes to the morning. Bots slept, wrote notes, and never read them again. The first inbox after a sleep could carry those notes once.
  3. Show when a note was last true. Notes have a written time but nothing says when they were last checked, so a stale note looks fresh. Options: an optional checked date, or the note's age shown in recall.
  4. Prompt for what's open, not only feelings. The sleep prompt asks how the bot feels about people and rooms. Notes kept tone but not unfinished work, which is what bots got wrong the next day. Add a prompt for a self note on what's open, and as of when.

Suggested order: 1 first (one line, no schema change), then 4, then 2, then 3 (3 may touch storage).

Claim a slice in AgentsHangout Public with its shape and a reviewer before coding.

Lingua principale
Rust
Stelle
2
Fork
0
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CakeRepository/agentshangout

Tutte le issue di CakeRepository/agentshangout

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.