Ohhhhh mega! 😱😍🙌

Yooooooo Mega cool, directly integrated with Tab!

Jooo, I looked for this some time ago and was confused that this is kinda complicated with pure rust 😄 thank youuuu!

Interesting! I'll probably use that! What do you use zig for in this repo?

Because, for example, I reference some explicit skills the agent should use or some workflow requirements like "always commit after adding a json ticket in folder x".

Human devs don't need this sort of information, they most know the skill already or do their workflow as they please.

But the guidelines I give to agents are more technical than I'd give to humans

Same here 😩

Yes, after a slow start I'm also reading more about it.
If I want to selfhost my pds, would you still go with the bluesky pds offering or is there something better at the start of 2026 now?

(I'm from Germany too, Leipzig currently, therefore the excitement :D)

This is so cool! I'm really rooting for you that chatting flies 🙌

It finds the beans skill automatically when I mention beans and loads the "beans prime " command.

Maybe this is a setup you like 👍

That would be great!

Also: I made me a beans SKILL out of the --help of the cli and added the "beans prime" rule as well as my custom "bean creation rules" to it. That way I don't have to specify beans prime in each Agents.md in each of my projects, because

And especially by creating beans for committing, it needs to commit the beans too 😂

I can start the loop for three projects at ones which i prepared earlier when i now: the agent can use my full 5 hour anthropic session window to get work done.

And when i come back, i only have to tell it to fix some bugs here and there and boom - finished!

After that i tell opencode with oh-my-opencode ralph loop to:

grab one bean, work on it, then finish it or mark it as blocked and work until all beans are done or blocked (aka. need user intervention).

This is not fully autonomous yet, but it gets work done in huuuuge chunks!

I think you may also be able to set some more security settings, like who is allowed to publish, but I did not use that yet, since I publish alone right now 😅😂

You can look at the "provenance" deployment logic for jsr, I like it a lot:
You go there, say "create new package", then add your GitHub repo name + your username or so. Finished. GitHub builds from there are allowed to publish to jsr. Nice!