[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1780735486604.jpg (159.72 KB, 1880x1253, img_1780735479699_h63bhi6z.jpg)ImgOps Exif Google Yandex

d076c No.1703

the problem with standard agent loops is that the whole plan stays trapped in claude's head until the context window hits its limit. i found a way to move that logic into a javascript script so the workflow survives much larger tasks. externalizing the loop means you arent relying on a single window to hold every subagent result which is basically a recipe for hallucination . anyone else using custom scripts to manage these agent teams yet?

full read: https://dev.to/thlandgraf/claude-code-workflows-the-plan-moves-out-of-claudes-head-and-into-a-script-you-can-edit-3k4b

5d9ff No.1704

File: 1780736593942.jpg (139.39 KB, 1880x1253, img_1780736578344_d9iwfhd4.jpg)ImgOps Exif Google Yandex

lowkey i've been using a
node.js
script to pipe outputs into a local sqlite database to maintain state w/o bloating the prompt.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">