📰 Dev.to · CodeKing

My local AI assistant could capture screenshots just fine, but Feishu and Telegram still received no image. The real bug was an upstream channel capability gate

Keeping an AI coding session alive is not enough. The real improvement came when my agent started recalling successful workflows, rules, and facts instead of re

Chat-based AI assistants feel useful until they need you to stay online. I fixed that by letting scheduled tasks wake the assistant up in the background and rou

Parallel AI tasks looked impressive until two of them tried to drive the same desktop. I fixed it with resource-aware queuing instead of blind cancellation.

I built CliGate so coding agents can use runtime sessions, local skills, and desktop controls from one local assistant.

Treating web chat as a special page instead of a real channel split my agent state in two and caused silent delivery failures.

A practical model for AI coding agents that need to remember projects, tasks, executions, and runtime sessions separately.

A real bug from wiring Claude Code and Codex into DingTalk: the bot acknowledged work, but the runtime result disappeared unless I fixed delivery and fallback p

I stopped letting my product assistant depend on whatever account or API key happened to win routing, and gave it an explicit model-source chain with fallbacks.

I wired Antigravity accounts into CliGate and learned the hard way that OAuth success, token refresh, project IDs, and chat source wiring are four separate prob

I wanted Claude Code to use Google Cloud billing instead of another Anthropic key, so I routed it through Vertex AI with one local gateway.

The agent I actually needed wasn't another coder — it was a dispatcher. Here's the control-plane vs execution-plane split I landed on and why.

CliGate is a local multi-protocol AI gateway that unifies Claude Code, Codex CLI, Gemini CLI, Telegram, Feishu, and DingTalk with account pools, app routing, st