ClikCode — AI skill for Claude Code

ClikCode

**The harness that logs in all your favorite AI coding providers — in the terminal and in VS Code.** Chats you can resume in any of them, and automatic account switching when you hit a usage limit.

Claude Code for one thing, Codex for another, Copilot because it came with the editor, something you tried once and kept. Each has its own commands, its own sign-in, its own idea of where your conversations live. None of them know the others exist, so picking one up means learning it again and leaving your work behind in the last one.

ClikCode sits in front of 29 of them, including four newer ACP agents under experimental support. One sign-in, one list of conversations, one set of controls, the same keystrokes whichever tool answers. It replaces nothing — your tools stay yours, the logins you already had keep working — and what it adds is this:

For the 21 harnesses with an ACP entry point or adapter, ClikCode uses ACP for ordinary turns. When an agent cannot carry a particular image, model, or reasoning choice over ACP, ClikCode uses that harness's CLI path where safe. Any other ACP agent can be added with `clikcode acp add`, and it then appears in the same provider list.

For example, `clikcode acp add my-agent /path/to/agent -- --stdio` registers an installed ACP executable without changing ClikCode. In VS Code, use **Add ACP Harness…** and enter launch arguments as a JSON array, such as `["--stdio", "--config", "two words"]`. The agent still needs its own usable credentials; a completed turn and resume should be checked before relying on it for work.

**Every tool, one way of working.** Stop memorizing flags. ClikCode asks each tool what it supports and offers you that — models, reasoning level, approval behavior — in the same place every time.

**All your accounts, at once.** Work and personal, two subscriptions, an API key kept for spillover. Keep them side by side and move between them in a keystroke. Signing in still happens inside the tool itself;