Record product demos that show real user actions and responses for each covered user journey. Add timed captions, inspect the finished clips, and include them in pull requests, with manual test instructions when recording is blocked.
Record at least one captioned demo for every covered CUJ through its real entry point.
Review the instructions the agent will receive before you install.
The demo is required. Record at least one clip for every covered CUJ; a CUJ with several entry points or steps may have more. Each clip shows the user action and the product's response through the CUJ's real entry point, never pytest output, assertions, test source, or debug logs.
Follow dev/recording-lanes.md for the recorder,
the per-surface mechanics, and captioning. Use the CUJ ID as the facet and
demo as the kind:
recordings/<ticket-key>/raw/demo-<cuj>.<ext> (add a
short suffix, e.g. demo-cuj-1-edit, for extra clips of the same CUJ).dev/caption_recording.py, rendering
to recordings/<ticket-key>/demo-<cuj>.mp4. Captions list the actions shown
and end with the observed result.caption and the PR Demo. A usable uncaptioned clip still counts.OMNIGENT_RUNNER_ID is set), strip the inherited runner variables as the
guide describes, and retry before reporting a blocker.Never commit recordings; they ride in the PR Demo section and the CI artifact bundle.
Recording should almost always work. When a covered CUJ really can't be recorded (the recorder can't start in this environment, or the surface needs hardware or an external account the sandbox doesn't have), still publish a ready PR and drive it as usual. For that CUJ:
recording_blocker to the specific blocker, with the command and error;manual_test: step-by-step instructions a human can follow to test the
journey, including setup, the inputs to give, and what they should see;The outcome is then partially_implemented, with that CUJ's recording in
remaining_work. Only declare clips you actually produced. Then load
feature-publish.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Test Omnigent’s native Antigravity integration with a live local server and the real agy CLI. Verify messages traveling between the web interface and terminal, mirrored replies, permission requests, interruption, session resumption, and process cleanup.
Test Omnigent’s Antigravity SDK integration against a live local server. Build test agents and run real conversations to check Gemini authentication, model selection, tool connections, and failures across the full execution path.
Create reference documentation directly from source code for public functions, classes, command-line commands, and endpoints. Organize parameters, defaults, return values, errors, and runnable examples, then check that the documentation matches the implementation.
Create an Omnigent agent directory using validated templates for configuration and instructions. Choose how the agent runs, then add web search, shell access, external tool connections, or subagents only when the task requires them.
Turn a selected range of commits or merged pull requests into release notes grouped by change type. Describe user-visible effects, link to supporting changes, and highlight breaking changes so readers can assess an upgrade.
Test Omnigent’s setup, help, and terminal interactions by driving the real CLI in an isolated environment. Capture rendered screens and compare checks before and after a change to establish whether a reported interface problem was fixed.