You: Run a security pass on release 4.12 before it ships. Test staging only and file what you find in Linear.
Adapt for security
Find the weak spots before anyone else does.
Build agents that review code, test your apps and audit access. Every finding comes with evidence and a fix.
Release 4.12 security pass
Code review
A security pass on every PR. Findings on the line.
An agent checks each change for injection, exposed secrets and broken access, and suggests the fix.
appsec

Security review on PR #2512 before we merge.
Read the diff across 9 files. One high: the new export endpoint skips the workspace check, so any signed-in user can download another team’s reports.

Leave it on the PR with a fix.
Done. Commented on reports/export.ts:41 with a suggested fix and a failing test that proves it.
Scoped testing
Test your apps like an attacker. Only where you allow.
Name a target and a scope; an agent probes it from a sandbox and writes up how to reproduce each finding.
appsec

Test the new billing portal on staging. Stay off production.
Scoped to staging.acme.dev/billing. Ran 186 requests from a sandbox: auth, access control, injection and rate limits.

Anything real?
Two. Invoice IDs can be guessed, and the coupon endpoint has no rate limit. Both reproduced, with the requests attached.
“It started with data access, but now every team at Wander runs on Adapt. It has become the operating layer for the entire company.”
Nathan PotterCTO, WanderAccess reviews
Find access nobody should have. Across every connected tool.
An agent checks who can reach what against who should, and flags old accounts, stale keys and public storage.
security

Run the quarterly access review.
Checked GitHub, Google Workspace, AWS and Snowflake against the HR roster. Found 4 accounts for people who’ve left, 2 API keys unused for 90 days and 1 public bucket.

Close the bucket and open tickets for the rest.
The bucket policy change is ready for your approval. SEC-121 to SEC-127 are open, each with its owner.
Remediation
From finding to fixed. Then tested again.
Each finding becomes a ticket with an owner; the agent drafts the fix and reruns the test once it ships.
appsec

Where are we on SEC-118?
The fix is in PR #2519. I reran the cross-workspace request against the preview, and it now returns 403.

Close it once it’s deployed.
Will do. I’ll retest on staging after the deploy and close SEC-118 with the result.
Questions
The repositories, cloud accounts and tools you connect, with the access you give it. Tests run from a sandbox against the targets you name.
Only if you point it there. Most teams test staging or previews, and the agent drafts changes for a person to approve.
No. It takes the reviews your team repeats between audits, and works alongside your scanners and formal pentests.
A security pass on pull requests. The inputs are clear and the findings are easy to check, so you can widen the scope from there.