First agent task

Connect an app, create a draft through an agent, and verify its recorded result.

Use your own agent app for authoring and Jetrepo for access, review, and results. This walkthrough creates unpublished test content.

Sign in with an account allowed by your deployment. Registration provisions a Default Organization; an invitation may give you access to another. Check the selected Organization before connecting an app or creating a Backend.

An Organization owns access. A Backend contains your content model and Environments. Membership alone does not grant permission to create or modify a Backend.

Connect your app

Open Connect an agent app from Overview or Connections. Choose Codex, Claude Code, Cursor, or VS Code and follow its setup instructions. Review the app, Organization, and requested access on the browser consent page.

Return to Jetrepo and check the authorized app names. Authorization belongs to your Organization; it does not prove the app has completed work in a particular Backend. Agent Auth is optional for this OAuth flow.

Create or select a Backend

If you already have a Backend, open it and select the intended Environment. Use Copy Backend context in connection setup, or Copy context under Your agent apps on Overview. The text includes exact scope IDs and a draft-only instruction. Expand its disclosure to read it.

For an empty Organization, ask the connected agent:

Inspect my Organizations and confirm the intended one. Create a Backend named
Journey Sandbox only if it does not already exist. Use the normal governed
workflow, return the Backend and Operation links, and do not publish content.

The agent needs backend.create and operation.execute to bootstrap a Backend. It discovers the live backend.create definition and returns the new main Environment. Manual Create Backend is also available when your role permits it; enter a name and optionally customize its icon and color.

Ask for a small draft

Paste the copied Backend context first, then send:

Inspect the existing model. Create an Article type only if needed, with a
required title and a plain-text body. Create one draft titled "First journey
test" with body "Hello from Jetrepo". Do not publish it. If Jetrepo requires
human Approval, return the review and Operation links and wait. Return links
to the completed work and report any failed items.

The agent needs delegated human access, operation.execute, and the exact model/content permissions required by the discovered definitions. Organization-owned Agent keys cannot author the model or draft content.

Review only when required

Autonomous Operations may finish without a review action. If the Operation is AWAITING_APPROVAL, open its link in Changes. Read the proposed values, scope, validation, and policy before deciding.

Approval requires operation.approve plus the policy’s approver permission. When a different person must approve, the requester and delegating human cannot approve; send the review link to another authorized member. A confirmation inside your agent app does not replace Jetrepo Approval.

Verify the result

Open Operations and inspect the recorded result. The title and body should match the request. Bulk work is grouped by resource type; open individual results to read their fields. A state describes the recorded step, so later work may have changed the resource.

Successful execution does not imply publication. Leave this task unpublished. When you intentionally want to deliver content, ask for a separate publication request and review its effective policy. Use Delivery to discover REST/OpenAPI and Context endpoints after publication.