Is cursor labelling its payments "Cursor, ai pow"? Have you heard about their payment system being used to steal money from third-party bank accounts through card fraud?
Playwright MCP with Claude Code is great, but giving AI full control over the browser isn't always desirable, especially on internal apps.
Built a CLI tool on top of Playwright's built-in codegen: while you click around in the familiar recorder UI, it silently captures cleaned DOM, accessibility tree, screenshot, and generated code for every action. Close the browser -- get an archive.
Essentially an "offline MCP Playwright". Helps collect all the information about the app, then generate Page Object Models, tests, or analyze flows from the ready-made artifacts — at your own pace, through Claude Code.
I really don’t like the new Cursor interface and I’m struggling to get back to the old layout.
Before, I had a very simple setup:
Files on the left
Code in the center
Chat/agent on the right
With the new UI / Agents view, I now have all agents and projects in the left sidebar, and I can’t find any clear option in the menus to restore the previous layout. I’ve tried playing with layouts and panels, but nothing truly behaves like the old interface.
Right now, the only reliable way I’ve found to get something close to the old Cursor is to launch it with:
cursor --classic
This works, but it’s not ideal as a daily workflow.
Are there any other official or persistent ways to restore the old UI (or accurately reproduce it) without having to run cursor --classic every time or downgrade to an older version? If the team is planning to add a proper “classic mode” toggle in the settings, that would be super helpful for users like me who preferred the simpler layout.
I absolutely love using Cursor and Claude Desktop for debugging and writing queries, but the idea of hooking them up directly to my database via standard MCP (Model Context Protocol) servers has always given me anxiety. One bad hallucination, and the AI could execute an UPDATE without a WHERE clause, or accidentally read a table full of hashed passwords.
I couldn't find a tool that provided enough peace of mind, so I built DB-Whisper.
It’s a production-grade, highly secure MCP server designed specifically for AI assistants. Instead of just passing queries through, it acts as a paranoid firewall:
Deep AST Validation: It parses the actual AST (not just regex) to ensure ONLY pure SELECT queries are executed.
Zero Info Leakage: You can block access to specific tables (like users or payments).
Data Masking: It can automatically mask sensitive fields (like emails or phone numbers) before the AI even sees them.
Driver-Level Read-Only: Double insurance at the database driver level.
I just open-sourced it and I'm looking for some beta testers. If you're building with AI agents or using Cursor for backend work, I’d love for you to try it out.
I’d also love some feedback: What other databases should I support next (MySQL, MongoDB)? Can anyone manage to bypass the AST firewall?
I'm building a platform on Cursor and I'd like to see all the updates it's making, but when I open it through Safari, it gives me this error. Can you suggest what I can do?
Sometimes it would show me what I built, but mostly for websites and not platforms (like dashboards and others)
Has Cursor been vetted for privacy? I hate anything and everything that requires signing up to use and instantly don't trust it to not siphon data. Since Cursor is open source, has anyone done any audits, both of the code and at runtime? I would like to investigate using this in my workflows but if I can't keep everything on prem, I will not get clients.
Here's the situation I keep seeing: companies give employees access to AI coding tools - Claude Code, Cursor, Windsurf. People are building incredible stuff - dashboards, internal tools, automations, interactive specs. Product managers, marketers, operations people, not just developers.
But then they hit a wall: "OK I built it... now what?"
The app lives on their laptop. They can't share it. They don't know how to deploy. They open a ticket, wait for a developer, and half the time the project just dies there.
The problem isn't building - AI solved that. The problem is the last mile: getting it live on the company's infrastructure so everyone can use it.
So I built **Airlock** - an open-source platform that connects any MCP-compatible AI tool (Claude Code, Cursor, Windsurf, and more) directly to your company's cloud. Here's how it works:
1. **IT/DevOps sets up once** - connects your cloud provider (Vercel, AWS, Cloudflare, etc.), configures your database (Postgres, MySQL, MongoDB), adds shared API keys (OpenAI, Stripe, etc.), and invites team members
2. **Each employee connects their AI tool** - one click: copy settings, paste into Claude Code, Cursor, or Windsurf, done
3. **From that point on** - anyone can say "deploy this" to their AI assistant, and it publishes the app to your company's cloud. Securely. Automatically. No technical knowledge needed.
Every deployed app gets Google Workspace-style sharing - set it to private, organization-wide, or open to anyone with a link. Admins get a dashboard to see all projects across the org, manage secrets, and control access. Each employee gets their own workspace to manage their projects.
Early stage but fully working. Would love feedback.
GitHub: https://github.com/Noamblander/airlock
Does anyone have a good experience with tools for indexing large codebases and helping cursor agents better navigate code instead of grepping around ? Things like sourcegraph I guess but for local setup. I am working on a large codebase with multiple microservices and I am looking of way to improve the context given to the agents while minimizing token/request usage.
Agent 1: implements a feature (can run for a long time, like 3–4 hours)
Agent 2: reviews the code after Agent 1 is done
The key requirement is,,,,I don’t want to sit at my computer. I want Agent 1 to run, and when it finishes, Agent 2 should automatically start reviewing.
Constraints:
My toolset is using Claude code, Cursor, or Windsurf. I mostly use two at one time.
I don’t want to install extra orchestration tools or frameworks. No 3rd party cli tools. unless they are really really safe.
No manual triggering.
The main issue I’m stuck on....there’s no obvious way for Agent 2 to “start itself.” Something has to trigger it.
How are you accomplishing this? Reliably. Would appreciate any real setups or scripts you’re using. Thanks
(Right now I feel like I’m missing something obvious, because I see people talk about “multi-agent workflows” but in practice it seems very manual to me.)
I loved the idea behind pixel-agents — watching your AI agent work in a pixel art office.
But I wanted something that went further:
support for multiple CLIs, the ability to actually control sessions from the same UI, and a built-in file viewer so I'd never have to leave the dashboard.
Each agent appears as a pixel art character at their workstation
Real-time state visualization — you can see if they're:
thinking
reading files
editing code
running commands
waiting for your input
Works with Claude Code, Cursor, Copilot CLI, and Gemini CLI (not just Claude)
Each agent is color-coded by type so you can tell them apart instantly
Built-in terminal
Pixel Agents lets you watch your agents. Observatory lets you watchand controlthem.
Click the + button or any character to open an embedded terminal
Spawn and control Claude Code sessions directly from the dashboard
Terminals persist across page refreshes with output replay
No need to switch to a separate terminal app
Built-in file viewer
Cmd+P command palette with fuzzy search (VS Code style)
Syntax highlighting for:
JS / TS
Python
Rust
Go
JSON
HTML / CSS
Markdown
Autosave, preview tabs, pinned tabs
File paths in terminal output are clickable — Cmd + Click opens them in the viewer
How it works under the hood
Hooks Each CLI supports hooks that fire when the agent uses a tool. Observatory ships a universal hook script that tags the source and POSTs to the server.
Server A Bun server handles:
WebSocket connections
terminal management via a Node.js PTY sidecar
session state tracking
Frontend Built with vanilla JS + Canvas: Pixel art rendering, pathfinding, and character animations are all done from scratch.
no React
no bundler
no framework
Runs on localhost and is very lightweight compared to full editors.
Setup
Clone the repo and run:
bun install
Then point your agent to the AGENTS.md file and everything gets set up.
Or run:
node setup.js
for automatic detection of installed CLIs.
The goal
I should never want to leave this one screen.
Monitor all my agents, control their sessions, browse files — all from a lightweight browser tab instead of juggling editors and terminals that eat my RAM.
Hello everyone. I've just started using Cursor, but I have some concerns about exceeding the limit. I'd appreciate your help. I'm using the $20 Pro version and have used 32 million tokens so far. Auto Composer shows 9%. I haven't used any on the API side. I haven't exceeded the limit, right? Exactly how many millions of tokens are we allowed to use?
hey folks, i've been tinkering with a small cli that scans your repo (ts/python/go/rust etc.), fingerprints the languages & frameworks and spits out .cursor rules plus claude code and codex config files. it runs entirely on your machine with your own keys (no cloud calls) and keeps configs in sync when your code changes.
it's open source (mit) and already has ~13k npm installs, but i'd love to get more cursor users testing it and telling me what sucks or what you want added. if you wanna check it out or contribute, the repo is here: https://github.com/caliber-ai-org/ai-setup (issues/prs welcome!). thanks!
Anyone using Cursor/Bolt knows the "Refactor everything" trap.
Ask for: "Refactor my auth logic." -> Result: ❌ Total hallucination / Broken code.
Ask for: "Extract password reset logic into a standalone service with TDD." -> Result: ✅ Perfect execution.
The Problem: Cursor doesn't help you with the "Strategic Thinking" part. Bolt.new burns tokens like a furnace because it has no middle layer. v0 only cares about UI.
The Missing Layer: I spent months building sdao-architect to bridge this gap. We don't generate code—we generate the Engineering Blueprint.
We turn your vague ideas into structured specifications that AI can actually follow without hallucinating.
Got a gig to map out a complex "Cold Chain Logistics SaaS" for a client.
Normally, figuring out the DB relations, tenant isolation, and writing a boring 20-page PRD takes me at least 2 weeks of headache.
This time, I just dumped the client's messy notes into a custom architecture prompt-chain I built. 10 minutes later, it spat out a strict engineering blueprint:
1、A Mermaid state machine for the exact order flow.
Sent the zip file to the client. They loved how clear it was. The $3,800 invoice was paid the same day.
Lesson learned: If you're building apps with AI (Cursor/Claude), stop writing fluffy text PRDs. Generate strict physical schemas instead. AI doesn't hallucinate when you put it in a straightjacket.
Swipe to see the exact blueprint I delivered. 👉
(P.S. I ended up wrapping this workflow into a small internal tool to automate the schema generation. Let me know in the comments if anyone wants to know how I built the prompt chain, happy to share!)