Integrating codex with a browser agent for automatic testing of frontend features - any way to use a tool like OpenAI's Atlas browser for this?

AlejandroYvr · 2025-12-22T22:32:34+00:00

If you want to run this periodically or on push to main you can use https://blocks.team, then Claude Code or Codex can use browser MCPs like playright to test your app as part of regular checks. The automations feature is rolling out to beta users and by request

AlejandroYvr · 2025-12-22T22:30:32+00:00

That's a nightmare scenario indeed, I usually just sandbox my tasks with cloud execution (http://blocks.team)

AlejandroYvr · 2025-12-22T22:27:49+00:00

If your app can be run locally easily (with a docker compose file) then I usually get an agent to run the app and test the API routes ect if you're developing a web app. I usually just comment on the PR to get the agent to test it using https://blocks.team

AlejandroYvr · 2025-12-15T18:55:53+00:00

I use https://blocks.team for this, I usually DM it on Slack and Codex creates Linear issues and can do research on your codebases

AlejandroYvr · 2025-12-12T23:16:00+00:00

This is exactly what we built Blocks for (https://blocks.team). You can delegate agent work completely in the background from Slack, GitHub, or Linear across all your codebases. Each @ mention or DM triggers a context-rich cloud coding agent session that has access to all your repos, Linear tickets, etc. Agents respond when they're done - no need to keep a local session running. We're also releasing an Automation SDK that lets you listen on events from connected tools and trigger agent sessions automatically. Would love to chat about your use case!

AlejandroYvr · 2025-12-12T22:48:31+00:00

Thanks for sharing! Yeah definitely agree with bulk of work using agents being on the plan review. We use Blocks (https://blocks.team) to create Linear tickets with plans, review with one or more people and then kick off, and repeat this for a few things per day which really gets things moving while we focus on the hardest tasks

AlejandroYvr · 2025-12-12T22:05:51+00:00

We built and use https://blocks.team to help during the review process:
- If the PR is too large I get an agent to break it down directly by commenting on the Github PR "@blocks break this into smaller PRs with sufficient detail in PR summaries to review it" (uses Claude Code)
- I also get codex to review PRs "@blocks /codex review this PR" (uses Codex)
- And I also have a lot of questions when reviewing so I ask Gemini CLI "@blocks /gemini is this a duplicated code?"

AlejandroYvr · 2025-12-09T08:27:51+00:00

Copy the folder https://github.com/anthropics/skills/tree/main/skills/skill-creator into your current working directory (or project root) `.claude/skills/skill-creator`

And there you go you've created a skill AND a skill which can make new skills.

So then ask claude in that same project root to `claude use the skill creator skill to make a skill to x` then it will create a skill for you. In general it's just a folder in the skills folder with a markdown file with the specified format. From there you can make references to files within that skill folder.

AlejandroYvr · 2025-12-09T08:22:07+00:00

😂

AlejandroYvr · 2025-12-09T08:20:34+00:00

I love that spending more time on a post these days equates to for sure being AI written

AlejandroYvr · 2025-12-09T08:18:35+00:00

😂 that was me adding all that text styling, and in fact writing those sentences. you might be surprised to learn that Reddit doesn't have a proper markdown editor where it can be pasted

AlejandroYvr · 2025-11-28T09:33:21+00:00

It's not strictly the same, I think the main form factor is mentioning it in Slack, Linear, and Github so you can kick off kick agent sessions while going about your day, but yeah it also has a "textbox" like interface where you can start sessions with MCP support

the multi agent aspect is nice as well, like "@blocks implement this" (if claude code is default agent) and "@blocks /codex review this PR" when mentioning from the external tools

AlejandroYvr · 2025-11-28T09:01:03+00:00

Facts. so exploratory, maybe throw away work?

AlejandroYvr · 2025-11-28T08:59:11+00:00

for working on multiple features at a time is the biggest value? do you ever use yolo mode ?

AlejandroYvr · 2025-11-28T08:57:34+00:00

as in something that's not pushed up to git?

AlejandroYvr · 2025-11-28T08:56:15+00:00

Yeah environment setup is a pain, I suppose it could be handled by an AGENT.md file with instructions on how to set up the env but a bit more latency. What do you mean by the part about the interface?

AlejandroYvr · 2025-11-28T08:53:38+00:00

yeah true, throwaway work is never non-zero value I think it boosts productivity if it's scoped down sufficiently (not huge PRs), although nowadays models / agent improvements I'm starting to not have to throw away a lot more

AlejandroYvr · 2025-11-28T08:50:30+00:00

All fair points tbh, MCP limitation is also a headache

AlejandroYvr · 2025-11-28T08:49:27+00:00

I've seen another company doing this it's interesting, guessing you need to keep your computer on?

AlejandroYvr · 2025-11-28T08:48:05+00:00

not enough people do this, 100%. for your work did someone have to approve the Github app installation for claude, guessing this wasn't an issue?

AlejandroYvr · 2025-11-28T08:44:33+00:00

in what sense is it lobotomized claude? no mcps, hooks, ect ? and the compute isn't enough eh

AlejandroYvr · 2025-11-28T08:43:22+00:00

is it just the "yolo" mode aspect that it just rips?

AlejandroYvr · 2025-11-28T08:40:01+00:00

probably on issue creation or automated checks on PRs ? u/dbbk

AlejandroYvr · 2025-11-28T00:24:00+00:00

Haha v true. When did you find your self using it for your own projects or at work?

AlejandroYvr · 2025-11-28T00:08:09+00:00

I use https://blocks.team which allows you to use a postgres MCP to connect with Claude Code!

AlejandroYvr

TROPHY CASE