How google/adk-web works
Project type and purpose
• This is a full-stack developer UI for the Google Agent Development Kit (ADK), implemented entirely as an Angular single-page application (SPA).
• Its purpose is to provide an interactive, visual interface for building, testing, and debugging AI agents powered by the ADK backend (a separate Python/Java API server).
File structure
• Top-level files and scripts:
• angular.json, tsconfig*.json, package.json / package-lock.json, karma.conf.js, karma scripts – Angular CLI configuration and build/test pipelines.
• clean-backend.js and set-backend.js – scripts to configure the API base-URL for local development.
• .github/workflows/angular-tests.yml – CI pipeline for running Angular tests.
• Public assets (public/, src/assets/):
• runtime-config.json – runtime config for API endpoints, feature flags, etc.
• audio-processor.js – custom audio processing in the browser.
• Source code (src/):
• src/app/components/… – a large set of Angular UI components grouped by feature tab (artifact-tab, eval-tab, chat-panel, trace-tab, etc.).
• src/app/core/models/… – TypeScript interfaces/models representing AgentRunRequest, Session, Trace, Eval, etc.
• src/app/core/services/… – Angular services that encapsulate HTTP and WebSocket calls to the backend; includes feature-flag, agent, eval, event, session, trace, artifact, audio playback/recording, download, local-file, stream-chat, video, UI state, etc.
• src/app/directives/… – custom Angular directives for resizing panels.
• src/app/testing/… – testing utilities and mocks for all core services.
• src/env/ and src/utils/ – environment constants and URL/ runtime-config helpers.
README for additional insights
• The README confirms:
• Angular CLI front-end at localhost:4200.
• Backend API server (Python/Java) at a configurable origin (default localhost:8000).
• CORS must allow the Angular origin.
• The UI is “built-in dev UI that comes along with ADK.”
Detail
• Break the Angular app into UI Components vs Core Services vs Directives/Utilities.
• Relationships among services (e.g. SessionService depends on HTTPClient and WebSocketService).