Skip to content

feat(files): per-chat/per-project association of uploaded files + storage-growth policy #357

Description

@umi-appcoder

Split out from #336 (item B3, the genuinely-missing part). Verdict: MISSING.

Non-image uploads already work server-side (no type restriction in handle_file_upload, server.py:6728). What's genuinely missing around uploaded files:

  • Per-chat / per-project association of uploaded files — uploads land in a shared location with no linkage to the conversation or project they belong to.
  • A storage-growth policy — no quota, TTL, or per-chat GC, so upload storage can balloon indefinitely on the 50Gi PVC.

Relates to the projects concept in #358 (per-project file association would naturally hang off a project entity).

Metadata

Metadata

Assignees

No one assigned

    Labels

    effort: M~daysenhancementNew feature or requestneeds-scopingNot ready to implement — needs design, a decision, or scoping first

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions