Viewing profile — keks0r

Does this mean, that the full node compatibility purely depends on oxc for transpiling? So oxc compatibility = nub compatibility?

How does this integrate with Git? is the CRDT stack mainly for syncronizing locally? and then "snapshotted" into git? Or how would the team collaboration part of this work?

Claude Code / Codex session metadata can actually tell a story about how you work with AI coding agents. 50 days ago we posted about analyzing 1.6k Claude Code sessions from our ow…

yes we had to tune the claude.md and the skill trigger quite a bit, to get it much better. But to be honest also 4.6 did improve it quite a bit. Did you run into your issues under …

Team of 4 engineers, 1 data & business person, 1 design engineer. I would say roughly equal amount of sessions between them (very roughly) Also maybe 40% of coding sessions in larg…

We dont expect anything, we put it out there, and we might be able to build trust as well, but maybe you dont trust us, thats fair. You can still run it yourself. We are happy abou…

1. can only partly be answered, because we can only capture the "edits" that are prompted, vs manual ones. 2. for us actually all of them, since we do everything with ai, and inves…

the skill usage was one of these "I am wondering about...." things, and we just prompted it into the dashboard to undertand it. We have some of these "hunches" where its easier to …

We used it across the team, and when you want to bring metrics together across multiple people, its easier on a server, than local.

Cool, whats the link? We have some learnings, especially in the "Skill guiding" part of our example.

Our focus is a little bit more cross team, and in our internal version, we have also some continuous improvement monitoring, which we will probably release as well.

The tool does have a quite detailed view for individual sessions. Which allows you to understand input and output much better, but obviously its still mysterious how the output is …

The 4% usage was about our internal team, and we have skills setup. So it is not necessary that they are not built, but rather that they were not used, when we expected them to be …

Ohh this is exciting, I kinda overlooked it. I assume there are still a lot of differences, especially for accross teams. But I immediately ran it, when I saw your comment. Actuall…

It will be only enabled for the repo where you called the `enable` command. Or use the cli `upload` command for specific sessions. Or you can run your own instance, but we will nee…

This is great. How are you "identifying" these stages in the session? Or is it just different slash commands / skills per stage? If its something generic enough, maybe we can build…

Ah sorry, the readme is more about how to run the repo. The "product" information is rather on the website: https://rudel.ai

Its our own sessions, from our team, over the last 3 months. We used them to develop the product and learn about our usage. You are right, they will remain closed. But I am happy t…

The docker-compose contain everything you should need: https://github.com/obsessiondb/rudel/blob/main/docker-compos...

There is also a docker setup in there to run everything locally.

Yes we added codex support, but its not yet extensively tested. Session upload works, but we kinda have to still QA all the analytics extraction.

We built rudel.ai after realizing we had no visibility into our own Claude Code sessions. We were using it daily but had no idea which sessions were efficient, why some got abandon…