Intent

Public Beta

Better than
Claude Code alone.

Orchestrate multiple agents from a living spec, preview in-browser, and ship without switching tools.

Download for Mac

See what you get

Add JWT auth middleware — acme-corp/api-gateway⌘K

Coordinator×

auth-middleware...×

a3f7b2c: Add...×

AGENTS / Coordinator / Coordinator agent

We need JWT authentication across the API gateway and auth service. Tokens should be issued by auth-service and validated by the gateway middleware.

I'll implement JWT auth across both services. Let me analyze the current codebase and create a plan.

2h ago

Make sure we support token refresh and handle expired tokens gracefully. Also add rate limiting to the token endpoint.

Good call. I'll add token refresh logic and rate limiting. Let me break this into parallel tasks across both repos.

1h ago

Go ahead and implement it. Start with the auth-service token issuance, then the gateway middleware.

I'll coordinate agents across both services. Spawning specialists now:

Auth Token AgentRunning...

Implementing JWT issuance and refresh in auth-service

// token-service.ts

export class TokenService {

async issueToken(user: User) {

const payload = { sub: user.id,

Gateway Middleware AgentRunning...

Adding JWT validation middleware to API gateway

// auth-middleware.ts

export function jwtMiddleware(

req: Request, res: Response,

Both agents are working in parallel across repos. Current progress:

• Auth Token Agent: Implementing token issuance, refresh, and revocation endpoints
• Gateway Middleware Agent: Adding JWT validation with RS256 and token expiry handling

Just now

Claude Opus 4.6@

Spec×

NOTES / Spec

JWT Authentication — Cross-Service Implementation

Overview

Implement JWT-based authentication across api-gateway and auth-service. Tokens are issued by auth-service using RS256 signing, validated by gateway middleware. Support token refresh, revocation, and graceful expiry handling.

Architecture

• auth-service: token issuance, refresh, revocation
• api-gateway: JWT validation middleware, rate limiting
• Signing: RS256 with rotating key pairs
• Token lifetime: 15m access, 7d refresh
• Storage: Redis for revocation list

Endpoints

• POST /auth/token — issue access + refresh tokens
• POST /auth/refresh — rotate refresh token
• POST /auth/revoke — add token to revocation list
• GET /auth/.well-known/jwks — public key endpoint

Tasks

✓Set up RS256 key pair generation

✓Implement token issuance endpoint

✓Add refresh token rotation

/JWT validation middleware in gatewayin progress

Rate limiting on /auth/token

Integration tests across services

Update API documentation

Add JWT auth middleware

acme-corp/api-gateway

Agent orchestration

A coordinator agent breaks down your task into a spec, then delegates work to specialist agents that run in parallel.

Coordinator

30m

I'll coordinate the JWT implementation across both services...

2 delegated agents

Auth Token Agent

running

Gateway Middleware Agent

running

Background agents3

Test Suite Agent

Lint & Type Check

Docs Generator

Context

Context about the task, shared with all agents in this space.

Spec

Changes5

Changes made to files by agents working in this space.

feat/jwt-auth → main

■auth-middleware.tssrc/middleware+89 -3

■token-service.tssrc/services+142 -0

■security.tssrc/config+12 -4

■auth.test.tstests/integration+67 -0

■routes.tssrc+8 -2

Files

The agents in this space are working off a copy of your files.

src

tests

config

docs

p 3000Terminallsnpm run test:watch --...

See It In Action

Orchestrate your agents like a system, not a swarm.

Intent — demo

Click to play demo

Before / After

What changes when you add Intent.

	Claude Code	Claude Code + Intent
Agent Model	One agent at a time	Multiple agents in parallel
Context	Context lost between sessions	Full codebase indexed
Workspace	Terminal tabs everywhere	Unified workspace
Spec	No shared spec	Living spec keeps agents aligned
Git	Manual branch management	Auto-commit and isolated worktrees

BUILD WITH DEEP CONTEXT

Every agent sees your entire codebase.

Every agent in Intent is powered by our industry-leading Context Engine. Whether it's the coordinator planning your work or specialists executing tasks, they all share deep understanding of your entire codebase.

Discover the Context Engine

Get Started

Build with Intent

Orchestrate your agents like a system, not a swarm. Define what gets built, delegate to agents that stay aligned, and maintain full visibility from first commit to merge.