Skip to content

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

Closed
benjackwhite wants to merge 2 commits into
mainfrom
posthog-code/agent-applications
Closed

feat(agents): agent-applications console (port from agent_platform)#2697
benjackwhite wants to merge 2 commits into
mainfrom
posthog-code/agent-applications

Conversation

@benjackwhite

@benjackwhite benjackwhite commented Jun 16, 2026

Copy link
Copy Markdown

What

Ports the agent_platform console (from posthog/posthog ass branch) into Code as a new agent-applications area for deployed agents. Reworks the /code/agents tab so its top level is generic agent design/config, with Scouts and the new Applications as sub-options.

This is a multi-milestone effort; this PR grows as each milestone lands. Draft until the chat + concierge are wired.

Milestones

  • M1 — IA rework + scaffolding: agent-applications feature, route tree (/code/agents/applications), surfaced as a subsection link card on the Agents landing.
  • M2 — API + domain: agent_platform domain types in @posthog/shared; PostHogAPIClient read methods (applications, stats, sessions, approvals, revisions, fleet); TanStack Query hooks; live fleet stat strip + application list + per-agent detail (overview + recent sessions).
  • M3 — SSE→ACP chat adapter: render deployed-agent chat through Code's native ConversationView (agent-ingress SSE events map ~1:1 onto ACP SessionUpdate).
  • M4 — Concierge dock: AI-driven config edits (port of the console concierge).
  • M5 — Standalone chat package: embeddable chat for deployed agents.

Notes

  • IA call (confirmed): Applications is a sub-option under /code/agents, not a new top-level sidebar tab.
  • Follows the inbox pattern: shared wire types → PostHogAPIClient methods → UI hooks. No core passthrough service (forbidden); the core service arrives in M3 with the chat reducer.
  • Verified per milestone: @posthog/ui/@posthog/shared/@posthog/api-client typecheck clean, Biome clean.

🤖 Generated with Claude Code

First milestone of porting the agent_platform console into Code.

Adds a new `agent-applications` UI feature for deployed agent-platform
agents, surfaced as a sub-option of the existing `/code/agents` config
landing (alongside Scouts), not a new top-level sidebar tab.

- agent-applications feature: list view chrome + empty feature module
- routes: /code/agents/applications (layout + index), regenerated tree
- ConfigureAgentsSection: "Applications" subsection link card

List data, the SSE→ACP chat adapter, and the concierge dock land in
later milestones.

Generated-By: PostHog Code
Task-Id: 3f40d432-67cc-4df1-bc7b-3ee34c7b1d70
@github-actions

github-actions Bot commented Jun 16, 2026

Copy link
Copy Markdown

React Doctor found no issues in the changed files. 🎉

Reviewed by React Doctor for commit 41160a4.

@greptile-apps

greptile-apps Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Reviews (1): Last reviewed commit: "feat(agents): scaffold agent-application..." | Re-trigger Greptile

M2: wire the agent-applications area to the agent_platform REST API.

- shared: agent-platform-types.ts — domain types for applications,
  revisions, sessions, approvals, fleet (plain TS wire shapes, matching
  inbox-types/git-types convention); exported as a subpath.
- api-client: PostHogAPIClient methods for the read surface (list/get
  applications, stats, sessions list/detail, approvals list + decide,
  revisions, fleet stats/live-sessions/approvals) using the raw fetcher,
  mirroring the signals methods.
- ui: query-key factory + TanStack Query hooks via useAuthenticatedQuery;
  list view now renders a live fleet stat strip + application rows; new
  per-agent detail route (/code/agents/applications/$idOrSlug) showing an
  overview stat strip + recent sessions.

Follows the inbox pattern (shared types → client methods → UI hooks); no
core passthrough service — the core service lands in M3 with the
SSE→ACP chat reducer, where there's real orchestration to own.

Generated-By: PostHog Code
Task-Id: 3f40d432-67cc-4df1-bc7b-3ee34c7b1d70

Copy link
Copy Markdown
Author

Superseding this with #2700 — a mid-task workspace reset left this branch unwritable by the signed-commit tooling (it only writes branches created in the same session). #2700 continues the exact same work (M1 + M2 here, plus M3a) and is where all further milestones will land. Closing this one to avoid confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant