Follow the thread.

_{English · 한국어}

A local SQLite file of your Jira — so "which epic is stuck?" is one query, not an unaskable one.

gadak mirrors Jira and Confluence into one local SQLite file — issues, comments, history, wiki pages — indexed together and searchable locally. This window is where that work lives on your machine: triage it in the desktop app or a browser tab, or let a coding agent ask in plain SQL and point the same window at the answer. One binary, one app, no gadak account.

The mirror is a cache you can throw away. On a connected workspace, if this project stops tomorrow, you delete a directory and have lost nothing: Jira stays the source of truth.

▶  Open the live demo  —  534 issues, in your browser, right now.
Public backlog  —  gadak's own roadmap, browsed in gadak. The GDK-nnn keys in commit messages resolve here. To file something, open a GitHub issue — the maintainer mirrors it into the backlog.

gadak sql "select epic_key, count(*) from issues_full where resolved_at is null
           and epic_key <> '' group by epic_key order by 2 desc"

That last query is the point: JQL has no GROUP BY. "Which epic is actually stuck?" is not a hard question — it is an unaskable one, until the data is a file. docs/RECIPES.md has the rest.

Run that query now, nothing installed: Datasette Lite loads the demo snapshot in this tab and the SQL runs client-side.

Measured against a live Cloud site (2,853 issues; medians, CLI startup included — method and the losing rows):

Question	REST API	gadak
Simple filter, 100 issues	706 ms	17 ms	42×
One issue with its full history	1,055 ms	54 ms	20×
Open issues per epic (GROUP BY)	3,924 ms · 7 API pages	24 ms · one query	162×
Anything over the change history	≈ 20 min (crawl every changelog)	one query	—

And the other side: the first full sync measured 26.4 s for 534 issues and 7.2 min for 2,865 (method and the losing rows), every watch tick costs ~6.7 s on a quiet site, and the mirror trails Jira by one sync interval.

▶ 90-second tour of the paper list (GIF, 7 MB)

_{Generated from e2e/demo/web-demo.spec.ts against the demo snapshot.}

macOS: download Gadak-<version>-arm64.dmg and open the window.

Windows (from 0.16): download Gadak-<version>-windows-x64.zip (or windows-arm64), unzip, run gadak-desktop.exe. The build is unsigned — if Windows blocks it, use the CLI path below. Details: docs/INSTALL.md.

Or, from a terminal:

brew install midagedev/tap/gadak        # the macOS app — the bundled CLI lands on PATH too
# CLI only (macOS + Linux via brew; Windows from the release zip):
brew install midagedev/tap/gadak-cli
gadak init && gadak sync    # Jira (and Confluence) -> ~/.gadak/gadak.db
gadak serve                # http://gadak.localhost:7777

Status: 0.16, still 0.x. Sync, read API, write-through, desktop, web, CLI, and MCP are verified against a live site. Honest inventory: docs/STATE_OF_PLAY.md.

Why

Jira search is a network round trip, and the wiki is a second search. An agent asked "what did we already fix, and what did we decide?" pages two REST APIs. Same cause: the data is not a file. docs/CONCEPT.md · docs/PAIN_POINTS.md.

⌘K is the one index — titles, bodies, comments, issues and pages. The chips on the list do not apply. That is why a comment-only word still finds the row.

_{Generated from e2e/demo/search-demo.spec.ts against the demo snapshot.}

Two surfaces, one store

	For	Looks like
App + Web UI	all-day triage	desktop app (no port) or gadak serve. j/k walk, x selects, s/a/l/c change status, assignee, labels, or comment from the list.
CLI + SQL	agents, scripts	gadak issue, gadak search (FTS, --jql, or a Jira URL), gadak sql, plus the file

Writes go through to Jira, then the mirror refreshes. App and web: comment, transition, assign, labels, priority, title. CLI: create (single or --batch), attach, edit, comment, transition, assign, and page create / page edit / page comment for the wiki (pages, titles, bodies and comments all through the origin). Hierarchy, item_refs, attachments: docs/CONCEPT.md. The window keeps one paper metaphor across four palettes — light, a neutral-cool dark, blue-black ink, and warm ember. The theme follows the system unless you pick one, and it belongs to the workspace, not the browser: gadak config set appearance.theme ink.

And two surfaces is not a closed list. Reading the mirror is one binary call (gadak search --json, ~20 ms), and opening anything in the app is one URL (gadak://view?issue=… — the scheme), so whatever can do those two things becomes a surface. A launcher, say:

_{Each keystroke is one gadak search --json; Enter is the deep link. A saved view travels the same way — gadak views open prints its link.}

That launcher exists: a Raycast extension that searches issues and wiki documents as you type, submitted to the Raycast Store. Until the review lands, one command installs it from the binary you already have (embedded, no checkout):

gadak raycast install

The macOS app has the same install as a button — Settings → Integrations lists Raycast, the agent skill and MCP, shows what is already installed, and runs the exact command it prints. Building on the extension itself: contrib/raycast/. And with no extension at all, a Raycast Quicklink pointed at gadak://view?issue={argument} covers the open-by-key half.

What's covered

Connected talks to Atlassian Cloud. Standalone (from 0.16) is a workspace with no Atlassian account — a minimal Jira origin that travels with the app. The mirror is a cache either way; every write goes through the origin. On standalone the durable file is the origin's persist file — issuetap.yaml in the profile's origin folder; back up that one file.

	Connected (Atlassian Cloud)	Standalone (from 0.16)
Issue read and search (FTS, JQL, SQL)	✅¹	✅¹
Create, comment, transition, assignee, labels, priority	✅	✅
Due date, description, custom-field edits (from 0.16)	✅²	✅²
Hierarchy	✅³	✅³
Wiki documents	✅⁴	✅⁵
Attachments	✅	✅
History / time in status	✅⁶	✅⁶
Agent surfaces (skill, MCP, SQL)	✅	✅
Boards and sprints	—	—
Dashboards	—	—
Jira notifications	—⁷	—⁷

1. SQL and FTS are local. --jql / a Jira URL maps a documented subset onto the in-memory filter; clauses gadak cannot express are listed, never dropped. Sprint, WAS, cross-field OR, and custom fields are among the refusals (decision 0007).
2. Dedicated endpoints for due date and description. Custom fields: kinds text, number, date, option, user, multi_option / version_array, gated by the issue's editmeta and the configured field allowlist. Cascading selects and textarea custom fields have no editor.
3. Epic grouping (epic_key, nearest hierarchy-level-1 ancestor) is first-class. Setting a parent is CLI create --parent / edit --parent only — there is no REST PUT {key}/parent. Sub-task create-meta flags are not surfaced, so create cannot tell that a type requires a parent.
4. Confluence Cloud is mirrored; page create, edit (title/body) and page comments write through it — gadak page create|edit|comment, POST pages/, PUT pages/{id}/edit, POST pages/{id}/comment.
5. Pages sync from the in-process origin. gadak page create|edit|comment and the REST verbs work here too; the UI has a page comment composer but no page editor yet.
6. Changelog is mirrored. Time in status is computed from status_changed_at, not stored as a column.
7. Jira's notification inbox, rules, and email are not mirrored. gadak has its own watch-feed OS alerts on macOS and Linux.

Linear. A Linear workspace mirrors and writes through the same verbs: add a "linear" block (apiKey, optional teamIds) to the profile's config.json and run gadak sync --source linear. Writes route by the mirror's source for the key — comment, transition (the team's workflow states, id-keyed), summary/priority/due-date edits, assign/unassign, and file attachments all pass through Linear's API and refresh the mirror row. Not yet: label edits, clearing a due date, and state history (status_changed_at stays NULL) each refuse honestly rather than half-applying; inline comment media attaches the file and drops only the body embed. Field mapping: internal/linear/MAPPING.md.

For agents

This is half the reason gadak exists. Reference: AGENTS.md. One paste per host: docs/AGENT_SETUP.md.

gadak skill install         # schema + query patterns, no extra process
# or, for hosts without a shell (Claude Desktop):
gadak mcp install claude    # pins this binary and profile into the registration

Both installs (and the Raycast one) are also buttons in the macOS app, with install state shown honestly: Settings → Integrations.

Setup is not a screen an agent has to click, either. Every field the settings dialog edits is a CLI verb over the same validation:

gadak config list                          # every editable path + its value
gadak config set appearance.theme ink      # per workspace, applied live

SQL answers; the window presents. And if you already have the JQL, skip the SQL — the clauses land as chips:

gadak sql --no-header "select key from issues_full where status_category = 'inprogress'
                       order by status_changed_at asc limit 5" | gadak views open --keys -
gadak views open --jql 'project = NMA AND priority = High AND resolution is EMPTY'

_{gadak views open writes a one-shot hash; the running app or serve tab applies it. Generated from e2e/demo/agent-demo.spec.ts.}

For hosts without a shell (Claude Desktop), the same mirror is an MCP server. Ask the thing Jira cannot answer at all, because the wiki is a second search: "what do we know about X?" One index holds both, so the answer can put a ticket and the design doc that drove it in the same sentence.

_{Five tools; no writes to the mirror or to Jira. A host with a shell can use gadak sql instead. Setup: docs/MCP.md.}

gadak views open is the "open in gadak" verb; gadak open KEY leaves for Jira. The list box takes the same JQL paste as gadak search --jql; clauses gadak cannot express are listed, never dropped. What JQL still cannot ask stays in gadak sql and docs/RECIPES.md. gadak sql opens the file mode=ro; MCP's gadak_query rejects anything that is not a SELECT. gadak api is the pass-through for endpoints the mirror does not model — read-only unless --write, never on MCP.

An agent that reads your mirror sends what it reads to whatever model it talks to. gadak itself sends nothing (SECURITY.md). Scope the mirror to what the agent should see.

Install

Atlassian Cloud, or (from 0.16) a standalone workspace with no Atlassian account. A connected site needs one API token — it covers Jira and Confluence on the same site.

1. The desktop app.

macOS: download Gadak-<version>-arm64.dmg from the latest release, drag to Applications. Signed and notarized. First launch walks through site, email, token, and projects. The CLI is inside the bundle; macOS does not put an app on your PATH:

/Applications/Gadak.app/Contents/Resources/bin/gadak install-cli

Windows (from 0.16): download Gadak-<version>-windows-x64.zip (or windows-arm64) from the same release, unzip, run gadak-desktop.exe. Unsigned (signing is GDK-211). If Windows shows Windows protected your PC or Smart App Control blocked an app that may be unsafe, that is not a virus finding — use the CLI path below. Do not turn Smart App Control off. docs/INSTALL.md.

2. The CLI, on Linux, Windows, or for the same UI in a browser tab.

No Atlassian account:

brew install midagedev/tap/gadak-cli     # macOS + Linux
gadak init --standalone
gadak create "the thing I just noticed"
gadak serve      # http://gadak.localhost:7777

Pair another machine. Home gadak serve is the origin. Mint an offer, paste it on the remote:

gadak pairing mint --label laptop                 # home: stdout is one offer line
gadak --profile laptop init --pairing-code-stdin  # remote: paste the offer
gadak --profile laptop status                     # confirm: paired with "laptop"
gadak pairing list                                # home: token table; remote: one status line
gadak pairing revoke laptop                       # home only

_home is this machine's routing token, not a device (revoke refuses it; mint --label _home rotates). Same verbs on the remote; a pairing: error is the whole message. The gate is in SECURITY.md.

Already have Jira:

brew install midagedev/tap/gadak-cli     # macOS + Linux
gadak init && gadak sync
gadak serve      # http://gadak.localhost:7777

Windows without Homebrew: from the latest release, download gadak_<version>_windows_amd64.zip (or windows_arm64) and checksums.txt. Unzip, put gadak.exe on PATH, then gadak init && gadak sync && gadak serve. This is the reliable Windows route in 0.16 if the unsigned desktop exe is blocked.

A Scoop manifest lives in contrib/scoop. The bucket is not published and scoop install has not been run on a Windows machine (docs/INSTALL.md).

Linux without Homebrew: from the latest release, download gadak_<version>_linux_amd64.tar.gz (or linux_arm64) and checksums.txt. One archive is the whole install — the web UI is inside the binary.

sha256sum --ignore-missing -c checksums.txt
tar -xzf gadak_<version>_linux_amd64.tar.gz
# put `gadak` on PATH
gadak serve             # http://gadak.localhost:7777
gadak install-service   # optional: systemd --user, survives reboot

Arch Linux: a checked PKGBUILD lives in contrib/aur/gadak-bin — makepkg -si there. Not in the AUR yet; upstream registration is closed (docs/INSTALL.md).

On Omarchy, the bar can answer the one question no cloud plugin can — what changed in your mirror. A shell-plugin widget in contrib/omarchy shows open·stuck straight from the local mirror (no token, no network) and click-opens the app. Run once on a real guest.

▶ The widget on a real Omarchy guest (PNG) — the bar badge is gadak sql's own numbers

_{Captured on the Arch + Hyprland verification guest (contrib/omarchy/README.md).}

Install script, release archive, source, Docker, wiki mirroring, profiles, upgrades: docs/INSTALL.md.

The rest

Making it yours. Two axes, no forking: docs/EXTENDING.md. Config: docs/CONFIGURATION.md. Enrichments: docs/PLUGINS.md.

How it works. One binary, one SQLite file; incremental sync plus a reconcile pass. docs/ARCHITECTURE.md. Why not an extension or Forge app: docs/decisions/0003-local-process.md.

Good fit / bad fit. Daily search latency, an agent over tracker and wiki, offline reads — yes. Boards, admin, wiki authoring, or a minute of staleness — stay in Jira. docs/CONCEPT.md.

How it compares. jira-cli talks to the live API per command. Linear is a different tracker. Rovo MCP searches both sources too, but it is hosted: no aggregate, no offline, and every call spends tokens. docs/FAQ.md.

More sources later. Confluence proved the spine is neutral. Next source, ranked by demand: docs/ROADMAP.md.

Documentation

• docs/INSTALL.md · docs/DESKTOP.md — install, first run, the desktop app
• AGENTS.md · docs/MCP.md · docs/AGENT_SETUP.md — SQL, CLI, REST, MCP, one paste per host
• docs/RECIPES.md — questions JQL cannot ask, as SQL
• SECURITY.md · docs/FAQ.md · MAINTENANCE.md — threat model, site load, who maintains this
• docs/EXTENDING.md · docs/PLUGINS.md — fitting gadak to your team
• docs/STATE_OF_PLAY.md · docs/CONCEPT.md · docs/PAIN_POINTS.md
• docs/ARCHITECTURE.md · docs/UX_PRINCIPLES.md
• docs/decisions/ · specs/000-product/ — why, and the contracts

Who makes this

One person, currently. Weigh that — and the other side: the mirror is a disposable cache of your own Jira, the 0.x contract is the three promises in data-model.md (issues_full and the RECIPES queries, gadak sql stdout, and gadak views open --keys -), the license is Apache-2.0, and the file is plain SQLite. Hard questions: docs/FAQ.md. What you do not have to take on trust, each with the command that checks it: PROMISES.md.

Contributing and feedback

CONTRIBUTING.md — and docs/GOOD_FIRST_ISSUES.md to start. Bug reports need your Jira deployment type (Cloud), the gadak commit, and the command you ran. Never paste real issue data, tokens, or site URLs into a public issue.

Using gadak with an agent and hitting friction? Open an issue with the question you asked and what the agent did.

License

Apache-2.0. See LICENSE and NOTICE.