Shaka has had learnings since v0.3. The system extracts corrections, patterns, and preferences from your sessions and loads them into context next time. The missing piece: what happens when you have hundreds of them. They compete for space. Related entries stay fragmented. Quality degrades under its own weight. v0.8.0 adds automatic memory maintenance. Related learnings get condensed into compound entries. Cross-project patterns get promoted to global. Low-value entries get pruned when space is tight. Runs in the background after sessions, conservative by default, original learnings are archived before every change. The system cleans up after itself now. v0.8.0 🤖 github.com/jgmontoya/shaka

Last time I posted about Shaka it had slash commands. That was v0.4.0. Since then I've been building the parts that make each session better than the last. It remembers across sessions now. Rolling summaries compress what you worked on into daily, weekly, and monthly context. You shouldn't have to explain what you did yesterday. It runs multi-step workflows. Chain prompts, commands, and scripts in YAML. Steps pass output to each other. Add loop: 3 and it iterates: review, fix, review again until clean. It catches AI slop. A WritingRules skill flags the "it's important to note" garbage, and Shaka scan scores any file so you can check before you post. It has a skill manager now. Install from GitHub or the Clawhub registry. Skills get scanned for sketchy stuff before install. And it ships a TDD skill that forces the AI into red-green-refactor instead of "write everything then pray." v0.7.1. 🤖 github.com/jgmontoya/shaka

Also make it privacy focused for increased hardness! View quoted note →

Got media working on the @White Noise TUI Inline image rendering, media upload/download and previews, profile pictures, reactions, message deletion, reply previews, NSec export, logout, follow-checks, view user profiles, create groups with members. All done by directly using the White Noise CLI. BTW you can point your agents to https://github.com/marmot-protocol/whitenoise-rs/tree/master/src/cli and tell them to try out the White Noise CLI. It works surprisingly well.

This was made to showcase what can be built with the new White Noise CLI, go check it out! It was vibe-coded in a couple of hours, so beware that there might be some bugs with it, but it works! And the CLI is intuitive enough that AI can understand it and work with it pretty quickly! View quoted note →

It turns out, I completely fucked my follows list. Nostr FTW!

White Noise CLI merged!! Check it out: https://github.com/marmot-protocol/whitenoise-rs/tree/master/src/cli View quoted note →

wn messages send <group-id> "This is how you will be able to send a message using the White Noise CLI"

Brewing some big plans 🦫

I created a small tool to search for stuff in nostr: NST: Nostr Search Tool It's very very basic but hey, if you happen to need a cli tool for searching stuff on nostr based on how close they're to you (or someone else) in the social graph you might find this useful

GitHub

GitHub - jgmontoya/nst

Contribute to jgmontoya/nst development by creating an account on GitHub.

Each time someone adds nip-04 support to a client, a cute baby marmot dies. View quoted note →

I kept copy-pasting the same prompts between Claude Code and opencode. Custom instructions here, custom commands there. Two tools, two configs, same workflows duplicated. Shaka v0.4.0 fixes that. `/slash-commands`, just markdown files with YAML frontmatter. Write it once, it compiles to both providers. Scope per project or go global. Override system commands with your own. Ships with /code-review because that's one I was copy-pasting a bunch. 🤖 github.com/jgmontoya/shaka View quoted note →

I implemented a "user search" feature in White Noise, and it was slow as fuck. So I had to do it again, properly this time. I am pretty satisfied with the result. Next release of White Noise is going to ship with a pretty decent search feature. You can read more about it here:

J.G. Montoya S.

Building User Search for a Decentralized Messenger

User search should be simple. Someone types a name, you show matching profiles. On a centralized app this can be done easily without even thinking ...

Do you know if there's any good diving accounts on nostr to recommend to my good friend @Aleups who's new in nostr??

I use opencode and Claude Code. I don't want to pick a side. PAI is a project that adds hooks, agents, skills and memory to AI coding assistants. I like a bunch of what it does. But the repo is hard to navigate, customization isn't obvious, and it only works with Claude Code. So I did what any reasonable person does and built my own thing. Shaka is my take. Clean directory structure you can actually reason about. Customizations that survive upgrades. It's still very simple and early stage, but I'm working on making it smarter. It's been running my setup for a while now and it's been really useful to me, so I figured it might as well be useful to you! Check out Shaka 🛠️ github.com/jgmontoya/shaka