Pick an issue 1
Open the issue you're working on. It becomes a room — title, context and prior conversation already in place.
Issue-first developer collaboration
Pull a partner into your issue. Work it together, in one chat.
jkx opens a live channel around every issue. Invite a partner — a teammate or an AI — into the same room, with the full ticket context already on the table. Trade insights, not screenshots.
Picking this up. Why are retries still firing
after a
410 Gone?
The retry policy treats
410 as transient.
In retry.ts:43 only 5xx +
network are gated. Want me to draft the patch?
Yes — and add a test for
410.
Reply in #UBR-582…
▍
How it works
Three steps, one conversation
jkx makes the issue itself the unit of collaboration. Open it, invite the people (or agents) who should be in the room, and keep the dialogue in one place.
Invite a partner 2
Pull a teammate or an AI agent into the same room. They walk in with the context — no copy-paste, no re-explaining.
Trade insights 3
Discuss, ask for diffs, request explanations. The conversation stays with the issue — so the next person picking it up already knows the story.
What's inside
Built so the conversation carries the context
One channel per issue
The ticket is the room. Anyone you invite walks in with the context already in place.
Human or AI partners
Invite a teammate to pair, or an AI agent for fast insights. Same room, same rules.
Conversation stays with the work
The discussion lives where the issue lives. The next person picking it up already knows the story.
Pair from any device
Phone, laptop or browser — same room, same conversation. Walk between them without losing your place.
Stop forwarding screenshots. Pair on the issue.
jkx makes the ticket the room. Bring a partner in — and keep the whole conversation attached to the work.