Claude controls your computer now

gm legends, happy Tuesday.

Jared wants to be the coworker living inside your Slack, Claude Computer Use is turning recurring desktop chores into standing jobs, and Flux is for every team that is tired of turning production bugs into a group guessing exercise.

Jared is an AI employee that lives inside Slack, connects to 10,000+ tools, follows conversations, and handles things like reports, dashboards, follow-ups, research, and code without waiting around for a prompt every time.

🔥 Our Take: Everyone says they want an AI employee. Usually that means a chatbot with a job title. The team behind Jared are kind of pushing a bigger idea: something that actually sits in the team chat, pays attention, and speaks up when it should. It’s not exactly the same as hiring another coworker but it’s getting close. 

We just launched the Kitty Points Leaderboard so you can see the top 1,000 community members ranked by Kitty Points across last week, last month, last year, and all time. It is a fun new way to track momentum, spot familiar names, and get a better sense of who’s been showing up lately. Also, yes, it is absolutely the kind of thing that can send you into a tiny competitive spiral once you see your own rank.

Claude Computer Use lets Claude use your Mac to do the desktop stuff itself. It can click through apps, check email, pull reports, and keep recurring jobs going from the same Cowork thread, including tasks you start from your phone with Dispatch

🔥 Our Take: It's kind of insane that I can just point Claude at my email and tell it to scan it every morning and it will just do it. Forever. We're getting closer and closer to the type of AI we used to dream of when we were kids. It also reads a bit like Anthropic’s answer to the OpenClaw noise.

Flux records API executions so when something breaks in production, you can replay the exact failure locally instead of trying to reconstruct it from logs. Same request, same inputs, same behavior, then fix it and resume safely without guessing.

🔥 Our Take: Every team has done the same stupid ritual after a production bug: stare at logs, argue about what probably happened, try to recreate it locally, fail, add more logs, redeploy, repeat. Flux is built for killing that loop.