Hi, I’m splitting my time between multi-cloud governance and optimizing my "vibe coding" workflow: Kexa (https://kexa.io)

An open-source multi-cloud governance framework powered by a YAML rule engine. We just reached a milestone by adding Database (DB) support.

The goal is to allow developers to audit configuration and compliance directly within DB instances, alongside standard cloud resources (AWS, GCP, Azure, K8s). We’re focusing on keeping the YAML rules as agnostic as possible so the same logic can apply across different environments without rewriting everything. rtk (https://github.com/rtk-ai/rtk)

This is a "scratching my own itch" project born from using Claude-code. While vibe coding, I got frustrated watching the agent spam ls -al or cat repeatedly just to "orient" itself.

It creates two main issues:

    The Token Tax: It burns through tokens for info the agent already has.

    Context Pollution: The context window fills up with redundant noise.

rtk acts as a CLI wrapper/filter to make LLM interactions more signal-to-noise efficient. It silences or summarizes redundant outputs so the agent only receives the necessary "delta." It’s a simple attempt to keep the context clean and make sessions last longer before the agent loses the plot.