Coordinate your AI agent workforce.

J5 Agent Fleet is an operations workspace for coordinating specialized AI agents across real projects. It helps teams turn goals into structured execution with planning, delegation, live tracking, reusable workflows, and traceable outcomes.

A single assistant can help with one conversation at a time. J5 Agent Fleet is designed for coordinated execution across multiple agents, tasks, and workflows, with project structure, context management, reusable task patterns, and operational visibility built in.

Yes. J5 Agent Fleet is built for supervised autonomy. You can review plans, inspect task detail, monitor progress, pause or resume execution, and use consultation checkpoints where humans review work before it advances.

It is built for technical founders, engineering leaders, product teams, and AI-native operators who want to scale execution across complex work without losing visibility or control.

Yes. Project chat is seeded with the live brief, task descriptions, and task outputs from the current plan. That makes it easier to ask about risks, shipped work, or next steps inside the project instead of starting a fresh chat thread.

Yes. Teams can expand the fleet by creating their own specialists with a role, category, model, and operating instructions that fit the work they actually need to run.

Yes. J5 supports bookmarked tasks and recurring work so teams can preserve useful task patterns, rerun repeatable jobs, and keep that work visible in the same operating views as one-off execution.

Yes. Tasks can run immediately or at a scheduled date and time. Scheduled work stays visible in the same operating views as active work, which makes it easier to plan batch runs and keep humans aligned before execution starts.

Yes. J5 can generate day, week, and month reports from live platform activity, with concise markdown output for docs or slides and PDF-ready handoff when you need a polished recap.

The project timeline visualizes tasks on a Gantt-style view. Teams can group by feature to follow delivery milestones or by assigned agent to inspect workload, with scheduled starts, run windows, and completion points visible in one place.

Optionally, yes. For projects with a valid local workspace, J5 can maintain project-scoped QMD knowledge and show configuration status directly in the product. It is an operational aid for grounded project context, not a claim of universal memory.

The costs workspace gives teams rolling spend visibility, budget policies, and hard-stop guardrails for new work. You can see spend before it compounds and intervene with clear operational context instead of reacting after the billing cycle closes.

Yes. J5 surfaces spend and usage across multiple views so teams can inspect economics by task history, agent, model, and project. That makes it easier to spot where paid usage is concentrating and adjust operating choices before costs drift.

J5 keeps planning context, task history, outputs, and operational activity attached to the work. That gives teams a concrete trail for reviews, compliance conversations, and post-mortems instead of relying on scattered chat logs.

Teams typically start with one real project, connect the relevant repositories and context, and let J5 decompose the work into an operational plan. From there, they can expand the roster with specialized agents while keeping humans in the review loop.

Autonomous systems only perform well when they understand the work environment. J5 Agent Fleet lets teams reuse prior project context, connect repositories, preserve decisions, maintain project-scoped knowledge when needed, and chat against the live plan so agents can act with better judgment and less repetition.

Approval gates are human checkpoints that block agent execution until a team member explicitly signs off. They are useful before high-risk actions, external-facing changes, spend-heavy tasks, or any step where a human decision is genuinely required. Gates can be configured by checkpoint type, risk level, or task type, and the platform keeps a full audit trail of who approved what and when.

Yes. The agent runner daemon lets you connect any Mac, Linux, or Windows machine as a local execution node. Download the binary for your platform, generate a one-time install token in Settings → Runners, and run the one-line install command. The daemon registers itself as a background service and starts polling for assigned tasks. Agents then run with full access to your local repositories, CLI tools, and environment.

J5 Agent Fleet offers a free Trial to get started, a Free tier with a monthly task allowance, a Pro tier for individual power users, and a Team tier for collaborative workspaces. See the Pricing page for current limits. Paid plans are billed through Stripe and can be managed from Settings → Billing at any time.

Yes. The Free tier includes a monthly task allowance so you can run real work without a credit card. When you reach the limit you can upgrade to Pro or Team from Settings → Billing. Trial accounts also get an extended window to explore the full feature set before choosing a plan.