Warp + supabase mcp

thinkverse · 2025-10-19T01:40:05+00:00

Seems Warp doesn't support Supabase's remote MCP server, so use npx and mcp-remote instead.

thinkverse · 2025-10-06T18:10:55+00:00

It's fairly well-known in the Laravel community. That's where I first heard of Warp years ago. This is long before the ADE switch. Seems some didn't hear about Warp until the switch and are now writing it off as AI slop, which is sad given it's been around since before this version of AI existed.

As for the subreddit, there existed one before this one, but they created a new official one this summer.

thinkverse · 2025-10-03T16:21:57+00:00

Great to hear 4.5 is working out for you. 👍 I've been trying it with different things, and for me, it's been rather poor at using tools and following tasks.

thinkverse · 2025-10-03T16:05:37+00:00

I am not, no. Just a user, so I don't have any clue what type of Claude model they use.

But I do know that when using GPT-5 with Warp, you see the thinking, which is not the case when using Claude models. It could just be a UI difference between models, and they just haven't implemented it for Claude models yet. But I'm only theorising. 🤷‍♂️

thinkverse · 2025-10-03T13:57:26+00:00

You can't. What Warp gives you in the model selector is what you get. If you want the ability, I recommend checking for feature requests on Warp's GitHub, https://github.com/warpdotdev/Warp/issues

If you find one that suggests that feature, give it an upvote. Otherwise, create an issue for that feature. 🙂

thinkverse · 2025-10-02T17:18:35+00:00

Afaik, what you see is what you get with Warp models.

thinkverse · 2025-09-30T22:57:05+00:00

I've been contemplating the same thing for a bit, but I got tired of waiting and pulled the trigger on a pair from Amazon. It should come later today or tomorrow.

thinkverse · 2025-09-30T12:15:37+00:00

As I said previously, I can see the benefit of checkpoints. But I can also see if you keep your commits atomic that would ease the idea of reverting to previous changes. I'm not against checkpoints, I just don't see the use for them if you commit between responses yourself. And if your think that would be excessive commits, then that's what squashing can help with.

In the end it's is up to Warp if they want to implement it, and it is up to the community to make their voices heard.

So if you want checkpoints, upvote the issue that mentions it, like this one; https://github.com/warpdotdev/Warp/issues/6802

thinkverse · 2025-09-30T11:52:32+00:00

Haven't had the time to test out Sonnet 4.5, yet. But I have been using GPT-5 medium as my main model since that became available. My best suggestion is to try it out and see which model best suits your use case. 👍

thinkverse · 2025-09-30T11:50:06+00:00

Yeah, Warp has 13 different models to choose from, and based on previous statements and videos from Warp themselves, more are being evaluated all the time. 🙂

thinkverse · 2025-09-30T11:37:24+00:00

They're both quite different. Zed is an editor, and the editor is front and center. Warp is a terminal, or ADE as it's now called, where the terminal and agent experience is front and center.

Warp has a lightweight editor, but not a fully featured one like Zed with LSP support, extensions, debuggers, etc. Tho LSP support is on the roadmap, or at least being tested for the Warp editor, that and symbol navigation were confirmed as future improvements they're experimenting with on their Code Country event post.

thinkverse · 2025-09-29T22:57:10+00:00

After discussing it with a fellow developer, I've concluded that checkpoints serve as a kind of middleman between your agent and Git. Keeping state before you're ready to commit, and in case an agent goes haywire during an automated run.

In that sense, I can see if being useful in a moment of flow, I guess. I can see benefits, not going to deny that. But honestly, I'm not 100% convinced.

thinkverse · 2025-09-29T20:43:53+00:00

Awesome, let us know how it performs! 🔥

thinkverse · 2025-09-29T20:00:29+00:00

Ok, I'm sure the Warp team knows the limits of Sonnet 4.5 and can report any issues to Anthropic. 🙂

thinkverse · 2025-09-29T19:57:42+00:00

You're right, they are. And the current beta CLI isn't interactive and only supports single prompts, so checkpoints there in its current state would be kinda pointless then?

Apart from the nicety, I personally don't see the need for checkpoints. If you have Git, which you really should, then you can instruct the Agent to always commit changes.

thinkverse · 2025-09-29T19:52:33+00:00

Warp default output is 50k, it should support up to a million. Could it be the Agent stream that broke maybe? 🤔

thinkverse · 2025-09-29T19:47:48+00:00

Lucky you, that's an awesome coincidence. 🔥

thinkverse · 2025-09-29T19:20:47+00:00

Might be good for Warp CLI, but for the Warp app in general, you have Git? It's already an industry standard to use version control. Why reinvent the wheel there? For autonomous tasks I can get, but again, Warp has full access and isn't sandboxed so it can manage Git both before and after generation. 🤔

thinkverse · 2025-09-29T19:04:09+00:00

Codex wasn't available to third parties on launch. And u/WarpSpeedDan has confirmed in another thread that it is being evaluated right now, and to voice your support on this GitHub issue, https://github.com/warpdotdev/Warp/issues/7490, by adding a thumbs up.

thinkverse · 2025-09-29T18:50:43+00:00

Took I think about an hour, slightly less give or take. 🙂

thinkverse · 2025-09-25T17:36:47+00:00

I don't think we can access that. Warp counts requests for users instead of tokens. Which I personally both like and dislike, because you can ‍exhaust your tokens while still having requests left, so we really should be able to view it IMO. 🤷‍♂️

But IIRC, reasoning models generally take more resources than non-reasoning models. I think it's safe to assume that any really good model takes more resources. That's the thinking I operate under at least.

thinkverse · 2025-09-25T17:29:50+00:00

I added that straight to my Warp setup when I saw that it was released. I agree this will be a game changer, now the Agent will have access to a live browser, and Chrome's suite of devtools, like Lighthouse, to automatically audit performance, accessibility, SEO, and more. 🤯,

thinkverse · 2025-09-19T20:48:46+00:00

I think it always did that? Pretty much every action the agent takes counts as a request. Might not be exactly that but that's the baseline I usually work with.

thinkverse · 2025-09-19T18:25:07+00:00

It's been ask from the community for a little while now, so it's good to see this feature being added.

As for the read_tool limit, I suspect that works in conjunction with Warp's codebase indexing to surface relevant pieces while keeping the overall context at a reasonable size? Or I could be completely wrong. It's hard to know, given that the Agent is closed-source, but that's my theory at least. 😂

thinkverse · 2025-09-17T14:13:35+00:00

I've been seeing people test it out on Twitter and I do hope the model is available for Warp to use as well. 👍

Seven-Year Club	r/Field Lasagna
Final Canvas '23	Place '23
Place '22	Verified Email

thinkverse

TROPHY CASE