The coding agent you know from GitHub.
Built for GitLab.
Copilot's coding agent, Claude Code in GitHub Actions and Codex's cloud tasks are built around GitHub repositories. If your code lives on GitLab, Nightsquire is that workflow: assign an issue, and get back a merge request that has been tested, scanned and reviewed.
If you have used one on GitHub, you already know how this works.
The workflow carries over. What changes is where it lives: in your GitLab, next to your pipeline, your scanners and your reviewers.
| What you know from GitHub | Nightsquire on GitLab | |
|---|---|---|
| Start a task | Assign the issue to the agent, or mention it | Assign the issue to @nightsquire-bot, or mention it in a comment |
| Where the work runs | GitHub Actions runners, or the vendor's cloud | Executors that serve only your organisation: managed in the EU, or a Linux VM of your own |
| What comes back | A pull request | A merge request linked to the issue: ready, or a draft that says what is still open |
| Asking for changes | Comment on the pull request | Comment on the merge request. It makes the change, runs every check again and answers in the thread |
| Project instructions | AGENTS.md, CLAUDE.md or Copilot instructions | The project's CLAUDE.md, plus notes about your GitLab that every run reads |
| A plan instead of code | Ask in a chat or a comment | Label the issue nightsquire::plan and get a plan in the issue, with follow-up issues when you ask for them |
| Merging | Your branch protection | Your team. The bot never merges. |
GitHub's agents as they were documented in October 2026. GitHub now calls Copilot's coding agent its cloud agent.
You get a merge request, not a first draft.
Every merge request has been through the checks you would run yourself, and says plainly what ran, what passed and what is left.
Your tests, before anything is pushed
The agent runs your tests and linters until they pass.
Your GitLab pipeline, with fix rounds
It waits for your CI on the pushed branch. A red pipeline gets read and fixed on the same branch.
SAST and secret detection
GitLab's own Semgrep and Gitleaks analyzers scan the pushed tree.
A separate security review
A read-only pass reviews the diff and the findings. Anything at or above your threshold keeps the merge request a draft.
It works where your team already works.
No copy of the repository on GitHub and no second place to review. The agent works inside your GitLab, next to everything that decides whether its work is good.
- Merge requests in GitLab, where your team already reviews.
- Your own pipeline and GitLab's scanners, waited for and acted on.
- One copy of your code, with the access rules you already have.
- Your team signs in with GitLab, so there are no new accounts to manage.
Things a GitHub agent can't give you.
Nightsquire is made by an Irish business and runs only on European clouds. Your GitLab can be anywhere.
Any GitLab, any tier
gitlab.com or your own self-managed instance, Free included. No Premium, no Duo.
Your hosts, if you want
Run the executor on a Linux VM of your own, next to your code, with one command. It only connects out.
Credentials the agent never sees
Each step gets a placeholder. The gateway swaps it for the real token on the way out.
Only what the requester could do
Before a run reads another project, Nightsquire checks the person who started it could read it themselves.
What GitHub users ask first.
Does GitHub Copilot's coding agent work with GitLab?
GitHub documents its cloud agent, formerly called the coding agent, for repositories hosted on GitHub. For repositories on GitLab, on gitlab.com or self-managed, Nightsquire gives you the same workflow: assign an issue, get back a reviewed merge request.
Can we use Claude or OpenAI models?
Yes. Nightsquire AI works without any setup and runs in the EU. Or bring your own Claude API key, or any OpenAI-compatible API: OpenAI, Mistral, OpenRouter, Azure OpenAI, or a model you host yourself.
Do we need GitLab Premium or Ultimate?
No. Any tier works, Free included, on gitlab.com or your own instance. On gitlab.com Free you give it a bot account of your own, because group access tokens need Premium there.
Does it use our CI runners?
The agent's own work runs on Nightsquire executors, managed or your own, not on your runners. Your pipeline runs on the branch it pushes, as it would for a colleague's push, and its result decides whether a fix round follows.
Does it merge its own work?
No. It pushes to its own branch and opens the merge request, with your team as reviewers. Merging stays with you and your branch protection.
What does it cost?
Pricing is coming soon. Nightsquire is in a closed beta; leave your email and we'll tell you when it opens to more teams.
Bring the workflow to your GitLab.
Nightsquire is in a closed beta. Leave your email and we'll tell you when it opens to more teams.