Oh, well this makes a lot of sense! Let's see how it handles node_modules.

What if the bits I'm transferring are "I don't remember the precise syntax, but here's a link to the relevant documentation."

Maybe this can help me prune my knowledge base of uninteresting pages. Then again, if they never consulted, are they really an obstacle?

I've been using a combination of `weave` and ad hoc "blackboard pattern" skills—some self-made, some borrowed—but I haven't really felt they've earned their keep. Maybe I'm not working in parallel enough, or else maybe I'm relying too much on a parent coordinator session to resolve conflicts.

I encountered similar issues before I built Foremerge, ie auto router, orchestrater and shared blackboard type memory structure. The agents were aware of what was put into memory but still did their own thing and created conflicts. I still see it in claude code today when it creates subagents without Foremerge setup for the project. It resolves itself but you can see it burning through token usage to do so. If your using a single agent you dont necessarily need Foremerge but it still helps when subagents get created automatically and gives you the audit trail of intent decisions essentially at almost zero cost of having the tool installed. Where Foremerge really shines is if you bounce back and forth between claude and codex with no single parent. I dont know Weave well enough to know where it sits. The question I'd ask about any of them is what happens if you kill it? If the agents stop then it's an orchastrator, if the agents continue and you just loosed the shared picture then its a coordinator like Foremerge.

How many sessions do you typically run at once and are they all children of the same parent?

Up to ~25, and they're not exactly "children", but I do have a coordinator agent that can selectively intrude on their sessions. I use `aoe` to spawn and communicate between worktree-isolated sessions:

https://www.pasteboard.co/XirzoTywU6lz.png

I think Foremerge would be extremely useful in your setup especially with 25 agents running in parallel. While aoe manages the physical layout and terminal communication (ie. spawning sessions, executing commands, wrappting tmux etc.), Foremerge would act as your logical synchronization layer that prevents the agents from stepping on each others toes. They should complement each other really well. do you know what causes the coordinator agent to intrude right now? is it both plans being on the blackboard or is it being triggered by diffs or failing merges?

Also the motivation behind CLIs and SDKs, right? And the way agents write Python regularly, these days, I am hopeful what can be offloaded to deterministic systems will be.

Remember that quality output is a necessary but insufficient property of a generative model.

Prompt-adherence is really hit-or-miss—especially if one lacks the visual vocabulary. Likewise with coding, I find junior devs don't think to prompt re: respecting this-or-that interface, or refactoring to point-free style, etc.

So, as others have said, the artist knows better.

Nice! I use an old madlibs library I built for D&D: https://github.com/gavmor/Dunmanifestin

that's very clever

Thanks, it introduces a little "jitter" that keeps the egg from rolling down the same face of the ridge every time. Possibly, the same could be accomplished with a judicious application of the temperature parameter.

But how to tell the model which section is supposed to be populated with spicy tokens?

"A DDOS on free resources" is called "moral hazard", AFAIK.

It's not saying there's something material out there which is relatable—it's saying that there's some ontological category, i.e. some Platonic or geometrically congruent notion, that is representative (if not constitutive) of the experience of being you.

I'm decompiling an obscure 1998 computer game using an LLM agent skill that I'm simultaneously developing from papers and books on reverse-engineering (a subject I've never previously engaged with) with the aim of migrating it (well, at least its assets) to the browser: https://esoteria.pages.dev

Here's the skill: https://github.com/gavmor/x86-cpp-reversing-skill

It's all slop, but it's battle-tested and producing results. It's quite fun and inspiring to see some of these assets like textures and geometry that are improperly decompiled, bit shifted or something like that. produces a lot of abstract, glitchy art.

To make sure that my process and results are reproducible, I've gotten back into maintaining Concourse CI pipelines. They were very useful when we were shipping a fork of k8s for VMware, and now they are a fun way of shipping cyberpunk billboard sprites to Cloudflare buckets.

I got back into Concourse in order to attempt a more rigorous approach to generative AI experimentation as well. Unfortunately, there are just so many odd techniques, configurations, loras, and utilities striking my fancy that my experiment pipelines have exploded into the dozens, and Concourse is not a large enough or a high-level enough organizing principle.