future-agi / future-agi/future-agi
Per-user attribute dashboards in the Users tab
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- Python
- Stars
- 2k
- Forks
- 628
- Avg merge
- 1d 50m
- Merged PRs (30d)
- 167
Description
Context
The Users tab today is a flat table at user-list-view.jsx. There is no per-user detail view and no analytics on individual users.
Scope
Add a user detail route accessible from the row. The detail view shows charts of that user's activity over time, scoped by user_id.
Files to touch
- frontend/src/sections/user/view/user-list-view.jsx
- New
frontend/src/sections/user/view/user-detail-view.jsx - New backend analytics endpoint(s) accepting a
user_idfilter, or reuse existing trace/eval analytics filtered byuser_id
Acceptance criteria
- Row click opens the detail view at a stable route (e.g.
/users/:id). - At least 3 charts: trace count over time, p95 latency, error rate.
- Charts handle empty state (user with no activity).
- Detail view has a back link to the user list.
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
Start with frontend/src/sections/user/view/user-list-view.jsx and inspect existing trace or eval analytics entry points for user_id filtering. Add the new user-detail-view.jsx and connect it through a stable route. Done means the row opens the detail view with three required charts, an empty state, and a back link to the user list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, python
- Domain
- analytics, backend, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100