Quickstart

Finish this guide with an approved Intent and a context bundle you can paste into your existing review workflow. You need access to the Orneos app and a team. Manual writing does not require an AI key.

Already working in another tracker? You can try an assisted review using an existing task and pull request. The workspace steps below are optional for that pilot; no board migration or released tracker integration is assumed.

1. Open one change

Sign in, choose your team in the sidebar, and open an issue for a real change. If you need a new issue, choose New issue or press c, enter a title and description, and create it. You can leave optional fields unset.

For a practice run, use this fictional task throughout the guide:

Export filtered issues to CSV — Let someone export the issues currently shown in a filtered view.

Your issue reference will differ from the illustrative ENG-42 used here. You do not need to configure labels or saved views to follow this guide.

2. Write the agreement

Open the issue’s Intent panel and choose Write manually. Fill in the labelled fields:

• Goal: Let someone export the issues currently shown in a filtered view to a CSV file.
• Acceptance criteria: Only matching issues are exported; the export includes the visible columns in their displayed order; an empty result produces a file with column headers and no issue rows.
• Not in scope: Scheduled exports, importing CSV, and exporting hidden columns.

These are requirements for the fictional change, not a claim that Orneos currently offers CSV export. Replace them with the actual agreement for your work. Enter acceptance criteria as separate items in the editor.

An AI draft is optional: personal keys or an enabled funded allowance can help prepare one. You still review and approve the writing yourself.

3. Approve and check it

Read the goal, each criterion and the exclusions, then choose Approve.

Check that it worked: the panel displays the approved revision, approver and time, and offers Revise. For a first approval, expect revision 1. Check pending or failed changes and allow the approval to reach the server before relying on a confirmed export.

If you revise the agreement later, the changed writing needs another approval. An editing session is not a saved draft: copy writing you need to keep before closing the tab. See Intent for revision and recovery behavior.

4. Copy the context

Use the issue’s Copy context bundle action. Paste the result into a document or your review tool so you can inspect it before sharing.

Check that it worked: the heading names the issue you chose. The Intent section identifies the approved revision and approver. If it instead says Approval pending or that confirmed Intent could not be established, reconnect, check the approval and copy again. A successful clipboard action alone does not prove that the agreement was confirmed.

Read any missing-source or truncation notices. Linked Vault references include eligible titles and links, not their page bodies. See an example export and troubleshooting.

5. Hand it to a reviewer or agent

Share the bundle together with the exact change to inspect, such as a pull request pinned to a commit. The bundle does not fetch repository code or test results for you. Only share material with recipients and tools your team permits.

You can use this request:

Review this exact change against the approved Intent in the bundle. For each criterion, identify the evidence you inspected and anything you could not verify. Call out missing context. Leave the acceptance decision to the human reviewer.

Ask your reviewer to distinguish supported criteria, discrepancies and unanswered questions. Orneos’s automated review is work in progress. If you want help preparing evidence and reviewing the result, request an assisted review; that service includes disclosed manual work.

If something gets in the way

What you see	What to do
No app or team access	Request early access, or ask the person who invited you to confirm your team access.
AI drafting is unavailable	Use Write manually; an AI key is not needed for manual writing.
Approval is pending or rejected	Inspect the pending/failed change. Keep local storage intact; Intent recovery explains retained submissions.
Copy fails or the bundle is incomplete	Follow Context bundles, then copy again.

Explore the workspace afterwards

Once you have handed off one change, explore issues, labels, saved views and keyboard shortcuts as needed. Offline and reconnect explains supported local work and its limits.