thomas bond

Two systems both contain Cooling Pump 447.

In one, that name refers to a product model. In the other, it refers to a specific pump installed at a customer s site. Same label, different things.

An incorrect merge can connect a service incident affecting one unit to every unit of that model. Suddenly, a question about production risk gets a convincing answer built on a false connection.

Entity resolution encodes an assumption about the world. And once applications and agents use the graph, that assumption travels.

Looking at the raw per-token math renting an A10G or L4 on AWS/Vultr looks way cheaper than paying per token to OpenAI at scale. What I'm worried about is the hidden time sink vLLM crashes prompt tuning across model updates latency optimization load balancing and keeping up with new quantization releases. As a solo founder my time is already stretched thin. Did switching to self-hosted models actually save you net money or did the extra dev/maintenance hours wipe out any hosting savings?

Hi Product Hunt! AgentDock launched here on 10 October. Since then it has had eleven updates, and the latest one is the biggest: AgentDock now works with many more agents than Claude Code and Codex.

New in 1.3: more agents

• Beyond Claude Code, Codex and Grok, AgentDock now reads Gemini CLI, GitHub Copilot CLI, OpenCode, Kilo Code, Antigravity CLI and Claude Cowork, and shows Cursor's agent under its own name. Their dots show when they're working, waiting for you and done, and their finished turns go into History, Activity and Tokens. Nothing to install.

• They're in preview until each one is checked in a live session: turn them on in Settings Agents. Answering from the Inbox and typing replies stay with Claude Code, Codex and Grok for now.

• Tokens from the other agents get their own series in the hover card and the Tokens widget.

• The full list, and what AgentDock reads for each agent: agentdockapp.com/agents

You asked, it shipped