I am locating the counterparty form and related project code.
unica.viewCatalog.Counterparties · ItemFormunica.searchINN · 3 matchesFree plugin · Unica 0.13.0
The full development cycle for an individual 1C developer with an AI agent: code and metadata, validation, build, and execution. For Codex, Claude Code and ZCode.
Interactive example
Add INN validation to the counterparty form.
I am locating the counterparty form and related project code.
unica.viewCatalog.Counterparties · ItemFormunica.searchINN · 3 matchesInteractive example: Add INN validation to the counterparty form.
For individual developers
Unica is free. Its purpose is to cover the full development cycle for an individual 1C developer. You define the task and review the result; the agent uses Unica tools to work on the project.
Find the relevant object, read its module, and inspect the existing implementation.
Edit code, metadata, a form, role, or report. Review a plan before writing to sources.
Read diagnostics, fix errors, and run checks in 1C.
Build a processor or distribution, work with configurations and infobases, and launch the client.
Unica helps you program. System design, teamwork, and multi-agent workflows require separate solutions.
The Unica plugin is free. AI services and the 1C platform license are provided under their suppliers’ terms.
Developer feedback

A case from practice. I was working on a multi-agent system, with my head full of that work and other thoughts. A developer from another project came over and said he was exhausted from wrestling with a DCS report: he kept trying and could not make it work. I knew he was experienced and simply worn out, so I had to help.
1) I took an ERP XML export, his report, and Unica, put them into the chat, and said: here is the problem, fix it. The agent fixed it. I gave the report to the developer, but it did not work: the data had changed, but incorrectly.
2) We took a screenshot showing what was wrong and sent it to the agent with: it does not work. We received the report and gave it to the developer. The report would not open. It turned out the agent had inserted its own comment before the query, which got in the way. We removed the line manually and checked the report: it worked as expected. On the next iteration, the agent corrected that as well.
The agent work took about 15 minutes in total. I am writing it as it happened: yes, it made mistakes, but that was the result.
The task was solved there and then, without additional struggle with infrastructure, RAG, or embeddings.

I have tried different technology stacks for agent-assisted development on the 1C platform, but Unica makes automated testing the easiest to set up. At the very least, Unica is a very strong tool among comparable solutions.

It happened on a Saturday morning. After an update to a standard Retail 3.0 file-based installation, we found a bug in DataMatrix code scanning at the cashier workstation. The background code-verification operation would hang in the verification and selection window. When scanning directly at the cashier workstation, the marking icon did not appear, and the mark was absent from the receipt, so it was not sent to Chestny ZNAK. I loaded the configuration on my computer, and GPT 5.5, using Unica — I think the version was around 0.4 at the time, though I may be mistaken; this was in early July — produced fixes for these bugs as an extension. The direct-scan marking icon was not fixed, but scanning through the verification and selection form worked correctly. That was enough overall, and the customer accepted it.

Today, with Unica+Luna, I fixed an error in a service that loads regulated documents from a medical information system: 15 minutes of work plus 15 minutes refining the prompt. Yesterday I had spent an hour and a half getting nowhere while reviewing it myself without AI. After 23 years of 1C development, the feeling is decidedly mixed.

Today, with Unica+Luna, 15 minutes of work plus 15 minutes on the prompt fixed an error…
I had spent two weeks building an integration. Before the demo, the other side changed the API specification. Out of desperation, I gave Codex — with Unica — the documentation, a key, and the sources, and asked it to help. Three hours later, I already had the new integration. I am not spreading the word within the team yet…
Installation
Choose Codex, Claude Code or ZCode. Git is required. 1C 8.3.27 is needed for operations that launch 1C; reading and editing sources does not require it. The core and required engines download automatically on first use.
Send the repository link to the agent. It will read the current instructions and run the commands.
Install Unica using the instructions at https://github.com/IngvarConsulting/unicacodex plugin marketplace add IngvarConsulting/unica-marketplace --ref main
codex plugin add unica@unicaAfter installation, open a new Codex task so Unica becomes available.
codex plugin marketplace upgrade unica
codex plugin remove unica@unica
codex plugin add unica@unicacodex plugin remove unica@unica
codex plugin marketplace remove unicaIf the plugin is missing, finish the current task after reinstalling and open a new one.
claude plugin marketplace add IngvarConsulting/unica-marketplace
claude plugin install unica@unicaAfter installation, run /reload-plugins or start a new session so Unica becomes available.
claude plugin marketplace update unica
claude plugin update unica@unicaclaude plugin uninstall unica@unica
claude plugin marketplace remove unicaIf the skills are missing, run /reload-plugins or start a new session after updating.
After installation, open a new ZCode task so Unica becomes available.
Keep only one Unica installation enabled. Start a new task after updating.
Build teamwork and multi-agent workflows yourself or with help from Ingvar Consulting. Start with an audit of task briefs, agent coordination, and change verification. You will receive a risk register and a practical improvement plan.
Analysis and design
For a system that supports analysis and design, use Unica Arch. It is a separate product and is not included in free Unica. Ingvar Consulting can demonstrate it on request and discuss how it fits your task.
The technical site describes Unica’s own architecture, tool implementation, and API contracts. It is intended for plugin developers and contributors.
Capabilities · Unica 0.13.0
55 skills guide the agent through 1C development tasks. Version 0.13.0 uses one API with logical object addresses for search, inspection, planning, applying changes, and validation. Long-running tasks can be tracked and cancelled.
MCP tools · 11
View the MCP runtime on GitHubUnica exposes this public API through MCP.
| Tool | What it does | Why this helps the agent |
|---|---|---|
unica.view | Shows what is in the project and opens an object by address: attributes, forms, templates, and code. | The agent inspects an object without needing to know where its files are stored. |
unica.resolve | Converts an address to a file and a file to an address. It does not search by name. | The agent requests a path only when needed; other tools work with logical addresses. |
unica.search | Searches BSL text, procedure and function declarations, and metadata names and synonyms. Searches can be scoped to one object. | The search stays within the relevant project branch. Results include object addresses and search completeness. |
unica.diff | Shows differences between two objects of the same kind. | Comparison needs no temporary file exports and changes nothing. |
unica.check | Without an address, checks workspace admission. With an address, runs all validators owned by that object kind: module, form, role, or DCS. | Diagnostics arrive as a list, so the agent can fix errors individually and see what remains. |
unica.apply | Plans an edit, such as adding an attribute, changing a property, or editing code. Returns a plan without changing sources and an executionToken; a subsequent token-only call executes the saved plan. | The agent reviews changes before writing. Execution needs only a token because the address and operations are already saved. |
unica.run | Without arguments, lists 13 runtime operations with support status; 10 are executable in this version. Covers workspace setup, infobases, configurations and extensions, snapshots, distributions, and client launch. For preview operations, dryRun: true previews and dryRun: false executes. | The dictionary comes from code with implementation status, so the agent avoids invented or unsupported commands. |
unica.docs | Searches platform help and development standards, or opens a document locator. Configuration documentation is not supported in this version. | Results identify each source and its search completeness. The agent can continue reading long documents page by page. |
Three additional MCP tools provide task status, results, and cancellation for clients without native MCP Tasks support.
| Tool | What it does | Why this helps the agent |
|---|---|---|
unica.task.get | Returns the current task state without waiting. | The agent checks progress without running the original operation again. |
unica.task.result | Waits for a task result within a bounded interval. | The agent receives a result or continuing-work status without repeating the operation. |
unica.task.cancel | Requests cancellation and returns the current task state. | Repeated cancellation requests are safe and do not restart the task. |
The Russian legal documents are controlling. English versions are available for the Marketplace.