Kamino Console

Kamino Console brings focused workflow tools into Visual Studio Code through a command surface and a multi-tab webview app.

Use it to run conversion, scanning, repository utility, diff, and HAR analysis tasks without leaving your editor.

Why Kamino Console

• One place for common workflow operations in VS Code.
• Guided workflows for files, folders, and pasted text.
• Result surfaces designed for quick copy/share of outputs and artifact paths.
• Storage-aware tooling with direct shortcuts to data, reports, logs, and database locations.

Quick Start

1. Install Kamino Console from the VS Code Marketplace.
2. Open the Command Palette.
3. Run Kamino Console: Open.
4. Pick a workflow tab: Converters, Content Scan, Repository, Text Diff, HAR Intelligence, or Settings.

Feature Areas

Converters

• Image conversion to PNG/JPG/JPEG.
• Video-to-GIF conversion with presets and advanced controls.
• QR code generation from text or URLs.

Content Scan

• FileIntel workflow for file/folder scanning and artifact inspection.
• Paste-text scanner for extracting structured entities from snippets.

Repository

• Text cleanup for pasted content or local files.
• Repository cleanup scanning (safe scan-first flow).
• File tree report generation for Markdown/text outputs.

Text Diff

• Unified text diff from two inputs.
• Compare from active editor content or selected files.
• Diff options including context lines and whitespace controls.

HAR Intelligence

• Load HAR sessions and run HARIntel pipelines.
• Inspect workflow, request, replay, security, and analysis views.
• Generate artifacts and reports for downstream investigation.

Settings

• Check runtime connection and version details.
• Review resolved storage paths and diagnostic information.
• Open data, database, reports, and logs folders directly.

Commands

• Kamino Console: Open
• Kamino Console: Inspect Active File
• Kamino Console: Convert Active File
• Kamino Console: Check Runtime
• Show Storage Info
• Open Data Folder
• Open Database File
• Open Reports Folder
• Open Logs Folder

Settings

• kaminoConsole.showInSidebar When enabled, Kamino Console opens in the activity bar sidebar instead of an editor panel.

• Configure runtime path and storage behavior from Kamino Console extension settings.

• Use storage mode options to choose between VS Code managed storage and shared app-data storage.

Troubleshooting

• Run the runtime check command to validate connectivity.
• If needed, set the executable path in extension settings to a known local binary.
• Use Storage Info to verify active storage mode and resolved paths.

Privacy and Data

Kamino Console can write outputs such as reports, logs, and artifacts to configured storage locations. Review the active storage mode in Settings before running data-producing workflows.

Developer Architecture

Kamino Console separates VS Code host code from React webview code.

• src/extension.ts: activation wiring only.
• src/adapters/vscode/webview: VS Code webview providers, host IPC guards, and host message routing.
• src/commands: VS Code command registration and extension-host command coordination.
• src/domain: plain TypeScript app and KyberCrystal models/argument shaping.
• src/messages: plain TypeScript host/webview message contracts, message router, and success/failure response helpers.
• src/react: browser-only React app code.
• src/services: extension-host services such as KyberCrystal process invocation.

New React features belong under src/react/features/<featureName> with page, options, types, commands, components, state, and utilities kept feature-local. Shared UI belongs under src/react/components using:

• 01-atoms: reusable controls and primitive UI styling.
• 02-molecules: reusable composed UI patterns such as result display and segmented controls.
• 03-compounds: feature-sized reusable blocks.
• 04-materials: app frame, page, and panel surfaces with no feature state.
• 05-shell: app shell composition, header, navigation, and page outlet wiring.

The expected request pipeline is:

Feature UI
  -> Feature State Hook
  -> React Message Bridge
  -> Message Contract
  -> Message Router
  -> KyberCrystal Service
  -> KyberCrystal Runtime

Feature command builders create typed payloads only. Feature state hooks own inputs, loading state, result state, error state, and bridge interactions. src/react/bridge/messageBridge.ts is the only webview-side owner of acquireVsCodeApi, postMessage, request ids, and subscriptions. src/messages/messageRouter.ts owns host message dispatch and success/failure envelopes; providers pass host-specific handlers into the router.

React code must not import src/services or VS Code APIs directly. Domain and message contracts must not import React or VS Code. KyberCrystal command argument shaping belongs in src/domain/kyber; process execution belongs in src/services/KyberCrystalService.ts.

Run guardrails from the repo root:

npm.cmd --prefix apps/KaminoConsole run verify
npm.cmd --prefix apps/KaminoConsole run check:architecture
npm.cmd --prefix apps/KaminoConsole run check:kyber

Source

• License: See apps/KaminoConsole/LICENSE