Daniel Grenemark

Why are you not running your agent overnight? The machine is on, the work still needs to get done, and the budget is the same budget. Eight hours buys one goal, one branch, and a report waiting at 08:00. Tell me what you would point it at first. I run one goal per night: /goal improve {target} in {scope} from {baseline} toward {goal state}, without {constraint}, until tomorrow 08:00. Then report where we started, what moved and by how much, why it moved, where we stand now, and what you recommend next.

I can now see what every agent session costs, which repo it spent it on, and what it did with it. Claude Code and pi, same dashboard, my laptop. Before this the only signal was a card statement a month later with one number on it. Shipped a local-first stack that closes it: → one 𝚌𝚘𝚖𝚙𝚘𝚜𝚎 𝚞𝚙 from a fresh clone, one loopback port, nothing leaves the machine → cost, tokens, sessions, tool decisions, lines of code, commits, PRs on a provisioned dashboard → every session as a readable conversation, each turn and tool call carrying its own tokens, cost, latency → read-only MCP: 22 tools, 0 write tools, so the agent queries its own history Claude Code emits OpenTelemetry natively. pi did not, so I shipped the extension too: 𝚙𝚒 𝚒𝚗𝚜𝚝𝚊𝚕𝚕 𝚗𝚙𝚖:@𝚍𝚎𝚜𝚎𝚔/𝚙𝚒-𝚘𝚙𝚎𝚗𝚝𝚎𝚕𝚎𝚖𝚎𝚝𝚛𝚢 Every instrument carries Claude Code's own name with the prefix swapped, 𝚌𝚕𝚊𝚞𝚍𝚎_𝚌𝚘𝚍𝚎. to 𝚙𝚒. So both agents land on the same panels and stay comparable. Same repo, same week, one axis. github.com/desek/agent-obser…

Your agent now remembers the approaches you rejected, not just the code that survived. Nothing in a repo records what was ruled out. Code shows what worked, and squash merge deletes the commit bodies where the reasoning lived. So the agent confidently retries the approach you threw away six weeks ago. Shipped two skills that close the loop: → /𝚌𝚑𝚎𝚌𝚔𝚙𝚘𝚒𝚗𝚝-𝚒𝚝𝚎𝚛𝚊𝚝𝚎 keeps a ledger of every attempt, including the discarded ones → /𝚌𝚑𝚎𝚌𝚔𝚙𝚘𝚒𝚗𝚝-𝚍𝚒𝚜𝚝𝚒𝚕𝚕 ranks which of them deserve to be a standing rule → nothing lands in 𝙰𝙶𝙴𝙽𝚃𝚂.𝚖𝚍 until you approve it Rules expire on purpose. A workaround for someone else's bug has to carry the test that retires it, so it dies with the bug instead of outliving it. npx skills add desek/governance

I built an MCP server that lets you manage your Outlook calendar and email from any AI assistant. Single Go binary. Runs locally. No cloud relay. No Entra ID setup. Just `go install` and start talking to your calendar. github.com/desek/outlook-loc… #MCP #AItools #AgenticAI

Winning the hot sauce competition for sure. It was a true pleasure hanging around at Dreamhack with you @BillyPacman 🕹

If only the @Deezer desktop app could (be scary and) adapt my Flow selection based on analyzing my app/window title usage. Would love if it noticed how I switch from coding in @code to fanatic googling in @googlechrome and adapted the music selection to it.

Anyone got a good whitepaper for managing scalabilty of @nodejs (with or without @Docker) solutions? #DevOps

Just did hands-on competitive/usability re-pro of @googlecloud against my deep @Azure knowledge and recent @awscloud gig #mindblown #wtf