the demo cut where the agent opens the PR without any dramatic zoom is honestly restraint I don't see enough of in launch videos. felt like watching a coworker not a magic trick.
G
Gabi Orłowska25d ago
any chance you'd share how you decided on Magic Sessions as the name over something more literal? asking because I'm writing about the naming trend in this category.
K
Kofi A.25d ago
issue to PR is the loop everyone claims to have solved but the tests step is where most of them faceplant. curious how you handle flaky ones without the agent just rerunning until green.
D
Denis Marquez25d ago
ok wait, are Magic Sessions scoped per repo or can one session touch a monorepo with multiple services? this is the difference between toy and tool.
R
Reetu M.25d ago
quick naive question, what happens if the agent picks up an issue that was already closed or is a duplicate? does it just work on it anyway?
Y
yuko25d ago
the tweet copy is doing that bullet list thing every AI launch does this month. would love to see someone break format and just post the raw PR link with no words.
S
Sven Lindqvist25d ago
building in the review-side of this problem and honestly rooting for you. if agents can open clean PRs my life gets easier, if they open slop PRs my life gets busier, either way I win.
C
Chibuzo G.25d ago
one more thing for the roadmap: let me queue five issues at once and get five draft PRs in the morning. batch mode is the real unlock.
A
Amara Okafor25d ago
hot take: 'ships like engineers' is a bold claim when most engineers I know don't ship either. call it what it is, a very patient junior.
T
Tomasz B.25d ago
we built something adjacent inside a big co in 2019 and shelved it because CI costs exploded. curious how you're modeling that here, because agents love to run the suite twelve times.
L
Liana Sparks25d ago
the video pacing is tight but that first four seconds needs a hook. right now it opens on a repo view which reads as 'ignore me' to anyone scrolling.
M
Mehdi Rezvani25d ago
reference points from my portfolio would put this closer to the async coworker category than the copilot category. positioning matters here, don't let people file you under autocomplete.
H
Hyeri Woo25d ago
compared to the last handful of coding-agent launches this week the demo actually shows a merge-ready diff instead of a terminal spinner. small bar, cleared.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
Trylle
The Git platform where agents ship like engineers.
The Git platform where agents ship like engineers.
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
Comments (13)
the demo cut where the agent opens the PR without any dramatic zoom is honestly restraint I don't see enough of in launch videos. felt like watching a coworker not a magic trick.
any chance you'd share how you decided on Magic Sessions as the name over something more literal? asking because I'm writing about the naming trend in this category.
issue to PR is the loop everyone claims to have solved but the tests step is where most of them faceplant. curious how you handle flaky ones without the agent just rerunning until green.
ok wait, are Magic Sessions scoped per repo or can one session touch a monorepo with multiple services? this is the difference between toy and tool.
quick naive question, what happens if the agent picks up an issue that was already closed or is a duplicate? does it just work on it anyway?
the tweet copy is doing that bullet list thing every AI launch does this month. would love to see someone break format and just post the raw PR link with no words.
building in the review-side of this problem and honestly rooting for you. if agents can open clean PRs my life gets easier, if they open slop PRs my life gets busier, either way I win.
one more thing for the roadmap: let me queue five issues at once and get five draft PRs in the morning. batch mode is the real unlock.
hot take: 'ships like engineers' is a bold claim when most engineers I know don't ship either. call it what it is, a very patient junior.
we built something adjacent inside a big co in 2019 and shelved it because CI costs exploded. curious how you're modeling that here, because agents love to run the suite twelve times.
the video pacing is tight but that first four seconds needs a hook. right now it opens on a repo view which reads as 'ignore me' to anyone scrolling.
reference points from my portfolio would put this closer to the async coworker category than the copilot category. positioning matters here, don't let people file you under autocomplete.
compared to the last handful of coding-agent launches this week the demo actually shows a merge-ready diff instead of a terminal spinner. small bar, cleared.