Hacker Newsnew | past | comments | ask | show | jobs | submit | AndyNemmity's commentslogin

The biggest issue I have with these systems is, I don't want a blanket memory. I want everything to be embedded in skills and progressively discovered when they are required.

I've been playing around with doing that with a cron job for a "dream" sequence.

I really want to get them out of main context asap, and where they belong, into skills.

https://github.com/notque/claude-code-toolkit


Blanket memory doesn't scale, totally agree. I built something similar in Atmita (https://atmita.com). Agents see short summaries of each other instead of full memory dumps, and automation run logs live in their own layer.

Isn't this the idea behind holographic memory? Chopping the image in half gets you the same image at half the resolution? Or so I've heard...

What you want is a context mipmap.

Then there was the Claude article describing using filesystem hierarchy to organize markdown knowledge, which apparently beats RAG.


I built an anarchist ai agent collective so that i could learn about agents when they were a new concept. i built it the week it came out for claude code.

it runs indefinitely without my feedback or until rates limit it.

The AI agents built all of it. Not me. I realized I hadn't looked at it in awhile, and was looking for new ideas to add to my own ai system i built after learning from it.

So I thought I'd share it incase it was interesting to anyone else.

Especially the people who can't get claude code to not stop for them. I have been the entire time able to have it run indefinitely without my interaction. :)

I think i started it with a single prompt, and then told it to build everything else out it needed. That it's in control. I didn't write any of what is in the repo. I didn't tell it what to do.

It's just what it did.

EDIT: also i should commit what it has... it doesn't care about committing, so there's a whole lot of stuff it's built that isn't up there. Let me do that now.

EDIT 2: also, nothing is my ideas or written by me. It's all the collective. So please don't think i made the readme, or anything. I am not communicating ideas here, I let them do their own thing


This is why I created the /do router. I don't want to have to think about what options there are, I want everything automatically routed so I can be blissfully unaware.

https://github.com/notque/claude-code-toolkit


It is so hot here already. I'm starting to wonder if it doesn't make sense to move somewhere more reasonable at this point.


stl ?


I don't think there are reasonable metrics.

I have a custom learning system. We are all trying things, that's where ai development is.

None of us know the best solution. We are all exploring in paths. I don't find memory and persistent long term context to be an issue for me, but I am using a full custom ai claude code setup, so perhaps I have sorted it for myself. Unsure.

Can you give a specific example? Like, talk through your workflow so I can understand it better?


I have a ai system i use. I'd like to release it so others can benefit, but at the same time it's all custom to myself and what i do, and work on.

If I fork out a version for others that is public, then I have to maintain that variation as well.

Is anyone in a similar situation? I think most of the ones I see released are not particularly complex compraed to my system, but at the same time I don't know how to convey how to use my system as someone who just uses it alone.

it feels like I don't want anyone to run my system, I just want people to point their ai system to mine and ask it what there is valuable to potentially add to their own system.

I don't want to maintain one for people. I don't want to market it as some magic cure. Just show patterns that others can use.


you don't have to maintain it. Especially in the age of ai, just giving people inspiration and something to vibe from is more than sufficient and appreciated


alright. i guess i'll create a new repo, remove out a bunch of very specific pieces, and put it up.

there's a lot of patterns i think are helpful for me.


That would be awesome. I believe with AI it's all about tailoring everything to your specific workflow and style, especially anything to do with the dev environment.


right, i'm having to cut out a lot of my pieces at the moment to try to get it into a release state.

i have checks of which types of repos i'm in with branching dev flows for each one.

it's going to be hard to communicate all of this genericly, but i am trying.


No worries if it's untenable or too much though, but I'll keep an eye on the commend thread in case!

For my part, I'm currently using oh-my-opencode harness with various skills extracted and tailored from superpowers / simonw / matt pocock. Working well enough so far, but keen to really evolve the skill flow and how they connect and are used in coordination with the various subagents.


I ended up releasing it. Let me know your thoughts

https://github.com/notque/claude-code-toolkit


if it's on github you could even archive it from the get-go


My experience agrees with this.

Which is why I use a skill that is a command, that routes requests to agents and skills.


https://vexjoy.com/posts/

Writing about AI so far, but who knows. Just started it.


I use Hacker News commenters.

There was someone a while ago who made a funny post about the type of Hacker News commenters. So I have 5 of them that will review things, and ended up being way more effective than I ever imagined they'd be.

│ contrarian-provocateur-roaster │ Challenge premises, explore alternatives │ "Have you considered..."

│ enthusiastic-newcomer-roaster │ Accessibility, onboarding friction │ "Wait, how do I even..."

│ pragmatic-builder-roaster │ Operational reality, production concerns │ "This won't survive 3AM pages" │

│ skeptical-senior-roaster │ Long-term maintenance, sustainability │ "Who maintains this in 2 years?" │

│ well-actually-pedant-roaster │ Terminology precision, verifiability │ "Technically, that's not..." │


This sounds great :D feel like sharing the prompt?


Here is one of the agents. I prefer large agents, so you can tweak it to your purposes. It also calls some of my skills and other pieces, but it will give you the "gist" of it.

https://gist.github.com/notque/e57cb975a3df7780824ce4085a59a...


I keep having the same conversation with people struggling with Claude Code.

Someone tells me it "forgets" their instructions. Or it hallucinates fixes. Or it ignores the rules they put in CLAUDE.md. And when I ask what their setup looks like, it's always the same thing: a massive system prompt with every rule for every language, stuffed into context.

So I wrote up how I solve this.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: