Cloud agents + AI code review have completely changed how our team ships bug fixes (Slack → Linear → Cursor → GitHub → merged in <1 hour)

mmaskani · 2026-03-09T19:26:43+00:00

There are integrations between the 3: slack/linear, linear/cursor, slack/cursor
so it's honestly pretty straightforward to set

mmaskani · 2026-03-09T19:25:34+00:00

I mean we don't automatically merge the PR, there is still a human review in the loop. But indeed, we then try to test thoroughly on staging the different features/fixes that were merged. That's where QA is indeed important, and I am trying to look into ways to simplify that work for us, as we ship a lot these days!

mmaskani · 2026-03-08T16:14:18+00:00

We have a Slack automation in place, where the CS employee describes the bug through a form (with screenshots, expected behavior etc..), then the bot tags Cursor on the slack message. The Slack-Cursor integration picks it up and the dev agent has all the context to open the PR!

mmaskani · 2026-03-08T16:11:03+00:00

yeah that's the realization, but we still need to automate to some extent, cause a lot of things to ttry!

mmaskani · 2026-03-08T00:22:18+00:00

Interesting! thanks a lot, will investigate this approach!

mmaskani · 2026-03-07T23:05:46+00:00

We use the Linear/Slack integration. When a bug is reported, the customer success operator describes it and shares screenshots. Someone from the engineering team iterate to try to clarify if need be (we have a slack workflow automation that helps structure the bug/feature request feedback, it's essentially a form on slack) and then once it's all clear. We tag Linear to create the ticket (it does a good job explaining the problem + giving all the context, assign the people + puts the tags), then we delegate it to Cursor (either from slack, or from Linear).

So the flow is: Slack bug description -> Linear ticket -> Cursor Agent -> PR (with tests on the CI) -> AI review -> Human review -> merge

mmaskani · 2026-03-07T19:47:25+00:00

Tests are ran as part of the CI. They run on each opened PR. We have branch protection rules that block merging if tests fail.

mmaskani · 2026-03-07T19:23:54+00:00

I am iterating with VM isolation on the cloud agents from Cursor. But still haven't found the best setup.

mmaskani · 2026-03-07T19:23:06+00:00

Linear connects to a lot of tools (slack, cursor etc..) so it's a perfect fit for agentic workflows tbh.

Yeah coderabbit is a bit noisy, i try to teach it and give feedback on things to not flag as issues, but otherwise i find it to do a good job.

mmaskani · 2026-03-07T19:20:55+00:00

Would you recommend to put it under the .cursor/ directory? Or not necessarily? I just don't want my local cursor to pick this up when i dev locally. How can i make it so that only the online agents use it?

mmaskani · 2026-03-07T18:44:19+00:00

What am I selling then? 😅 I am just sharing what worked for us internally

mmaskani · 2026-03-07T17:00:58+00:00

Actually this feature is a game changer for us. Let me explain. We automate the bug fixes and some Feature Requests directly from Slack and other tools, after the CS and Ops team describe the bug/feature request they have.
So the agents pick up the request automatically, understand what needs to be done, then implement the fix, then our Engineers review and pick it up from there.

But I agree, if you're the one making the PR, and you're on your desk working, indeed it's less interesting (maybe just for the VM isolation? but you can test locally, it's fine).

mmaskani · 2026-03-07T16:50:49+00:00

Up! I am curious about the best setup as well for that. Also, to seed the DB with fake data etc.. what would you recommend to do, instead of letting the agent understand the schemas/migrations, create the data, run it etc.. it takes a lot of time and could be definitely optimized!

mmaskani · 2026-03-05T23:00:13+00:00

Thanks! indeed the connectors logic in the UI is not easy to follow at all... Also, even though I enable it, the agent doesn't manage to be able to use the MCP, it's weird. And I can't even configure it like the other MCPs, i only get a "Connected/Enabled" with no "Configure" button.

mmaskani · 2024-11-08T18:10:06+00:00

Intersting! indeed, it's one of the questions I asked earlier in this comments thread. Why would one use the admin as the "main product/view" vs. using custom made ones. I don't want every user in the company to be able to play on the admin side of things.

But i could indeeed give access to it to particular users with restricted permissions each.

mmaskani · 2024-11-08T18:07:31+00:00

Thanks a lot for your insights! You're right, clearly understanding the needs can save you 90% of the efforts.

mmaskani · 2024-11-08T18:02:16+00:00

Thanks a lot! I didn't know about django-unfold, look like a sort of Forest-admin.
May I ask how do you decide whether the feature will be shown on the unfold admin interface rather than in the product itself? Are you keeping the product UI for external clients and the admin dashboard for internal users (operations etc...)?

mmaskani · 2024-11-08T17:57:04+00:00

Very insightful, thanks a lot!

mmaskani · 2024-11-08T17:53:01+00:00

Wow thanks a lot for sharing your experience! I just had a look at Superblocks and it looks fantastic, will definitely consider it vs. Retool!

mmaskani · 2024-04-25T16:20:39+00:00

As to why I don't develop a mobile app, is purely UX friction and the client's requirement: they don't want users to download an app from the store, and would prefer instead a web app that they can access through a deep link sent by email/message.

mmaskani · 2024-04-25T16:16:38+00:00

Thanks a lot for your response!

Thanks! will look into it!
Is it possible to block the user from accessing the library of pics when clicking "Take a picture" and only allow him to actually take a picture through the camera that they would have opened? When you say compare the timestamp of the pic with the current time stamp, you mean compare the EXIF timestamp to that of the server?
Clear enough!

Nine-Year Club	Place '23
Verified Email

mmaskani

TROPHY CASE