Skip to content

Clawdius 1.125.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 30 Jun 17:15
v1.125.0
517a93a

Clawdius 1.125.0

A 💌 love letter to Visual Studio Code, Claude Code, and Clawd.

The first release of Clawdius — a fork of Visual Studio Code built around Anthropic's official Claude Code plugin. It's the editor you already know, with Claude Code wired in and a set of native tools for working with it: it tracks your token usage, lets you configure Claude Code without hand-editing JSON, shows what fills your context window, and connects through whatever Claude Code provider you already use (a Claude subscription, AWS Bedrock, Google Vertex, or a custom endpoint).

What's inside

Claude Code, built in

On first launch, Clawdius installs Anthropic's official anthropic.claude-code plugin from Open VSX and signs in with your existing ~/.claude login — the same engine as the CLI, no second account, no reimplementation. The pane opens in the sidebar. VS Code's Copilot chat is retired so Claude is the default: github.copilot and github.copilot-chat are blocked from install, the Claude Code plugin is protected from accidental removal, and a status-bar safety net re-offers it if it ever goes missing.

The chat surface registers Claude Opus, Sonnet, and Haiku as selectable models (vendor clawdius), each backed by the local CLI. A per-model effort dropdown (Low through Max) maps to the CLI's effort flag and defaults to your ~/.claude/settings.json.

Token and context awareness

A status-bar meter shows session and weekly token use, computed locally from your Claude Code transcripts, with a hover popup for account identity and capacity. The full Usage dashboard breaks the same numbers down by window and model, with a per-day chart, a contribution heatmap, 24-hour activity, and streaks. It works in local windows and over SSH/WSL remotes — in a remote window the stats and subscription limits are read on the remote machine, where your ~/.claude actually lives. It refreshes only when you open it; the one network call it makes is a user-initiated capacity fetch from Anthropic using your existing OAuth token.

The Context Budget Inspector reports, for the file you are editing, what Claude actually loads: memory, rules, and skills, split into what applies every turn, what loads on demand, and what is skipped, each with an estimated token cost. It also shows the measured cached prefix from your last session. A status-bar pill flags the file's always-on total when it crosses a threshold you set, and a Lint Claude Context command writes Problems-panel markers for memory and rule files whose always-on cost runs high.

The Control Center

A native pane edits your ~/.claude and project .claude configuration so you never have to touch raw JSON, with a Global / Project / Project-local scope selector. Its tabs cover:

  • Permissions: the default permission mode and the allow/ask/deny rule lists, with a builder for built-in tools, MCP tools, or raw rules.
  • MCP: add, toggle, and inspect Model Context Protocol servers, with per-server approval and opt-in live tool discovery.
  • Skills: enable or disable individual skills, plus the bundled-skills kill switch.
  • Plugins: manage marketplaces and install plugins from the merged catalog.
  • Hooks: a structured editor for lifecycle hooks and the disable-all switch.

Two more controls sit in the status bar: a permission-mode pill (Plan, Ask before edits, Edit automatically, Bypass) and an effort pill with a block-bar meter that also toggles Ultracode.

Remote development (SSH and WSL)

Clawdius builds its own remote extension host (REH) server for Linux x64 and arm64 and serves it from the GitHub release. With the Open Remote - SSH or Open Remote - WSL extensions, a remote session pulls the matching server tarball straight from the release instead of a Microsoft CDN, and the Claude Code plugin and the usage tooling run on the remote machine where your code and ~/.claude live.

Updates

"Check for Updates" compares your version against the project's GitHub releases and, when a newer one exists, links you to it. An update-channel setting (clawdius.update.channel) chooses Stable or Pre-release; a pre-release build defaults to the Pre-release channel. An optional check-on-startup setting exists and is off by default, so out of the box launch makes no request. Updates are notify-and-link — there is no in-app auto-download or install.

Privacy and trust posture

No telemetry, no crash reporting, no automatic update pings. Out of the box the only outbound traffic is what you start: a Claude turn, an extension you install, the on-demand usage fetch, or a Check-for-Updates you run. Outbound link clicks are gated by default to github.com and the Claude sign-in domains (claude.ai, claude.com). The extension gallery is pinned to Open VSX, and anthropic and jeanp413 are trusted publishers so their extensions install without a prompt.

One trust default to know: because Open VSX does not Microsoft-sign extensions, Clawdius defaults extensions.verifySignature to false. Forcing verification would block every install, including into remotes, with a "Signature verification was not executed" error. Set extensions.verifySignature: true to turn it back on.

Themes and branding

Clawdius ships Dark, Light, High Contrast, and High Contrast Light themes tuned toward Claude's palette, and rebrands the application throughout (name, data folders, the clawdius:// URL protocol, and the issue/license/release links). A "Sponsor Clawdius" action links to GitHub Sponsors.

Platforms and signing

Every published artifact is signed:

  • Windows x64 and arm64 — Azure Trusted Signing (the default ClawdiusSetup per-user installer, the ClawdiusSystemSetup all-users installer, and the portable zip).
  • macOS arm64 and x64 — Apple Developer ID signing plus Apple notarization (.dmg and .zip).
  • Linux x64 and arm64 — GPG-signed SHA256SUMS (.deb, .rpm, and tarball); the .deb/.rpm also publish to Cloudsmith.
  • REH server x64 and arm64 — GPG-signed SHA256SUMS.
  • Snap x64 and arm64 — built and attached here.

Install

Pick your platform; full per-platform steps and exact asset names are in the README.

  • Windows: run ClawdiusSetup-<arch>-<version>.exe (per-user, no admin), or ClawdiusSystemSetup-<arch>-<version>.exe for all users; a portable zip is also provided.
  • macOS: open Clawdius-darwin-arm64-<version>.dmg (Apple Silicon) or Clawdius-darwin-x64-<version>.dmg (Intel) and drag Clawdius into Applications.
  • Linux (Debian / Ubuntu): sudo apt install ./clawdius_*_amd64.deb
  • Linux (Fedora / RHEL / openSUSE): sudo dnf install ./clawdius-*.x86_64.rpm
  • Snap: sudo snap install --classic --dangerous ./clawdius_*_amd64.snap (arm64: ..._arm64.snap)

Known limitations

  • Extension signature verification is off by default (see the trust note above).
  • The Snap Store listing isn't live yet, so the snap installs with --dangerous; both x64 and arm64 snaps are built and attached.
  • Updates are notify-and-link — "Check for Updates" points you to the new release; there is no in-app auto-download or install.
  • A signed app from a new publisher has little reputation yet, so SmartScreen (Windows) or Gatekeeper (macOS) may warn on first launch; the README covers how to proceed.

Built on

Visual Studio Code 1.125 (microsoft/vscode). Clawdius is an independent fork and is not affiliated with or endorsed by Microsoft or Anthropic.

Repository: https://github.com/chapmanjw/clawdius
Full feature tour and screenshots: see the README.

Assets 34
Loading