SkillFoxx

1C AI sandbox client-server workflow

1c-ai-sandbox-client-server

A devcontainer plus a Hyper-V VM with a 1C server that isolate an AI agent from the host machine so a wrong command cannot touch real files or drives

  • 44 ★ on the repository
  • Last commit
  • MIT
Workflow

Extended access

Why this level

  • Deploys a virtual machine and Docker containers with full administrator rights on the host
  • Scripts handle real 1C platform license data if DEV_LOGIN and DEV_PASSWORD are set
All reasons and checks
Russian stack

steelmorgan/1c-ai-sandbox-client-serverAuthor:SteelMorgan

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add workflows/1c-ai-sandbox-client-server

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Deploys a virtual machine and Docker containers with full administrator rights on the host
  • Scripts handle real 1C platform license data if DEV_LOGIN and DEV_PASSWORD are set

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

What it does

The project sets up two isolated parts for safely letting an AI agent work with 1C. The client part is a Linux dev container with 1C thick and thin clients, including the Configurator, a headless Xvfb display and wrapping for the Claude, Codex, Gemini and DeepSeek Harness CLI agents with ready bootstrap scripts. The server part is a separate Ubuntu VM in Hyper-V with a Docker Compose stack of a 1C server, PostgreSQL and Apache for web publications, deployed by a PowerShell script that downloads and patches the Ubuntu ISO automatically. The idea is that the agent works only inside the container and the VM and physically cannot delete or change anything on the host.

Who it is for. For 1C developers who want to give an AI agent real access to the 1C platform but worry a wrong command could touch a working drive or a production infobase.

Good fit when

  • You want to give an agent a real 1C client and server, but isolated from the host machine
  • You have a Windows host with Hyper-V and Docker Desktop to deploy the server VM
  • You work in Cursor or VS Code with Dev Containers

Not a fit when

  • You do not have a Windows host with Hyper-V: the server scenario is only verified there, Linux hosts are untested
  • You need a lightweight setup without a virtual machine and Docker

Example request

Deploy the sandbox, bring up the demo test infobase and publish it through the web client

Limitations

The server scenario is only verified on a Windows host with Hyper-V and PowerShell run as administrator, Linux hosts with KVM, QEMU or VirtualBox are untested. Per the author, community license auto-activation is currently broken on the platform side, so the DEV_LOGIN and DEV_PASSWORD variables should be left empty. Deployment requires Docker Desktop, Hyper-V and downloading the official Ubuntu ISO.

How to disable. Remove the dev container from VS Code or Cursor and delete the virtual machine in Hyper-V Manager if it is no longer needed.

FAQ

Why build a sandbox like this at all?

The author lost 10 years of family photos to an AI agent's mistake and built an isolated environment so the agent physically cannot delete anything outside the container and VM.

Which CLI agents are already set up?

.devcontainer/cli-agents has ready bootstrap scripts for Claude, Codex, Gemini and DeepSeek.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools

1C AI development environment

1C AI Development Environment

Russian stack

1C development environment with an MCP server offering 10 tools: 11 BSL analyzers, JSON DSL to XML, dependency graph, and EPF build without 1C

MCP serverBroad access18
Russian stack

A guide with working scripts on safely connecting an agent to 1C and Bitrix24: OData, webhooks and a catalog of 14 vetted tools

WorkflowExtended access13
Russian stack

A skill for 1C platform batch operations: build and unpack data processors, load and dump configurations and extensions, launch the base

SkillBroad access129
Russian stack

A Pi Coding Agent profile for 1C development: ASK, PLAN and BUILD modes, specialized subagents, per-configuration knowledge and optional MCP tools

PluginBroad access21
Russian stack

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

CLIExtended access66

README in short

The README explains the project's motivation with a story of losing personal files to an agent's mistake, and describes the architecture of a client dev container and a server Hyper-V VM with a connection diagram. It gives step by step instructions for preparing .env files, running the server-part deployment script and publishing infobases through Apache, plus explicit limitation warnings: tested only on a Windows host.

README badge

Report a problem