v1.0.0 — Now Available

Your AI Coding Agent
for Jira + Git

One command. AI picks up your work, creates a Jira ticket, checks out the right branch, and pushes code — automatically.

→ Get Started View Commands
zsh — nxt-agent
$npm install -g nxt-agent
✓ nxt-agent installed globally
$agent auth
🌐 Opening Jira authorization in browser...
✅ Jira Connected: xxx
$agent task
? Which AI model are you using? › OpenAI
? Overview: Add dark mode to settings page
🎟️ Ticket Created: PROJ-421
🌿 Created branch: feature/PROJ-421-add-dark-mode
🚀 Pushed to origin
What it does

Built for engineers who ship fast

Every command is designed to reduce the gap between intent and execution.

🤖

Any AI Model

Works with OpenAI, Claude, Gemini, Grok, or any tool you use. Model-agnostic by design.

🎟️

Real Jira Tickets

Creates issues directly in your Jira project via OAuth — no copy-paste, no tab switching.

🌿

Smart Branching

Detects existing representative branches per ticket. Reuses or creates — never duplicates.

👀

Activity Monitor

Watches your workspace for file changes and prompts ticket flow the moment you start coding.

🔐

OAuth 2.0 Auth

Secure browser-based login. Tokens stored locally. No copy-pasting API keys.

📦

Auto Commit & Push

Jira Smart Commits format. Commits linked to tickets. Pushed to your remote automatically.

Installation

Get running in 3 minutes

Choose your setup type below. Individual for solo developers, Organization for team rollout.

Step-by-step setup

Install globally via npm

🚧 Coming Soon — npm package publish in progress. Check back shortly.

Authorize with Jira

Run the auth command. Your browser will open — sign in and click Allow.

terminal 
agent auth
✅ On success, you will see: Jira Connected: your-workspace-name

Verify connection

terminal 
agent status

You should see your workspace name, account, site URL, and a valid token status.

Run your first task

terminal 
agent task

Fill in the prompts: AI model, overview, expected outcome, acceptance criteria. Agent handles the rest.

ℹ️ For organizations, each developer installs nxt-agent independently but shares the same Atlassian OAuth App credentials via a shared .env.example in your repo.

Admin: Create one Atlassian OAuth App for your org

One admin creates the OAuth app on Atlassian. All team members use the same Client ID and Client Secret.

→ Go to developer.atlassian.com/console/myapps → Create OAuth 2.0 (3LO) app → Callback URL: http://localhost:3000/callback → Scopes: read:jira-work read:jira-user write:jira-work

Admin: Add .env.example to your repo

Commit this file (no real values) so every developer knows exactly what to set.

.env.example 
# Atlassian OAuth App (get from your team admin)
JIRA_CLIENT_ID=
JIRA_CLIENT_SECRET=

# Your Jira project key (e.g. PROJ, WEB, APP)
JIRA_PROJECT_KEY=PROJ

# Do not change unless using a custom redirect
JIRA_REDIRECT_URI=http://localhost:3000/callback
⚠️ Add these to your repo's .gitignore: .env and .agent/

Each developer: Install and configure

terminal 
# 1. Install
npm install -g nxt-agent

# 2. Copy and fill in credentials
cp .env.example .env
# (edit .env with Client ID and Client Secret from admin)

# 3. Authorize — opens browser per-developer
agent auth

# 4. Verify
agent status
ℹ️ Each developer's agent auth authorizes under their own Atlassian account. Tickets are created as that developer in Jira.

Standardize project key across the team

Set JIRA_PROJECT_KEY to your main project key. This ensures all team members create tickets in the same Jira project automatically.

.env 
JIRA_PROJECT_KEY=MYPROJECT

Optional: Enable auto-monitor on workspace start

Add to your project's package.json scripts so monitor starts automatically when developers open the project:

package.json 
"scripts": {
  "dev": "agent monitor & your-dev-server"
}
CLI Reference

All commands

Every command the agent exposes, with what it does.

agent auth
# Opens browser for Jira OAuth login.
# Saves access token, refresh token, workspace, cloudId locally.
# Must be run once per machine before using other commands.

agent auth
agent status
# Prints workspace path, Git branch, remote origin,
# live Jira connection, account name, email, token health.

agent status
agent task
# Interactive ticket + branch + code + push workflow.
# Prompts: AI model, overview, expected outcome, acceptance criteria.
# Reuses existing branches matching the ticket ID if found.

agent task
agent task "add dark mode"   # optional seed prompt
agent monitor
# Watches workspace for file changes.
# Shows macOS native popup + terminal prompt when activity detected.
# Auto-starts if authenticated and no explicit command is given.

agent monitor
Configuration

Environment variables

All configurable values for .env

Variable Required Default Description
JIRA_CLIENT_ID Required — From Atlassian Developer Console OAuth app
JIRA_CLIENT_SECRET Required — From Atlassian Developer Console OAuth app
JIRA_PROJECT_KEY Required PROJ Your Jira project key (e.g. APP, WEB, CORE)
JIRA_REDIRECT_URI Optional http://localhost:3000/callback OAuth callback URL — must match Atlassian app settings
JIRA_SITE Optional — Fallback workspace URL if accessible-resources returns empty
⚠️
Always add to .gitignore:
.gitignore 
.env
.agent/
Get Early Access

Interested in nxt-agent?

We're onboarding early users and teams. Reach out — we'll get you set up personally.

→ hello@nxtgenstack.in

No spam. Just a human reply.