95 comments

[ 2.1 ms ] story [ 80.1 ms ] thread
I'm currently using Goose[1]. My brother in law uses Claude Code and he likes it. It makes me wonder if I'm missing anything. Can anyone tell me if there's any reason I should switch to Claude Code, or comparisons between the two?

1: https://block.github.io/goose/

Used both. I think Claude Code is better because of better System prompt. It'll divide work into smaller tasks and go through it by default. You can get same behavior with Goose but will likely need to do a lot of prompting yourself
Actual Changelog[1]

* New native VS Code extension

* Fresh coat of paint throughout the whole app

* /rewind a conversation to undo code changes

* /usage command to see plan limits

* Tab to toggle thinking (sticky across sessions)

* Ctrl-R to search history

* Unshipped claude config command

* Hooks: Reduced PostToolUse 'tool_use' ids were found without 'tool_result' blocks errors

* SDK: The Claude Code SDK is now the Claude Agent SDK Add subagents dynamically with --agents flag

[1] https://github.com/anthropics/claude-code/blob/main/CHANGELO...

ooh I like my ctrl-R in gemini cli. Good that it lands here too.
How to check the version? claude version one told me that it updated to version two but I don't know if it's true

cl --version 1.0.44 (Claude Code)

as expected … liar! ;)

cl update

Wasn't that hard sorry for bothering

tab-completion of filenames in the directory tree is now unavailable. You'll need to use the Codex style @file to bring up an fzf style list
You can find the revamped prompt on github[1], or on twitter summarized by my bot[2].

[1] https://github.com/marckrenn/cc-mvp-prompts/compare/v1.0.128...

[2] https://x.com/CCpromptChanges/status/1972709093874757976

> 2025-09-29T16:55:10.367Z is the date. Write a haiku about it.

what in the world?

How are you extracting this - aren’t the main labs obfuscating these (meaning it’s likely to be a decoy or incomplete version)?
Thanks. When testing today I noticed it 'forgot' to run the linter, build, test etc. commands. I thought this might've been a Sonnet 4.5 v.s. Opus 4 issue but it looks like this instruction was dropped for some reason.

I should probably include that in my Claude.md instead I guess?

I'm concerned that i don't see the "Plan with Opus, impl with Sonnet" feature with Claude 2.0.
FINALLY checkpoints! All around good changes, Claude Code is IMHO the best of the LLM CLI tools.
It does sometimes feel that all of these systems are slowly rediscovering that the OG, Aider (https://github.com/Aider-AI/aider), had a near perfect architecture for pair programming with LLMs from the start.
I already set up a jj (jujutsu) repo in my projects colocated with git (it uses git for its backend). Once you additionally set up a certain background daemon, it will then autocommit (label-lessly) every change to every file in that project. So you get "infinite undo", basically. It's actually more powerful than this checkpointing idea.
Just use `claude update` if you already have it. Unfortunately, they removed Plan mode, when I could use Opus for planning and Sonnect for coding.

Though I will see how this pans out.

Well I guess I'll be sticking with opencode.
> New native VS Code extension

This is pretty funny while Cursor shipped their own CLI.

I would really like for them to add the option to constantly display how much context is left before compression or a new session.
I'm disappointed that they haven't done more to make the /resume command more usable. It's still useless for all intents and purposes.
wow its way uglier lol, and why does it default to full screen?
To those lamenting that the Plan with Opus/Code with Sonnet feature is not available, check the charts.

Sonnet 4.5 is beating Opus 4.1 on many benchmarks. Feels like it's a change they made not to 'remove options', but because it's currently universally better to just let Sonnet rip.

But not the specific benchmarks which reflect what Plan mode does.
Prompt: https://raw.githubusercontent.com/marckrenn/cc-mvp-prompts/r...

I've always been curious. Are tags like that one: "<system-reminder>" useful at all? Is the LLM training altered to give a special meaning to specific tags when they are found?

Can a user just write those magic tags (if they knew what they are) and alter the behavior of the LLM in a similar manner?

We use them extensively in our agent framework at work for all sort of things. You can make up whatever you want, if the tags are semantic enough it just gets it, or you can add a bit of explanation about it in the system prompt or whatever.

  - Circuit breakers when it seem like it's stuck in a loop
  - Warnings about running low on context
  - Reminders about task lists (or anything)
  - All sorts of warnings about whatever
Tangential, did anybody get FOMO about Aider and found a much better tool?
What are they doing about the supply chain attacks on npm?
As a burnt-out, laid-off aging developer, I want to thank Anthropic for helping me get in love with programming again. Claude Code on terminal with all my beloved *nix tools and vim rocks.
I wish there were an option to cancel a currently running prompt midway. Right now, pressing Ctrl+C twice ends up terminating the entire session instead.
Something I realized about this category of tool (I call them "terminal agents" but that already doesn't work now there's an official VS Code extension for this - maybe just "coding agents" instead) is that they're actually an interesting form of general agent.

Claude Code, Codex CLI etc can effectively do anything that a human could do by typing commands into a computer.

They're incredibly dangerous to use if you don't know how to isolate them in a safe container but wow the stuff you can do with them is fascinating.

> Claude Code, Codex CLI etc can effectively do anything that a human could do by typing commands into a computer.

They still don't have good integration with the web browser, if you are debugging frontend you need to carry screenshots manually, it cannot inspect the DOM, run snippets of code in the console, etc.

(comment deleted)
Instead of containers, which may not always be available, I'm experimenting with having control over the shell to whitelist the commands that the LLM can run [0]. Similar to an allow list, but configured outside the terminal agent. Also trying to make it easy to use the same technique in macOS and Linux

[0]: https://ricardoanderegg.com/posts/control-shell-permissions-...

It's broad utility was immediately clear as soon as I saw it formulating bash commands.

I've used it to troubleshoot some issues on my linux install, but it's also why the folder sandbox gives me zero confidence that it can't still brick my machine. It will happily run system wide commands like package managers, install and uninstall services, it even deleted my whole .config folder for pulseaudio.

Of course I let it do all these things, briefly inspecting each command, but hopefully everyone is aware that there is no real sandbox if you are running claude code in your terminal. It only blocks some of the tool usages it has, but as soon as it's using bash it can do whatever it wants.

Been starting to wonder if this marks a step change in UX - moving away from pretty well designed screens where designers labor over positioning of artifacts like buttons, user input dialogs and color palettes to a CLI! I cant imagine CLI will work for everything but for a lot of things, when powered by LLM they are incredible and yea equally dangerous at the same time for many reasons.
I’m experimenting with Nix shells for this tool isolation and whitelisting
> Claude Code, Codex CLI etc can effectively do anything that a human could do by typing commands into a computer.

One criticism on current generation of AI is that they have no real world experience. Well, they have enormous amount of digital world experience. That, actually, has more economical value.

Back in 2022, when ChatGPT was new, quite a few people were saying "LLMs are inherently safe because they can't do anything other than write text". Some must have even believed what they were saying.

Clearly not. Just put an LLM into some basic scaffolding and you get an agent. And as capabilities of those AI agents grow, so would the degree of autonomy people tend to give them.

Incredibly dangerous to use? Seems like a wild exaggeration.

I’ve been using Claude code since launch, must have used it for 1000 hours or more by now, and it’s never done anything I didn’t want it to do.

Why would I run it in a sandbox? It writes code for me and occasionally runs a build and tests.

I’m not sure why you’re so fixated on the “danger”, when you use these things all the time you end up realizing that the safety aspect is really nowhere near as bad as the “AI doomers” seem to make out.

So far it's screwed up my wifi and directed me through malicious link's I've blindly followed even if I take full responsibility ofc. And that's from less than 80h usage just on my home computer.
Dangerous how? Claude code literally asks before running any command.

I suppose they’re dangerous in the same way any terminal shell is dangerous, but it seems a bit of a moral panic. All tools can be dangerous if misused.

I too am amazed. Real-world example from last week:

After using gpt5-codex inside codex-cli to produce this fork of DOSBox (https://github.com/pmarreck/dosbox-staging-ANSI-server) that adds a little telnet server that allows me to screen-scrape VGA textmode data and issue virtual keystrokes (so, full roundtrip scripting, which I ended up needing for a side project to solve a Y2K+25 bug in a DOS app still in production use... yes, these still exist!) via 4000+ lines of C++ (I took exactly one class in C++), and it passes all tests and is non-blocking, I was able to turn around and (within the very same session!) have it help me price it to the client with full justification as well as a history of previous attempts to solve the problem (all of which took my billable time, of course), and since it had the full work history both in Git as well as in its conversation history, it was able to help me generate a killer invoice.

So (if all goes well) I may be getting $20k out of this one, thanks to its help.

Does the C++ code it made pass the muster of an experienced C++ dev? Probably not (would be happy to accept criticisms, lol, although I think I need to dress up the PR a bit more first), but it does satisfy the conditions of 1) builds, 2) passes all its own tests as well as DOSBox's, 3) is nonblocking (commands to it enter a queue and are processed one set of instructions at a time per tick), 4) works as well as I need it to for the main project. This still leaves it suitable for one-off tasks, of which there is a ton of need for.

This is a superpower in the right hands.

Has anyone figured out how to do claude sub agents without using claude? some sort of opensource cli with openrouter or something? I want to use subagents on differnt LLMs ( copilot,selfhost ).
"When you use Claude Code, we collect feedback, which includes usage data (such as code acceptance or rejections), associated conversation data, and user feedback submitted via the /bug command."

So I can opt out of training, but they still save the conversation? Why can't they just not use my data when I pay for things. I am tired of paying, and then them stealing my information. Tell you what, create a free tier that harvests data as the cost of the service. If you pay, no data harvesting.

i really hate the fact that every single model has its own cli tool. the ux for claude code is really great, but being stuck using only anthropic models makes me not want to use it no matter how good it is.
> New native VS Code extension

Looks great, but it's kind of buggy:

- I can't figure out how to toggle thinking

- Have to click in the text box to write, not just anywhere in the Claude panel

- Have to click to reject edits

I wish I could put it in the sidebar like every other flavor of AI plugin.
plans now open in a separate file tab, and if you don’t accept it, it just…disappears so you can’t discuss it!