The list of projects for a quarto-hub instance is represented as an automerge document so that users can share their project list across different browsers.
Currently, this management happens entirely at client side. This is operationally the easiest option because it doesn't require server-side management of a (user_id, project_list_document) table.
Unfortunately, this means that LLM agents do not have access to a user's list of projects. This means that a user can't ask an LLM about a project by name (because the LLM doesn't know what projects are available).
The list of projects for a quarto-hub instance is represented as an automerge document so that users can share their project list across different browsers.
Currently, this management happens entirely at client side. This is operationally the easiest option because it doesn't require server-side management of a (user_id, project_list_document) table.
Unfortunately, this means that LLM agents do not have access to a user's list of projects. This means that a user can't ask an LLM about a project by name (because the LLM doesn't know what projects are available).