shroomdog-original
17 articles
Claude Tag: Not Your Personal Secretary, It's the Whole Channel's Teammate
Claude Tag is Anthropic's second-generation Claude in Slack, launched June 2026. Unlike typical chatbots: one thread is one persistent work session, and anyone in the channel can jump in mid-conversation to steer it. But the sandbox evaporates, and credentials never enter the sandbox — this security design is the baseline we'll compare against when we build our own.
Self-Hosting Your Own Claude Tag on LINE
Claude tag only officially supports Slack. Want an AI assistant that comes when you call on LINE? Build it yourself. Use OpenClaw to spin up a LINE bot on a VPS — messages come in from LINE's official cloud, the gateway catches them, and the agent replies. This post covers the replicable skeleton, three security must-haves, and why freedom always comes with responsibility.
The "Intranet Claude Tag": Enterprise Deployment and the Post Office Problem
A team wants OpenClaw on their intranet, coworkers tagging it in Teams. Outbound is sorted via a forward proxy. But inbound? Teams messages come from Microsoft's cloud — pure intranet is physically impossible. The post office problem: what moves inside the building (GitLab issues), what needs a door (DMZ + Teams), and why the extra architecture hassle is the right answer.
The 2026 OpenClaw Triple Breach: Freedom Isn't Free
In early 2026, OpenClaw got hit three times: 20,000+ gateways exposed to the internet, 20% of marketplace skills were trojans, and link previews became exfiltration vectors. Attackers had a smooth ride until they hit a closed door — and 'proper configuration' suddenly mattered. Self-hosting freedom comes with self-hosting responsibility.
Dan Koe Teaches You to Write a Spec — the Agent Being Deployed Just Happens to Be You
A million-subscriber anti-algorithm influencer says the way to take life back is writing himself a spec. Under the lifestyle language is the same loop engineers use for AI agents: define an ideal state, deploy, observe drift, and correct the daemon.
gu-log Is Really Just a Very Picky Editorial Desk
Without guardrails like CI, the pre-commit gate, the tribunal, and the validator, how bad do AI-written articles get? gu-log has 500+, and the answer needs no imagination — this post, SD-26, is the specimen: it passed every score and still read very AI. The story of a picky editorial desk.
Let Agents Dream: Weekly Maintenance That Turns Repeated Work Into Skills
Vaibhav Srivastav's Codex prompt is interesting because it describes an agent maintenance loop: look back at recent work, find repeated workflows, and package only high-confidence patterns into Skills, automations, or subagents. It is agent dreaming: turning busy work into capability.
Codex Is Becoming the Runtime Kernel for AI Agents
OpenClaw and Hermes are both handing low-level coding-agent execution to Codex app server. This is not just a model switch. It is the agent product stack separating model, execution engine, and chat surface.
Don’t Rebuild the AI Agent Wheel: Learn to Teamfight With Your AI Teammate and Stop It From Feeding
LLMs are not gods, and they are not just tools. They are more like DOTA teammates: great at last-hitting, occasionally great at feeding. The human job is not to fight AI for the same lane, but to cover taste, map awareness, context ownership, and strategic judgment.
Context Window: The Day a Model Wakes Up
A context window is a model's day: how many lessons, messages, tool results, and task events Ryland can experience before sleep, compression, or collapse.
Fire Truck vs. Succulent — Vector Database vs. Agent Search, in Simple Math
Someone deployed Milvus to search 5,000 vectors. That's like calling a fire truck to water a desk succulent. This post uses dead-simple math to compare vector databases vs. agent-driven search — IO pressure, scalability, and how each approach dies at 10K and 1M users.
AI Agent Memory Architecture: The One Thing Claude Code's Source Code Taught Me
Every new session, your AI agent forgets everything. Claude Code's leaked source hid a three-layer memory architecture and a design principle — 'Memory is hint, not truth' — that changes how you think about building agents. Here's the full breakdown.
5 Bad Design Patterns from the Claude Code Source Leak
The Claude Code source leak had everyone excited about KAIROS and model codenames. But the same codebase had a 3,167-line function, zero tests, silent model downgrades, and regex emotion detection. These aren't just Anthropic's mistakes — they're AI-generated code's default failure modes.
Prompt Cache Economics — Why Your AI Bill Is Higher Than You Think
Prompt caching should save you 90% on token costs — but one obscure bug can silently make you pay 10x more. From DANGEROUS_uncachedSystemPromptSection to the cch=00000 billing trap hidden in Claude Code's DRM, here's why prompt engineers now need to be accountants too.
The AI Agent Initiative Problem — When Should an Agent Act on Its Own?
You spent months building a powerful AI agent. It just sits there waiting for you to say something. That's not a technical problem — it's a design philosophy problem. From KAIROS's Heartbeat Pattern to OpenClaw's background sessions, this is about when to let your agent decide to act on its own.
Undercover Mode Asked a Question Nobody Wants to Answer
Hidden inside Claude Code's leaked source was a ~90-line file called undercover.ts — designed to make AI commits look like human commits. This surfaces a question the industry hasn't agreed on: when AI writes your code, should anyone know?
Can AI Test Itself? — From Claude Code's Zero Tests to Self-Testing Agents
Claude Code has 512K lines of TypeScript, 64K lines of production code, and zero tests. The sharper question is not why Anthropic skipped tests, but why it did not use its own AI coding tool to write them. Can the same brain write and grade the exam?