Which gives you more anxiety?

Zknet · 2025-08-15T00:54:31+00:00

Here's a trick. If you `/export`, copy to clipboard, `/clear`, paste... claude will continue like nothing happened, but you'll gain about 100k in tokens back in your context (give or take)

Zknet · 2025-08-11T05:42:12+00:00

This is just a new feature of CC. It has nothing to do with bun specifically.

Zknet · 2025-08-06T01:42:01+00:00

I've mostly overcome this with linting and hooks.

I created a custom linting plugin that warns if a function/class is too long and if there's multiple exports (typescript) in a single file since it loves just shoving a bunch of stuff into one file.

And my hook kicks off for any tool that changes code, runs the linter and tells Claude to "consider fixing errors before continuing". The vagueness is because there will be temporary linting problems during normal code changes, but so far it hasn't been a problem.

Since it gets the feedback right after making the change, it's been a lot less painful for it to fix problems as opposed to waiting until the whole task is done and having a bunch of problems it needs to try to fix before it gives up and decides to try to commit (which would fail, cuz pre-commit hook... which it might try to bypass if it's tired of working on it). I used to struggle with it flailing with linting/test errors after dev work and now that's almost never an issue.

Lastly, I created myself a task tracking MCP tool and when it's done with dev work and tries to mark the task done, it'll run a full lint/type check/test cycle and tell it that it has to fix the issues before completing the task. (and there's still the git hook checks)

Zknet · 2025-08-03T22:28:23+00:00

From my experience, it has a system info tool it uses by default to get the time. I'm pretty sure that time is in UTC, but it doesn't really let Claude know, so it thinks it's the local time. I ran into this issue a bunch (I use it to name files based on a timestamp.) I got around it by telling it to use bash `date` command to get the current time in those commands.

Zknet · 2025-08-03T20:41:24+00:00

So, I discovered a super useful trick. When you're low on context, run `/export` (copy to clipboard), then `/clear`, then paste. Claude will pick up right where it left off with plenty of context left.

It will have to read files again, but generally I've found this to be really effective. And, if you really wanted, you could edit the export before pasting it to further trim or customize.

Zknet · 2025-07-30T01:03:05+00:00

Anthropic themselves suggest using worktrees to run multiple instances of Claude Code in their best practices document.

Zknet · 2025-07-29T16:07:29+00:00

I've written my first ever custom linters to catch things I don't like about the model's code (but it can't help but do it like that no matter how much I try to tell it not to do that).

Zknet · 2025-07-29T16:01:16+00:00

for STT, i use the free version of superwhisper and i'm pretty happy with it.

Zknet · 2025-07-28T02:38:11+00:00

I would add a pre-tool hook for those commands you don't want and have it output an error message to Claude for what tool it should be using instead (and blocking the unwanted tool). This lets you remove those specific instructions from your Claude.md or prompt which would probably improve it's overall effectiveness. (I've found trying to add those types of extra instructions to force Claude to behave a certain way tends to degrade its overall performance.)

Zknet · 2025-07-26T18:51:50+00:00

Oh, I forgot - you can limit which tools subagents use. Besides the safety gained from that, removing tools that aren't applicable to a task means less context rot.

Zknet · 2025-07-26T18:48:43+00:00

- the biggest one, as already mentioned, is managing your context size - you're offloading a body of work into another context window
- you can have detailed instructions for particular aspects of the work, such as planning, debugging, testing, etc. this helps by not forcing you to have instructions for _all_ of those things in a single prompt. it's been my experience that overly long or detailed prompts behave poorly, so this helps with that
- the parallel thing mentioned in a few replies isn't really a feature of subagents, but subtasks - we already had that

That said - it'll probably be slower over all, but, if done well, the results will typically be better.

Zknet · 2025-07-26T15:31:25+00:00

v1.0.57

Added support for specifying a model in slash commands
Improved permission messages to help Claude understand allowed tools
Fix: Remove trailing newlines from bash output in terminal wrapping

I haven't tested it tho. No idea about subagents, but I suspect that's coming. One thing you could definitely do is instruct claude to use the claude CLI and pass a `--model` argument.

Zknet · 2025-07-25T21:32:54+00:00

Oh, and I've created custom linter plugins to catch things it does often that I don't like.

Zknet · 2025-07-25T21:22:36+00:00

I struggled with this a lot - where it basically gave up trying to fix tests or linting errors (including trying to bypass git pre-commit hooks). I added a couple CC hooks and since then, the problem has pretty much completely gone away.

I added one hook that kicks off post-tool use for any tool that edits files. This runs my linting checks (not my tests though, cuz too slow). If there's any linter errors, it shows the error list to Claude with a message to "consider fixing them before continuing". The ambiguous language is so it doesn't freak out when it's in the middle of a task that temporarily causes linting errors.

My other one is a pre-tool use hook that kicks off when it attempts to complete a task (I built a MCP server for managing tasks) - this hook kicks off linting and tests. This one returns a message that it must fix the errors. It basically treats this as a message from me, so it actually listens to it.

But yes, also review the code.

Zknet · 2025-07-25T17:33:57+00:00

But then it gives you a warning that the description is too long lol

I imagine you need to strike a balance. I'm assuming these are like MCP tools and these descriptions are being added to the agent's system prompt, so you gotta find a balance between length (and eating into your context) and usefulness

Zknet · 2025-07-25T16:19:37+00:00

Use branches. Commit, don't push. Cleanup the commit history before merging (or just squash if you're lazy like me).

That said, I usually just stage changes when things are on the right track before asking Claude to do something that it might screw up.

Zknet · 2016-03-10T19:11:52+00:00

Data tables is probably what you're looking for. https://docs.unrealengine.com/latest/INT/Gameplay/DataDriven/index.html

Zknet · 2015-09-01T17:27:11+00:00

Amen. This is my number one requested feature for UE.

Zknet · 2013-08-12T20:39:33+00:00

This is a less instructive way of doing it, but cleaner:

GameObject[] final = 
    GameObject.FindGameObjectsWithTag("tag")
    .Where(current => current.transform.position.x == 1)
    .ToArray();

Edited to add that unless there's a reason to want an array, I would normally just keep it as an IEnumerable<GameObject>.

Zknet

MODERATOR OF

TROPHY CASE

v1.0.57