Universal Claude.md – cut Claude output tokens
101–110 of 192 posts
Re: Universal Claude.md – cut Claude output tokens
#102From the file: "Answer is always line 1. Reasoning comes after, never before." LLMs are autoregressive (filling in the completion of what came before), so you'd better have thinking mode on or the "reasoning" is pure confirmation bias seeded by the answer that gets locked in via the first output tokens.
Is this true? Non-reasoning LLMs are autoregressive. Reasoning LLMs can emit thousands of reasoning tokens before "line 1" where they write the answer.
Re: Universal Claude.md – cut Claude output tokens
#103Someone measured how this reduced token efficiency, spoilers: efficiency is highest without any instructions. https://github.com/drona23/claude-token-efficient/issues/1
Re: Universal Claude.md – cut Claude output tokens
#104Earlier quoted context omitted.
I wrote a skill called /handoff. Whenever a session is nearing a compaction limit or has served its usefulness, it generates and commits a markdown file explaining everything it did or talked about. It’s called /handoff because you do it before a compaction. (“Isn’t that what compaction is for?” Yes, but those go away. This is like a permanent record of compacted sessions.) I don’t know if it helps maintain long term…
Did you call it '/handoff' or did Claude name it that? The reason I'm asking is because I noticed a pattern with Claude subtly influencing me. For example, the first time I heard the the word 'gate' was from Claude and 1 week later I hear it everywhere including on Hacker News. I didn't use the word 'handoff' but Claude creates handoff files also [0]. I was thinking about this all day. Because Claude didn't just use…
Re: Universal Claude.md – cut Claude output tokens
#105Re: Universal Claude.md – cut Claude output tokens
#106From the file: "Answer is always line 1. Reasoning comes after, never before." LLMs are autoregressive (filling in the completion of what came before), so you'd better have thinking mode on or the "reasoning" is pure confirmation bias seeded by the answer that gets locked in via the first output tokens.
Is this true? Non-reasoning LLMs are autoregressive. Reasoning LLMs can emit thousands of reasoning tokens before "line 1" where they write the answer.
Re: Universal Claude.md – cut Claude output tokens
#107Re: Universal Claude.md – cut Claude output tokens
#108It seems the benchmarks here are heavily biased towards single-shot explanatory tasks, not agentic loops where code is generated: https://github.com/drona23/claude-token-efficient/blob/main/... And I think this raises a really important question. When you're deep into a project that's iterating on a live codebase, does Claude's default verbosity, where it's allowed to expound on why it's doing what it's doing when it…
Re: Universal Claude.md – cut Claude output tokens
#109Re: Universal Claude.md – cut Claude output tokens
#110I love how seamless and intuitive Codex is in comparison:
~/AGENTS.md Meanwhile Claude doesn't even see that I asked for indentation by tabs and not spaces or that the entire project uses tabs, but Claude still generates codes with spaces.. >_<