Skip to content
GUIJam
Please leave a star!11 stars

GUIJam for Jira security and privacy

  • No Atlassian passwords or API tokens on your machine. GUIJam keeps one revocable pairing token in ~/.config/guijam/trackers.toml, readable only by you.
  • Jira stores only a hash of that token, in the app's own storage.
  • Your permissions, not the app's. Before every read and write, the app checks the paired person's own Jira permissions on that ticket, including each search result. Posting a result needs Add comments, Create attachments and Edit issues, plus Transition issues to move a ticket.
  • Scoped to your projects. Pairing records, as you, the projects you can browse, and GUIJam only touches those.
  • Revocable. Revoke a device in the GUIJam panel, or run npx guijam jira unpair, which also revokes it in Jira. A person can have up to 10 paired devices.
  • Rate-limited and size-capped. 120 requests a minute per device, 5 MB per request and 3 MB per image. Each change posts at most once.
  • No AI in Jira. The app makes no AI calls. AI runs only in your own CLI, which gets no write tools; GUIJam writes your files itself.
  • Ticket text is untrusted. It reaches your AI CLI marked as untrusted input, and GUIJam validates every edit before writing it.

What leaves your machine#

With Jira paired, GUIJam itself sends something for the first time: the screenshots and diffs of changes you link to a ticket, only to your own Jira site, through the app your admin installed. Turn off Post before/after screenshots on the linked ticket for sensitive screens. See also Security and privacy for GUIJam itself.

Documentation