1C: Platform Tools
A VS Code and Cursor extension for 1C: vanessa-runner commands, metadata, debugging, tests and skills for AI agents.
- 240 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- vanessa-runner commands run on the developer machine and can change infobases, configurations and extensions
- Skill sets are downloaded from GitHub on every call and land in the agent's folders
Install
- Works in
- Services
Manual install
Install the `1C: Platform Tools` extension from the VS Code Marketplace or Open VSX and open a project with a `packagedef` file. In the 1C: Tools tree, Skills for AI section, add skills to your agent's folder. To let an agent call commands, install the `1C: Platform Tools MCP` extension.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- vanessa-runner commands run on the developer machine and can change infobases, configurations and extensions
- Skill sets are downloaded from GitHub on every call and land in the agent's folders
This is third-party code. Review the repository files before installing.
What it does
1C: Platform Tools is an extension for VS Code, Cursor, Windsurf and VSCodium for 1C:Enterprise development. One interface gathers vanessa-runner commands, a metadata tree, a test panel (Vanessa, xUnit, YAxUnit, OneScript), debugging and pipelines. Projects in configurator format, 1C:EDT and OneScript are supported. For agents, the Skills for AI section installs skill sets (cc-1c-skills, OneScript, Vanessa Automation, YAxUnit, xUnit) into `.cursor/skills`, `.github/skills` or `.claude/skills`. Commands run through the trigger file `.cursor/1c-platform-tools-run-command` or the separate 1C: Platform Tools MCP extension.
Who it is for. 1C developers who keep configurations in VS Code or Cursor and want to give an agent the extension's commands and platform skills.
Good fit when
- A configuration is kept in EDT or configurator export format and Vanessa and YAxUnit tests run from the editor.
- An agent in Cursor or Claude Code gets skills for 1C XML, forms, data composition and metadata.
- Each branch has its own infobase and the launch profile switches in the status bar.
- Platform commands run in Docker without a local 1C install, including in GitHub Codespaces.
Not a fit when
- Development happens only in the configurator or 1C:EDT without VS Code.
- The machine has neither the 1C platform nor Docker: commands will not run without them.
- An agent needs direct command calls with results: install the separate MCP extension for that.
Example request
Run the YAxUnit tests of the current 1C project, show the failing ones and open the failure location in code.Limitations
The 1C:Enterprise 8 platform is required, along with OneScript, OPM and vanessa-runner, installed from the Dependencies section. Skill sets download from GitHub on every call, so they cannot be obtained without GitHub access. The extension itself can be taken as a `.vsix` file from releases. It activates when the workspace holds a directory with a `packagedef` file. Direct command calls with results come from the separate 1C: Platform Tools MCP extension.
How to disable. Disable or uninstall the extension in the extensions panel. Delete the skills manually from `.cursor/skills`, `.github/skills` or `.claude/skills`, wherever they were copied.
FAQ
Does the extension work in Cursor?
Yes. Cursor, Windsurf and VSCodium install it from Open VSX, with the same panels and commands as VS Code.
How do I give an agent 1C skills?
In the 1C: Tools tree open the Skills for AI section and choose a set: cc-1c-skills, OneScript, Vanessa Automation, YAxUnit or xUnit. The target folder is `.cursor/skills/`, `.github/skills/` or `.claude/skills/`.
How does an agent run extension commands?
Through the trigger file `.cursor/1c-platform-tools-run-command` holding one command ID, for example `1c-platform-tools.run.designer`. The extension runs the command and deletes the file.
Is a local 1C platform required?
No, if commands run in Docker through `ibcmd`. This also works in GitHub Codespaces.
Which project formats are supported?
Configurator export, 1C:EDT and OneScript. In EDT format there is no shared `src` directory: the configuration and extensions sit at the project's top level.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise toolsA VS Code and Cursor extension that exposes 1C: Platform Tools commands to the agent: tests, launch profiles, configuration builds and infobase work
A VS Code and Cursor extension pack for 1C development: platform tools, an MCP bridge to them, and BSL syntax support
Cursor skills for 1C
1C Cursor skills
A set of Cursor skills for 1C: an analyst skill with a task template, configuration and extension editing, SKD, forms, tests and platform tooling
1C AI Development Kit: 1C skill collection
1C AI Development Kit
A set of 52 Claude Code skills and agents, plus Cursor rules, for the full 1C:Enterprise 8.3 development cycle, assembled from several community projects
The 1c-dev Claude Code plugin: discussing a 1C task in dialogue, a technical spec, dependency-aware steps, and executing one verified step at a time
A shared skill and tooling infrastructure for 1C development, wired in as a git submodule and laid out across several agents at once
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| 1C: Platform Tools (this card) | no | 240 | ||
| 1C: Platform Tools MCP | no | not required | 44 | exposes the extension's commands to an agent over MCP; this card is the commands, panels, debugging and skill installation themselves |
| 1C Platform Extension Pack | no | not required | 28 | a pack of three VS Code and Cursor extensions for 1C; this is the single main extension with platform commands |
README in short
The Features section lists the panels: tools, projects, administration, artifacts, metadata, tests, debugging, pipelines and ER diagrams. Separate sections cover installation per editor, a quick start with `packagedef` and work without a local 1C install.