ohh so there’s a subscription to manage my subscriptions 😭
i actually built something fun + free to use
i added up my subscriptions
$464.31/mo, $5,572/yr, $15.27 every single day 💀
thats 3 weeks in bali, gone
so i built track my subscriptions
> 217+ services with real prices
> see what you pay per month, year and day
> get your tier (im a "subscription royalty" )
> share a receipt-style page at /@kalashvasaniya
> get renewal, free trial + price increase alerts
> upload a bank statement to find every subscription (it never leaves your browser)
> mcp server, openapi + llms.txt so ai agents can use it too
live now: trackmysubscriptions.com
Local AI is quietly becoming one of the biggest shifts in tech.
Models now run on laptops.
Voice cloning happens on-device.
Meeting notes stay private.
Coding agents work without sending every file to the cloud.
The next major AI product may run on hardware you already own.
You become a good mentor by remembering what it felt like to be lost.
You become a good architect by remembering what it felt like to write your first broken function.
Everyone starts out as the one with questions, not the answers.
Era 1 (Autocomplete): it finished your line. You typed, it guessed the next few words, keystroke by keystroke.
Era 2 (Prompting): it finished your prompt. You asked, it answered, one exchange at a time, staying in the loop for every step.
Memory is the reason:something that keeps track of what the last 5 tasks taught it, so the fleet doesn't relearn the codebase every time out. One internal Cursor case reportedly runs at 20-100 pull requests a day, on a single migration with no one reviewing each diff line by line
I'm still catching up to Era 2's habits. Which Era are you actually in right now?
cursor.com/blog/third-era
cursor.com/blog/projects
Prompt engineering. Context engineering. Harness engineering. Loop engineering. Now graph engineering.
Is this a new layer of engineering, or just this year's rename?
Beads is a persistent memory system for coding agents, and it's already at 26k+ stars on GitHub.
It's a distributed graph issue tracker powered by Dolt. Instead of messy markdown plans, agents get a dependency-aware graph where work can be claimed, closed, and blockers released. That makes long-horizon planning and work discovery much easier without losing context.
The CLI is bd, and it runs on macOS, Linux and Windows. If you need shared state across machines and agents, it supports push and pull through Dolt.
github.com/gastownhall/beads
Eventually, you stop reading every line a new developer writes.
Not because they became perfect, but because they learned what "done" means on your team. Tests pass, edge cases are handled, and they check their own work.
That's the shift we're now seeing with AI agents: 𝗹𝗼𝗼𝗽 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴.
The idea has been gaining attention as engineers at companies like Anthropic and OpenAI have been moving from manually prompting agents toward designing systems where agents can work, evaluate, and iterate on their own.
For the last couple of years, we've been the reviewer: prompt, read the output, judge it, prompt again.
Loop engineering changes that. Define what "done" means, build the checks into the system, and let the agent iterate until it meets the standard.
But you can only step back once you've explained what good looks like.
Developers learn that through experience and code reviews. Agents only know what you define.
The real work isn't just making agents autonomous. It's making "good" explicit enough for them to work without us.
Firecrawl open-sourced a fast Rust library that classifies any PDF in ~20ms and extracts clean Markdown locally. No OCR needed for text-based PDFs. github.com/firecrawl/pdf-ins…
For decades, the playbook was simple.
We gathered requirements, wrote code, tested it, and shipped it. Then we did it all over again.
Over the years, the process evolved. Waterfall. Agile. DevOps. AI copilots.
But every one of those shifts had one thing in common.
Humans were still doing the work.
That's what makes this moment feel different.
Today, an agent can plan a task, write the code, review it, test it, and even ship it.
If the one doing the work has changed, shouldn't the lifecycle change too?
That's where the idea of the Agentic Development Lifecycle (ADLC) comes in.
The focus shifts from writing every line of code to defining goals, providing context, connecting tools, setting guardrails, and continuously evaluating outcomes.
Maybe the biggest shift isn't that AI writes code. It's that we're learning how to build great agents.
P.S. This is my first video created with an AI avatar. Still experimenting, but I had fun putting it together.
Voicebox is an open-source AI voice studio that runs entirely on your machine. It’s already past 44k stars on GitHub.
Voicebox clones any voice from just 10 seconds of audio, supports 7 TTS engines, and lets you dictate directly into any app or talk to agents in your own voice. It integrates with Claude via MCP, handles 23 languages, and includes a multi-track timeline editor and voice profile manager. MIT licensed, free, no cloud required, no subscription. Available for macOS, Windows, and Linux, built with Tauri.
It’s being called an open-source alternative to ElevenLabs and WisprFlow. A REST API is included for automation.
If you’re into local-first voice AI, this is worth a look.
github.com/jamiepine/voicebo…
Floci is a free open-source drop-in replacement for LocalStack. Supports AWS, Azure, and GCP emulators. Starts in 24ms and idles at 13 MiB. Has a Testcontainers module. No account or auth needed. github.com/floci-io/floci
The last few days have been pure chaos in AI/tech.
• GPT-5.6 landed. OpenAI launched the Sol, Terra, and Luna models, along with Ultra mode for more advanced multi-agent workflows.
• Grok 4.5 landed. Built in collaboration between Cursor and xAI, with competitive pricing and strong early feedback for large codebases.
• Bun 1.4 shipped. The Zig → Rust rewrite is wild, and the fact that AI helped migrate such a massive codebase makes it even more interesting.
• Meta released Muse Spark 1.1, another aggressively priced agentic/coding model.
• Cognition shipped SWE-1.7 with major performance improvements, plus new Vercel SDK and Better Auth integrations.
And that's just yesterday.
Already on the horizon:
• Seedream 5 Pro
• Gemini 3.5 Pro (reportedly around mid-July)
• GPT-6 rumors are getting louder
It genuinely feels like the AI tooling landscape is changing every week now.
What caught your attention?


















