Skip to main content
← Back to GitLab Issues

Support — GitLab Issues

Last updated: May 2026

Stuck on something? Most things are covered here. If not, email larry@lostendfound.com.

Getting started

Connecting a GitLab instance

  1. Open the app and click Add Instance in the sidebar.
  2. Enter the base URL of your GitLab instance — https://gitlab.com for the SaaS version, or your self-hosted URL (e.g. https://gitlab.acme.internal).
  3. Paste a personal access token with at least the read_api scope. Add api if you want to comment, change labels, or edit issues from inside the app.
  4. Click Connect. The token is saved to the macOS Keychain.

You can connect as many instances as you like and switch between them from the sidebar.

Creating a personal access token

In GitLab: User Settings → Access Tokens. Pick read_api for read-only use or api for full edit access. The app needs no other scopes.

Common questions

Does the app work with self-hosted GitLab?

Yes. Any GitLab Community Edition or Enterprise Edition install reachable from your Mac. If your instance is behind a VPN, make sure the VPN is connected before opening the app.

Does it work with Gitea, Forgejo, or GitHub?

Not yet. The app speaks GitLab's REST and GraphQL APIs specifically.

Where does the app keep my data?

  • Issue caches → ~/Library/Application Support/GitLab Issues/
  • Tokens → macOS Keychain (under the app's bundle identifier)

Nothing leaves your Mac except the requests you'd make in a browser. See the Privacy Policy for details.

My issues aren't showing up

  • Check the instance is reachable: open its URL in Safari.
  • Confirm the token isn't expired (GitLab → User Settings → Access Tokens).
  • Pull-to-refresh on the issue list, or use ⌘R.

How do I switch between assigned / opened / closed views?

The filter bar at the top of the issue list. Common filters have shortcuts: ⌘1 (assigned), ⌘2 (opened by me), ⌘3 (mentioned), ⌘4 (all open).

Can I create a new issue?

Yes — ⌘N from any view. Pick a project, write title and body, set labels/assignee/milestone, then ⌘↩ to submit.

Troubleshooting

"Could not authenticate" error

Your token is wrong, expired, or missing the read_api scope. Regenerate it on GitLab and update the instance settings in the app.

App is slow on a large instance

Use the per-instance settings to scope the projects the app indexes — pin only the projects you actually work in instead of fetching every project you can see.

Keyboard shortcuts cheatsheet

Press ⌘? anywhere in the app for the full list.

Contact

For anything not covered above:

  • Email: larry@lostendfound.com
  • Bug reports / feature requests: include your GitLab version (CE/EE and version number), macOS version, and steps to reproduce. Screenshots help.

Replies typically within two business days.