How best to use Browser/Chrome with Claude for testing and debugging

1 points by jaigupta 146 days ago | 2 comments

During development or bug hunting, I would want Claude to use Chrome directly. It is very useful. Previously I used to use playwright-mcp and now using Claude Chrome extension.

However, using this eats up all the context. I tried creating an agent for this using model sonnet[1m] for it. This kind of works but agents ends up doing a lot more than just using Chrome. It forgets that it is supposed to complete the flow or view console logs, take screenshots and give complied result back but it rather starts working on the issue in hand. Maybe it is because of poorly written Agent or poorly written Claude.md.

How is everyone working with playwright-mcp/Claude Chrome?

reify 146 days ago |

The best way to use claude in the browser is not to use it at all

It forgets! It doesn't forget, it doesn't have a memory or a human brain.

maybe!

Consider your own life. look back at your childhood and remember, running home from school on a beautiful sunny day, playing with your friends, remember the freedom. How many years ago was that? 20, 30, 40, 50, and you still remember it like it was yesterday

AI DOES NOT HAVE ANY MEMORIES SO IT CANNOT FORGET.

jaigupta 145 days ago | |

When I said forget, I meant that it does not follow instructions in .claude/agents/chrome-tester.md and rather starts working on stuff that was going on in main context.

I am not sure if I need to write better CLAUDE.md (main context) or better agent file .claude/agents/chrome-tester.md for this case.

I get what you were trying to say but AI does have memory, fixed memory files that we can modify and we may also write creative prompts for dynamic memory for e.g. while troubleshooting keep adding learnings to learning.md file so that you know what all was tried. It also have in-built memory in the sense that it has a lot of built in knowledge. Okay, I admit to be incorrect on purely technical point of view but in just simpler terms.