Skip to main content
Version: main

Architecture

GigaAgent uses a FastAPI backend, a LangGraph execution graph, a module system, and a bundled React UI.

Layers​

Browser and web UI
├─ page: /
├─ runtime UI config: /app-config.js
└─ external API prefix: /api
LangGraph development server (`giga_agent dev`)
├─ LangGraph routes: /api/...
└─ GigaAgent routes: /api/agent/...
GigaAgent FastAPI app
├─ internal prefix: /agent
├─ core routes: /agent/files, /agent/connectors, /agent/llms, ...
├─ module routes: /agent/{module.id}/...
└─ BaseAgent + BaseModule + LangGraph graph
Providers
├─ language model and embeddings
├─ sandbox runtime
├─ search
└─ image generation

Connecting external services​

External services of two kinds meet in a single connections catalog in the web UI: MCP servers from modules/mcp/catalog.json and integration modules from the modules/integrations/ package (Yandex Mail, Yandex Calendar, Yandex Disk, VK). An integration module carries its own OAuth support (auth.py, provider.py) with automatic token refresh. The registry in core/integrations/registry.py resolves providers by walking the loaded agent modules; the agent registers itself at startup via set_current_agent().

Widgets in the UI​

Some tools return structured results that the web UI renders as interactive widgets: an inbox, a calendar, a Yandex Disk file browser. The tool-to-widget mapping lives in front/src/components/widgets/registry.ts; shared widget building blocks live in front/src/components/widgets/kit/. The server side marks such results through modules/integrations/widget_hint.py, so the agent does not restate widget contents as text.

Graphs and subgraphs​

The default graph path is giga_agent.agents.run:graph:app. The app registers the main giga_agent graph, deep_research, and compatibility subgraphs: landing, presentation, meme, lean_canvas, and podcast.

API prefixes​

Inside FastAPI, routes start with /agent. Through giga_agent dev, browser calls usually use /api/agent/....