Cognisant-llc

Sublime Claude Code — Development skill for Claude Code

Development community

Claude Code IDE integration for Sublime Text 4 — in-editor diff review, live selection context, @-mentions.

How to install Sublime Claude Code

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Cognisant-llc/sublime-claude-code and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Sublime Claude Code does

Claude Code IDE integration for Sublime Text 4 — in-editor diff review, live selection context, @-mentions. Speaks the official IDE protocol (WebSocket/MCP). Unofficial community plugin.

Alternatives in Development

README

Claude Code IDE for Sublime Text

**English** | [日本語](./README.ja.md)

**Run six Claude Code sessions in parallel and still know what changed where.** Native [Claude Code](https://claude.com/product/claude-code) integration for Sublime Text 4: a **Recent Activity** pane lists every file your sessions touched — grouped project → session → file, one click to open — next to in-editor diff review (accept/reject), live selection sharing and `@`-mentions, over the same WebSocket/MCP protocol as the official VS Code and JetBrains extensions.

**Unofficial community plugin** — not affiliated with or endorsed by Anthropic. "Claude" and "Claude Code" are trademarks of Anthropic, PBC.

![Six Claude Code sessions write docs in six projects; the Recent Activity pane in Sublime Text lists each file by project and session as it lands, and one click opens it](docs/demo.gif)

**Status: 0.3.x, all features working** — the IDE server with context sharing, in-editor diff review, parallel multi-session support, and the Recent Activity pane are implemented and tested end-to-end against the real Claude Code client ([releases](https://github.com/Cognisant-llc/sublime-claude-code/releases)). Package Control listing is pending; the manual install below works today.

Motivation — why Sublime Text in the LLM era?

Now that an agent writes much of the code, what should an editor be? Our answer:

  • Instant and lightweight. Sublime opens in a blink and stays at ~100–300 MB while agent sessions, terminals, and browsers eat the rest of your RAM. The editor is where you read and judge code; it should never be the heavy part of the stack.
  • Trivially extensible by you. In an LLM-first workflow, the editor is personal infrastructure: when Claude can write a Sublime plugin in minutes, a scriptable Python API beats a marketplace of prebuilt features. You compose exactly the cockpit you want — this plugin itself is proof.
  • No bundled AI, by choice. AI-native IDEs (Cursor, Windsurf,