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 and writes the fix. Set PR or merge tools to Ask to pause for approval in Slack, or Block to deny them.
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 Dev, Yasmine uses dedicated Fargate compute. Runtime identity, repository state, and credentials are tenant-scoped and encrypted; AWS may operate the underlying hosts. You can use included models or an eligible supported connection, and selected providers process requests under their terms. Push and PR actions follow the workspace's Allow, Ask, or Block policy.
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