Item detail

joewinke/jat

joewinke/jat is an MIT-licensed, open-source agentic IDE that pairs an AI agent harness with a visual dashboard for live sessions, task management, an embedded code editor and terminal, and parallel swarm workflows with auto-proceed rules, so AI coding agent builders and developer-tools teams can ship a single workspace that runs many AI coding agents side-by-side instead of juggling separate CLIs

Score7.9
Popularity8.0
Risklow
TierGold
Score breakdown
Usefulness8.0
Novelty9.0
Momentum7.0
Maturity6.4
Open-source/build8.4
Evidence7.2
Workflow potential9.4
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for AI coding agent builders, developer-tools teams, and power-user developers who need an MIT-licensed, open-source agentic IDE that pairs an AI agent harness with a visual dashboard for live sessions, task management, an embedded code editor and terminal, and parallel swarm workflows with auto-proceed rules, so they can ship a single workspace that runs many AI coding agents side-by-side

Who should use it

AI coding agent builders who need an MIT-licensed, open-source agentic IDE that runs many AI coding agents side-by-side from a single visual dashboarddeveloper-tools teams who want a workspace that combines an AI agent harness, task management, an embedded code editor and terminal, and parallel swarm workflowspower-user developers who need an MIT-licensed agentic IDE with auto-proceed rules and live session visibility instead of juggling separate CLIs and chat windowsopen-source contributors who want an MIT-licensed alternative to closed-source, vendor-locked AI coding agent IDEs

Who should skip it

Skip if the source link, docs, or setup requirements do not match your workflow.

Risk explanation

It is an MIT-licensed agentic IDE that runs AI coding agents in parallel with auto-proceed rules, so review which auto-proceed rules are enabled by default, scope which repositories and files the agents can touch, confirm audit log retention and rollback discipline match your developer-tools security requirements, and gate any production rollout behind a code-review checkpoint before enabling parallel swarm workflows against shared codebases.

Evidence links

Closest alternatives / related signals

agentic-ideai-codingai-agentsswarmparallel-workflowsdeveloper-toolsopen-sourcemit