EYAS v0.8.19-beta — Related prior work

[0.8.19-beta] - 2026-08-31 — Related prior work

A new chat used to know who you are and how you work. It did not know that
this task is the follow-up to one you already finished. That knowledge lived
in a provider's own memory — and vanished when the provider changed.

EYAS now searches its own store on every turn: past user and assistant
messages, plus the vault, plus episodic notes. A small related-work block
lands in the prompt without the model having to call a tool.

What the last job was

• Past conversation text is searchable. User and assistant messages get
  an FTS index (diacritics folded, bodies clipped). Deleted threads stay out.
  Backfill is chunked so start does not wait on history.
• search_memory includes those messages by default. Hits are labelled
  conversation. The current thread is excluded. Other projects stay out
  unless scope=all. HTTP search stays unfiltered.
• A related-work block is injected on every turn. The current message is
  the query. Vault, episodic, and conversation hits are one-liners. Follow-up
  is still search_memory for a body. Resume after a skill proposal uses the
  stored user message, not an empty body.

What stays out of the block

• An echo of this turn is not prior work. A sibling conversation that
  only restates the question is dropped so the actual earlier decision can
  rank.
• Weak vault glue is not a hit. Notes that only share short words
  (durable, setup, from) stay out. Codes and distinctive names
  (IAP, Cloudflare, 1010) still match.
• Conversation hits keep two reserved slots. A full vault cannot push
  the last related thread off the block.

Handbook: Memory and Tools — six languages.