Skip to content
| Marketplace
Sign in
Visual Studio Code>Programming Languages>Gaionix CoderNew to Visual Studio Code? Get it now.
Gaionix Coder

Gaionix Coder

Gaionix AI

|
7 installs
| (0) | Free
VS Code extension for Gaionix Coder autonomous coding agent
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Gaionix Coder VS Code Extension

Official VS Code extension for Gaionix Coder, providing a native coding assistant powered by the bundled high-performance Rust Agent Core (gaionix-coder-agent).

Features

  • Bundled Agent Core: Automatically resolves and launches the bundled local Rust binary (gaionix-coder-agent) over JSONL stdio IPC.

Gaionix Coder 1.2.0 supports six platform-specific VSIX targets: win32-x64, win32-arm64, darwin-arm64, darwin-x64, linux-x64, and linux-arm64. Each VSIX includes only its matching native gaionix-coder-agent runtime. This release adds attachment handling and a curated Skills Marketplace with source review, trust approval, workspace pins, and automatic activation of relevant trusted skills. Target-to-Rust-triple mappings and object-format checks are centralized in scripts/release-targets.js; packaging rejects absent, dirty, stale, or wrong-architecture executables.

The Release candidate artifacts GitHub Actions workflow uses a native runner for each target, then uploads a target-named VSIX, integrity manifest, and standalone CLI/TUI archive. The workflow does not publish a Marketplace release. The standalone archive includes both gaionix-coder and the sibling gaionix-coder-agent required by the CLI, plus an embedded manifest, README, and external SHA-256 sidecar. Users do not need Rust or Cargo. Linux archives target Ubuntu 22.04 / glibc 2.35 or newer; Windows MSVC builds may require the Microsoft Visual C++ 2015–2022 Redistributable. See docs/packaging.md for the matrix and commands.

Packaged builds include an agent-provenance.json manifest with the Rust source commit and binary SHA-256. The runtime reports the same identity during JSONL initialization; the extension refuses initialization when the packaged binary does not match its manifest. Packaging refuses a dirty source tree or a stale staged executable. The runtime also supports --build-info for local verification.

  • Provider Support: Seamless configuration for Gaionix Gateway and OpenAI-Compatible custom model endpoints.
  • Model Capabilities: Monochrome SVG icons identify reported reasoning, image input, tool calling, and structured output; hover for labels. Context badges show the model catalog limit, which may exceed the configured chat budget. Missing metadata is shown as unavailable. Native PDF support is verified separately.
  • Secure Credentials: Stores API keys securely in VS Code SecretStorage.
  • Durable Sessions: Multi-turn workspace conversations with state persistence and recovery.
  • Interactive Diff Preview: Review and approve code edits before they are applied.

Color and theme

Gaionix uses its existing muted orange accent for actions, selected states, icons, and focused controls. The accent follows the current VS Code theme; surfaces, text, borders, and hover states use VS Code theme colors so the extension fits both dark and light themes. Success, error, and warning colors are reserved for their matching status messages.

Usage

  1. Install Gaionix Coder from the Visual Studio Marketplace, or use the matching platform VSIX from the 1.2.0 release. Do not install a package with a different platform suffix.
  2. Click the Gaionix Coder icon in the Activity Bar.
  3. Configure your provider credentials via the settings view.
  4. Start a new session and send coding prompts.

Advanced settings

Advanced controls save automatically: Max Steps, Max Tool Calls, Send While Active, Automatic Compaction, and Composer Formatting. The status below Advanced confirms persistence or reports a save failure. Save applies provider configuration and credentials.

Max Steps and Max Tool Calls apply to new turns, including queued turns when submitted. A running turn retains its captured settings. Use Continue using current settings to continue with updated limits. Set a limit to 0 for Unlimited; clear Max Tool Calls to follow Max Steps.

Reasoning streams use a bounded live preview and load full history when expanded. Large messages retain their complete text as plain text to keep the panel responsive. Both sidebar locations reconcile the matching turn's terminal status when refreshed; refreshing does not rerun the model.

Skills

Featured skills are available in Marketplace. Inspect the pinned source revision and downloaded files before installing; choose whether to trust the skill in the installation dialog. Trusted skills can be pinned to the workspace and selected automatically when relevant, or selected manually from Installed. Uninstalling removes the skill files from that scope. Global Gaionix skills are stored in ~/.gaionix-coder/skills; skills installed globally by other agents in ~/.agents/skills are not automatically added to Gaionix. Workspace skills use <workspace>/.agents/skills.

Attachments

Attach supported workspace files, selected code ranges, or images to VS Code prompts. Attachment Processing Mode controls whether Gaionix uses verified native model input, local extraction for supported content, or native input only. Model support is checked conservatively; failed submissions restore the draft and its attachments.

Development & Packaging

# Compile TypeScript extension & run tests
npm run compile
npm test

# Build release Rust binary and package VSIX
npm run package:vsix:darwin-arm64

Extension Host integration tests

npm run test:extension-host runs noninteractive Restricted Mode, activation/runtime-provenance, runtime-unavailable, and runtime-provenance-mismatch scenarios. It creates disposable workspaces and isolated VS Code user-data/extensions directories; it does not open Workspace Trust management or wait for manual input. The Restricted Mode case checks that VS Code leaves the extension inactive and does not start the runtime. The separate activation/provenance smoke explicitly activates the extension from the test harness in an untrusted workspace, so it is not evidence of normal user activation policy.

The production-sidebar mock-task scenario is opt-in because VS Code requires an explicit trust decision for its disposable workspace:

GAIONIX_EH_SCENARIOS=mock-task npm run test:extension-host

The runner prints the canonical path of the exact disposable workspace and waits up to 90 seconds. In the Extension Development Host opened by that command, use Manage Workspace Trust to trust only that exact folder. The runner then starts a fresh host with the same isolated profile and workspace. If the decision cannot be made in that host, the scenario fails with a timeout diagnostic and cleans up its spawned process group. The scenario is considered passed only if the actual sidebar composer submits the prompt, the local mock provider receives both requests, the read-only file tool runs, and persisted session telemetry plus the task report meet their assertions. No provider billing is generated by this local mock.

Press Ctrl+C to cancel the test runner. It terminates the active Extension Host process group, returns a signal-specific exit code, and removes the disposable profile/workspace after cleanup.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft