Skip to content

Comment on LLM function calls don't scale; code orchestration is simpler, more effectiveparent

Comments

You don't have to use full write.

Use grep & edit lines. and sequences instead of full files.

This way you can edit files with 50kl loc without issue while Claude will blow out if you ever try to write such file.

In that case grep is fine, but if I have a specific artifact I need to transport from one function to another, I'll need some sort of background set / get.

Another example.

I have web pages fetching.

But web page fetching bring a lot of JS / noise.

So the fetched page instead use https://jina.ai/reader/. I get Markdown. But is this enough. No, there still a lot of links and stuff, so I again do another pipe and pass to strip a lot like URL's I usually don't need as focus here on content.

then the artifact is saved ONCE in the filesystem. I don't get why you use artefacts in the first place.

Edited in FS. Then next agent/tools directly read.

The issue is the workflow here as you make everything getting thru the model and combining tools you control and tools you don't control ( Claude Artefacts). But default I disable EVERYthing from Claude. And use filesystem. With that I have git diff to check the changes, and can as I said do such granular changes and edits.

As I said the issue is in your workflow.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.