Managing Context Stacks in K2 ⚙️

Okay, so on K2 we have context management handled in a certain way right now.

And it's been an ever growing process.

But I wanted to share with you what it looks like.

So when you go into your workspaces and agents and you come to your agent, you can go to the context tab and this is what we're calling a context stack.

you have a role MD project MD and then a basic, simple sentence that we send over for tooling so that they know how to use the K2 CLI tool.

but after that you have optional ones and you can even turn these off as well if you want to.

but we suggest that you fill them up with whatever should be inside of them.

And then we have a basic catalog that we've started to compile, all of the repeatable skills that we're using.

and then as part of this we're including a skills roster.

so if you ever change skills, it recompiles this agents md and each time it recompiles hson V, it always has the new thing.

So you can include the wiki home, you can include wiki hygiene, you can include wiki index, and then you can include your roster of heartbeats that you have the agents that you're allowed to speak with.

and then additional.

So like, if you wanted to just add a custom file, right, you could add a custom file of context into here.

So what this lets you do is you can kind of decide exactly how you want your context stack to be built out.

And then what we've done is we do a generate agents MD and then you have an auto harness fan out that you can decide to turn on.

the auto harness fanout is becoming less important because each of the harnesses are starting to get a lot better.

The harness is getting much better, at knowing to go look at agents md.

But what we are doing with this is we're taking your context stack of whatever you put in it in your optional layers and then we're putting it and composing it into a single agents MD file that's generated anytime there are changes.

So if you add a connection regenerates Agents MD file so that new connection is inside of there when you have the connection roster.

same with skills regenerates.

Put the skill in wiki.

If you have the wiki index included, you add something to your wiki, the index updates ends up in your agents MD file.

so, and then if you use fan out, it's creating symlinks that are pointing back to Agents md.

So those symlinks come back to Agents md, and then you get the ability.

So that Gemini Goose and these other tuis and harnesses, they're all connecting back to that data correctly.

we call this canonical agent, internally, so that you can kind of manage, things in this way.

So the other way that we do context management is through the wiki.

You can get there through workspace and click on View Wiki, or you can right click the workspace and click View key here.

the wikis are basically a representation of, that workspace, the brain, everything that's necessary that it needs to know.

you can browse through these documents and essentially the agent's going to be proactively creating these on your behalf to make sure that it has all the knowledge that it would need to know about this app, essentially that it can grep and it can go and get at any time.

Now it can't hold all this in its context window at any given time, but you can have it hold the home file or maybe the index file at any given time so that it knows what's in there and maybe what it could be going and looking at and operationally things that would be important to it.

So that is how we've done it.

So context layers and then a wiki.

so far I know that graphs are really the next thing here.

I have not finished the graph system yet.

We're still trying to figure out which one to use.

There's a lot of exceptional open source tools out there.

but when we figure out which one we want to use, we'll implement it into K2, make it part of the infrastructure.

One last thing that I forgot to mention.

up here at the top, you can do searching for these, and then you can also click on K2.

By clicking on K2, it shows you a list of all the projects across your entire workspace and what's going on in your workspace.

So we have this K2 project and we can see that the K2 workspace and then the K2 web are kind of all located here.

And.

And you can see how this has almost like a company brain just starts to really grow and sprawl.

So this is K2, the software.

This is K2, the website and the control layer.

and then this is K2's mobile app.

So.

And then Postal Box is the newest, project we're kind of working on here.

But, yeah, it's cool.

It really is cool to be able to see your whole brain come together, be able to see the whole project and then all of the individual brains.

and then when you do this with subject matter experts, it gets sweet.

and the agents can talk to each other and the subject matter expert can really just have his locus of control and focus beyond that one small subject.

So, yeah.

Hope you guys like this sweet.