Workflow account: Elusive reviews and managed CI
Elusive is an early external application using Redgold for repository reviews and remote Linux CI. Its developer is the Redgold operator's brother. This is a first-party account of that integration, not an independent customer testimonial or a claim of proven revenue, savings, or review accuracy.
The integration provides a concrete starting point for a managed offering: configure the repository, run the review, keep the evidence visible, and help operate the underlying environment.
What the application needs
Elusive uses the review bot to assess pull requests and remote Linux builds as part of its effort to reduce CI costs. Those are related engineering workflows, but their outcomes must be measured separately. A completed review does not establish cheaper builds; metered builds do not establish a paid invoice or net savings.
| Workflow | Redgold's role | Evidence that matters |
|---|---|---|
| Pull-request review | Repository context, review stages, synthesis, and a posted result | The reviewed commit, findings, stage outcomes, and maintainer assessment |
| Project continuity | Retained conversations and available context sources | Workspace ownership, readable source links, and explicit retrieval status |
| Remote Linux CI | Isolated execution, job admission, resource limits, and usage accounting | Completed jobs, wait and run time, resource usage, and the total billed cost |
A recorded review
The September 14, 2026 integration work record describes a completed review of Elusive pull request 968. The run completed triage, repository-index and local code-context retrieval, three review perspectives, a judge stage, and synthesis. The tests perspective failed. GitHub received a formal review requesting changes on the checked commit, and the root and child conversations belonged to the public Elusive workspace.
That record establishes that the integration produced a real repository-visible review. It does not establish that all stages succeeded or that the findings were correct. The same work record identified problems with cost-receipt lookups and previously unavailable memory retrieval. Those observations are historical integration evidence, not a statement that they remain unresolved in today's deployment.
What operating the workflow taught us
Repository access is only one part of a managed review. The webhook, workspace binding, execution environment, context sources, review conversations, and usage accounting must agree about ownership and the run being evaluated.
The CI integration also encountered a capacity mismatch: jobs continued to target a worker pool after that pool's allowed capacity was reduced to zero. The September 15 repair record describes moving the authorized CI lane to existing isolated workers while retaining resource deadlines and serial admission. This illustrates why a managed service needs to own failed-job diagnosis and capacity configuration alongside the happy path.
Three practical lessons carry into onboarding another repository:
- Make incomplete review stages and unavailable context visible to maintainers.
- Agree review depth, rerun allowances, and spending controls before enabling repeated automation.
- Evaluate total operating cost and reliability, including waiting, retries, and human support, when comparing CI arrangements.
What has not been established
This account does not publish a before-and-after CI bill, a measured reduction in engineering time, a review accuracy score, or a revenue figure. The current customer relationship does not by itself establish demand from unrelated teams. Those would require their own evidence and permission to publish it.
For your own pilot, record eligible pull requests, completed and incomplete reviews, accepted findings, model and compute charges, and maintainer time. For a CI comparison, use comparable workloads and include Redgold's full price and any migration or management fees. See budgeting automated reviews.
Start with one repository
Use the managed review setup guide to define the repository, context, limits, and first review you will assess. You can request a paid managed setup without granting repository access or starting a subscription in the request form. Scope and pricing are agreed during onboarding.