Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code Cheat Sheet

cc.storyfox.cz

Post reply on HN
Print view View original

101–110 of 215 posts

Re: Claude Code Cheat Sheet

#102

Post by mohsen1 »

phasE89 wrote: post #2

I 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…

`^` is the symbol for the Control key not `⌘`

Re: Claude Code Cheat Sheet

#105

Post by arrowsmith »

sbinnee wrote: post #88
briHass wrote: post #75

Earlier quoted context omitted.

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.

It matters to me. Claude code is more extensible. They put a lot of efforts to hooks and plugins. Codex may get the job done today. But Claude will evolve faster.

None of that matters if the model is worse. I say this as someone who uses both Claude Code and Codex all day every day — I agree with others in this thread that CC has much better UX and evolves faster, but I still use Codex more often because it's simply the better coder. Everything else is a distant second to model quality.

Re: Claude Code Cheat Sheet

#106

Post by therealdrag0 »

joegibbs wrote: post #92
dangoodmanUT wrote: post #22

I 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. B…

Huh? Did you see the cheat sheet? Most of it is a UI of the terminal and shortcut variety, and much of it is exposed in other IDEs as a traditional UI.

Re: Claude Code Cheat Sheet

#107

Post by kstenerud »

ffsm8 wrote: post #98
kstenerud wrote: post #91

Earlier quoted context omitted.

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.

Hey thanks for this! I hadn't thought about leveraging devcontainer.json, but it's a damn good idea. I'm building yoloAI for exactly this use case so I hope you don't mind if I steal it ;-)

One thing to be aware of with the pure devcontainer approach: your workspace is typically bind-mounted from the host, so the agent can still destroy your real files. Network access is also unrestricted by default. The container gives you process isolation but not file or network safety.

I'm paranoid about rogue AIs, so I try to make everything safe-by-default: the agent works on a copy of your workdir, you review a unified diff when it's done, and you apply only what you want. So your originals are NEVER touched until you explicitly say so, and network can be isolated to just the agent's required domains.

Anyway, here's what I think will work as my next yoloAI feature: a --devcontainer flag that reads your existing devcontainer.json directly and uses it to set up the sandbox environment. Your image, ports, env vars, and setup commands come from the file you already have. yoloAI just wraps it with the copy/diff/apply safety layer. For devcontainer users it would be zero new configuration :)

Post reply on HN