weftcloud
Request early access

WEFT CLOUD / AI REVIEW

“Done” can use
another set of eyes.

Give your agents specific feedback before you accept the work. Cloud reviewers examine plans, designs and code; your workflow decides what happens next.

01 / PLAN

Before it fans out.

Question the scope and assumptions while the plan can change.

02 / DESIGN

Before it becomes code.

Return specific concerns for the implementing agent to resolve.

03 / CODE + ACCEPTANCE

With the repository in view.

Agentic reviews inspect supplied files and can use tools.

FROM THE WORK RECORD

A missing field.
A consequential catch.

A recorded Cloud review found a rebuild payload that could erase stored task fields. The agent corrected it; a subsequent review approved the revision.

11¼ minReview call → correction acknowledged

Read the development study ↗
FINDING → REVISION → ANOTHER LOOK
AI REVIEW / FINDINGA rebuild could erase stored task fields. Original fields missing Preserve original fields
IMPLEMENTING AGENTRevise the change
REQUIRED CHECKSReview again
Your workflow gates decide when the work can advance.
Check the revision before the task advances.

Diagram adapted from a recorded finding.

Inspect the finding and source notes
AGENT / WORK RECORDCloud · hosted AI code review
  1. Implementing agent → Weft Cloud
    Review the projection rebuild change against the task.
  2. Cloud AI reviewer
    NEEDS_REVISION · HIGH The rebuild payload omits stored task fields. A full-document overwrite could erase them.
  3. Implementing agent
    Use the complete live payload. Add regression assertions for retained fields.
  4. Implementing agent → Weft Cloud
    Review the corrected files.
  5. Cloud AI reviewer
    APPROVED · the erasure finding is resolved.
  6. Work record
    Correction acknowledged. Corrective PR #1074 merged.
Condensed replay of recorded work · July 18, 2026. Playback changes this example only.
Source and scope

The raw transcript and corrective Git diff corroborate this case. The completion call followed the first review call by 11.246 minutes; the subsequent approval arrived before that completion. APPROVED did not mean zero minor suggestions. This was model-driven Cloud review, distinct from the bundled OSS structural checks and repository build/test verification.

A FINDING HAS SOMEWHERE TO GO

Revise the task.
Keep other work moving.

A failed required gate can hold a transition and send the task back for revision. Keep AI review alongside your build, test and structural checks.

You set acceptance criteria and resolve choices that need your judgment.

See an agent ask and remember →
  1. IMPLEMENTAgent submits the change
  2. REVIEW + REQUIRED CHECKSFinding? Return for revision ↶
  3. ACCEPTANCEInspect the evidence
YOUR NEXT PROJECT

Start with one thing you want to delegate.

Request early access to Weft Cloud. Start with your own coding agent, or bring your team and the agents they already use.

Request early access ↗