SkillFoxx

Type a name, a task or a service

v8-runner

A Rust CLI and MCP server for the local 1C development loop: builds, syntax checks, YAxUnit and Vanessa tests, dumping changes

CLIMedium riskRussian stack

alkoleft/v8-runner-rustAuthor: alkoleft

Install

cargo build --release

Build from source, the binary lands in target/release/v8-runner.

This is third-party code. Review the repository files before installing.

What it does

v8-runner replaces a pile of scripts and manual Designer, EDT and Vanessa Automation runs with one entry point. A single v8project.yaml describes sources, the working infobase, tools and tests, and config init or bootstrap creates it from the repository layout or an existing infobase. It then offers incremental builds, module syntax checks, YAxUnit and Vanessa Automation runs, dumping, converting and loading cf, cfe, epf and erf files, and launching 1C clients. For agents there is an MCP server over stdio or HTTP with a narrow tool set, plus machine-readable --json-message output.

Who it is for. For 1C developers and teams who need a repeatable local build and test loop for themselves, CI and agents.

Good fit when

  • You want the agent to build the project, check syntax and run tests on its own
  • You want to replace scattered bat scripts with one config and command set
  • You want YAxUnit or Vanessa Automation to run with one command after a build

Not a fit when

  • The machine has no 1C platform or EDT
  • You need to work with a server infobase in production

Example request

Build the project, check server module syntax and run all YAxUnit tests

Limitations

Requires an installed 1C platform, and EDT for EDT projects. AGPL-3.0 license. Some features depend on the build backend: not every operation works through IBCMD. There is no separate connection preflight for server infobases yet.

How to disable. Delete the v8-runner binary and the server block from your MCP client config. v8project.yaml and v8project.local.yaml in the project can be removed manually.

Security check

  • Runs the 1C platform and loads configurations into infobases
  • Stores infobase credentials in a local file

README in short

The README presents v8-runner as a single entry point for local 1C development and walks through a quick start: building the binary, creating the config, downloading YAxUnit, Vanessa and client MCP, preparing the infobase, building, syntax checks and tests. A capability table groups commands into project setup, verification, file materialization, direct launch and MCP. The repository also ships a SKILL for Codex and detailed configuration and architecture docs. AGPL-3.0 license.

FAQ

Are EDT projects supported?

Yes, source sets can be DESIGNER or EDT format, and init imports the workspace for EDT.

Where do infobase passwords go?

Into v8project.local.yaml next to the main config. That file is added to .gitignore automatically.

Editors’ pick

An MCP server built into the Netdata agent: metrics, logs, alerts and live process, service and container data for an AI assistant

MCP serverMedium risk80.5K
Editors’ pick

GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent

MCP serverHigh risk32.9K
Editors’ pick

A GitHub Action that runs Claude Code in pull requests and issues: answers mentions, reviews and makes changes

PluginHigh risk8.9K
Editors’ pick

An AI assistant for Kubernetes that turns plain-language requests into kubectl operations and doubles as an MCP server

CLIHigh risk7.6K