I Replaced 5 Browser Tabs With One CLI and My AI Agent Got Scary Good
Let me set the scene: I’m debugging something mundane, ask Claude “hey, what’s blocking this ticket” and instead of the usual shrug — “I don’t have access to your Jira, can you paste the details?” — it just… tells me. Linked PR, four commits, twenty CI runs, the parent epic, the sprint. Like it had been sitting in on every standup I’ve ever skipped.
That’s TWG. And I have complaints, compliments, and a mild identity crisis about what it means for how I work now.
Okay, but what is it?
TWG stands for TeamWork Graph, which is a very serious name for a tool that is basically a nosy coworker who’s read every Jira ticket, every PR, every Confluence page, and every Slack thread in the company, and will happily gossip about the connections between them if you ask nicely.
Technically, it’s a CLI that pre-joins Jira, Confluence, GitHub/Bitbucket, and Slack into one graph you can query. Practically: it’s the thing that lets an AI coding agent stop pretending it lives in a sealed room with only your git log for company.
Isn’t this just the Atlassian MCP with a costume on?
No, and this is the part everyone gets wrong on first glance.
An MCP integration is a translator. You ask for a Jira ticket, it fetches a Jira ticket. You ask for a PR, it fetches a PR. Every question is a separate trip, and if your question actually spans three systems — “is this ticket done, and did the fix actually ship, and who reviewed it” — you’re the one holding four API responses together with narrative glue.
TWG skips the glue. It already did the joining, ahead of time, so a single query returns the shape of the work, not just one flat fact about it:
$ twg context get SOME-TICKET
Code → linked PR, 4 commits, 20 CI runs
People → assignee
Delivery → parent epic, sprint, project
One call. No stitching. The MCP is a phone line to one office; TWG is the org chart, the seating map, and the group chat, already cross-referenced.
Here’s the plot twist nobody warns you about
Give a tool this much cross-system visibility and it will, without fail, immediately snitch on your organization’s data hygiene.
Ask it for every ticket under a label your team’s been using for years, and there’s a real chance it comes back empty — not because the tickets don’t exist, but because someone typed the label as DMIntegration in 2023 and everyone since has been assuming it was dm-integration with a hyphen like a normal person. TWG doesn’t fix that. It just holds up a mirror and says “this is what you actually have,” which is somehow both incredibly useful and mildly enraging.
Same story with status fields. A ticket marked “In Review” feels like it should have a PR attached. Sometimes it doesn’t — because “in review” meant a design doc, not code, and nobody updated the status. TWG won’t lie to make the ticket feel more finished than it is. It’ll just tell you: no PR exists. Which, annoyingly, is usually correct.
The tool isn’t smarter than your process. It’s just the first thing that’s ever been honest about your process at this scale.
Where it actually pays off for me + my agent
I don’t run TWG by hand most days — the AI agent does, mid-conversation, because a bunch of skills are wired to reach for it automatically. What that unlocks in practice:
- What’s blocking this ticket? — one call returns the PR, builds, epic, sprint. No tab-switching.
- “Is this actually shipped, or just marked done?” — cross-checks the ticket against merged code, which catches the special kind of lie where a ticket says “Done” and the branch says otherwise.
- “Catch me up on this while I was out” — reconstructs what changed across systems without me reading three days of Slack.
- “What’s actually on my plate?” — a real rollup, not a vibes-based guess from memory.
The point isn’t that TWG is magic. It’s that it turns “let me go check four places and get back to you” into “here,” which is the entire difference between a tool that assists you and a tool that just adds more tabs.
The part where I tell you to actually try it
If you want to poke at it directly instead of letting an agent do it for you:
twg whoami - sanity check that you're actually logged in
twg doctor - full health report on auth, connectors, everything
twg context get <KEY> - the whole graph for one ticket, PR, or doc, in one shot
twg jira workitem query '<JQL>' - for when fuzzy search is lying to you (it will, eventually)
twg rovo list-apps - see what's actually connected before you blame your permissions
twg work-tree / twg pr-tree - a rollup of what's yours right now
The actual takeaway
TWG isn’t replacing your API integrations. It’s replacing the fifteen minutes you spend every day manually being the API integration — clicking between Jira and GitHub and Slack, holding the whole picture in your head because nothing else will.
It won’t fix your mislabeled tickets. It won’t write your missing PR. But it will tell you, immediately and without flattery, exactly which of those problems you actually have — which turns out to be the more valuable thing most days.