csg
Résumé ↗
Menu
← All projects

Agents · Full-stack / Full-stack prototype

Astra

One conversation, connected workflows.

A multi-agent assistant with chat, task, calendar and email workflows, backed by persistent services and connected Google integrations.

FastAPI · React · PostgreSQL · Redis · Docker

View repository ↗

01 / THE PROBLEM

What needed solving.

Productivity work is spread across conversations, tasks, calendars and email. Astra explores an assistant that coordinates these workflows through one interface while keeping state in backend services.

02 / FOLLOW THE WORKFLOW

See how it fits together.

A simplified example of the documented flow. Sample outputs are authored illustrations, not live model predictions.

AstraIllustrative workflow

Illustrative conversation

“Help organize tomorrow’s work.”

Start with a productivity request.

Agent orchestration

Plan → calendar and task tools

The assistant coordinates relevant tools.

OAuth-connected services

Google Calendar · Gmail

Use the configured service integrations.

Redis supports runtime state

Tasks + conversation → PostgreSQL

Keep workflow state for the dashboard.

03 / ENGINEERING

The decisions behind it.

Separate UI, orchestration and services

React and Vite provide the dashboard. FastAPI exposes APIs and WebSockets, with modular services, repositories and tool integrations behind the conversational flow.

Give state a durable home

PostgreSQL stores persistent records; Redis supports cache and runtime state. This keeps the interface from being the only place where a workflow exists.

Include operational components

Docker Compose connects the services. Prometheus and Grafana configuration provides a foundation for monitoring, distinct from a verified production service-level objective.

04 / EVIDENCE & LIMITS

Claims with context.

2Named Google integrations: Gmail and Calendar
API + WebSocketDocumented interaction channels

The public documentation describes task and conversation workflows, OAuth integrations, persistence, container deployment and monitoring. These are documented capabilities; the reviewed overview does not establish a successful-task rate or production uptime.

Current limits & next validation

Connected workflows depend on provider credentials and integration configuration. A useful next check is a fixed task suite with explicit expected actions, failures, permissions and recovery behavior. No real email or calendar action occurs in this portfolio example.

05 / READ THE SOURCE

Go deeper.

Based on public repository documentation reviewed on 7 November 2026. Results are attributed to the project’s recorded evaluations; they were not rerun for this portfolio.

NEXT PROJECTScalable RecSys Engine

TOOLS BEHIND THE WORK

Explore the stack. Drag the ribbon or select a tool.