Your AI. Their AI. Kunobi connects them. Keep the AI you already use and work on it together. If you a technical ninja, check soon → @_kunobi_ninja_
Joined August 2025
- Tweets443
- Following168
- Followers143
- Likes694
kunobi retweeted
it is very frustrating when CI takes a long time, even with a tiny PR.
This is a first step that helps a lot...
However, we are already building something much more innovative for v2
RT @_kunobi_ninja_: Follow along!
There are many episodes and features to enjoy! 🍿🍿🍿
AI is awesome, Rust & C++ deserves better! https://…
Kunobi started with clusters. The bigger problem turned out to be context.
Your AI knows things. Their AI knows things. Humans are still the copy-paste layer.
We’re building Kunobi to change that, while Ninja keeps going deeper into infrastructure.
kunobi retweeted
Everyone who hates on Rust due to disk usage consumption is apparently incapable of telling Claude "hey, Rust uses a lot of disk space, can you help fix that" and have it install Kache for them
kunobi retweeted
Yes. kache is a content-addressed compiler cache that restores artifacts into each target/ via hardlinks or reflinks. Identical outputs from worktrees or agents share the same disk blocks instead of duplicating them, which cuts the space waste while speeding rebuilds. cargo install kache then kache init is the quick path.
We will be posting a complete, fair and comprehensive comparison soon.
There is still a lot of room for improvements.. but yes, faster and more convenient rust + ai experience.
Bring the love back to worktrees, they are your friends when used well.
kunobi retweeted
This plus we need to separate the concept of "AI assistance" from the intelligence it needs to consume.
To preserve some relative freedom, keep these separate:
- intelligence ( models + energy )
- memory ( data, persistance )
- relationships ( network effects )
kunobi retweeted
Kache sharpens Rust DevEx by wrapping rustc with blake3 content-addressed keys. After init, cargo stays identical yet reuses artifacts across worktrees, branches and CI via zero-copy COW restores. Builds hit fast, disk stays lean, and tools like why-miss plus monitor surface exact reasons. Especially useful with AI coding loops that churn code while deps stay stable—less waiting, tighter iteration.
kunobi retweeted
Separating your sources of:
- intelligence ( models + energy )
- memory ( data, persistance )
- relationships ( network effects )
is critical to maintain some relative freedom.
Otherwise, there isnt much left. You are outsourcing most of what we are.
kunobi retweeted
Kache shines as a zero-copy content-addressed build cache for Rust, C/C++ and CUDA. It hashes compiler inputs so identical code reuses artifacts across Git worktrees, branches or CI runs—no full rebuilds, minimal disk use via hardlinks/CoW. Transparent after kache init: keep running cargo (or make/cmake) as usual, with optional remote sharing. Perfect for multi-worktree workflows.
kache v0.28.1
thanks @aljohri for the fixes!
github.com/kunobi-ninja/kach…
