> Ctrl+P to print. Works on mobile too.

There’s something funny about this statement on a description of a key bind cheat sheet. I can’t seem to find ctrl on my phone and I think it may be cmd+p on mac.

What version of Claude Code is this? I don't have the /cost command mentioned here.

Wow nice! Thank you.

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

FYI in US Letter Size it fits into a perfect 1 page...and a blank 2nd page. at least here on macOS firefox

Are you OK opening up the source?

Warp Terminal supports CMD + V on Mac to paste an image

Yes, this also applies to some other commands as well: CTRL+G opens the external editor, not CMD+G on Mac.

I thought it was CTRL SHIFT V. Is that Linux only? Ctrl V sends some kind of funky key combo.

https://code.claude.com/docs/en/env-vars

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 reverting if the copies performed worse or enhancing if they performed better. Then it creates 5 copies of itself branching git worktrees from main branch ..........

After 43 iterations, it can turn any website using any transport (WebSocket, GraphQL, gRPC-Web, SSE, JSON API (XHR), Encoded API (base64, protobuf, msgpack, binary), Embedded JSON, SSR, HLS/Media, Hybrid) into a typed JSON API in about 10 - 30 minutes.

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.

Claude Code will be the first to AGI.

It's just abhorrently slow, it does a lot but I always thouhgt TUI were fast but the amount of times it doesn't register my input is way too much.

Yet all the people OpenAI bought out recently say Codex is “the future”

codex is far better in terms of performance than claude code.

> I think this is the argument for UIs

To quote The Godfather II, "This is the business we have chosen."

The most popular and important command line tools for developers don't have the consistency that Claude Code's command line interface does. One reason Claude Code became so popular is because it worked in the terminal, where many developers spend most of their time. But using tools like Claude Code's CLI is a daily occurrence for many developers. Some IDE's can be just as difficult to use.

For people who don’t use the terminal, Claude Code is available in the Claude desktop app, web browsers and mobile phones. There are trade-offs, but to Anthropic’s credit, they provide these options.

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.

not really, mostly its self explanatory, it has poweruser things that are discoverable within a few minutes of reading the help. Weirdly the cheat sheet is actually missing things that you can find inside claudes help like /keybinds .

I keep hearing that, and I have yet to go there. I find the permission checks are helpful – they keep me in the loop which helps me intervene when the LLM is wasting time on pointless searches, or going about the implementation wrong. What am I missing?

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!

I don't think ultrathink works anymore.

This is your new programming language in 2026.

C is "just another abstraction on top of what we already had" (Assembly). Doesn't mean it's not useful

Claude is actually hilariously bad at knowing about itself. But if you have the secret knowledge that there is a skill on how to use Claude baked into Claude code you can invoke it. Then it’s really pretty decent

it doesn't need to exist, its all in claudes help, and easily discoverable.

Similar to prompting hacks to produce better results. If the machine we built for taking dumb input that will transform it into an answer needs special structuring around the input then it's not doing a good job at taking dumb input.

Reminds me of Vercel's Rauch talking about his aggressive 'any UX mistake is our fault, never the user's' model for evaluating UIX. (It is/was Guillermo who says that, right?)

> Ctrl-F "help"

> Ctrl-F "h"

> 0 results found

Interesting set of shortcuts and slash commands.

This. TUIs are not the correct paradigm for agentic operations. They are too constrained, and too linear.

You have a sad narrow point of view about what UX can be.

If you print something that changes daily, you are making a dead tree snapshot that starts going stale before the toner is dry, and unless you just love stacking obsolete paper on your desk, the PDF is going to win every time. A printout get old instantly.

Yeah, I think it is. It's printable if you want to have a hard copy and it's up to you when to check for a new version. Since it's auto-updated (ideally) no matter when you visit the site you'll get the most up to date version as of that day. The issues (which I don't think this suffers from) would be if formatting it nice for printing made it less accurate or if updating it regularly made it worse for printing - these feel like two problems you can generally solve with one fix, they aren't opposed.

If you align your printer and desk just right, youll have the new cheatsheet sliding onto your desk before Claude's even done updating itself.

Ask Claude to set up a cron job to print it daily

just use claudes help, if you want to know keybinds, just do /keybinds (which is not in the cheat sheet)

ugh we were promised a brave new world and still have the same crap printers

just buy a mac mini, septup an openclaw instance to track changes on this and call your printer, also order new paper when it runs out :)

so is the Unix command line ...

It’s not as if you need to know every keystroke and command to use the tool. Nor are all the config files and options not a thing in a GUI. There’s lots of inline help and tips in the CLI interface, and you can learn new features as you go.