devs get attached to their tools so much. it's okay to move on to a new thing. Neovim, Tmux... they served us well, but you can move on to a different thing, it's okay
@mattyp Any plans to improve the syncing process for mobile projects? At times it just dies between syncing main/coordinator agent and the secondary ones.
Prompt:
Build me a read-only PR Risk Dashboard for my repos. Score every open PR 0-100 for deploy risk based on size, risky areas touched (migrations, env vars, billing, auth), CI status, review status, how far behind main it is, and age. Show headline tiles, a High/Medium/Low strip, and compact PR cards with a score bar and chips. Tap a card for blockers and next steps. Mobile-first.
Took Melvin's dashboard idea and built one for PR deploy risk
Every open PR gets a 0-100 score: migrations, env vars, billing, auth, CI, conflicts, age
Tells me what's safe to ship and what needs me first
Prompt in replies👇 https://t.co/KbJzCHcDV5
I made a Grok Bot Activity Dashboard
Ask your Chief of Staff to build a running document where you can see all bot's activities, progress, and status
Hope you guys find this useful
Prompt in replies👇
@leerob The ability to Pin Pages or artifacts a bot has built. Sometimes it gets messy and sometimes more if you have a single bot that takes charge of doing only that.
@tebayoso@cursor_ai@grok@bot Creo que tiene que ver con el plan que tienes en @bot .
Cooper es el plan de equipos, Spar es de la subscripcion a SuperGrok
Asumo que cuando unifiquen todo será mucho más sencillo.
@brolag Creo que si venís del mundo de tmux el cambio hace más sentido. Yo diría las siguientes ventajas.
- tus agentes se pueden comunicar entre ellos
- podes conectarte a sesiones remotas
- extensibilidad mediante plugins
- buen soporte para worktrees
- corre lo que ya tenes/usas