A desktop Git client for Windows and macOS with an optional AI assistant.
Built with Rust (Tauri 2) and Svelte 5. It drives the git you already have installed, so
hooks, credentials, credential.helper and configuration are exactly the same as in your
terminal, with no layer in between that can drift. On top of that it adds a clear interface
for staging changes line by line, browsing history, managing branches, remotes, tags and
stashes, and drafting commit messages, pull request descriptions or conflict resolutions with
the official AI CLIs you already pay for.
Hard rule: nothing that rewrites your repository happens without your confirmation, and the AI only proposes.
Version 0.1.0-alpha.11 — the current build. Installers are on the releases page:
Ariadna_0.1.0-alpha.11_x64-setup.exe(Windows),Ariadna_0.1.0-alpha.11_universal.dmg(macOS), a portable ZIP andSHA256SUMS.txt. They are unsigned alphas: read Installation first.
What has actually been tested, against what, and where. If something has not been run against the real service, it says "not verified" here:
| Area | Status | Evidence |
|---|---|---|
| Git engine: status, staging per hunk and per line, commit, amend, cursor-based log, branches, merge, rebase, cherry-pick, conflicts, remotes, stash, tags, clone with PAT | Verified against real git |
Rust workspace test suite; CI runs it on Linux, macOS and Windows |
| User interface | Verified with Vitest and axe in jsdom; contrast measured | Vitest suite in CI; docs/contraste.md |
| End-to-end | Verified on Linux with tauri-driver: real UI flows (16) plus visual regression with 16 baselines |
e2e/README.md |
| GitHub pull requests | Verified against the real API (2026-11-11) on a disposable private repo: 72 checks, 5 limitations of GitHub itself, 0 failures | docs/pull-requests.md |
| Azure DevOps pull requests | NOT VERIFIED: no account or PAT available; tested only against a simulated server (wiremock) |
docs/pull-requests.md |
| AI with Claude | Verified with claude 2.1.319: flags, claude auth status --json, CLAUDE_CONFIG_DIR |
docs/checklist-humo-ia.md |
| AI with GitHub Copilot | Verified with GitHub Copilot CLI 1.0.112 (2026-11-14): flags, prompt over stdin, JSONL, tools denied, detection |
docs/ia-copilot.md |
| AI with Codex | Verified with codex-cli 0.169.0 (2026-11-17): exec flags, prompt over stdin, JSONL, codex login status, CODEX_HOME isolation |
docs/ia-codex.md |
| Installers | They build (NSIS x64, universal .dmg, portable ZIP) but are unsigned |
Installing without a signature (Spanish) |
- One tab per repository, with the session restored on start, deduplication by real path (linked worktrees share a tab), hibernation of hidden tabs and tabs you can resize by dragging their right edge (112–420 px, remembered between sessions).
- Changes: diff per hunk and per single line (checkboxes, click, Shift+click and
keyboard), stage/unstage by block or by line, and a commit bar with
Ctrl/⌘+Enter. - Diff view: one column (the classic view) or two columns — old on the left, new on the right — in the changes panel and when reading a commit or a stash. Unchanged lines appear on both sides and deleted/added blocks are aligned. The choice is remembered.
- Stash: save (with or without untracked files), list, view the diff, apply, pop and drop with confirmation; conflicts on apply land in the Conflicts panel.
- History: by default the full graph — every local and remote branch plus tags, in
topological order, so you can see where things fork and merge at a glance — with two buttons
(Full graph / Current branch) to narrow it down on huge repos. Paginated by cursor
in Current branch (constant cost even on 100,000-commit repos), with local filter, global
search (message, author, hash) and per-commit diff. Right-click a
commit (or
Shift+F10) for Create tag…, copy SHA/subject and Generate change report (.md): the AI drafts a Markdown report for that commit — what changes functionally, risks and sensitive areas, possible bugs, and what to test — shown in a viewer and saved toinformes-cambios/<sha>-informe.mdonly when you press Save (never overwritten). - Branches in a persistent rail on the left, always visible: a nested tree by every
segment (
origin/release/1.0/hotfixcollapses underorigin/→release/→1.0/, with a count per folder), switch, create, rename, delete (second confirmation when unmerged), merge, and upstream with ahead/behind counters. - Context menu per branch (right click, or the Menu key /
Shift+F10): switch, create from it, merge into the current one, rebase, fetch, push, pull the current branch, update this branch from its remote without switching to it, rename, delete locally or on the remote, create a tag, copy name/SHA, diff against the current branch, compare with any other branch, open on the web and create a pull request. Actions that do not apply stay visible but disabled, with the reason in the tooltip. Full table:docs/menu-ramas.md(Spanish). - Remotes: list with the provider recognised, add, rename, remove, fetch, pull and push the current branch, plus "Open in browser" / "Create pull request".
- Conflicts in a three-way panel (ours/base/theirs) with an editable result; mark as resolved, continue or abort merge, rebase and cherry-pick. Optional "Resolve with AI" proposes a full file without conflict markers, which you review before using.
- Tags: list (lightweight and annotated), create on HEAD, on a commit or from the branch context menu, delete locally and publish/delete on the remote.
- Clone from a URL (GitHub, Azure DevOps, GitLab, Bitbucket or generic) with an
optional PAT, a GitHub CLI (
gh) or GitLab CLI (glab) session you already have, or an OAuth device flow (ready but off until aclient_idis configured). Secrets are used once and forgotten, never stored (see Security). - Pull requests for GitHub and Azure DevOps: list, detail with safe Markdown, create (with
the title and description drafted by the AI if you want), check out the branch, review
with inline comments, vote and complete/abandon. When a PR has conflicts, "Resolve
conflicts with AI…" reads them with
git merge-tree, offers up to three resolutions per file (all reviewed before choosing) and, with a native confirmation, leaves the merge prepared locally with the resolved files staged — the commit and the push stay yours. - Settings (General, Git, AI, Accounts), light/dark theme with a two-state toggle in the
title bar (
systemlives in Settings and in the palette), command palette, native menu and shortcuts. Interface available in Spanish and English.
Not in this version: init, submodules, LFS, worktrees beyond detecting them, interactive
rebase, a visual cherry-pick, a standalone commit graph view, auto-updater and app stores.
Requirements: Windows 10 (22H2) or 11, x64 (ARM64 best effort) · macOS 15 or later ·
git 2.39 or later on PATH. On Windows the installer checks for WebView2 and installs
it if missing; no administrator rights needed.
The 0.1.0 alphas are unsigned, so the system will warn or block depending on the machine's configuration. Step-by-step guide, what changes once there is a signature and what we do not promise: docs/instalacion-sin-firma.md (Spanish).
Summary:
- Windows — SmartScreen shows "Windows protected your PC": More info → Run anyway. If the machine has Smart App Control enabled, the installer cannot run (not even with "Run anyway"); the only real fixes are a code signature or turning Smart App Control off, which is the user's or their company's decision, not Ariadna's. There is a portable ZIP and a guide to the options that do work (Windows Sandbox, another machine): docs/windows-sin-instalar.md (Spanish).
- macOS — Gatekeeper will say it cannot verify the app. On macOS 15 right-click → Open
is no longer enough: go to System Settings → Privacy & Security → Open Anyway (or
xattr -dr com.apple.quarantine /Applications/Ariadna.app). Company-managed Macs may block it by policy.
Ariadna uses no API keys and no third-party proxies: it launches the official CLIs
with the session you already have on the machine, and the prompt travels over stdin
(never through argv).
| Provider | CLI | Status |
|---|---|---|
| Claude (Pro/Max/Ultra or Team/Enterprise) | claude |
Verified with claude 2.1.319 |
| GitHub Copilot (any plan) | copilot |
Verified with GitHub Copilot CLI 1.0.112 (2026-11-14) |
| Codex (ChatGPT Free/Go/Plus/Pro/Business/Enterprise) | codex |
Verified with codex-cli 0.169.0 (2026-11-17) |
-
Model per provider: Settings › AI lets you pick the model for each provider. None of the three CLIs publishes a model list (their
--helponly documents--model/-m), so the drop-down holds a short list of aliases each CLI documents itself (sonnet,opus,haiku,fablefor Claude;autofor Copilot; none for Codex) plus Other…, which opens a text field with basic validation (letters, digits and- _ . : /, 64 characters max, otherwiseINVALID_MODEL). The value is saved in the app settings and used on every call:--modelfor Claude and Copilot,-mfor Codex. Empty means "the CLI's own default". -
Cloning a repository that needs credentials never asks for a token you already have: if
gh(GitHub) orglab(GitLab) are installed and signed in, Ariadna offers that session and reads nothing else; the token stays in memory in Rust, never crosses the IPC and is never stored. A PAT is only needed when there is no session (or for Azure DevOps and Bitbucket, which have no supported CLI here). -
Auto mode: Claude → Codex → Copilot, skipping only the ones not installed and only among the providers you have consented to.
-
Personal and Company profiles: each repo is bound to a profile; the profile decides which providers are allowed and, when the CLI supports it, with which configuration directory (
CLAUDE_CONFIG_DIR,CODEX_HOME). Claude and Codex isolate the session — verified with the real CLIs — so the Company profile can have its own login. Copilot shares the login between profiles (its token lives in the system keychain and there is no verified way to isolate it), so the AI settings show a permanent warning while the active profile is Company. -
Consent the first time per profile and provider, with a preview of what is sent;
.env*,*.pem,id_*,*.key,*.pfxare excluded and secrets are redacted. -
The AI only proposes: the result is a proposal you can accept, edit or discard; it never writes to the worktree, the index or the refs.
Before using AI with company code, check your account terms and internal rules: individual plans (Claude Pro, ChatGPT Plus, Copilot Pro) may use your inputs for training unless you opt out, while organisation plans exclude it by contract. Summary with dates and links: docs/terminos-ia.md (Spanish).
- Tokens: Ariadna does not store, cache or log PATs or tokens. To clone, the secret is
handed to
gitonce through a temporaryGIT_ASKPASS, used in memory (zeroize) and destroyed; for pull requests it is requested fromgit credential fillon every call. It never appears inargv, a URL,Debugoutput or an error message. - Processes:
gitand the CLIs are spawned without a shell, with an absolute path, an allow-listed environment (GIT_TERMINAL_PROMPT=0,GCM_INTERACTIVE=never, no*_API_KEY),fsmonitorand external hooks disabled for reads, and a process tree that is terminated on close (Job Object on Windows, process group on macOS). - Hostile repositories: validated paths (
../, UNC,\\?\, reserved names,.gitwith NTFS variants,-rf, magic pathspecs), refs checked withgit check-ref-formatand patches built fromgit diffbytes. - Network: the only traffic of our own is the repository provider's API for pull requests,
only on your action or with the panel open; TLS always verified, no telemetry. It honours
the proxy (
HTTPS_PROXY/HTTP_PROXY/NO_PROXY) and the system certificates (SSL_CERT_FILE,SSL_CERT_DIR), including those a company installs, implemented and tested incrates/ariadna-hosting/src/net.rs. - Public repo:
gitleaksscans every commit (.githooks/pre-commit, installable withsh scripts/install-git-hooks.sh) and CI runs it over the whole history.
Svelte 5 UI ──typed IPC──▶ Tauri commands ──▶ AppCore ──▶ RepositorySession
│ │
│ ▼
│ GitEngine ──▶ ProcessRunner ──▶ git
├──▶ AiService ──▶ AiProvider ──▶ claude | codex | copilot
└──▶ ariadna-hosting ──▶ PullRequestProvider ──▶ GitHub / Azure DevOps REST
State lives in Rust; the interface is a view with no git or AI logic. The contract between
both sides is docs/ipc.md. Each piece of the workspace:
| Crate | Contents |
|---|---|
crates/ariadna-process |
Process launcher: no shell, cooperative cancellation, timeout, byte cap, Job Object / process group |
crates/ariadna-git |
Git engine and parsers (status --porcelain=v2 -z, diff, log, branches, remotes, diff3 conflicts); per-repo serialised session, stash, line-level patches (partial), clone, credentials and askpass |
crates/ariadna-ai |
AI providers via the official CLI, allow-listed environment, prompts, secret redaction, profiles and queue |
crates/ariadna-hosting |
Provider recognition (RemoteInfo), HTTP client (reqwest + rustls) with system proxy and CA (net.rs), GitHub and Azure DevOps pull requests |
src-tauri/ |
Tauri application: windowless testable core, IPC commands, file watcher, menu, settings and session.json |
ui/ |
Svelte 5 + TypeScript interface (bilingual Spanish/English) |
Requirements: stable Rust (rust-toolchain.toml), Node 22 and the Tauri 2 system
dependencies.
# Rust: format, lint and tests
cargo fmt --all --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace --no-fail-fast
# Interface
cd ui
npm ci
npm run check && npm test && npm run build
npm run dev # Vite on 127.0.0.1:5173 (simulated backend when opened in a browser)On Windows it is safer to build from WSL (cargo over /mnt/c): some machines block
freshly compiled build scripts with Smart App Control and cargo build fails with "An
Application Control policy has blocked this file" (error 4551). The dev profile already
builds those scripts with light optimisation to reduce it, but WSL is the reliable path.
End-to-end and visual tests (Tauri driver, Linux):
cd e2e && npm ci
xvfb-run -a -s "-screen 0 1440x900x24" npm test # UI flows against the packaged app
xvfb-run -a -s "-screen 0 1440x900x24" npm run visual # visual regression (16 baselines)Performance tests (#[ignore], synthetic repos with 50,000 files and 100,000 commits):
cargo test -p ariadna-git --test perf -- --ignored --nocaptureDetailed documents are currently written in Spanish.
| Document | Contents |
|---|---|
docs/ipc.md |
Contract between Rust and the interface: commands, events and error codes |
docs/diseno.md |
Interface design: branch rail, centre views, detail panel and the reasons behind them |
docs/menu-ramas.md |
Branch rail context menu: every action, shortcuts, what each one requires |
docs/pull-requests.md |
What is verified about pull requests (GitHub and Azure DevOps) and what is not |
docs/rendimiento.md |
Measured performance on 50,000-file and 100,000-commit repositories |
docs/contraste.md |
Contrast measurements against WCAG 2.2 AA |
docs/terminos-ia.md |
Anthropic, OpenAI and GitHub Copilot terms: individual vs organisation |
docs/checklist-humo-ia.md |
Manual smoke checklist with the real AI CLIs |
docs/ia-copilot.md |
GitHub Copilot CLI: flags, stdin, tools denied, what is still unverified |
docs/ia-codex.md |
Codex CLI: flags, JSONL, CODEX_HOME isolation and the WSL launcher |
docs/oauth-cli.md |
OAuth device flow for cloning: GitHub/GitLab app registration and scopes |
docs/instalacion-sin-firma.md |
Opening unsigned alphas on Windows (SmartScreen, Smart App Control) and macOS (Gatekeeper) |
docs/windows-sin-instalar.md |
Testing on Windows without installing (Windows Sandbox, portable ZIP) |
e2e/README.md |
End-to-end suite and visual regression: how to run it and how to update baselines |
Free code signing provided by SignPath.io, certificate by SignPath Foundation.
- Signed artifacts: the Windows NSIS installer and its executable, built only in GitHub Actions from this repository.
- Committers and reviewers: @jamartif.
- Signing approvers: @jamartif; every release is approved by hand.
- Privacy: This program will not transfer any information to other networked systems unless specifically requested by the user or the person installing or operating it. No telemetry; the network is used only when you ask for it (git operations against your remotes and, if you enable AI, the official CLI you choose).
- macOS is not covered by this policy: the
.dmgis ad-hoc signed until there is a Developer ID certificate.
Full details in docs/firma-de-codigo.md (Spanish).
MIT. Use it, modify it and redistribute it; if you publish a modified version, keep the copyright notice.