Back to browse
GitHub Repository

a generative dashboard for your team's standup.

16 starsTypeScript

I built a standup app so I'd stop switching between Linear,GitHub,Slack

by heyavi·Mar 4, 2026·5 points·5 comments

AI Analysis

●●SolidSolve My ProblemSlick

Replaces 6-tool context-switching with natural language queries, but LLM agents for project management aren't novel.

Strengths
  • Natural language interface actually solves the tab-switching pain; 'What's at risk?' beats manual review.
  • Interactive components and real-time filtering beat chat-only outputs; renders actual dashboards, not text.
  • Encrypts API keys client-side; respects that storing GitHub/Linear tokens is genuinely risky.
Weaknesses
  • Tightly coupled to Linear + GitHub; adding Jira, Azure Boards, or other tools would require major refactoring.
  • No offline or cached views; depends on constant API calls, so if Linear is down, standup dies.
Category
Target Audience

Engineering managers and team leads running standups

Similar To

Cursor · Continue · Sourcegraph Cody

Post Description

We are a small team and my standup workflow was: open Linear, find who's working on what, switch to GitHub, check PRs, switch back, share my screen, ask people to give updates they could've just typed. All so I could answer "what's everyone doing and is anything stuck."

So I built a thing where I just ask. "How's the team" pulls up an overview. "What's Avi working on" shows their issues sorted by status with their PRs. "Anything at risk" shows stale and unassigned work. It renders actual interactive components, not chat responses, I can filter by status, priority, repo, whatever.

The whole point is I shouldn't have to ask 6 people to stop what they're doing so I can get context I could've gotten from the tools we already use. The information is all there in Linear and GitHub. It just takes 20 minutes of tab-switching to piece it together, or a meeting where everyone takes turns reading their tickets aloud.

Built it with Tambo (I'm an engineer there, full disclosure). You register components with schemas and the AI decides which one to render based on what you ask. The components fetch their own data from Linear and GitHub APIs.

It's not an anti-standup thing exactly, more that I think most of what happens in standups is information retrieval, and that part can just be a tool. The actually useful part of standups (unblocking each other, quick decisions) is a 2-minute conversation, not a 15-minute ceremony.

Similar Projects

Steward – a background agent that closes 80% low-risk noise

Personal chief of staff for your inbox, but unproven safety gates at scale.

Bold BetShip It
867762462f
103mo ago