Your GitLab repos and the reasoning behind them.

Install the Oynix CLI

Everything Oynix does runs from one small command-line tool on your own machine — there's nothing to deploy or host. Open your terminal (Terminal on Mac, PowerShell on Windows) and paste this in to install it:

• Don't have a terminal open? On Mac press ⌘+Space, type "Terminal", hit Enter.
• Paste the line, press Enter, and wait for it to finish — that's it.
• Check it installed: run oynix --version (it should print a version number).

Sign in

Tell Oynix who you are. This opens your browser to sign in with GitHub and links this computer to your workspace — it's how your edits, decisions and presence get attributed to you.

• Run the command; your browser opens automatically.
• Approve the sign-in with GitHub, then return to the terminal.
• If your team uses a workspace key, paste it when asked (a teammate with the master key issues it).

Create a token

GitLab → Preferences → Access Tokens. For self-hosted, note your GitLab host URL too.

Connect GitLab

Run the command. Paste your token and the repo (owner/name); add your host URL if self-hosted; pick code, PRs, or both.

Sync anytime

Oynix indexes the repo and links merge requests to the code they changed.

Check it worked

List your connectors to confirm GitLab shows up and is syncing. Once it's synced, ask the graph a question that should now have an answer from GitLab.

• You should see GitLab listed as "connected".
• Try it: oynix ask "what did we decide about …?" — answers can now draw on GitLab.