quarto-hub important feature: "preferred" project list
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 255
- Forks
- 17
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 109
Description
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).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by tracing the client-side automerge project-list management, then determine how a server-side list could be exposed to LLM agents; done means an agent can discover a user's projects by name across browsers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ai, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100