One instrument. One useful task.
Inspect the interface after the fix
Step 1: A cracked reflection
Fix a UI with browser feedback.
Still frames · every step is available
“Inspect the interface after the fix.”
Fix a UI with browser feedback.
See who does what
Choose the task, workspace and permitted scope.
Fix a UI with browser feedback. Start here: Configured browser tool → inspect → scoped fix → inspect again.
The actual target UI is checked after the change.
Browser feedback uses configured browser tools and their own authentication.
Copy an example instruction
Illustrative task shared across these lessons. Adapt the scope and file ownership to your project. Try the complete example and inspect its tests →
Add a saved-filter control. Keep the change focused. Inspect the existing filtering behaviour, implement the control, and run the relevant checks. Ask a separate agent to review the diff without editing it. Collect its findings and resolve confirmed issues before proposing a commit.
Before you start
Run your project's development server. Open Armoury (Settings) → Integrations and enable Browser Automation. Launch the agent from Code Overlord so it can access the configured browser tools. Browser Automation uses its own profile. If the application requires sign-in, that browser needs an authenticated session; it does not automatically inherit your personal browser's login.
Illustrated explanation · The scene explains the workflow. Follow the guide to perform it in the app.
About this demonstration
Instructions reviewed against product 1.5.119. Authored illustration; no application execution is claimed.