OneScript CLI

OneScript is a CLI for automation in the 1C language, running scripts outside the platform and adding packages through opm.

  • 590 ★ on the repository
  • Last commit
  • MPL-2.0
CLI

Broad access

Why this level

  • The runtime executes supplied scripts with the user’s access to files, network and system operations.
All reasons and checks
Russian stack

evilbeaver/onescript

Install

Manual install

Text for your agent

Open https://github.com/EvilBeaver/OneScript and select the OS distribution. Explain FDD/SCD dependencies before setup. Read the script first and execute only an approved operation against test data.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • The runtime executes supplied scripts with the user’s access to files, network and system operations.

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

What it does

OneScript is a CLI and runtime for text scripts written in the 1C:Enterprise language. Developers invoke programs through `oscript` without installing the 1C platform on the target computer. The project independently implements its virtual machine and does not use 1C system libraries. Common packages are bundled, with more in oscript-library through opm. Version 2 uses .NET 8, with distributions for Windows, Linux and macOS. Scripts run directly through `oscript`; dependencies on 1C platform features need separate compatibility checks.

Who it is for. 1C developers automating operational tasks in a familiar language on machines without the 1C platform.

Good fit when

  • A developer writes an operational script for a machine without 1C installed.
  • A team moves the same automation between Windows and Linux.
  • An administrator selects a runtime-bundled distribution instead of setting up .NET separately.
  • A script author adds an oscript-library package for a recurring task.

Not a fit when

  • A script relies on 1C platform libraries unavailable in the independent implementation.
  • A user wants an MCP connection to an information base without writing code.
  • An operator would run an unfamiliar script with access to working files and credentials.

Example request

Prepare a OneScript task for a working-folder copy and show all file operations before executing it.

Limitations

The implementation does not use 1C:Enterprise libraries, so scripts depending on the platform need compatibility review. Version 2’s Linux FDD distribution requires .NET Runtime 8.0, while SCD bundles it. In the Mono-based 1.x branch, debugging needs `mono-complete` from the Mono Project repository. A source build without a C++ compiler omits the NativeApi bridge and excludes it from the resulting distribution.

How to disable. Remove `oscript` from schedules and scripts. Stop running scripts, then remove the runtime directory or its PATH entry; files created by scripts remain.

FAQ

How do I install OneScript?

On Windows, download and run the installer from https://oscript.io or https://github.com/EvilBeaver/OneScript/releases. For Linux or macOS, select your system’s distribution from the releases page.

Which Linux archive should I choose?

SCD includes .NET Runtime. FDD needs a separate .NET Runtime 8.0 installation. Choose for your environment, extract it and use `chmod +x oscript`.

Is the 1C platform required?

No. OneScript runs scripts on its own virtual machine. Review dependencies on 1C libraries first and replace them with suitable packages where needed.

Where are additional packages?

The README points to https://github.com/oscript-library and the opm package manager. Select a package through its documentation and review its actions before including it in a script.

Why does NativeApi fail to build?

The bridge requires a C++ compiler. `NoCppCompiler=True` excludes native components; use it only when your scripts do not depend on them.

Discussion

No questions or reviews yet.

Russian stack

A local OneScript MCP server for searching a 1C configuration dump right from Cursor

MCP serverExtended access18Repository stars
Russian stack

A toolkit for 1C development with an agent: skills, rules, roles, an MCP server for the NinjaLive extension and an OpenCode installer for Windows

WorkflowBroad access1Repository stars
Russian stack

Ready-made methods for Telegram, Bitrix24, VK, CDEK, Yandex Disk, databases and other APIs in 1C, OneScript and the oint CLI

CLIBroad access693Repository stars
Russian stack

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

SkillBroad access129Repository stars

onec-hbk-bsl: BSL linter and MCP

1C HBK BSL (onec-hbk-bsl)

Russian stack

A BSL CLI linter and formatter with 180 diagnostics, an LSP server for VS Code and Cursor, and MCP tools for local AI assistants

CLIExtended access13Repository stars
Russian stack

A set of skills, rules and MCP servers for 1C Enterprise 8.3 development where the agent works from real code and docs, not from memory

SkillBroad access35Repository stars

README in short

The README separates Windows, Linux and macOS setup and the .NET 8 and Mono branches. SCD and FDD differ in bundled runtime. Contributor sections cover builds and BSL tests.

README badge

Report a problem