WORK ITEM
SUP-2
Customer support platform
IN PROGRESSAgent-ready work context
Your entire work world,connected in the terminal.
Atlassian Teamwork Graph CLI gives Codex the context behind every ticket, decision, document, person, and pull request—so it can move from scattered facts to grounded action.
✓ Permission-aware✓ OAuth 2.1✓ Built for AI agents
›
Research SUP-2 and map every related decision.
Querying connected work context
✓
Context assembled
4 sources · 7 relationships · permissions respected
CONTEXT LINKED
✦ CODEX READY
One context layer across your work stack
JJiraCConfluenceBBitbucketGGitHubSSlackDDrive+ connected tools
The context advantage
Not another search box.
A map of how work connects.
Teamwork Graph understands the relationships between work—not just the objects. Your agent gets the surrounding decisions, owners, dependencies, and activity it needs to reason well.
DECISION
Architecture brief
Why the current direction was chosen
RELATES TO SUP-2CODE
Pull request #21
Implementation, review, and test state
IMPLEMENTS SUP-2OWNERSHIP
Universal Dragon
Accountable owner and next action
OWNS SUP-201
→Connected records
Issues, docs, code, messages, people
02
→Relationship context
Ownership, history, dependencies, intent
03
Grounded action
Briefs, decisions, updates, execution
Universal Dragon workflows
Ask in plain language.
Act with full context.
The command is simple. The graph work behind it is not. TWG CLI follows the relationships across your tools and returns the context an agent needs to move the work forward.
01
Issue intelligence
Research before you build
›
Research SUP-2. Show decisions, owners, blockers, and related code.
JiraConfluenceGitHub
✓A grounded implementation brief—not an isolated ticket.
02
Release confidence
Turn changes into a release story
›
Prepare the QBIT NOVA release brief and flag unresolved risks.
JiraBitbucketDocs
✓Changes, intent, reviewers, and risk in one clear narrative.
03
Incident handoff
Take over without losing history
›
Give me the incidents, runbooks, owners, and open follow-ups.
JSMConfluenceSlack
✓The operational picture needed for a safe handoff.
04
Weekly command brief
Summarize momentum and drift
›
Summarize this week. What moved, stalled, or needs my decision?
ProjectsGoalsTeams
✓Progress, dependencies, and next decisions without tab-hopping.
One prompt to proof
Context moves through a clear trust path.
›_
Describe the outcome
Ask Codex what you need in natural language—research, summarize, prepare, or act.
⌬
TWG maps the context
The CLI queries allowed sources and follows relationships across the work graph.
✓
Codex delivers grounded work
You get a result tied to real issues, documents, people, decisions, and code.
Permission-aware by design
The graph only shows what you can already see.
Teamwork Graph CLI works through your authenticated Atlassian identity. Existing organization controls and user permissions stay in the loop while your agent gains connected context.
Explore authenticationOAuth 2.1 identity
Short-lived authentication tied to the user running the agent.
Existing permissions
No new access is created by installing or using the CLI.
Cloud-connected context
The local CLI queries Atlassian cloud services; an online connection is required.
Launch the command center
Bring Teamwork Graph context into Codex.
Install from a full interactive terminal, complete Atlassian OAuth, then verify the connection. The setup also installs the skills your agent uses to discover TWG commands.
01 macOS or Linux terminal02 Atlassian account access03 Interactive OAuth login
01
curl -fsSL --retry 2 https://teamwork-graph.atlassian.com/cli/install | bash -s -- --plugin codexAfter setup and OAuth complete, verify the connection:
02
twg doctor✓Ready when doctor is healthyBitbucket-specific commands require a separate token.
Open official installation guide
Never paste passwords, tokens, or one-time codes into chat.
Quick answers
Before you connect.
Is Teamwork Graph CLI the same as Atlassian CLI?+
No. TWG CLI is agent-first and adds graph-style, cross-product context. It is designed for AI agents working across connected work—not only human-driven administration.
Does it respect my existing permissions?+
Yes. The CLI surfaces only data the authenticated user is already authorized to access. Installing it does not grant new access.
Can it run offline?+
No. The CLI is a local binary, but it accesses Atlassian cloud data and services, so a network connection is required.
How does authentication work?+
TWG CLI uses OAuth 2.1. Bitbucket is the current exception and requires a separate Bitbucket token when you need Bitbucket-specific commands.