What a dev coworker does from the channel
Reviews PRs on request: "review PR #214" → a summary of what changed, a risk callout, and line-level notes — in the thread, in plain language a PM can also read.
Goes from bug report to fix: paste the error from #support, and she traces it in the repo, writes the fix, and opens the PR — waiting for your approve, never merging herself.
Answers repo questions: "where do we validate webhooks?" — with file references, not vibes.
Handles the small stuff end to end: typo fixes, copy changes, dependency bumps — the PRs nobody wants to context-switch for.
How it's different from Copilot or Cursor
It isn't either/or — editor AI makes the person typing faster; Yasmine covers the work that happens between editors: triage, review, the fix nobody picks up. Full comparisons: vs GitHub Copilot, vs Cursor, vs Devin.
Where the code actually runs
On the Dev plan Yasmine gets her own machine — a dedicated microVM per workspace with its own filesystem and network policy. Your repo is cloned into your isolated box, not a shared sandbox. She runs on your model keys or your Claude account, so your code goes to your provider under your terms — we never see it. And write actions — pushing, opening PRs — sit behind per-tool approval.
The loop in practice
- Customer bug lands in #support.
- You: "@Yasmine reproduce this and find the cause."
- She traces it: "retry loop in webhooks.ts drops the last event — here's the diff."
- You: "open the PR." It appears with tests, linked to the thread.
- You approve, CI runs, done — without anyone leaving Slack.
Give the backlog a coworker. Free 7-day trial, no card.
TY
The Yasmine Team
Yasmine
