What I'd like
I'd like to be able to hand a task off to Devin from inside jcode, without leaving the session to go set it up somewhere else.
Why
Some work is slow, boring, or just better done in the background: big refactors, dependency bumps, chasing flaky tests, clearing out backlog chores. Right now jcode is great for the work I'm doing right now, but there's no good way to say "go do this one on the side and tell me when it's done." Devin is built for exactly that, so it would be nice if the two could talk to each other.
What it might look like
- I point jcode at a task and say "send this to Devin."
- jcode starts the run and keeps track of it, the same way it tracks other background work.
- I can check on it, send follow-up notes if Devin asks a question, and get pinged when it finishes or gets stuck.
- When there's a pull request at the end, jcode shows me the link.
- Setup should be a one-time thing: drop in an API key and it just works.
Nice to have
- A quick way to see everything currently running on Devin.
- A short doc explaining when it's worth delegating to Devin instead of doing it locally.
Open questions
- Should this feel like part of the existing swarm/background-task flow, or its own thing?
- How much should jcode surface about cost/usage?
What I'd like
I'd like to be able to hand a task off to Devin from inside jcode, without leaving the session to go set it up somewhere else.
Why
Some work is slow, boring, or just better done in the background: big refactors, dependency bumps, chasing flaky tests, clearing out backlog chores. Right now jcode is great for the work I'm doing right now, but there's no good way to say "go do this one on the side and tell me when it's done." Devin is built for exactly that, so it would be nice if the two could talk to each other.
What it might look like
Nice to have
Open questions