Command
Build release artifacts from committed sources — .cf for the main configuration and .cfe per extension, with optional version bump, changelog and git tag.
Command
Build release artifacts from committed sources — .cf for the main configuration and .cfe per extension, with optional version bump, changelog and git tag.
Command
Toggle the caveman communication style — set CAVEMAN (on|auto|off) in .dev.env for the whole project; on|off|auto persist, lite|full|ultra switch the session level.
Command
Check a 1C XML configuration dump for duplicate UUIDs, and optionally regenerate them.
Command
Check availability of 1C MCP servers and install/start the missing ones.
Command
Read-only check for available updates of the 1C MCP server images (stable and -beta channels) and of the 1c-rules ruleset, without pulling or installing anything.
Command
Load the configuration into the test infobase from .dev.env and run UI tests in the web client.
Command
Diagnose whether 1c-rules is installed, connected, configured, and usable by the current agent.
Command
Toggle orchestrator economy mode via ORCHESTRATION in .dev.env; on enable, offers to configure per-tier subagent models and to set up the rtk output-compression proxy.
Command
Aggregate accumulated rule-friction signals into user-approved behavior rules in LLM-RULES.md (ruleset self-improvement loop).
Command
Extract configuration objects from infobase to files for editing.
Command
Initialize a 1C project — test infobase from an existing IB / .cf / .dt, full source dump (cf + all cfe) into a git repository, first commit.
Command
Install agent-browser (token-efficient headless browser CLI + MCP) for 1C web UI testing.
Command
Install Cognee MCP as optional persistent agent memory and register it in the active AI client.
Command
Install DitriX EDT-MCP into a local 1C:EDT installation and connect the active AI client.
Command
Install Windows-MCP (desktop UI automation MCP) as a last-resort alternative to home-grown screenshot/OCR.
Command
Download the 1C MCP server distribution from vibecoding1c.ru and install all servers from it, in the stable or the beta image channel.
Command
Detect and optionally install the supported 1C development tools through one guided menu.
Command
Toggle lightweight QA mode — set VERIFICATIONDEPTH (full|standard|lite) in .dev.env and, at level lite, disable UI testing (UITESTING=off).
Command
Dump the configuration from the infobase defined in .dev.env into the current repository files.
Command
Rebuild the test infobase to the effective snapshot — optional DT data baseline, then the current cf + cfe sources from git.
Command
Adapt the ruleset to the model that is actually running — normalize a free-form model name to a profile slug and write AGENTMODEL (opus5|sonnet5|fable5|gpt56) into .dev.env.
Command
Send a problem report about a 1C MCP server or about the 1c-rules ruleset to the support service (Yandex Cloud Function -> Yandex Database).
Command
Show the status of your support tickets about MCP servers and the 1c-rules ruleset, and close a ticket you no longer need.
Command
Closed deploy → test → fix → redeploy loop against the test infobase, until the scenarios pass or the iteration budget is exhausted.