Help with G-Code for DevOps — what your administrator can fix, what we can fix, and what to send us.
G-Code for DevOps runs inside your own Azure subscription. Your prompts, your work items and your inference capacity never pass through GeekIt's systems, and we hold no logs, telemetry or copies of your data.
That is a deliberate design choice, and it has one practical consequence for support: we cannot look anything up. To help you, we need you to tell us what your system is doing.
This page explains who to ask, and what to send.
If you use G-Code inside a work item and something is not working, your Azure DevOps administrator or platform engineer can resolve most issues faster than we can. They can see your organization and the proxy. We cannot.
Ask them first if you see any of the following.
The proxy address has not been configured. Your administrator sets this once for the whole organisation.
Your account is not in the group your organization authorized to use G-Code. An administrator can add you.
This is a security check, and it is working as intended. Your administrator needs to confirm the change before the panel will run again. The panel gives you a "Copy the details for your administrator" button — use it, as it copies exactly what they need.
Your organization supplies its own inference capacity under its own agreement with its provider. GeekIt does not resell or meter model usage, so this is for your administrator to raise with that provider.
This happens once, for a limited group of organisations, and it does not mean anything is wrong. The panel re-shows the notice when it detects that your organisation's AI provider configuration may have changed since you last accepted it. An earlier version of that check could miss a real change on some proxy deployments; the fix makes the check reliable, and the one-time side effect is that anyone on an affected proxy sees the notice once more, the next time they open the panel. Accept it and you will not see it again unless your organisation's configuration genuinely changes afterwards. There is nothing for you or your administrator to fix.
Your organisation runs its own copy of the G-Code service, and that copy checks it is licensed before it answers. Right now that check is not passing. This is not caused by anything you did, and there is nothing to retry.
Your platform team runs that service and holds its licence, so they are the ones to tell. Putting a replacement licence in place takes effect without a redeploy or a restart. Tell them what you saw and when.
Contact us directly when the problem is with the extension or the proxy software itself, rather than with your organisation's configuration of it. Typically:
The panel behaves incorrectly when your administrator confirms it is configured correctly.
The proxy fails to start, or fails to deploy from the supplied infrastructure templates.
An error message is wrong, misleading, or names the wrong person to ask.
Email: support@geekitmea.com
Because we cannot look anything up, please include all of the following. A report without them will come back to you asking for them, which costs you a round trip.
Correlation ID — shown on every error the panel displays. Copy it exactly. It is how your administrator finds the matching entry in your own proxy's logs.
Extension version — your Azure DevOps administrator can read it under Organization settings, Extensions.
Proxy version — your platform engineer has this; the proxy reports it at its /v1/health endpoint.
What you expected, and what happened, in your own words.
The exact message shown, as text or a screenshot, including anything it told you to do.
Please do not send us prompts, work item content, source code, credentials, tokens or connection strings. We do not need them and we would rather not receive them. If you believe the content itself triggered the problem, describe its shape — length, language, whether it contained code — not the content.
We are a small team in the Beirut time zone (UTC+2/+3).
Security reports — acknowledged within 2 business days.
The extension or proxy is unusable — acknowledged within 3 business days.
Everything else — acknowledged within 5 business days.
These are acknowledgement targets, not resolution targets. We will tell you what we know and what happens next.
Email security@geekitmea.com. Please do not open a public issue or post details anywhere public until we have replied.
Tell us what you found and how to reproduce it. You do not need a working exploit.
Please do not test against anyone else's deployment. Every installation is a separate customer's Azure subscription, so testing against one without their permission is testing against them, not against us.
We will acknowledge within one business day and keep you informed while we work.
G-Code for DevOps is a paid product, licensed on a bring-your-own-licence basis.One licence covers every Azure DevOps organization under the agreed tenants. GeekIt invoices you directly; nothing is billed through the Visual Studio Marketplace.
For a quote, or any question about pricing or licensing, email geekitsales@geekitmea.com. For anything else, email support@geekitmea.com.
Your licence is checked inside your own tenant, by the deployment itself. It makes no request to GeekIt or to any licensing authority. If a licence expires, the product stops for everyone in the organization until a replacement licence is applied. There is no reduced or read-only mode. Applying a replacement takes effect without a redeploy or a restart.
Your organization supplies its own inference capacity under its own agreement with its provider. GeekIt does not resell, meter or bill for model usage, and cannot see what you spend on it.