1c-devtools-cursor

Manages 1C:Enterprise configurations, extensions, and BSL debugging inside Cursor IDE.

4|Updated May 16, 2026
One-click install
npx skills add https://github.com/reason-machines/devtools-skills --skill 1c-devtools-cursor-reason-machines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 1c-devtools-cursor
Source: https://github.com/reason-machines/devtools-skills/tree/main/skills/1c-devtools-cursor
Command: npx skills add https://github.com/reason-machines/devtools-skills --skill 1c-devtools-cursor-reason-machines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developing for 1C:Enterprise 8 typically requires switching between the Configurator, command-line tools, and version control, fragmenting the workflow. This Skill brings infobase management, configuration source export/import, extension handling, and BSL debugging directly into Cursor IDE. ## Core Features & Use Cases - Configuration & Extension Management: Load, update, export, and build configurations (src/cf, .cf) and extensions (src/cfe, .cfe) via command palette commands. - BSL Debugging: Attach to the dbgs.exe debug server with breakpoints, watch expressions, call stack navigation, and step commands for BSL modules. - Infobase & External Files: Create empty infobases, export/import .dt files, and build or disassemble external reports and processors. - Use Case: A 1C developer exports configuration changes to src/cf, commits them to Git, and teammates apply incremental updates using build/commit/Commit.txt, all without leaving Cursor. ## Quick Start Ask the agent to set up a 1C project in Cursor by creating the packagedef, env.json, and launch.json files, then create an empty infobase and load the configuration from src/cf.

Frequently Asked Questions about 1c-devtools-cursor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug 1C BSL code in Cursor IDE?▼

Set breakpoints in .bsl files, press F5, and select a launch configuration such as "1C: Launch with background jobs" or "1C: Attach". The extension connects to the dbgs.exe debug server on the configured port and supports watch expressions, call stack navigation, and step commands.

How to export 1C configuration to source files for Git?▼

Use the "1C: Export to src/cf" command for a full export or "1C: Export update to src/cf" to export only changes. Teammates apply incremental updates with "1C: Update from src/cf", which reads the changed file list from build/commit/Commit.txt.

What are the prerequisites for 1C development in Cursor?▼

You need Node.js 18.x or higher, OneScript (oscript) installed, and a Windows environment variable named oscript pointing to oscript.exe. The extension auto-activates when a packagedef file exists in the project root.

Why is the 1C Dev Tools extension not activating in Cursor?▼

The extension only activates when a packagedef file exists in the project root. Ensure the file is present, restart Cursor, and check the Output panel under "1C Dev Tools" for errors.

Why are variables not showing in the Watch panel while debugging BSL?▼

Local variables do not display in the default view, so select the correct frame in the Call Stack panel and manually add the variable to Watch. You can also increase varFetchDelayMs in the debug timings settings or use the "Calculate value" button for complex expressions.

Can I manage multiple 1C extensions from Cursor?▼

Yes, extensions are stored as subdirectories under src/cfe, one per extension. Commands like "1C: Load from src/cfe" and "1C: Export update to src/cfe" operate on all extensions at once, and you can build or disassemble .cfe binary files.