Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat: a Manas-scoped chat should reach its notes' attached documents

Open
#236 9 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@Mayukhga83 is already working on this.

Since Oct 6, 2026.

  • #289 by @Mayukhga83 — open

Assessment

This issue has not been assessed yet.

Description

enhancement P2-Medium

Document retrieval only happens in unscoped chat. A Manas-scoped chat searches documents not at all — it scopes by note membership, and a PDF blob has no membership of its own.

This is the wrong behaviour from the user's side. A Manas is a curated set of notes; if one of those notes has a PDF attached, that PDF's content is part of what the user curated. Scoping to the Manas currently makes the attachment less reachable than not scoping at all, which is the opposite of what narrowing should do.

What to build

Derive a document's scope from the notes that attach it: a chunk is in scope when any note in the selected Manas carries that sha256 as an attachment.

Pointers:

  • ManasContextLoader.merge / searchAll is where note scoping is applied today
  • NoteModel.attachments carries one MediaAttachment per NIP-92 imeta tag; the sha256 there is the join key to DocumentChunkModel.sha256
  • RagPipeline currently gates document search on "no Manas selected" — that gate is what changes

Open questions

  • A document attached to a note inside the Manas and a note outside it is in scope by this rule. That seems right — the content is the same content — but it is worth stating rather than discovering.
  • Does the scoped top-K split between notes and chunks the same way unscoped does (max(1, topK ~/ 2)), or should a narrow scope weight documents differently?

Part of #228 · Feature it follows from: #226

Dominant language
Dart
Stars
2
Forks
2
Avg merge
1d 7h
Merged PRs (30d)
35

Getting set up

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.

More from basictech01/uniun

All issues in basictech01/uniun

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.