It's missing the most important CLI flag! (--dangerously-skip-permissions)
If you're gonna do that, make sure you're sandboxing it with something like https://github.com/kstenerud/yoloai or eventually you'll have a bad time!
Claude Code Cheat Sheet
91–100 of 215 posts
Re: Claude Code Cheat Sheet
#92I think this is the argument for UIs - it should be self-explanatory since it's singificantly simpler than an IDE
I used to think UIs would be better for agents, but I changed my mind: UIs suit traditional software very well because there are only X actions that can be performed - it makes sense that if you have an image converter that can take X, Y and Z formats and convert them to A, B and C then you should have a UI that limits what the user can do, preventing them from making mistakes and making it obvious what's possible.
But for something like Claude Code there are unlimited things you can do with it, so it's better for them to accept a free-form input.
Re: Claude Code Cheat Sheet
#93I use Claude Code daily but kept forgetting commands, so I had Claude research every feature from the docs and GitHub, then generate a printable A4 landscape HTML page covering keyboard shortcuts, slash commands, workflows, skills system, memory/CLAUDE.md, MCP setup, CLI flags, and config files. It's a single HTML file - Claude wrote it and I iterated on the layout. A daily cron job checks the changelog and updates t…
What version of Claude Code is this? I don't have the /cost command mentioned here.
Re: Claude Code Cheat Sheet
#94Shocking how far ahead Claude Code is from Codex on the CLI front.
With Claude Code I created an agent that spawns 5 copies of itself branching git worktrees from main branch using subagents so no context leaks into their instructions. The agent will every 60 seconds analyze the performance of each of the copies which run for about 40 minutes answering the question "what would you do different?". After they finish the task, the parent will update the .claude/ files enhancing itself…
> Next I'm going to set it loose on 263 GB database of every stock quote and options trade in the past 4 years. I bet it achieves successful trading strategies.
I bet it doesn't achieve a single successful (long term) trading strategy for FUTURE trades. Easy to derive a successful trading strategy on historical data, but so naive to think that such a strategy will continue to be successful in the long term into the future.
If you do, come back to me and I’ll will give you one million USD to use it - I kid you not. Only condition is your successful future trading strategy must solely be based on historical data.
Re: Claude Code Cheat Sheet
#95Earlier quoted context omitted.
With Claude Code I created an agent that spawns 5 copies of itself branching git worktrees from main branch using subagents so no context leaks into their instructions. The agent will every 60 seconds analyze the performance of each of the copies which run for about 40 minutes answering the question "what would you do different?". After they finish the task, the parent will update the .claude/ files enhancing itself…
cringe
I agree, but there’s another comment further down responding with ‘based’, so to each their own I suppose.
Re: Claude Code Cheat Sheet
#96Shocking how far ahead Claude Code is from Codex on the CLI front.
With Claude Code I created an agent that spawns 5 copies of itself branching git worktrees from main branch using subagents so no context leaks into their instructions. The agent will every 60 seconds analyze the performance of each of the copies which run for about 40 minutes answering the question "what would you do different?". After they finish the task, the parent will update the .claude/ files enhancing itself…
Claude Code can't even succeed at programming. The idea of it turning into AGI is laughable.
Re: Claude Code Cheat Sheet
#97Earlier quoted context omitted.
Yet all the people OpenAI bought out recently say Codex is “the future”
The bigger question is: does Anthropic have a big enough moat to matter? I've used/use both, and find them pretty comparable, as far as the actual model backing the tool. That wasn't the case 9 months ago, but the world changes quickly.
I don’t believe there will ever be a real moat in terms of technology, at least not for the next year or so. The arms race between the major players still changing month to month, and they will all be able to do what their competitors were doing g three months ago.
None of them are particularly sticky - you can move between them with relative ease in vscode for instance.
I think the only moat is going to be based on capacity, but even that isnt going to last long as the products are moved away from the cloud and closer your end devices.
Re: Claude Code Cheat Sheet
#98It's missing the most important CLI flag! (--dangerously-skip-permissions)
If you're gonna do that, make sure you're sandboxing it with something like https://github.com/kstenerud/yoloai or eventually you'll have a bad time!
Personally I usually just create a devcontainer.json, the vscode support for that is great and I don't really mind if it fucked up the ephemeral container.
Which for the record : hasn't actually happened since I started using it like that.
Re: Claude Code Cheat Sheet
#99CMD + V to paste an image is wrong. On Mac it's the same as Windows, CTRL + V. You use CMD + V to paste text.
Yes, this also applies to some other commands as well: CTRL+G opens the external editor, not CMD+G on Mac.
Re: Claude Code Cheat Sheet
#100Shocking how far ahead Claude Code is from Codex on the CLI front.
With Claude Code I created an agent that spawns 5 copies of itself branching git worktrees from main branch using subagents so no context leaks into their instructions. The agent will every 60 seconds analyze the performance of each of the copies which run for about 40 minutes answering the question "what would you do different?". After they finish the task, the parent will update the .claude/ files enhancing itself…
Comments like this should include how much $$$ you spend on tokens.