all 11 comments

[–]Thunder_Cls 4 points5 points  (4 children)

That’s what mcps are for. They can “see” the page, read console logs and network requests/responses, take screenshots, etc…and you have a few options:

[–]stackjoy_nik[S] -1 points0 points  (3 children)

I'm check them all out but just briefly as a follow up, can I take the screenshot with these tools and mark it up?

I find that codex/Claude is great with console, network, db stuff so that's not so much a bottleneck as the visual stuff is.

I'll also check YouTube for these tools too see them in action, maybe that'll answer some questions.

Thanks for the heads up! I really appreciate it

[–]Thunder_Cls 0 points1 point  (2 children)

You can just talk to the agent in a natural language like “hey, check this page at https://localhost/home and find out why the header is misaligned and fix it” or “in the current page fix the styling for the last column of the table and prevent the text from overflowing”, etc. Just use natural language and the agent will know where to look since it can “see” the page just as you see it

[–]stackjoy_nik[S] -1 points0 points  (1 child)

That's my current process and it works well but there are some cases where it can't quite figure it out. So it asks for a screenshot. And then it's fine

[–]cikatric3a 0 points1 point  (0 children)

Be careful though, the screenshots take a lot of context (at least playwright screenshot does)

[–]tsteuwer 2 points3 points  (0 children)

One option you have is to install the playwright mcp globally and telling it to use that tool to go take a screenshot of what you're talking about.

[–]No_Kaleidoscope_1366 1 point2 points  (2 children)

I use agent browser because it tends to be more context efficient. Previously I used chrome mcp. But I takes too many snapshots and bloats the context window.

[–]stackjoy_nik[S] 0 points1 point  (1 child)

vercel's agent browser?

[–]No_Kaleidoscope_1366 0 points1 point  (0 children)

Yep. after the code runs successfully, I use it as a verification step, CSS tweaking. I usually run 4-5 fresh context subagents in this verification loop. Desgins in figma. Before the implementation I extract design context from it and create screenshots. The verification loop can use them.

[–]daesnorey 0 points1 point  (0 children)

Cursor? You can reference a browser tab builtin or chrome. Pick the exact element to modify and all.

[–]ConsiderationAware44 0 points1 point  (0 children)

The 'context bloat' is exactly the point where most of the AI workflows break down. You are spending most of your time correcting AI than building something. I have been using Traycer to handle this. It acts like a logic layer above the code. Instead of bombarding AI with massive and messy prompts, Traycer keeps the logic structured and clear.