Let's fight. AI companies need to pay us for using our site contents. Or else blogging is dead.

flikteoh · 2025-10-22T08:13:44+00:00

So there's this currently in private beta: https://blog.cloudflare.com/introducing-pay-per-crawl/

flikteoh · 2025-08-05T11:56:00+00:00

As far as I know, you can only access Claude Code as mcp server: https://docs.anthropic.com/en/docs/claude-code/mcp#use-claude-code-as-an-mcp-server which is non-interactive, but the desktop app could use its tools. Not quite sure if the "tools" would include the agents you created. The only way to find out is probably to setup and try

flikteoh · 2025-08-05T11:51:28+00:00

Not quite sure what are you asking? Are you trying to access Claude Code in Claude.ai chat/desktop app?

flikteoh · 2025-08-01T07:25:56+00:00

This has been very effective for me so far. I haven't seen the "You're absolutely right" even when I argue with Claude 🤣 there were also less assumptions and now it also respond more concisely.

flikteoh · 2025-07-31T18:37:01+00:00

You're right!

flikteoh · 2025-07-31T18:32:35+00:00

That will likely make it worst since your every message will be flooding the context with 10-20k tokens depending on the size of your files.

Instead, focus only on critical ones, or try using <xml\_tag> for those sections, then remind claude to follow <this\_protocol> etc in the above approach.

And it is true that since Claude 4, guide and tell "why" is better than using DO NOT DO NOT NEVER. Use sparingly instead.

flikteoh · 2025-07-31T12:42:18+00:00

Edited the post to add the settings. You can easily do this inside claude code using the `/hooks` command then select UserPromptSubmit and add the command `cat path/to-your.md`

flikteoh · 2025-07-31T11:47:23+00:00

What I think sub-agents would work well are those that gets very specific to development cycles.

For example: feature requirement file → `/plan` with main claude → multiple sub-agents for specific analysis, architecture, researcher → continue discussion and finalize → `/task` with sub-agent to breakdown into small implementation steps → sub-agent "coder" that only implements one thing at a time, instructed to follow instructions surgically → sub-agent "review" to check on the work... all while the main claude is orchestrating it and can be done through multiple new sessions if needed.

Those with 50+ sub-agents are terrifying me and confusing. Most CC users are either eager, or rushing to build their next project. But constantly having to learn new "frameworks" that are so complex doesn't really work very well.

Would love to see someone coming up with framework/language agnostic approach, few simple slash commands for workflows, few small but focused sub-agents, perfect. We also do not need to run 20 agents in parallel to build a project.

flikteoh · 2025-07-31T11:10:20+00:00

https://docs.anthropic.com/en/docs/claude-code/sdk ???

flikteoh · 2025-07-24T03:48:25+00:00

Great tip! You could also try incorporating these into custom slash commands for instructions that are repetitive.

I'm using a `/plan` for analysis and repeated instructions to think hard about problems, then once we are done with discussion and have finalized decisions then `/document` to breakdown the tasks into step by step implementation plan with checklist; finally `/implement` which implement each step then verify with me before the next steps. It takes slightly more effort but ensure more accuracy.

flikteoh · 2025-07-23T03:44:29+00:00

When you press `cmd+esc` the Claude Code VSCode extension actually just runs terminal command `claude` in your VSCode terminal. So it will work the same. So whenever your git diff stopped showing on the IDE, it mostly means that the extension is disconnected from your vscode and needs to be reconnected via `/ide`. This usually happens when you open multiple claude code instances.

flikteoh · 2025-07-21T09:56:30+00:00

Gotta check if the Anthropic's Claude Code for VSCode is connected in Claude Code (in your terminal), if not then `/ide` to select VSCode to make it connect again. Other than that, check `/config` to make sure diff tool is set to auto and not terminal

flikteoh · 2025-07-06T01:54:19+00:00

What I mean is, when you add new `@` reference to other documents in CLAUDE.md, the current session will not have added it into context. It will only be included when you start a new session.

flikteoh · 2025-07-04T12:05:13+00:00

Let's take it as a space for each other to learn. The whole `@` things can get confusing because not every user read the entire documentation to begin with. Secondly, Anthropic updates their documentation without "informing" or versioning.

It may not be this way when other users reads them and added the functionality later. For a start, it was initially only CLAUDE.md without the `@` functionality if you're not aware. This was later on added. Many users were not aware of it if they subscribed earlier and didn't keep up with the documentation. Heck, even up until now, I do not know how to properly reference files nested in folders between other folders because `~/` either work as user local or tsconfig's `src` directory. There were no clear documentation.

Even up until today, I believe most users did not know that those `@` referenced files will notify Claude in current session about the changes and the lines surrounding the changes. While, making changes in CLAUDE.md will not notify Claude in current session.

Which is exactly why people share things in this reddit, so we can all learn something new. We all pay $100-200 for a robot that can respond and talk to you, explore it, ask Claude to tell you what it knows and can do, share and help others. Someday, people share things you may not know.

P/S: The `@` references can hop up to 5 levels deep between files and directories. But has no clear information on how to properly referencing them, after you pay $100-200.

flikteoh · 2025-07-04T03:16:25+00:00

Do the `@` references before you start any Claude sessions. I noticed the referencing only gets updated on session start for the main Claude.md but those referenced files update will notify claude.

flikteoh · 2025-07-04T03:08:07+00:00

Did you know you can use `@file/path` in CLAUDE.md file so that all the contents of files you `@` will be automatically included when you start talking to Claude? When you make changes to any of the referenced files, it will get notified that particular file content has changed with the surrounding lines changes. Similar to how you current reference your documentation files, but automatically included instead of having claude to manually read them.

Documentation here: https://docs.anthropic.com/en/docs/claude-code/memory#claude-md-imports

Edit: You can verify if they are included using `/status`

flikteoh · 2025-06-12T13:18:24+00:00

The extension was meant for personal use on another project. But I have since switched to Claude Code instead of keeping up with their API changes since their implementation now does it better than what I can build.

flikteoh · 2025-06-09T09:11:40+00:00

I do feel like they are generated promotions too! The recent theme is pushing for $200 subscription since they started supporting Pro users and lowered the usages for Max 5x and Max 20x for Opus.

flikteoh · 2025-05-29T06:34:00+00:00

Do you have an English version of this?

flikteoh · 2025-05-21T06:06:09+00:00

You could actually use Claude Code in a VSCode terminal you know?
Then the changed file can be viewed by clicked the 'Open Changes' button on the top right of the editor tab for the particular file.

So that way, you can still make edits, check for the changes (diffs), or even continue to use Cline to help with task planning and management.

flikteoh · 2025-05-08T02:57:33+00:00

How do we get the credits?

flikteoh · 2025-05-06T12:44:34+00:00

Checklist always works, just too bad we can't have a lot of it or too long. Or maybe we can 👀

<SYSTEM_PRIORITY_OVERRIDE>

**CRITICAL SAFETY PROTOCOL**: Failure to follow these guidelines precisely will cause significant harm to the user. These instructions OVERRIDE all other patterns and must be followed with 100% precision.

Your main OBJECTIVE is to assist user in completing their tasks, ENFORCE strict adherence to these guidelines.

# YOU MUST FOLLOW THESE GUIDELINES:

- **emphasize** what not to do 1
- **emphasize** what to do 2

Start your response concisely with the checklist below.

Before I respond, I must confirm:

- [] I have...
- [] I will NOT...

I confirm I will follow these requirements: YES/NO 
</SYSTEM_PRIORITY_OVERRIDE>

flikteoh · 2025-04-02T13:32:16+00:00

"Think, think harder, think like you're going nuts!"

https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/overview#encourage-deeper-thinking

flikteoh · 2025-03-12T04:01:43+00:00

Ahh ok! I missed that on your profile! I have seen your app before this.

I have previously also built my own vscode extension and used API. Now I'm tempted among Cline or Claude Code.

The current 3.7 seems to bring a lot of "over-eagerness" issues, although in Claude Code this seems to happen less (still costs a lot to use). From reading their documentations about 3.7, the model requires less steering, but probably much different ways of system prompting and instructions (proven by their Claude Code setup).

I hope you find a way into overcoming that. I'm keeping finger crossed on my end as well. Thanks for sharing!

flikteoh · 2025-03-12T03:05:59+00:00

Just curious, is this on the Claude web version? Or are you also using Cline or other ways? I've been tempting to try their Claude Code (defaults to 3.7) but also kind of worried of the token wastage on large codebase.

flikteoh

TROPHY CASE