feat(agents): agent-applications console (port from agent_platform)

[benjackwhite]

Ports the agent-applications console (deployed "agent applications") from posthog/posthog's agent_platform into posthog/code, surfaced under /code/agents → Applications. Each console feature is re-implemented in code's layered architecture and style — deployed-agent conversations render through code's native ConversationView via an SSE→ACP adapter rather than porting the console's bespoke chat.

Supersedes #2697 — its branch became unwritable after a workspace reset; this continues the same work on a fresh branch.

What's included

• Browse & monitor — agent list with inline analytics, a per-agent overview, a cross-agent live-now panel, and filterable session history → read-only transcript (Conversation + structured Logs) with a KPI strip and "fired by" cron badge.
• Approvals — per-agent and fleet-wide approval queues with a master/detail decide flow (approve / reject + edited args + reason) and the proposing session embedded for context.
• Configuration — filesystem-style spec/bundle explorer (model · instructions · triggers · tools · skills · mcps · secrets · limits) + a revision picker with freeze → promote → archive lifecycle, Slack setup, and cron "run now".
• Secrets & memory — guarded set / rotate / clear of encrypted env keys; a memory file browser with BM25 search + tables (render-only).
• Observability — spend / sessions / failure-rate / p95 KPIs (trends + WoW deltas) over the team's own $ai_* events, blended onto the Applications overview and a per-agent board.
• Live chat + Agent Builder — a per-agent Chat preview (stream / send / cancel / resume) against the agent ingress, plus an always-on Agent Builder dock that chats with the deployed meta-agent to inspect, debug, and edit agents: it sees the current page (context envelope + get_context), drives the UI (focus_*), and runs an interactive set_secret punch-out. Authoring happens server-side via consent-gated staged draft revisions.

Architecture

• Wire types in @posthog/shared/agent-platform-types (plain TS, snake_case). Reads on PostHogAPIClient via useAuthenticatedQuery hooks; live-chat state in a @posthog/core store with transport in a renderer hook.
• SSE→ACP mappers are pure, unit-tested modules that translate each agent-ingress event into the ACP message code's buildConversationItems already reduces — no re-implementation of the console's runnerReducer.
• Render-first / Agent-Builder authoring: this surface renders config and exposes only operational mutations (enable/disable, promote/freeze/archive); creating and editing agents is the Agent Builder's job. The ingress base URL is region-derived (dev → localhost).
• Out of scope (owned elsewhere): billing and the registry.

Backend routes (/api/projects/{teamId}/agent_applications/…, /agent_fleet/…) currently live on posthog/posthog's agent_platform branch, not production Cloud yet.

🤖 Generated with Claude Code

[github-actions]

React Doctor found 10 issues in 6 files · 10 warnings.

10 warnings

src/features/agent-applications/agent-builder/AgentBuilderDock.tsx

• ⚠️ src/features/agent-applications/agent-builder/AgentBuilderDock.tsx:265 JSX element passed as a prop jsx-no-jsx-as-prop
• ⚠️ src/features/agent-applications/agent-builder/AgentBuilderDock.tsx:273 JSX element passed as a prop jsx-no-jsx-as-prop

src/features/agent-applications/components/AgentChatPane.tsx

• ⚠️ src/features/agent-applications/components/AgentChatPane.tsx:114 JSX element passed as a prop jsx-no-jsx-as-prop

src/features/agent-applications/components/AgentConfigurationPane.tsx

• ⚠️ src/features/agent-applications/components/AgentConfigurationPane.tsx:111 Chained array iterations js-combine-iterations
• ⚠️ src/features/agent-applications/components/AgentConfigurationPane.tsx:116 Chained array iterations js-combine-iterations
• ⚠️ src/features/agent-applications/components/AgentConfigurationPane.tsx:128 Spread copy before sort() js-tosorted-immutable

src/features/agent-applications/components/AgentMemoryPane.tsx

• ⚠️ src/features/agent-applications/components/AgentMemoryPane.tsx:265 Array index used as a key no-array-index-as-key

src/features/agent-applications/components/AgentRevisionBar.tsx

• ⚠️ src/features/agent-applications/components/AgentRevisionBar.tsx:125 Spread copy before sort() js-tosorted-immutable

src/features/agent-applications/components/FileExplorer.tsx

• ⚠️ src/features/agent-applications/components/FileExplorer.tsx:100 Control missing accessible label control-has-associated-label
• ⚠️ src/features/agent-applications/components/FileExplorer.tsx:218 State only used in handlers rerender-state-only-in-handlers

_{Reviewed by React Doctor for commit a03ee55.}

[greptile-apps]

Comments Outside Diff (1)

1. packages/ui/src/features/agent-applications/components/AgentApplicationDetailView.tsx, line 1024-1044 (link)

   Identical EmptyState defined in both view components

   AgentApplicationDetailView.tsx and AgentApplicationsListView.tsx each declare a file-private EmptyState({ title, description }) component with identical markup. This duplicates the same idea in two places. A shared component (e.g., in a common components/ folder or inlined from a shared primitive) would say it OnceAndOnlyOnce.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: packages/ui/src/features/agent-applications/components/AgentApplicationDetailView.tsx
   Line: 1024-1044
   
   Comment:
   **Identical `EmptyState` defined in both view components**
   
   `AgentApplicationDetailView.tsx` and `AgentApplicationsListView.tsx` each declare a file-private `EmptyState({ title, description })` component with identical markup. This duplicates the same idea in two places. A shared component (e.g., in a common `components/` folder or inlined from a shared primitive) would say it OnceAndOnlyOnce.
   
   How can I resolve this? If you propose a fix, please make it concise.

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Prompt To Fix All With AI

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
packages/shared/src/agent-platform-types.ts:69-76
**`AgentAggregateStats` uses camelCase while the file's own convention is snake_case**

The file header explicitly states "Field names stay snake_case to match the JSON exactly" and every other REST-API type in this file follows that — `AgentApplication.team_id`, `AgentRevision.created_at`, `AgentSpec.max_turns`, etc. `AgentAggregateStats` is the only exception, using `liveCount`, `sessionsInWindowCount`, `spendInWindowUsd`, etc.

If the Django endpoint returns the standard `live_count`, `sessions_in_window_count` shape (which DRF does by default), every field on the cast result will be `undefined` at runtime. The `?? 0` fallbacks in `AgentApplicationsListView` and `AgentApplicationDetailView` will then silently show 0 for all stats — sessions, spend, failures, and approvals — regardless of actual activity.

### Issue 2 of 2
packages/ui/src/features/agent-applications/components/AgentApplicationDetailView.tsx:1024-1044
**Identical `EmptyState` defined in both view components**

`AgentApplicationDetailView.tsx` and `AgentApplicationsListView.tsx` each declare a file-private `EmptyState({ title, description })` component with identical markup. This duplicates the same idea in two places. A shared component (e.g., in a common `components/` folder or inlined from a shared primitive) would say it OnceAndOnlyOnce.

_{Reviews (1): Last reviewed commit: "feat(agents): typed SSE event union + tr..." | Re-trigger Greptile}

[greptile-apps]

AgentAggregateStats uses camelCase while the file's own convention is snake_case

The file header explicitly states "Field names stay snake_case to match the JSON exactly" and every other REST-API type in this file follows that — AgentApplication.team_id, AgentRevision.created_at, AgentSpec.max_turns, etc. AgentAggregateStats is the only exception, using liveCount, sessionsInWindowCount, spendInWindowUsd, etc.

If the Django endpoint returns the standard live_count, sessions_in_window_count shape (which DRF does by default), every field on the cast result will be undefined at runtime. The ?? 0 fallbacks in AgentApplicationsListView and AgentApplicationDetailView will then silently show 0 for all stats — sessions, spend, failures, and approvals — regardless of actual activity.

Prompt To Fix With AI

This is a comment left during a code review.
Path: packages/shared/src/agent-platform-types.ts
Line: 69-76

Comment:
**`AgentAggregateStats` uses camelCase while the file's own convention is snake_case**

The file header explicitly states "Field names stay snake_case to match the JSON exactly" and every other REST-API type in this file follows that — `AgentApplication.team_id`, `AgentRevision.created_at`, `AgentSpec.max_turns`, etc. `AgentAggregateStats` is the only exception, using `liveCount`, `sessionsInWindowCount`, `spendInWindowUsd`, etc.

If the Django endpoint returns the standard `live_count`, `sessions_in_window_count` shape (which DRF does by default), every field on the cast result will be `undefined` at runtime. The `?? 0` fallbacks in `AgentApplicationsListView` and `AgentApplicationDetailView` will then silently show 0 for all stats — sessions, spend, failures, and approvals — regardless of actual activity.

How can I resolve this? If you propose a fix, please make it concise.

[benjackwhite]

(Reply from a Claude Code session, on Ben's behalf — flagging that an agent verified this, not a human.)

False positive — the stats endpoint explicitly serializes camelCase, not DRF-default snake_case. See products/agent_platform/backend/presentation/views.py → the AgentAggregateStats inline_serializer, whose fields are liveCount, sessionsInWindowCount, spendInWindowUsd, lastActivityAt, failedInWindowCount, pendingApprovalsCount. So the camelCase TS type matches the wire shape and the values resolve at runtime. Leaving as-is.

[greptile-apps]

_{Reviews (2): Last reviewed commit: "docs: stamp M6 commit SHA + clear stale ..." | Re-trigger Greptile}