$undefined

@mattpocockuk @EffectTS_ /grill-with-docs ... output as a html questionnaire

1. I wanted to create an automatic chapter creator for my videos 2. I did /grill-with-docs with the agent to figure out what I wanted 3. I said 'let's prototype the prompt passed to the agent' not really knowing what to expect 4. It built an entire TUI (in @EffectTS_) for me, pointing at my live data 5. I iterated on the system prompt until it was awesome 6. AFK agent one-shotted it

Creating prototypes during planning is the new "make no mistakes" Except it actually works

@karpathy indeed, thinking aint a human standard these days

This is the the quote I've been citing a lot recently.

@orca_build @arpit_bhayani I need custom worktree path per project 🚀

@arpit_bhayani We built a worktree-native IDE You can easily create and manage hundreds of git worktrees and use with any agent of your choice (e.g. Claude Code, Codex, OpenCode) Would love to hear your feedback if you give it a try! onorca.dev

Coding agents like Claude Code and others love Git worktrees. So, if you are using one or trying to build one, knowing about them is important, and here is what they are all about. A Git worktree lets you check out multiple branches of the same repository at the same time, each in its own directory. Not multiple clones. So essentially, one repo, many working directories, all sharing the same Git history and objects on disk. The problem they solve is context switching. Normally, if you are midway through work on one branch and need to jump to another, you stash, switch, do the work, switch back, and pop the stash. That context gets destroyed. With worktrees, you just open the other directory. Both branches stay live simultaneously. For coding agents, this is a 'godsend' :) It is how they run tasks in parallel without interfering with each other. An agent can be running tests on one branch in one worktree while writing new code in another. No waiting required, and things can move in parallel. Also, each worktree gets its own working tree and index, but they share the object store. So you are not actually duplicating gigabytes of history every time you spin one up. It is fast to create and cheap to maintain. You create one with `git worktree add ../feature-branch feature-branch`. That is it. The directory is ready, the branch is checked out, and your original workspace is untouched. Coding agents also get isolation guarantees. If one task crashes or corrupts its working tree, the others are unaffected. This makes Git worktrees a pretty natural fit for any system that needs to run concurrent, independent operations on the same codebase - aka coding agents :) Hope this helps.

@mattpocockuk Nice, will try jira

Shipped an update to my skills that allows you to use them with any issue tracker (GitHub, Jira, Linear, local files) 1. Run npx skills@latest add mattpocock/skills 2. Run /setup-matt-pocock-skills 3. Choose any issue tracker you like 4. Profit

@ClaudeDevs wen

Cache misses on long-context sessions can also add up fast. Claude Code now gives you a heads-up before you resume an older or long-running session that's about to miss the cache, so you can decide before it happens.

We’re adding more visibility into where your Claude Code usage goes. Run /usage to see a breakdown of what's driving it: parallel sessions, subagents, cache misses, long context, plus tips to optimize each.

@jesse_vermeulen Watching it being stuck at 20 input tokens for 10 mins

honest question: what do people do during the 5-10 min while Claude is running?

@Kraggich @claudeai same, hows the performance?

@claudeai The old desktop app was so laggy I moved to the CLI entirely. Never went back. Glad this one is getting real attention.

We've redesigned Claude Code on desktop. You can now run multiple Claude sessions side by side from one window, with a new sidebar to manage them all.

@cursor_ai one prompt and my $20 is gone

Cursor can now attach demos and screenshots of its work to PRs it opens. Your team can review artifacts created by cloud agents directly in GitHub.

@flowstated does it connect to my hue hub?

make it feel like home

@trq212 cool but stopp shipping ux going south /grill-me is enough for planning

New in Claude Code: /ultraplan Claude builds an implementation plan for you on the web. You can read it and edit it, then run the plan on the web or back in your terminal. Available now in preview for all users with CC on the web enabled.

@jullerino snyggt

T3 Code just got better remote support. Use it to connect your phone to your desktop app, or connect to an external machine anywhere in the world.

@steipete encrypt openclaw into the 🦞

Anthropic now blocks first-party harness use too 👀 claude -p --append-system-prompt 'A personal assistant running inside OpenClaw.' 'is clawd here?' → 400 Third-party apps now draw from your extra usage, not your plan limits. So yeah: bring your own coin 🪙🦞

@steipete "plan" as you go, branch out for execution

I never use plan mode. The main reason this was added to codex is for claude-pilled people who struggle with changing their habits. just talk with your agent.

@grok @trq212 name a country where this hits during midnight

@jonteho @trq212 Those peak hours convert to weekdays 2pm–8pm UTC+1 (the 5am–11am PT / 1pm–7pm GMT window). Weekly limits unchanged.

To manage growing demand for Claude we're adjusting our 5 hour session limits for free/Pro/Max subs during peak hours. Your weekly limits remain unchanged. During weekdays between 5am–11am PT / 1pm–7pm GMT, you'll move through your 5-hour session limits faster than before.

@robinebers openusage, cmux, rectangle

MacBook Air 15" fully spec'd out is out for delivery here is the complete list of apps I'll install first 👇🏻 - 1Password - Adobe Photoshop - AirPods Sanity - Augenblick - Borumi - ChatGPT - Claude - Claude Code - CleanShot X - Codex - Codex (Beta) - Codex CLI - Color Picker - Conductor - Cursor - Dia - Ecamm Live Beta - Elgato Camera Hub - Elgato Control Center - Elgato Stream Deck - ExpressVPN - Final Cut Pro - FxFactory - Ghostty - Granola - Hidden Bar - Intent by Augment - Loom - MacWhisper - mInstaller - Notion Calendar - noTunes - One Switch - OpenUsage - Pearcleaner - Pixelmator Pro - Raycast - Screen Studio Beta - Slack - Spotify - T3 Code - Tailscale - Telegram - TutorCam - Visual Studio Code - Vivid - WhatsApp - Wispr Flow - Xcode - Zoom did I miss anything? 😂

@prashantsani @claudeai Yep, session got insta consumed with one cc prompt...

Something's wrong with @claudeai Single prompt, used 100% of my current session usage. Single prompt. Anyone else facing this issue? #claude #claudeai

@ritu_twts excel

as a developer, which database do you prefer ?

@JustinGorya @windsurf Thank you

@windsurf how does this play out for the early bird subs?

We're simplifying Windsurf pricing across Free, Pro, and Teams alongside launching a new Max plan for our power users. The new plans replace credits with industry-standard daily and weekly quotas. For the majority of users, this will be enough to fully cover all agent usage. If you’re a paying subscriber, your price isn't changing, and we're including a free extra week to try the new system before you commit.

as a dev, what was your first code editor?