Skip to the content.

CLike VS Code Extension

CLike logo

CLike at a glance — what CLike does, area by area.

AI-native software engineering assistant for day-to-day coding and Harper-style solutioning inside VS Code. Works with the CLike Orchestrator and CLike Gateway across multiple providers and model families.

CLike is not just an agent that writes code; it is an AI-native platform that orchestrates verifiable capabilities across specs, plans, code, tests, reviews, and release gates.

Clike is

Install and first steps: docs/INSTALL.md · docs/GET_STARTED.md

What the extension does today

The extension currently supports three main interactive modes inside the chat panel:

It is designed to work with:

The extension is provider-aware, model-aware, and keeps a persistent chat timeline per model/history scope.


Current highlights

Chat modes

Execution: cloud or local agent

Every chat mode can run via the cloud or via a local agent (Claude Code / Codex CLI), selected with the Execution preference in the chat header. There are three canonical modes:

The default is prefer agent. Legacy values are normalized automatically at runtime, so older persisted settings keep working: auto → cloud_only, hybrid → prefer_local_agent, prefer_claude_code → prefer_local_agent, claude_code_only → local_agent_only.

Multi-model / multi-provider chat

The chat header supports:

The extension preserves model selection better than older revisions and avoids unnecessary resets when reopening chat.

Bubble timeline

The chat keeps a persistent bubble timeline with:

RAG support

The extension supports manual RAG flows:

Attachments

The chat supports:

These are used across Free / Coding / Harper flows.

Layouts

clike.chat.theme (also the Layout selector in the chat):

What each area shows and the settings that change the UI: docs/chat-ui.md.


Quick start

1. Backend

Start the CLike stack (see the main README). The services listen on loopback and require a service token:

2. Extension

Install the packaged extension:

./build_ext_vs.sh        # npm ci, lint, tests, vsce package, install

Open windows keep the version they loaded: reload them (“Developer: Reload Window”). A window still running the previous version says so at its next run, with a Reload Window button.

or develop it:

npm ci
npm run check            # ESLint + node:test

then press F5 to launch an Extension Development Host.

3. Service token

Run CLike: Set Service Token and paste the CLIKE_API_TOKEN of the stack (stored in VS Code SecretStorage, sent only to the configured orchestrator/gateway URLs). Then run CLike: Chat (Q&A / Harper / Coding).

Defaults worth knowing

3. Use the chat header

Select:

Then start working in Free, Coding, or Harper mode.


Slash commands

Type commands directly in the chat input.

General

Harper workspace

KIT flow

The extension currently supports a base KIT run by default, plus optional explicit follow-up phases.

Eval / Gate

Finalization

RAG


Current Harper behavior

/init

The workspace initializer creates the Harper scaffold and support files such as:

/plan

The plan flow is expected to produce promotion-grade planning artifacts, including:

/kit

The extension supports REQ-based KIT execution and explicit KIT follow-up phases.

At the UX level, the current direction is:

This keeps the extension compatible with more selective and cost-aware workflows.


Command Palette commands

The extension currently contributes these key VS Code commands.

Chat / core

Coding / patching

RAG

Git / promotion

Eval / governance


UI guide

The chat header contains:

Prompt area

The prompt area supports:

Panels / tabs

Generation output is rendered through tabs:

Bubble timeline

The timeline keeps contextual continuity for each chat context and supports timestamped interaction traces.


Settings

Current configuration keys exposed by the extension include:

Chat / UI

Execution / local agent

Eval / gate / auto-eval

Backend endpoints

Optimization / behavior

Apply behavior

Git integration

Routes


Typical flows

Free mode

Coding mode

Harper mode

Typical flow:

  1. /init <name> [--path <abs>] [--force]
  2. complete or refine IDEA.md
  3. /spec
  4. /plan
  5. /kit REQ-XXX
  6. optionally:
    • /kit REQ-XXX --integrity
    • /kit REQ-XXX --hardener
    • /kit REQ-XXX --promotion-eval
    • or explicit --phases=...
  7. /eval <REQ-ID>
  8. /gate <REQ-ID>
  9. /finalize

Troubleshooting

Chat opens but something looks stale

Reload the VS Code window and reopen chat, especially after source changes in development mode.

KIT target selection issues

If /kit REQ-XXX does not behave as expected, verify:

Provider/model issues

If a model/provider combination does not behave correctly:

RAG issues

If manual RAG commands do not return expected results:


Backend endpoints (reference)

Orchestrator

Gateway


Current positioning

This extension is no longer just a simple chat panel.

Today it acts as a VS Code front-end for an AI-native software delivery workflow, combining:


Changelog summary for the current state

Compared with earlier simpler revisions, the extension now includes or exposes:


Repo

Part of the CLike project family:

Use together for the full workflow.