Developer tools / Xynapse

Xynapse IDE

Build with AI.
Stay in control.

Your editor, terminal, Git and AI assistant in one workspace. From a question about code to an inspectable plan for changing it.

Try Xynapse
  • Windows x64
  • Open source
  • Your models and credentials

01 / Workflow

Context. Plan. Changes.

Assistance at every development step, with explicit access modes.

01

Project context

Attach files, selected code, diffs, diagnostics and terminal output. Work with the context you choose.

02

A mode for the task

Chat explains code, Plan inspects without edits, Agent implements changes. Full is for explicitly authorized system tasks.

03

Several perspectives

BVC collects independent proposals, adds critique when needed and saves the final plan.

04

Provider choice

Configure chat, editing and autocomplete models. YandexGPT and GigaChat adapters are available; your provider bills model usage.

A demo, step by step

One small defect. The complete engineering loop.

  1. Open a project

    Choose a task and attach the relevant files.

  2. Review a plan

    Run BVC, inspect proposals and agree on the scope.

  3. Make changes

    Give the plan to the agent and inspect the diff.

  4. Verify the result

    Run tests and review the changes before accepting them.

02 / Research

Results you can inspect.

Author manuscripts with methods and limitations. No claim of journal acceptance or publication.

60SWE-bench Verified tasks
11open Python repositories
21.3%fewer calls than a full council

A budget for multi-role analysis

In the research protocol, 32 tasks used the short 6-call route and 28 used the extended 10-call route: 472 calls instead of 600.

Full council
600
Adaptive BVC
472

Quality is a separate measure

Resolved tasks in the same sample: direct 4/60, single plan 7/60, BVC 5/60, full council 6/60. Neither superiority nor non-inferiority of BVC quality was established. These are research-protocol results, not a promise about the current release.

Experiment methodology ↗
PDF / 01

Adaptive BVC budget

A rule for choosing a short or full route. Calls, tokens and estimated cost.

Read PDF
PDF / 02

Reproducible BVC evaluation

Protocol, paired method comparisons and official patch evaluation.

Read PDF
PDF / 03

BVC before the first edit

Upfront planning, conversational prompts and repeatability.

Read PDF
PDF / 04

Controlled network egress

A Xynapse IDE cold-start study: 19 source checks and three independent 60-second runs.

Read PDF

No TCP/UDP events attributed to the tested Xynapse.exe were observed in the cold-start study. This applies to one build and scenario, not complete network isolation. Model calls, DNS, Git and differently named processes are outside the result.

03 / Transparent arithmetic

Explore the call budget.

Scale the observed route mix to a different batch size. A new set of tasks can produce a different result.

Full council600
BVC calls472
Calls saved128

Observed research mix: 28/60 tasks with critique. Formula: N × (6 + 4p); full council: N × 10. This model does not estimate patch quality, time or current API prices.

Estimated cost in the same sample: RUB 1,838.46 vs RUB 2,402.61, using a frozen research tariff. These are not provider invoices or current prices.

Download calculation data ↓

04 / Try it

Your project. Your next step.

Use the complete editor or add the assistant to a compatible VS Code installation. Configure your provider before the first request.

IDE 1.108.0 bundles Assistant 1.0.0. The standalone VSIX updates Assistant to 1.0.1 and BVC to 0.1.1. Windows executables are currently unsigned.

Keep the project close

The QR opens this project page. Download it for a slide or print.

Download QR · PNG ↓Print QR · SVG ↓
QR: https://clickn.dev/xynapse/

Dzhabrail Khalilov

Xynapse author and independent researcher. Open to product discussions, integrations and scoped pilots.

GitHub ↗

Let’s
talk.

A question, an idea,
or something that could work better?

There’s a person
behind these projects.

Send me a message. Bug reports, suggestions, and ideas for working together are all welcome.

github.com/jabrailkhalil
Your message goes straight to my private Telegram inbox.

I’ll reply using the
contact you leave here.