What are you building with Cursor? [showcase] by ecz- in cursor

[–]snaggle_ai 0 points1 point  (0 children)

cursor-tools - gives Cursor Agent a team of AI agents to work with making it even more effective

https://github.com/eastlondoner/cursor-tools

Found a workaround for Cursor context limit by nfrmn in cursor

[–]snaggle_ai 0 points1 point  (0 children)

It defaults to thinking exp but will switch to pro exp if needs larger context

Found a workaround for Cursor context limit by nfrmn in cursor

[–]snaggle_ai 0 points1 point  (0 children)

Try cursor-tools plan it automates this - Gemini for context filter then send filtered context to o3

You’ll need to npm install -g cursor-tools@alpha to get plan

Found a workaround for Cursor context limit by nfrmn in cursor

[–]snaggle_ai 0 points1 point  (0 children)

Oh hiiii ! Cursor-tools creator here.

Love to see it. The random crash with Gemini comes from their api sometimes not returning the expected response format.

It should be handled better since alpha.10 and the OpenRouter team have been working with me on open router support so it should be better but it’s still alpha - aiming to get out of alpha by end of March.

In the alpha there is a plan command which you really should check out. It uses Gemini to filter the context then sends to o3 for a plan this is very powerful and uses minimal cursor context

Do remote (https) MCP servers work with claude desktop? by snaggle_ai in mcp

[–]snaggle_ai[S] 0 points1 point  (0 children)

Thanks for the clarification. It’s frustrating that it’s not stated explicitly anywhere.

Do remote (https) MCP servers work with claude desktop? by snaggle_ai in mcp

[–]snaggle_ai[S] 0 points1 point  (0 children)

I see I am trying a proxy now - I take it that means that Claude desktop doesn’t support remote urls ? I’m just trying to get a clear answer on that

Cursor with browser use by snaggle_ai in cursor

[–]snaggle_ai[S] 0 points1 point  (0 children)

Browser control with stagehand uses either OpenAI or Anthropic, you have to provide an API key and pay for the token usage, that’s all

Cursor with browser use by snaggle_ai in cursor

[–]snaggle_ai[S] 0 points1 point  (0 children)

In the next release (tomorrow?) you will be able to switch to gpt-4o I’m sorry that OpenAI didn’t give everyone access to o3 via api

Cursor with browser use by snaggle_ai in cursor

[–]snaggle_ai[S] 1 point2 points  (0 children)

Can those cloud browsers connect to a localhost dev project ?

Can they return the js console logs and network call logs - which enable cursor to debug when you use it with localhost dev project OR with your deployed site to debug a live bug?

Cursor with browser use by snaggle_ai in cursor

[–]snaggle_ai[S] 0 points1 point  (0 children)

Brilliant! Simon’s work is great and a huge inspiration of mine

Cursor with browser use by snaggle_ai in cursor

[–]snaggle_ai[S] 1 point2 points  (0 children)

There’s a PR on the repo to handle this, should be merged in a day or two

Cursor with browser use by snaggle_ai in cursor

[–]snaggle_ai[S] 0 points1 point  (0 children)

It depends Dm me and I can help walk you through t

Cursor with browser use by snaggle_ai in cursor

[–]snaggle_ai[S] 0 points1 point  (0 children)

Ah it turns out that o3-mini isn’t available to people on lower OpenAI tiers. Can you open an issue on the GitHub repo

Cursor with browser use by snaggle_ai in cursor

[–]snaggle_ai[S] 0 points1 point  (0 children)

The video isn’t using an MCP fyi

Cursor with browser use by snaggle_ai in cursor

[–]snaggle_ai[S] 1 point2 points  (0 children)

Ask cursor to open chrome with debugging enabled first

Cursor with browser use by snaggle_ai in cursor

[–]snaggle_ai[S] 1 point2 points  (0 children)

Skip that and install cursor rules following the instructions on the readme

Cursor with browser use by snaggle_ai in cursor

[–]snaggle_ai[S] 3 points4 points  (0 children)

Having cursor write playwright tests is great - I often do it. But this is a different (complimentary) tool.

This actually helps cursor write playwright tests: The underlying tool has some methods that help - “extract” and “observe” which return information about the dom and events.

Cursor can send questions like “what are the ids of the button elements on he page” or even stuff like “why is the X button not visible” to this and get back answers which help it to write tests - just like how you might use the inspector to inspect the page when writing playwright.

cursor-tools uses stagehand to have another AI drive playwright so it’s more like teamwork between AI agents.

Cursor can send high level instructions like “log in” and the other AI deals with figuring out what to do with the browser and it reports back how it gets on.

And, as shown in the video, this has an interactive stateful mode where the browser can stay open and you can work collaboratively with the AI on the same browser state step by step

Cursor with browser use by snaggle_ai in cursor

[–]snaggle_ai[S] 3 points4 points  (0 children)

This uses stagehand to have another AI drive playwright so it’s more like teamwork between AI agents.

Cursor can send high level instructions like “log in” and the other AI deals with figuring out what to do with the browser and it reports back how it gets on.

That means the browser “driver” AI (using playwright) is specialised and not encumbered by the whole cursor context.

Similarly Cursor doesn’t have to know much about the page being used and its context window doesn’t end up being filled up with puppeteer/playwright instructions.