SIMY
  1. SIMY
  2. Guides

GUIDE

SIMY Delivery Loop: Build with the CLI

Build, check and repair within one task. Receive a change with evidence you can inspect, and make the intended delivery boundary clear from the start.

SIMY · Updated

Start from the SIMY CLI

In an environment with SIMY CLI installed and your account and AI executor connected, run simy in a terminal. Its Agentic Loop console lets you create a development request. These steps describe the CLI console.

simy
# Enter the following inside the SIMY console
/new
/repos
/branch main
/executor codex

Use /repos to select an authorized local repository. Replace main with the correct base branch for your project. Use /executor claude if that is your connected provider. Enter /help to check the commands available in your version.

Describe the result and its acceptance criteria

This is an example request. Explain who benefits, what must remain intact, the evidence you need and whether delivery includes publishing. The request does not waive repository checks or grant permissions that you have not authorized.

Improve the contact form's success message so users understand that the request was sent and what happens next. Preserve the submission logic. Check the mobile experience and show the changes and verification results. Wait for my review before merging or publishing.

Example request

Choose assurance for the risk of the change

Choose a level at the start of the work. Risk determines the minimum suitable level. Every level preserves repository requirements and approvals. Duration depends on scope and external waiting, not a universal time per level.

  • Level 5: authentication, payments or sensitive information; inspect adjacent boundaries and recovery.
  • Level 4: persistence or shared APIs; inspect integrations, retries and operational effects.
  • Level 3: ordinary features and fixes; verify the main journey and independent review.
  • Level 2: small reversible presentation changes; check the direct behavior and regression.
  • Level 1: copy, documentation or metadata; verify artifacts, the diff and links.

Respond to pauses and inspect the final result

Use /continue <guidance> for a waiting run, including the missing decision or information. For example: /continue Proceed without changing submission logic. Use /pause to pause, /resume to resume, and /stop to stop the selected run. Read the proposed action before giving any required approval.

Inspect the diff, actual test results, independent review and outstanding checks. Creating a PR, merging, publishing and verifying production are distinct states. Confirm that the work reached the delivery boundary you requested.