Inspiration

Shipping software often comes down to one stressful question: is this release actually safe to ship? Teams usually answer that by jumping between GitLab issues, merge requests, CI pipelines, release branches, and notes. Inquisitor was built to turn that messy release-check process into an agentic workflow.

What It Does

Inquisitor investigates a GitLab release and produces a readiness report. It checks release blockers, failing CI, open issues, merge request status, and missing regression-test evidence. Then it gives a release score, explains the risks, and recommends next actions.

It also keeps humans in control: before preparing follow-up actions, Inquisitor asks for approval instead of silently changing project state.

How We Built It

Inquisitor is a hosted web app with a GitLab-style adapter layer and an MCP endpoint for agent tooling. The app includes:

  • A release investigation agent
  • A GitLab evidence adapter
  • A hosted demo interface
  • A Streamable HTTP MCP endpoint at /mcp
  • Approval-gated follow-up action preparation
  • A seeded GitLab demo project for release-risk scenarios

The agent workflow is designed around Gemini-style reasoning: plan the investigation, inspect GitLab evidence, score release risk, and recommend approved actions.

Challenges

The biggest challenge was integrating real-world agent tooling cleanly. MCP setup, hosted deployment, and platform compatibility took several iterations. We also had to make the demo clear enough that judges can see the difference between a chatbot and an agent that actually performs a release investigation.

What We Learned

We learned that useful agents need more than a good answer. They need context, tools, safety boundaries, and a clear human approval loop. Inquisitor showed how an agent can help teams make better operational decisions without removing human judgment.

What’s Next

Next, Inquisitor could support richer GitLab project data, live CI inspection, automatic release notes checks, Slack notifications, and configurable release policies for different engineering teams.

Built With

Share this project:

Updates