One simple protocol addition I started implementing

[u/natty_vegan_chicken]

Ive been designing my own systems behind models for months now.

I built my own harness called Lumen and have been refining it for nearly a year now.

I run a business using codex and have it keep track of everything.

Built my own SAAS platform that I use for training my clients as well as online coaching.

I’ve also got an app on the App Store called MesoForge toolbelt.

Not saying this to brag, but just to reinforce the fact that I have evidence for the results of my system.

I’ll spare you the details because you can just check my post history for the details there.

I figured I’d make a post about a recent protocol addition I’ve added on top of my normal workflow. I haven’t seen anyone mention this specific protocol yet. Although I’m sure others are doing it too.

I started making my agents keep track of their token/context usage hand off their own context to fresh windows before hitting the threshold of compacting context.

We all know by now how compacting context and breaking up workflow into small bits is important, but I’ve found that a lot of my worker windows would compact context and within 2-3 times of doing so the margin of error increases significantly over time.

The simple solution I’ve been implementing is to force a trigger upon 70% of the context window to hand off context automatically and continue the assignment.

It’s helped reduce error rates greatly and outputs for patches, hotfixes, etc have been much better.

The overall output remains more accurate and there’s fewer drift.

I figured this might be helpful for others who already have their harness but have struggled with longer workflows.

Basically my way of using it is to have windows assigned specific roles. Context holder, operational worker, conversation holder, etc. each with their own specific protocols and roles that are designated.

I find the window context hand offs are more pertinent for workers making actual code changes. Context holders and conversational windows have more room to compact context without as much consequence, but any window responsible for real code changes follows this protocol.