piclaw

Tau is kind of taken as a name, BTW, by the Python harness from Huggingface. And I do agree Pi is great, but what makes it great is the back-end (pi-durable, pi-ai, etc.). I've been working on https://github.com/rcarmo/piclaw for most of the year, as well as https://github.com/rcarmo/gi and https://github.com/rcarmo/go-ai (as ports of pi and pi-ai/durable/etc., plus 3 or 4 pi-durable add-ons for Obsidian and other desktop apps) and the internals of pi are a grand thing indeed, because it was designed from the outset to be able to extend itself (which many people miss, because many people confuse the harness with the TUI).

You can turn those tools off. In fact, that is what I am doing right now in https://github.com/rcarmo/piclaw until I am positive the new MCP stuff has full parity with the MCP adapter I've been shipping for the past six months or so. I'm actually pretty happy that they did it, since 90% of what I have to integrate in enterprises is MCP-driven (it's a security and auth boundary that has become pretty much mandatory for any third-party agents wanting to reach into corporate data) and this lets me use Pi directly. Am just being cautious about the first version, because, well... it's a first version, and I like my tools stable. (I actually played around with the idea of using QuickJS myself for codemode, but since I rely on Bun that gives me the ability to use other things... never got around to do it though.)

link: https://github.com/rcarmo/piclaw/blob/main/skel/.pi/skills/t...

Not native, but a webapp: https://github.com/rcarmo/piclaw

I created https://github.com/rcarmo/piclaw to use for long-running background tasks (spec to plan to targeted code) because I needed something that could run on a server (I never run agents locally) and check on via any browser. I don’t think any messaging app will provide a good (or trustworthy) way to get to my own machines, so Tailscale+web it is. Right now these things manage most of my homelab (scoped Proxmox tokens and Portainer), help me with my projects and even bug fix themselves (they’re certainly more than good enough given guidance).

I implemented a few additional strategies in https://github.com/rcarmo/piclaw/tree/main/runtime/src/exten... - including Codex-native server-side compaction. They all have slightly different trade-offs, but I run very long sessions quite successfully

Depends on what you are using. I have been experimenting with various compaction techniques in piclaw (https://github.com/rcarmo/piclaw/blob/main/docs/pipelined-co...) and Codex has native "opaque" server-side compaction at a dedicated OpenAI endpoint.

well, I created https://github.com/rcarmo/piclaw, and as a result of that I have several permanently running agents and entirely too many projects going at once. That's _my_ "messing with AI"...

You should just integrate with pi.dev, like I did for https://github.com/rcarmo/piclaw (which has replaced Obsidian for me). I too integrated a terminal and a WYSIWYG Markdown editor (as well as plugins for a mindmap, kanban, etc.)

I added a chat tool to https://github.com/rcarmo/piclaw, so any active session can chat to each other, regardless of what model they run. It's led to interesting outcomes: https://x.com/rcarmo/status/2054185558402904338?s=20