Their CI take is early but promising: https://radicle-ci.liw.fi/

This just describes a watcher service that kicks jobs off on an external CI system and logs the results? Not much more detail than that.

Gitlab and Github have pages and pages going over the domain language used to configure the job triggers. Jobs can trigger other jobs either in response to completion or as a dependency etc etc.

I would say these radicle-ci designs as they are now are actually quite rudimentary. That's perfectly fine for an early project but at this point I think you have to say that they won't have a CI system ready for quite some time.

I don't understand why you'd want them to built another CI system. Just for the sake of it?

Feels like using a free Jenkins gets you everything you want. Doesn't need more than a container or Java either.

That's also perfectly fine if that's what it is. I would just phrase that as "They don't have CI but they provide hooks."

it's a little of both: on the one hand we're working on CI integrations (through generic webhooks or CI-engine-specific adapters that basically implement the CI engine's API [1]), so you can keep on using your existing CI solution. On the other hand, yes, there is also work towards a new CI engine (Ambient [2]), which aims to make it safe and secure to run CI on other people's code, which is important when working towards a distributed, community-ran, CI system. We should have more docs regarding the CI story up on radicle.dev in the next week or two.

[1] - https://radicle.network/nodes/index.radicle.garden/rad%3Az3G... , [2] - https://ambient.liw.fi/

Radicle is really underrated, especially when working with agents. I find it a joy to use for my agentic workflows.

If there's purely an agentic forge one day, it's likely going to be a distributed one, with cryptographic identities and signed artifacts by default.

AD: Feel free to post on our Zulip [^1] about your experiences of agentic workflow if you haven't already! Some of the team are interested in developing the agentic workflow experience.

[^1]: https://radicle.zulipchat.com/

Doesn't even come close to Zulip in terms of features.

Zulip used to have a really neat feature where you could open up certain channels to be indexable by search engines. Basically turning it into an open forum. The feature is still sorta around but completely broken. Quite unfortunate imo. It was a really neat solution to the walled garden problem with team chats

Zulip product lead here -- I'm not aware of anything in this space that used to work and no longer does.

There's long been a way to make Zulip channels searchable with zulip-archive (https://github.com/zulip/zulip-archive), and that continues to be available.

Making the app-native web-public channels accessible to search engines is a big technical project, tracked as https://github.com/zulip/zulip/issues/21881.

Ah thanks for the correction. For some reason I mixed up Zulip with Linen.dev

https://www.linen.dev/

I guess this feature has been requested for Zulip for a long time

https://github.com/zulip/zulip/issues/21881

How does it compare to MatterMost [1]?

[1] https://mattermost.com/

It doesn't have these pesky message and user limits, unlike Mattermost[1].

[1] https://github.com/mattermost/mattermost/issues/34271

Gotcha! Though that is not for the self-hosted version IIUC?

But yea, rust-chat in a way seems like more of a proper open source project ...

For self-hosted version as well, unless you patch it.

"AD" ?

His initials

Advertisement

What makes it a joy to use with agents?

Probably less issues with account management and rate limits.