ComplyEaze Bridge: TallyPrime MCP server for Claude Desktop

ComplyEaze Bridge is an open-source (Apache-2.0) TallyPrime (also written Tally Prime) MCP server for Claude Desktop. It connects Claude Desktop to the TallyPrime running on your own computer, and it is built for chartered accountants, CA firms and accountants. What Claude reads from your books goes to your AI provider as part of the chat. You can ask about the trial balance, outstanding receivables and payables with ageing, ledger movement and vouchers, the purchase and sales registers, the stock summary, and the Profit and Loss and Balance Sheet (a book with stock items is expected to be refused for these two). It checks ledger names before you post. For bank statement to TallyPrime vouchers, it proposes Payment, Receipt and Contra vouchers from a password-protected SBI, HDFC or Union Bank of India statement PDF, and it prepares Journal, Payment, Receipt and Contra vouchers as an import file that you review and import into TallyPrime yourself. Posting is off by default, so as installed it never posts to TallyPrime: it reads from it and prepares files on your computer. If you turn posting on in the extension, it posts vouchers one at a time, after you approve each one.

Tally Solutions also offers its own TallyPrime MCP plug-in for Claude Desktop; its help pages (last updated 18 September 2026) list tools in six groups: company, master, accounting, inventory, outstanding and transaction. ComplyEaze Bridge is not made by, or affiliated with, Tally Solutions, and we have not run the two side by side. TallyPrime also has its own Bank Statement import, which takes statement files in the formats Tally lists for each bank.

Current release: mcp-v0.5.1 (9 October 2026), for Windows x64 and Apple Silicon Macs, as a Claude Desktop extension (an .mcpb file); it has not been run in other MCP clients. We check each release before we publish it: the release check confirms that each package launches, lists its tools and parses a synthetic encrypted bank statement. It does not run against TallyPrime, and nothing we can run covers every Tally edition, set of books or setting. What has been run against a real TallyPrime, and what has not, is listed below. Install it · What changed · Security and privacy · How to connect Claude to TallyPrime · How to choose a TallyPrime MCP server safely

Not yet code-signed; your computer may warn you before opening it.

Try asking (on a test company first):

• "List the loaded companies."
• "Show the outstanding receivables and payables, with ageing, as of 31 March."
• "Show the trial balance for 1 April to 31 March."
• "Check these ledger names against the book before I post: …"

Its tools. Release 0.5.1 installs these 23, in name order. None of them changes your TallyPrime books, and every call adds a receipt line, with no figures, to a log on this computer.

With posting turned on in the extension, two more appear: post_import posts one saved voucher after you approve it in a ComplyEaze Bridge window, and acknowledge_post_review asks you, in its own window, to record that you reviewed a posted voucher whose ledger now points to a different master.

How it handles your books

• Local connection only. It talks to Tally's own XML gateway on a loopback address, so it cannot be pointed at a remote Tally host. It cannot tell whether that local port is forwarded to another machine; do not forward one across the internet. The Tally connection sends nothing to a ComplyEaze server.
• Your AI provider sees what the assistant reads, just as it sees the rest of the conversation, including company, party and ledger names, amounts, dates, narrations, references, GSTINs and, when it reads ledger details, PAN, bank account numbers, IFSC, MSME or Udyam registration numbers, email, phone and address, and, when it builds a voucher file, that file's local path (which can include your computer user name). The setting takes one value, not both: shorten party and ledger names and bank account numbers to their first two and last two characters (four or fewer become “…”), or drop narrations. Neither hides amounts, company names, PAN, GSTIN, IFSC, MSME or Udyam registration numbers, contact details or references, and a shortened name can still be identified, not least from the GSTIN or PAN sent beside it. See Before you use it with client data below.
• Posting is off by default in the extension. If you installed an earlier version, check the setting: an earlier default may still be saved as on. When you turn posting on, each voucher waits for your approval in a separate ComplyEaze Bridge window. No Bridge tool lets the assistant approve it, and an approval counts only when that window returns a fresh one-time token. After posting, the voucher is read back from Tally so you can see what landed. Four known limits remain: ComplyEaze Bridge cannot undo a posted voucher (you correct it in Tally); a company renamed to, or loaded under, the target company's name (or one differing only in case or spacing) just after its last check could still receive the voucher, if it has the voucher's ledgers, and ComplyEaze Bridge cannot always say where it went or prevent it; a ledger renamed and replaced in that same moment could receive the entry, and not every such change is noticed; and the approval window covers only ComplyEaze Bridge, so another Tally connector in the same Claude Desktop that can change entries can do so without it. Read Before you turn on posting first.
• Tool calls leave receipts in a log on your computer: the company's Tally identifier, and a fingerprint of what was asked and of what came back, written whether the call succeeds or is refused.
• You accept the Terms of Use first. The extension asks you to accept the ComplyEaze Bridge Terms of Use (version 2026-10.1) in its settings, and every tool refuses with terms_not_accepted until you do. (In 0.5.0, after an update from 0.4.2, Claude Desktop may not start the extension: on a Mac with an error that does not mention the Terms, on one Windows computer with no error; #1413.)
• Open source under Apache-2.0.

What has been run against a real TallyPrime

Each line below is recorded in the repository or on the linked issue or pull request, unless marked as reported by the owner. Each ran on licensed TallyPrime Silver 7.1 and synthetic companies unless stated. The MCP guide and ADR 0004 hold the full record.

• Reads: 27 checks on an unpublished macOS arm64 build (PR #228), recorded in the 6 September 2026 assessment. Some later reads were also run live on development builds, for example the trial balance on a debug build with synthetic companies (#246, whose record does not name the Tally release or licence tier). Not every read has its own recorded live run.
• Posting one Journal, on a development build from 22 September 2026 (issue #579), and a Payment, a Contra and two Receipts (one of three entries) with the approval dialog on macOS (PR #600), each read back as posted. These builds predate the release published on 26 September 2026 (version 0.3.0).
• Native posts of ten batches on licensed TallyPrime Gold 7.1, in one session on 28 September 2026, on a development build and one client book (the import request was captured for nine of them); their approval step was not recorded (protocol reference).
• The published 0.3.0 package on Windows x64, in Claude Desktop (with no paid plan; we make no claim about other plans): reads only, against licensed TallyPrime Gold 7.1 with one client book, on 28 September 2026, in a session separate from the development-build posting above (reported by the owner; no logs were kept).
• A candidate build of 0.4.0 on Windows 11, on 1 October 2026 (the build CI produced for the version pull request: the same code as the release apart from a comment in one test file). The maintainer installed it in Claude Desktop with a new Claude account that has no paid plan, against licensed TallyPrime Silver 7.1 holding one synthetic company. With the Terms setting off, a call was refused and nothing was read. With it on, tally_status, vouchers, validate_masters, purchase_register, stock_summary and local_data_report answered. One voucher post was declined in the Windows approval window and nothing was sent; one was approved, and one Journal was posted and then verified by verify_import. The same candidate's macOS build was started and read the company list, and in Claude Desktop on macOS its tools loaded in a chat. The record is the maintainer's dated notes and screenshots, kept privately. This was one run, not a controlled test of each key of the window.
• A build of 0.4.1 on a Mac, on 2 October 2026. What was run: the package CI built for the version pull request, not the published file. The maintainer installed it in Claude Desktop over an installed 0.4.0, as an upgrade; the Terms setting and the other settings carried over, and the extension's server process started again on its own after the upgrade (its start time was read from the process list). tally_status and list_companies then answered against licensed TallyPrime Silver 7.1 holding the lab's own synthetic companies. The record is our dated notes, kept privately. What was not run: the published file is built again on another runner, and its program file differs from the one tested. We ran both builds without Tally: each reports version 0.4.1, lists 21 tools and gives the same answer to tally_status. We have not installed the published file in Claude Desktop.
• A build of 0.4.2 on a Mac, on 3 October 2026. What was run: the package CI built for the release candidate, not the published file. The maintainer installed it in Claude Desktop on a Mac that had 0.4.1: it did not replace 0.4.1 but installed as a second extension (the author line changed in 0.4.2, and Claude Desktop builds an extension's identity partly from it); the settings did not carry over. tally_status and list_companies then answered against licensed TallyPrime Silver 7.1 holding the lab's own companies. The record is our dated notes, kept privately. What was not run: the published file is built again on another runner, and its program file differs from the one tested. We ran the published Mac file without Tally: it reports version 0.4.2, lists 22 tools with posting off (24 with it on), and refuses a call with the Terms setting off. We have not installed the published file in Claude Desktop, and nobody on our side has installed the Windows package in Claude Desktop on a Windows PC.
• A build of 0.5.0 on a Mac, on 8 October 2026. What was run: the package CI built in the merge queue for the version pull request, not the published file. The maintainer installed it in Claude Desktop over an installed 0.4.2: it replaced 0.4.2 as an update, with the Tally port, Response redaction and the posting setting as they were; the old Terms setting was gone and the new one had no value. Before the box was ticked, and before any quit, Claude Desktop did not start the extension, and a request failed with a 400 error that did not mention the Terms. After it was ticked and saved the extension started at once and tally_status answered, though the assistant first called a leftover second entry for the same extension, which failed the same way; after Claude Desktop was quit and reopened there was one connector and the company list was returned. The record is the maintainer's dated notes, kept privately. What was not run: the published file, quitting and reopening without ticking the box, installing over a release older than 0.4.2, a fresh install, and Windows.
• A package for 0.5.1 on a Mac, on 8 October 2026. What was run: a package built on that Mac from the Terms-setting change (#1436), with only its version set to 0.5.1; not a published file and not the CI package. The contributor installed it in Claude Desktop 2.26454.2 on macOS 26.6.2 with Tally not running and posting off: as a fresh install; over 0.4.2 (switched on with its Terms accepted; left off and then switched on); over 0.5.0 as an update leaves it and with the Terms ticked; and after 0.4.2 was removed. Claude Desktop started the program as soon as the extension was switched on each time, except once, over a 0.4.2 left switched off, where the assistant had no ComplyEaze Bridge tools until Claude Desktop was quit and reopened. With the Terms off, the call was refused and named the Terms; with them ticked, it reached the Tally check and reported Tally unreachable. A user-level BRIDGE_TERMS_ACCEPTED set to true did not change that: the program's own value stayed false. The record is on #1436. What was not run: a read of a live Tally with it, the published file, and Windows.
• Builds of 0.5.1 on a Windows computer, on 9 October 2026, India time (#1413). One Windows 10 computer (22H2), Claude Desktop 2.26454.2 from the Microsoft Store, TallyPrime Release 7.1 Silver, a company made for the test. What was run: the CI build of commit d744d25a (an earlier commit than the published file; later commits reworded some tool texts and the notes): a fresh install; an update from 0.4.2 and from 0.5.0 (as an update leaves it, and with the Terms ticked); a user-level BRIDGE_TERMS_ACCEPTED set to true; the company list; one bank-statement import file of six vouchers, built under 0.5.0 and under this build and compared, and this build's file imported by hand and read back (the verification found all six, the narrations were read back, and an August trial balance agreed with Tally's own screen; a first build under 0.5.0 into the company, which then held ledgers but no voucher, was refused as empty_book_first_import, so one more ledger and one 1 April voucher were imported into Tally outside ComplyEaze Bridge first, and that voucher is in the trial balance); an unchanged re-import of that file (matched to the six vouchers, none added); and a switched-off extension through two updates (it stayed off, with no tool and no error in the chat; switching it on was enough). Then steps 1 and 2 again on the CI build of the merged commit b91038a9, and step 1 on the published 0.5.1 file (checked against its .sha256 file and its build attestation), with Tally closed. The published 0.5.0 file over 0.4.2 was not started on this computer: the chat had no ComplyEaze Bridge tool and showed no error. What was not run: a changed re-import, steps 2 to 11 on the published file, posting, and other Windows versions, Tally editions or Claude Desktop builds. The record is the contributor's reports on #1413.
• The bank-statement path through its fourth step, on a Mac, on 4 and 5 October 2026, with that same CI-built 0.4.2 candidate (installed on 3 October; not the published file), against licensed TallyPrime Silver 7.1 holding the lab's own synthetic companies. The synthetic HDFC-format statement parsed (six rows, its totals matched the figures supplied); the name check found no "Suspense" ledger and building the file was refused, with no file written; after "Suspense" was created in Tally by a separate one-ledger import, outside this tool, a file of six vouchers was built. We have not imported that file or read it back, and no real statement has been run. The record is our dated notes, kept privately.

Not yet run by us in a controlled test: posting with a published package against a live TallyPrime; each way of declining in the Windows approval window (one was tried); the tools answering through Claude Desktop on macOS after the Terms are accepted (tally_status and list_companies answered on a CI build of 0.4.1, again on a CI build of 0.4.2 and on one Mac on a CI build of 0.5.0); posting on TallyPrime Education; posting on TallyPrime Gold with its approval step recorded. Each release package is built and launched, its tool list checked and a synthetic encrypted bank statement parsed, on hosted CI runners for Windows x64 and Apple Silicon Mac.

Not in the latest release

• Stock quantities, and stock reads on books with many masters of any kind; sales, purchase or tax posting; creating masters; bill-wise allocation
• TallyPrime Education mode: the trial balance, Profit and Loss, Balance Sheet, the stock summary and the masters read are refused; so is a read of vouchers, ledger movement, either register or another date-window read whose window starts or ends on a day other than the 1st, 2nd or 31st; so is an import file or a post with a voucher dated on any other day (posting on Education has not been run)
• The stock summary on a book with inventory turned off, or on a company split by year when a sibling year's company is loaded at the same time
• Deleting or undoing a posted voucher (correct it in Tally)
• Reads on very large books can fail or take longer than the assistant waits (#485, #703)
• A base currency other than INR. On a book with several currencies: the foreign-currency ledgers and vouchers themselves (they are set aside or withheld, and named), ledger movement, Profit and Loss and Balance Sheet, the purchase and sales registers (each refuses the whole read, with no rows, if one voucher in it names a set-aside ledger), and posting
• Tally Cloud Access or any remote Tally host
• Intel Macs, and a code-signed installer

Is this for you

It is aimed at a practising accountant or a CA firm that already keeps client books in TallyPrime and wants to ask questions of them, or post entries into them, through an AI assistant such as Claude Desktop.

What it does today

• Reads the loaded companies, ledger masters, trial balance, vouchers in a date window, outstanding receivables and payables, and ledger movement.
• Checks ledger names before you post. Give it the names from a bank statement or an invoice and it reports which exist in the book and which are near-misses needing your decision. Reading the ledger list first is the single biggest cause of an import being rejected wholesale when it is skipped.
• Records what it did. Every tool call Bridge runs — read or write, and whether it succeeds or is refused — appends a receipt to a log on your own machine, identifying the company it touched and fingerprinting what was asked and what came back. Reads keep those fingerprints as evidence alongside. A prepared batch records the local endpoint it was built for, and a native posting is refused if that endpoint has changed since; that is a safety check kept in Bridge's internal import ledger, not a line in the proof report a reviewer opens. A reviewer can read the log rather than take a summary on trust.

Before you turn on posting

Whether writing is on depends on how you installed it. Everything above is reading. When writing is off, the write tools do not merely refuse — they are absent from the tool list entirely, so an assistant cannot see that they exist.

• The Claude Desktop extension turns voucher posting off by default. Four known limits in posting remain. Tally aims an import at a company by its name and cannot bind it to a company's GUID. Bridge's last request before the post checks that exactly one loaded company has the target's GUID and name, and that no other loaded company has the same name ignoring case and spacing; otherwise it refuses the post (#607). A company renamed to, or loaded under, the target's name (or one differing only in case or spacing) in the moment after that check could still receive the voucher, if it has the voucher's ledgers. Bridge may flag afterwards that the loaded companies changed, but cannot always say where the voucher went, and cannot prevent it (accepted residual, #574). A ledger renamed and replaced in that same moment means the post can land in the replacement ledger. Bridge marks the result as needing reconciliation when it sees that the ledger now resolves to a different master; a change that leaves the company's master mark unmoved, or is reverted before that check, is not seen, and a regroup in that moment is not detected (#623). And Bridge has no tool to delete or undo a voucher it has posted, so a wrong post must be corrected by hand in Tally. It records the REMOTEID each post sends, but no delete tool exists yet (#579, #582). And the approval window covers only ComplyEaze Bridge: another Tally connector in the same Claude Desktop that can change entries can do so without it. Turning on Allow voucher posting (Journal, Payment, Receipt, Contra) in the extension settings adds post_import, which posts one saved voucher of those types; every posting still waits for your approval in a separate Bridge dialog. Leave it off unless you accept those risks. Voucher file preparation and bank-statement parsing, which write nothing to Tally, stay available with the setting off. If you installed an earlier version, check the setting: an earlier default may still be saved as on.
• A source build turns writing off by default. Preparing a file needs BRIDGE_AGENT_ENABLE_IMPORT; posting additionally needs BRIDGE_AGENT_ENABLE_WRITES, which grants both.
• A source build also needs BRIDGE_TERMS_ACCEPTED=true. The extension asks for that as its "I accept" setting; without it every tool refuses.

With writing on:

• Prepares vouchers as a local file — Journal, Payment, Receipt and Contra. Bridge writes the file; it does not send it.
• Posts one saved Journal, Payment, Receipt or Contra per approval, and only after you approve that exact voucher in a dialog on your own machine. The assistant cannot approve it. Bridge then reads the voucher back so you can see what actually landed. You can also import a prepared file through Tally yourself; verify_import then reads that back.
• Posting has limits. It creates no masters, posts no sales, purchase, tax or inventory entries, and never alters or deletes a voucher. A company with more than one currency defined is refused.

What it does not do

• The Tally path uploads nothing to ComplyEaze. Bridge reads it over a local connection and hands it to the assistant you are talking to; nothing in the Tally path sends it to a server of ours.
• It will not post anything without a separate, explicit step after the file is prepared.
• It is not a Tally replacement, a reporting suite, or a filing tool.

The desktop app

The extension is built from the same source library as the desktop app. Packages up to 0.3.0 contained an unfinished document-upload feature and an AXAL sign-in, which no tool of the extension reached. That code was removed (#914) and releases from 0.4.0 on do not contain it; the only network client in ComplyEaze Bridge's own code connects to Tally on your own computer. No desktop installer is published. See Security and privacy.

Before you use it with client data

One thing to understand before you use it. When you ask an AI assistant for financial data through Bridge, the assistant's provider sees what it reads, including company, party and ledger names, amounts, dates, narrations, references, GSTINs and, when it reads ledger details, PAN, bank account numbers, IFSC, MSME or Udyam registration numbers, email, phone and address, and, when it builds a voucher file, that file's local path (which can include your computer user name). That is a property of using a hosted assistant, not of Bridge. ComplyEaze Bridge can, before sending, shorten party and ledger names and bank account numbers to their first two and last two characters (four or fewer become “…”), or drop narrations (BRIDGE_AGENT_REDACTION takes one value, not both). Neither hides amounts, company names, PAN, GSTIN, IFSC, MSME or Udyam registration numbers, contact details or references, and a shortened name can still be identified, not least from the GSTIN or PAN sent beside it — figures always go with the answer. Decide this deliberately for client data.

What it costs

ComplyEaze has not set a price for ComplyEaze Bridge and does not sell licences to it; there is no account with us, subscription or licence key. The code of a release you download stays under the licence it was published with (Apache-2.0 for current releases). We have not decided whether to charge for anything in future.

What you pay or provide today:

• TallyPrime: your own licence.
• Claude Desktop: Anthropic's plans. On 1 October 2026 we ran a candidate build of 0.4.0 (not the published file) on Windows with a Claude account that had no paid plan, on one synthetic company; we make no claim about other plans or larger books.
• Your clients' data: what Claude reads goes to Anthropic, under Anthropic's terms for your plan; through ComplyEaze Bridge, ComplyEaze does not receive it (Privacy Policy, sections 4 to 6).
• Your checking: check results in Tally before you rely on them.

Support and updates are not guaranteed (Terms of Use, section 4.4). Our liability is limited as section 14 sets out, including its fallback and exceptions; read it before client work.

Installing it

Before you install, turn on Tally's HTTP gateway. TallyPrime does not listen for ComplyEaze Bridge by default. In Tally's own connectivity / client-server configuration settings, set Tally to act as a server ("acts as Both" in Tally's own words) and note its HTTP gateway port — 9000 by default, but configurable. To check it is actually on, open http://localhost:9000/status (substitute your port) in a browser: a running gateway answers with a short Tally XML response, and a browser that cannot connect means the gateway is still off — unless Tally is running in a Windows virtual machine on a Mac, in which case run this check inside that VM, or only once your local forwarding is working. A Mac browser that cannot connect may mean the forwarding described below is missing rather than that the gateway is off. If instead it hangs without answering, Tally may simply be busy behind another request — wait and retry rather than changing the setting.

The latest published release of the Claude Desktop extension is the one to install. Follow the installation guide to install and configure it. Before you do, know what it is and is not:

• Bridge is still being developed. A release may contain errors, so try it on test data first and keep current backups. It is not yet code-signed or notarized, so your operating system may warn before opening it. Each package has a .sha256 file and a provenance record so you can confirm exactly which bytes and which source commit you downloaded.
• Checked only as far as launching. The release build confirms the package starts and lists its tools. It does not establish that it works against your Tally, or in conversation inside Claude Desktop. What has been run against a real TallyPrime, and on which builds, is listed above; the published 0.5.1 package itself has been installed on one Windows computer with Tally closed, and has not been run by us against a live TallyPrime; an earlier CI build of 0.5.1 was run against TallyPrime 7.1 Silver on one Windows computer (see the 9 October 2026 entry above).
• Windows x64 and Apple Silicon Macs only. Intel Macs are not supported.
• On a Mac, Tally must run on that same Mac, in a local Windows virtual machine or through approved local forwarding. Bridge only talks to Tally on your own computer, so a separate PC or a Tally elsewhere on your network cannot be reached by typing its address.
• It does not update itself. To upgrade, install a newer release from Claude Desktop's Extensions settings and keep the data folder. Release 0.4.2 installed beside an older release instead of replacing it (seen on a Mac; not tried on Windows). A build of 0.5.0 made by our checks (not the published file) replaced 0.4.2 on one Mac and kept its Tally port, Response redaction and posting setting: there, tick the new Terms setting, check the posting setting, then quit and reopen Claude Desktop. Installing over a release older than 0.4.2 was not tried: remove it first. If Settings, Extensions lists two ComplyEaze Bridge entries (as happened when 0.4.2 was installed beside an older release), remove the older entry before you use either, enter your settings in the new one, including Response redaction, which starts at none, tick the new Terms setting, and quit and reopen Claude Desktop.

The Bridge desktop application is a separate program and has no published installer; building it from source is described under Contributor quick start below.

The rest of this file is for people working on Bridge. The repository is self-contained: build and development commands resolve files relative to the clone, not to a developer-specific directory. It holds a Tauri desktop application and the MCPB packaging path for Claude Desktop, with React/TypeScript and Rust components for Tally and local database operations.

First useful result

Install the latest published release of the Claude Desktop extension with the installation guide. For source use, the contributor quick start below builds the desktop app; to run the MCP server from source, follow the source MCP setup.

Before requesting financial data through an MCP client, the client may send the selected Tally result to its AI provider, including company identity, party or open-bill details, amounts, dates, narrations, references, GSTINs and, when it reads ledger details, PAN, bank account numbers, IFSC, MSME or Udyam registration numbers, email, phone and address, and, when it builds a voucher file, that file's local path (which can include your computer user name). Source installations default to BRIDGE_AGENT_REDACTION=none; set it to mask_parties or drop_narration (one value, not both) before launch when that better fits the workflow. These settings shorten party and ledger names and bank account numbers or drop narrations; they do not hide amounts, company names, PAN, GSTIN, IFSC, MSME or Udyam registration numbers, contact details or references. The package installation settings expose the same choices.

For a first result, run tally_status to check that TallyPrime and its Licensed or Education mode are observed, then list the loaded companies. Select a company with exactly one observed INR currency master and request receivables or payables. In Education mode, explicitly supply an as_of date on day 1, 2, or 31; an omitted date defaults to today and may be refused. Bridge rechecks product, mode, dates and currency for the financial read; other or unobserved products/modes, no currency master, non-INR, or multiple currency masters are refused.

The desktop also offers local XML draft preparation through Prepare file. It preserves source observations beside editable proposals and saves a local draft for later review.

For contributors, use the setup and development path below.

Supported development hosts

Bridge is intended to build and run on Windows and macOS 12.4 or later. Run platform checks on a native host for each operating system; a successful build on one operating system does not verify the other.

Shared prerequisites:

• Node.js 24 (>=24.15.0) and Corepack (.node-version pins the CI baseline)
• the Rust toolchain pinned by rust-toolchain.toml
• Perl 5 with Locale::Maketext::Simple for the bundled SQLCipher/OpenSSL build
• LLVM/libclang for SQLCipher binding generation (LIBCLANG_PATH may be required)
• the operating-system dependencies listed in the Tauri prerequisites

On Windows, install the Microsoft C++ build tools, WebView2 components, and a complete Perl distribution such as Strawberry Perl. If another incomplete perl.exe appears first on PATH, set OPENSSL_SRC_PERL to the complete Perl executable. Install LLVM as well; if libclang.dll is not discoverable, set LIBCLANG_PATH to its directory (commonly C:\Program Files\LLVM\bin). On macOS, install Xcode Command Line Tools. Bridge's macOS bundles require macOS 12.4 or later.

Contributor quick start

Run these commands from the repository root in PowerShell, Command Prompt, or a POSIX-compatible shell:

corepack pnpm install --frozen-lockfile
corepack pnpm exec playwright install chromium webkit
corepack pnpm test
corepack pnpm run build
corepack pnpm run cargo:check
corepack pnpm run tauri:dev

pnpm test includes Chromium and WebKit evidence-drawer focus suites; installing the lock-pinned browsers after dependencies is therefore required once for each developer environment. tauri:dev starts the Vite development server and desktop application. It does not require a fixed checkout location. The first Rust build can take several minutes.

For a release build, run corepack pnpm run tauri:build on each target host. CI-produced bundles are unsigned smoke artifacts only. Do not redistribute a desktop installer until the signing, notarization, provenance, and rollback gates in the release runbook are complete.

Platform verification

Before claiming support for a platform, run the following on that platform:

corepack pnpm install --frozen-lockfile
corepack pnpm run build
corepack pnpm run cargo:check
corepack pnpm run tauri:build

Also manually exercise the affected Tally workflows. Vendor integrations may require host-specific software even though repository paths and project commands are portable.

Integration trust boundaries

Bridge restricts native network and file access even if the renderer is compromised:

• Tally connections are loopback-only (localhost, 127.0.0.0/8, or ::1). Remote plaintext Tally hosts are intentionally rejected.
• Showing an export in the file manager accepts only a file ComplyEaze Bridge exported since it started; any other path the renderer sends is refused before anything is launched.

Privacy and safe diagnostics

Do not commit or attach real customer, company, tax, certificate, credential, financial, or document data. Before sharing logs, screenshots, fixtures, or reproduction steps, replace personal and customer data with synthetic values and remove local usernames and absolute paths. See SECURITY.md for private reporting and handling requirements.

Repository map

• src/ - React UI and API bindings
• src-tauri/ - Rust core and Tauri configuration
• docs/ - architecture, roadmap, and operational guidance
• .github/ - issue and pull-request templates plus CI configuration

Governance

• Agent responsibilities
• Contributor guide
• Review checklist
• Security policy
• Rectification guidelines
• Roadmap
• Managed Git guidance
• Source and asset provenance
• Release process

License

Bridge is licensed under the Apache License, Version 2.0. Attribution notices are provided in NOTICE. The ComplyEaze logo and icon files are not licensed under Apache-2.0; see NOTICE and TRADEMARKS.md. The historical v0.1.0 release remains under the MIT license shipped with that tag; current development source is version 0.5.1 under Apache-2.0.