plan
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
sprint 1
- figure out how to log conversations with litellm
- get litellm to identify applications
sprint 2
- have yaml like interface for conversations/applications/people
- get a ui up and running
sprint 3
- get litellm multi-tenancy to work
- use something like supabase for the sso/account management
backlog
- backend the conversations with git
- expose the git endpoints for users
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by breaking the plan into separate issues, beginning with the LiteLLM conversation logging and application-identification goals. Define the scope and acceptance criteria for each milestone before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript, supabase, yaml
- Domain
- authentication, backend, frontend, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100