1
Set the work, tests and boundaries up front.
Approve the scope and its test together. The approved test is locked by hash, so if the agent edits it, the receipt fails.
Agent work.
Clear evidence.
See what passed against approved scope and tests.
Know what still needs review.
From approved scope
to recorded evidence
Crewly captures what agents did, checks it against your scope and tests, and gives you a clear record to review.
2
Your agent works. Your CI runs the checks.
Keep your existing coding agent and GitHub workflow. Crewly reads the pull request and the evidence your CI provides.
3
See what passed, what needs review, and what’s out of scope.
Review the result and its limitations before sharing a receipt. A passed test is not a production release or a security review.
Illustrative workflow · sample data Choose a step to explore it
A clearer handoff
The result.
And the full picture.
A summary says the work is done. A receipt tells you what was checked, which version was approved, and where a person still needs to look.
Open the annotated sampleTry the workflow
Sample · made-up data · nothing is savedRequest · scope v3
Checkout retry
Add a bounded retry when checkout payment fails. Do not change pricing, tax, or the refund path.
Test to approve with it
- a declined card can be retried
- retries stop after two attempts
- the customer sees a clear error after the last retry
Approving records this exact version and its test together. The agent starts from it.
Know the limits.
A receipt records evidence. It does not replace code review, a security assessment, or production verification.
Built around the work
Different teams.
One clear handoff.
Give your client
something concrete.
Agree on scope. Review the evidence. Share a clear receipt your client can open without creating an account.
See the client experienceKeep reviewers
in the picture.
Bring approved scope, pull requests and check results into the same conversation. Make the next review easier to understand.
Explore how Crewly worksYour workflow. Your decisions.
Stay in control
of the handoff.
Keep your agent and CI
Your agent works in your repository. Your CI runs the approved test. Crewly reads the results.
Review before you share
Preview the receipt, choose what to include, and share the link yourself. Nothing is sent for you.
Clear boundaries, visible evidence
Approved tests are locked by hash. If the agent edits it, the receipt fails. Receipt limitations stay visible alongside the result.
Can the agent cheat the test?
It can try, and Crewly checks the specific ways: deleting, skipping or weakening tests, editing the approved test, and editing CI. These checks flag, and a person decides. A diff check can't see everything: a hard-coded answer would pass, so keep reviewing the code.
What does a receipt not cover?
Behavior outside the approved test, code quality and security, and the production deploy. Every receipt lists this.
What does a reviewer see?
A page with the approved scope, what was checked and what wasn't, in plain language. You preview it first. The link needs no login, expires (30 days by default) and can be revoked. Cost and agent telemetry are hidden unless you choose to show them.
Does Crewly share anything automatically?
No. You publish a link and share it yourself.
Does it need Slack?
No. Crewly runs in the browser: a project is one GitHub repository, and requests are written and approved on the web. You can connect Slack in Settings for notifications and to send requests in. The receipt comes from the pull request your agent opens.
Is Crewly certified?
Crewly is not SOC 2 certified. The security page lists the controls in place today and what is not built.
Make the next handoff a clear one
Less guessing.
More evidence.
14 days free, then $99 per client project a month. No card.