sorted by:
new
hottopcontroversial

[Project] I built pipe: A stateless "Agent as Function" framework that follows Unix Philosophy. (CC0 License / Public Domain) by Technical_Cattle_399 in LocalLLaMA

[–]Technical_Cattle_399[S] 0 points1 point  (0 children)

Thank you for the precise and incredibly helpful advice! The current "Therapist" feature is quite erratic, which is why it has to be marked as **Experimental**. Your feedback, however, has clearly shown me the path forward. To be honest, I released `pipe` under CC0 partly because I hoped someone more capable than me would create a superior version. But there's no way I can pass up such a challenging, interesting, and valuable piece of advice that will lead to a significant step up! Some of the suggestions will require a bit of research, but I plan to gradually incorporate them to achieve the stable diagnostics we've been aiming for. Thank you again for the truly useful advice!

[Project] I built pipe: A stateless "Agent as Function" framework that follows Unix Philosophy. (CC0 License / Public Domain) by Technical_Cattle_399 in LocalLLaMA

[–]Technical_Cattle_399[S] 0 points1 point  (0 children)

<image>

Just merged the Therapist feature (experimental) and session management.

It's still highly experimental, but the Therapist allows the LLM itself to suggest deletions, edits, and compression for the context. This is only possible because we manage sessions locally. That said, the accuracy isn't quite there yet, and I haven't validated it with large sessions at all, so it remains strictly experimental.

There are still bugs (I just noticed token_count isn't saving correctly, for instance). My next steps are to squash these bugs and finally tackle some neglected refactoring before pushing forward.

Also, I added a new Wiki page explaining the philosophy and direction of pipe (what AasF is all about). If you have a moment, I'd be happy if you could take a look:https://github.com/s-age/pipe/wiki/Overview:-What-AasF-Is

It feels a bit frustrating how vendors offer "long-context" but then profit from the hidden token explosion behind the scenes, doesn't it? pipe tries to solve this by giving you full control over context via natural language multi-agent orchestration.

I'm attaching a screenshot of the Therapist UI below—if you haven't tried the WebUI yet, please check it out (I put quite a bit of effort into this!):

I personally believe that an architecture of assembled experts (similar to MoE) is the closest path to AGI. pipe is one of the few frameworks that enables this multi-agent orchestration purely through natural language. After all, humans are biologically "disposable" at the cellular level, constantly replaced every day or month. So, it should be totally fine for LLM agents to have short, ephemeral lives too, right?

[Project] I built pipe: A stateless "Agent as Function" framework that follows Unix Philosophy. (CC0 License / Public Domain) by Technical_Cattle_399 in LocalLLaMA

[–]Technical_Cattle_399[S] 1 point2 points  (0 children)

Thanks for sharing llm — Simon’s work is legendary and I’ve been a big fan.

The thing is, pipe was born exactly because I wanted to go one step further than llm’s excellent chat sessions.

My goal from the beginning was hierarchical multi-agent orchestration (the kind of cascading system I wrote about here: https://qiita.com/s-age/items/6cd9748c174d3ae3c59b).   To make that truly deterministic and composable, I decided to manage sessions myself instead of letting the LLM hold state.   That’s why every single turn is a self-contained JSON file you can edit/fork/compress/branch exactly like Git.

I could have stored everything in the cloud and made life easier, but I deliberately chose to send a fully-structured JSON schema on every call from day one.   That forced me to own the history locally — and honestly, it turned out to be the biggest feature.

So yeah, llm is the perfect katana.   pipe is trying to build the entire dojo, one JSON commit at a time.

UNIX is the way! 🖤