AutoGPT is the vision of accessible AI for everyone, to use and to build on. Our mission is to provide the tools, so that you can focus on what matters.
refactor(claude): Split `autogpt_platform/CLAUDE.md` into project-specific files (#11788)
Reinier van der Leer4cd5da678d73
diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.mdindex 870e6b4b0a..3c72eaae18 100644--- a/.github/copilot-instructions.md+++ b/.github/copilot-instructions.md@@ -160,7 +160,7 @@ pnpm storybook # Start component development server**Backend Entry Points:**-- `backend/backend/server/server.py` - FastAPI application setup+- `backend/backend/api/rest_api.py` - FastAPI application setup- `backend/backend/data/` - Database models and user management- `backend/blocks/` - Agent execution blocks and logic@@ -219,7 +219,7 @@ Agents are built using a visual block-based system where each block performs a s### API Development-1. Update routes in `/backend/backend/server/routers/`+1. Update routes in `/backend/backend/api/features/`2. Add/update Pydantic models in same directory3. Write tests alongside route files4. For `data/*.py` changes, validate user ID checks@@ -285,7 +285,7 @@ Agents are built using a visual block-based system where each block performs a s### Security Guidelines-**Cache Protection Middleware** (`/backend/backend/server/middleware/security.py`):+**Cache Protection Middleware** (`/backend/backend/api/middleware/security.py`):- Default: Disables caching for ALL endpoints with `Cache-Control: no-store, no-cache, must-revalidate, private`- Uses allow list approach for cacheable paths (static assets, health checks, public pages)diff --git a/.gitignore b/.gitignoreindex dfce8ba810..1a2291b516 100644--- a/.gitignore+++ b/.gitignore@@ -178,4 +178,5 @@ autogpt_platform/backend/settings.py*.ign.*.test-contents.claude/settings.local.json+CLAUDE.local.md/autogpt_platform/backend/logsdiff --git a/autogpt_platform/CLAUDE.md b/autogpt_platform/CLAUDE.mdindex a5a588b667..62adbdaefa 100644--- a/autogpt_platform/CLAUDE.md+++ b/autogpt_platform/CLAUDE.md@@ -6,141 +6,30 @@ This file provides guidance to Claude Code (claude.ai/code) when working with coAutoGPT Platform is a monorepo containing:-- **Backend** (`/backend`): Python FastAPI server with async support-- **Frontend** (`/frontend`): Next.js React application-- **Shared Libraries** (`/autogpt_libs`): Common Python utilities+- **Backend** (`backend`): Python FastAPI server with async support+- **Frontend** (`frontend`): Next.js React application+- **Shared Libraries** (`autogpt_libs`): Common Python utilities-## Essential Commands+## Component Documentation-### Backend Development+- **Backend**: See @backend/CLAUDE.md for backend-specific commands, architecture, and development tasks+- **Frontend**: See @frontend/CLAUDE.md for frontend-specific commands, architecture, and development patterns-```bash-# Install dependencies-cd backend && poetry install--# Run database migrations-poetry run prisma migrate dev--# Start all services (database, redis, rabbitmq, clamav)-docker compose up -d--# Run the backend server-poetry run serve--# Run tests-poetry run test--# Run specific test-poetry run pytest path/to/test_file.py::test_function_name--# Run block tests (tests that validate all blocks work correctly)-poetry run pytest backend/blocks/test/test_block.py -xvs--# Run tests for a specific block (e.g., GetCurrentTimeBlock)-poetry run pytest 'backend/blocks/test/test_block.py::test_available_blocks[GetCurrentTimeBlock]' -xvs--# Lint and format-# prefer format if you want to just "fix" it and only get the errors that can't be autofixed-poetry run format # Black + isort-poetry run lint # ruff-```--More details can be found in TESTING.md--#### Creating/Updating Snapshots--When you first write a test or when the expected output changes:--```bash-poetry run pytest path/to/test.py --snapshot-update-```--⚠️ **Important**: Always review snapshot changes before committing! Use `git diff` to verify the changes are expected.--### Frontend Development--```bash-# Install dependencies-cd frontend && pnpm i--# Generate API client from OpenAPI spec-pnpm generate:api--# Start development server-pnpm dev--# Run E2E tests-pnpm test--# Run Storybook for component development-pnpm storybook--# Build production-pnpm build--# Format and lint-pnpm format--# Type checking-pnpm types-```--## Architecture Overview--### Backend Architecture--- **API Layer**: FastAPI with REST and WebSocket endpoints-- **Database**: PostgreSQL with Prisma ORM, includes pgvector for embeddings-- **Queue System**: RabbitMQ for async task processing-- **Execution Engine**: Separate executor service processes agent workflows-- **Authentication**: JWT-based with Supabase integration-- **Security**: Cache protection middleware prevents sensitive data caching in browsers/proxies--### Frontend Architecture--- **Framework**: Next.js 15 App Router (client-first approach)-- **Data Fetching**: Type-safe generated API hooks via Orval + React Query-- **State Management**: React Query for server state, co-located UI state in components/hooks-- **Component Structure**: Separate render logic (`.tsx`) from business logic (`use*.ts` hooks)-- **Workflow Builder**: Visual graph editor using @xyflow/react-- **UI Components**: shadcn/ui (Radix UI primitives) with Tailwind CSS styling-- **Icons**: Phosphor Icons only-- **Feature Flags**: LaunchDarkly integration-- **Error Handling**: ErrorCard for render errors, toast for mutations, Sentry for exceptions-- **Testing**: Playwright for E2E, Storybook for component development--### Key Concepts+## Key Concepts1. **Agent Graphs**: Workflow definitions stored as JSON, executed by the backend-2. **Blocks**: Reusable components in `/backend/blocks/` that perform specific tasks+2. **Blocks**: Reusable components in `backend/backend/blocks/` that perform specific tasks3. **Integrations**: OAuth and API connections stored per user4. **Store**: Marketplace for sharing agent templates5. **Virus Scanning**: ClamAV integration for file upload security-### Testing Approach--- Backend uses pytest with snapshot testing for API responses-- Test files are colocated with source files (`*_test.py`)-- Frontend uses Playwright for E2E tests-- Component testing via Storybook--### Database Schema--Key models (defined in `/backend/schema.prisma`):--- `User`: Authentication and profile data-- `AgentGraph`: Workflow definitions with version control-- `AgentGraphExecution`: Execution history and results-- `AgentNode`: Individual nodes in a workflow-- `StoreListing`: Marketplace listings for sharing agents-### Environment Configuration#### Configuration Files-- **Backend**: `/backend/.env.default` (defaults) → `/backend/.env` (user overrides)-- **Frontend**: `/frontend/.env.default` (defaults) → `/frontend/.env` (user overrides)-- **Platform**: `/.env.default` (Supabase/shared defaults) → `/.env` (user overrides)+- **Backend**: `backend/.env.default` (defaults) → `backend/.env` (user overrides)+- **Frontend**: `frontend/.env.default` (defaults) → `frontend/.env` (user overrides)+- **Platform**: `.env.default` (Supabase/shared defaults) → `.env` (user overrides)#### Docker Environment Loading Order@@ -156,130 +45,12 @@ Key models (defined in `/backend/schema.prisma`):- Backend/Frontend services use YAML anchors for consistent configuration- Supabase services (`db/docker/docker-compose.yml`) follow the same pattern-### Common Development Tasks--**Adding a new block:**--Follow the comprehensive [Block SDK Guide](../../../docs/content/platform/block-sdk-guide.md) which covers:--- Provider configuration with `ProviderBuilder`-- Block schema definition-- Authentication (API keys, OAuth, webhooks)-- Testing and validation-- File organization--Quick steps:--1. Create new file in `/backend/backend/blocks/`-2. Configure provider using `ProviderBuilder` in `_config.py`-3. Inherit from `Block` base class-4. Define input/output schemas using `BlockSchema`-5. Implement async `run` method-6. Generate unique block ID using `uuid.uuid4()`-7. Test with `poetry run pytest backend/blocks/test/test_block.py`--Note: when making many new blocks analyze the interfaces for each of these blocks and picture if they would go well together in a graph based editor or would they struggle to connect productively?-ex: do the inputs and outputs tie well together?--If you get any pushback or hit complex block conditions check the new_blocks guide in the docs.--**Handling files in blocks with `store_media_file()`:**--When blocks need to work with files (images, videos, documents), use `store_media_file()` from `backend.util.file`. The `return_format` parameter determines what you get back:--| Format | Use When | Returns |-|--------|----------|---------|-| `"for_local_processing"` | Processing with local tools (ffmpeg, MoviePy, PIL) | Local file path (e.g., `"image.png"`) |-| `"for_external_api"` | Sending content to external APIs (Replicate, OpenAI) | Data URI (e.g., `"data:image/png;base64,..."`) |-| `"for_block_output"` | Returning output from your block | Smart: `workspace://` in CoPilot, data URI in graphs |--**Examples:**-```python-# INPUT: Need to process file locally with ffmpeg-local_path = await store_media_file(- file=input_data.video,- execution_context=execution_context,- return_format="for_local_processing",-)-# local_path = "video.mp4" - use with Path/ffmpeg/etc--# INPUT: Need to send to external API like Replicate-image_b64 = await store_media_file(- file=input_data.image,- execution_context=execution_context,- return_format="for_external_api",-)-# image_b64 = "data:image/png;base64,iVBORw0..." - send to API--# OUTPUT: Returning result from block-result_url = await store_media_file(- file=generated_image_url,- execution_context=execution_context,- return_format="for_block_output",-)-yield "image_url", result_url-# In CoPilot: result_url = "workspace://abc123"-# In graphs: result_url = "data:image/png;base64,..."-```--**Key points:**-- `for_block_output` is the ONLY format that auto-adapts to execution context-- Always use `for_block_output` for block outputs unless you have a specific reason not to-- Never hardcode workspace checks - let `for_block_output` handle it--**Modifying the API:**--1. Update route in `/backend/backend/server/routers/`-2. Add/update Pydantic models in same directory-3. Write tests alongside the route file-4. Run `poetry run test` to verify--### Frontend guidelines:--See `/frontend/CONTRIBUTING.md` for complete patterns. Quick reference:--1. **Pages**: Create in `src/app/(platform)/feature-name/page.tsx`- - Add `usePageName.ts` hook for logic- - Put sub-components in local `components/` folder-2. **Components**: Structure as `ComponentName/ComponentName.tsx` + `useComponentName.ts` + `helpers.ts`- - Use design system components from `src/components/` (atoms, molecules, organisms)- - Never use `src/components/__legacy__/*`-3. **Data fetching**: Use generated API hooks from `@/app/api/__generated__/endpoints/`- - Regenerate with `pnpm generate:api`- - Pattern: `use{Method}{Version}{OperationName}`-4. **Styling**: Tailwind CSS only, use design tokens, Phosphor Icons only-5. **Testing**: Add Storybook stories for new components, Playwright for E2E-6. **Code conventions**: Function declarations (not arrow functions) for components/handlers--- Component props should be `interface Props { ... }` (not exported) unless the interface needs to be used outside the component-- Separate render logic from business logic (component.tsx + useComponent.ts + helpers.ts)-- Colocate state when possible and avoid creating large components, use sub-components ( local `/components` folder next to the parent component ) when sensible-- Avoid large hooks, abstract logic into `helpers.ts` files when sensible-- Use function declarations for components, arrow functions only for callbacks-- No barrel files or `index.ts` re-exports-- Do not use `useCallback` or `useMemo` unless asked to optimise a given function-- Avoid comments at all times unless the code is very complex-- Do not type hook returns, let Typescript infer as much as possible-- Never type with `any`, if not types available use `unknown`--### Security Implementation--**Cache Protection Middleware:**--- Located in `/backend/backend/server/middleware/security.py`-- Default behavior: Disables caching for ALL endpoints with `Cache-Control: no-store, no-cache, must-revalidate, private`-- Uses an allow list approach - only explicitly permitted paths can be cached-- Cacheable paths include: static assets (`/static/*`, `/_next/static/*`), health checks, public store pages, documentation-- Prevents sensitive data (auth tokens, API keys, user data) from being cached by browsers/proxies-- To allow caching for a new endpoint, add it to `CACHEABLE_PATHS` in the middleware-- Applied to both main API server and external API applications-### Creating Pull Requests-- Create the PR aginst the `dev` branch of the repository.-- Ensure the branch name is descriptive (e.g., `feature/add-new-block`)/-- Use conventional commit messages (see below)/-- Fill out the .github/PULL_REQUEST_TEMPLATE.md template as the PR description/+- Create the PR against the `dev` branch of the repository.+- Ensure the branch name is descriptive (e.g., `feature/add-new-block`)+- Use conventional commit messages (see below)+- Fill out the .github/PULL_REQUEST_TEMPLATE.md template as the PR description- Run the github pre-commit hooks to ensure code quality.### Reviewing/Revising Pull Requestsdiff --git a/autogpt_platform/backend/CLAUDE.md b/autogpt_platform/backend/CLAUDE.mdnew file mode 100644index 0000000000..53d52bb4d3--- /dev/null+++ b/autogpt_platform/backend/CLAUDE.md@@ -0,0 +1,170 @@+# CLAUDE.md - Backend++This file provides guidance to Claude Code when working with the backend.++## Essential Commands++To run something with Python package dependencies you MUST use `poetry run ...`.++```bash+# Install dependencies+poetry install++# Run database migrations+poetry run prisma migrate dev++# Start all services (database, redis, rabbitmq, clamav)+docker compose up -d++# Run the backend as a whole+poetry run app++# Run tests+poetry run test++# Run specific test+poetry run pytest path/to/test_file.py::test_function_name++# Run block tests (tests that validate all blocks work correctly)+poetry run pytest backend/blocks/test/test_block.py -xvs++# Run tests for a specific block (e.g., GetCurrentTimeBlock)+poetry run pytest 'backend/blocks/test/test_block.py::test_available_blocks[GetCurrentTimeBlock]' -xvs++# Lint and format+# prefer format if you want to just "fix" it and only get the errors that can't be autofixed+poetry run format # Black + isort+poetry run lint # ruff+```++More details can be found in @TESTING.md++### Creating/Updating Snapshots++When you first write a test or when the expected output changes:++```bash+poetry run pytest path/to/test.py --snapshot-update+```++⚠️ **Important**: Always review snapshot changes before committing! Use `git diff` to verify the changes are expected.++## Architecture++- **API Layer**: FastAPI with REST and WebSocket endpoints+- **Database**: PostgreSQL with Prisma ORM, includes pgvector for embeddings+- **Queue System**: RabbitMQ for async task processing+- **Execution Engine**: Separate executor service processes agent workflows+- **Authentication**: JWT-based with Supabase integration+- **Security**: Cache protection middleware prevents sensitive data caching in browsers/proxies++## Testing Approach++- Uses pytest with snapshot testing for API responses+- Test files are colocated with source files (`*_test.py`)++## Database Schema++Key models (defined in `schema.prisma`):++- `User`: Authentication and profile data+- `AgentGraph`: Workflow definitions with version control+- `AgentGraphExecution`: Execution history and results+- `AgentNode`: Individual nodes in a workflow+- `StoreListing`: Marketplace listings for sharing agents++## Environment Configuration++- **Backend**: `.env.default` (defaults) → `.env` (user overrides)++## Common Development Tasks++### Adding a new block++Follow the comprehensive [Block SDK Guide](@../../docs/content/platform/block-sdk-guide.md) which covers:++- Provider configuration with `ProviderBuilder`+- Block schema definition+- Authentication (API keys, OAuth, webhooks)+- Testing and validation+- File organization++Quick steps:++1. Create new file in `backend/blocks/`+2. Configure provider using `ProviderBuilder` in `_config.py`+3. Inherit from `Block` base class+4. Define input/output schemas using `BlockSchema`+5. Implement async `run` method+6. Generate unique block ID using `uuid.uuid4()`+7. Test with `poetry run pytest backend/blocks/test/test_block.py`++Note: when making many new blocks analyze the interfaces for each of these blocks and picture if they would go well together in a graph-based editor or would they struggle to connect productively?+ex: do the inputs and outputs tie well together?++If you get any pushback or hit complex block conditions check the new_blocks guide in the docs.++#### Handling files in blocks with `store_media_file()`++When blocks need to work with files (images, videos, documents), use `store_media_file()` from `backend.util.file`. The `return_format` parameter determines what you get back:++| Format | Use When | Returns |+|--------|----------|---------|+| `"for_local_processing"` | Processing with local tools (ffmpeg, MoviePy, PIL) | Local file path (e.g., `"image.png"`) |+| `"for_external_api"` | Sending content to external APIs (Replicate, OpenAI) | Data URI (e.g., `"data:image/png;base64,..."`) |+| `"for_block_output"` | Returning output from your block | Smart: `workspace://` in CoPilot, data URI in graphs |++**Examples:**++```python+# INPUT: Need to process file locally with ffmpeg+local_path = await store_media_file(+ file=input_data.video,+ execution_context=execution_context,+ return_format="for_local_processing",+)+# local_path = "video.mp4" - use with Path/ffmpeg/etc++# INPUT: Need to send to external API like Replicate+image_b64 = await store_media_file(+ file=input_data.image,+ execution_context=execution_context,+ return_format="for_external_api",+)+# image_b64 = "data:image/png;base64,iVBORw0..." - send to API++# OUTPUT: Returning result from block+result_url = await store_media_file(+ file=generated_image_url,+ execution_context=execution_context,+ return_format="for_block_output",+)+yield "image_url", result_url+# In CoPilot: result_url = "workspace://abc123"+# In graphs: result_url = "data:image/png;base64,..."+```++**Key points:**++- `for_block_output` is the ONLY format that auto-adapts to execution context+- Always use `for_block_output` for block outputs unless you have a specific reason not to+- Never hardcode workspace checks - let `for_block_output` handle it++### Modifying the API++1. Update route in `backend/api/features/`+2. Add/update Pydantic models in same directory+3. Write tests alongside the route file+4. Run `poetry run test` to verify++## Security Implementation++### Cache Protection Middleware++- Located in `backend/api/middleware/security.py`+- Default behavior: Disables caching for ALL endpoints with `Cache-Control: no-store, no-cache, must-revalidate, private`+- Uses an allow list approach - only explicitly permitted paths can be cached+- Cacheable paths include: static assets (`static/*`, `_next/static/*`), health checks, public store pages, documentation+- Prevents sensitive data (auth tokens, API keys, user data) from being cached by browsers/proxies+- To allow caching for a new endpoint, add it to `CACHEABLE_PATHS` in the middleware+- Applied to both main API server and external API applicationsdiff --git a/autogpt_platform/backend/TESTING.md b/autogpt_platform/backend/TESTING.mdindex a3a5db68ef..2e09144485 100644--- a/autogpt_platform/backend/TESTING.md+++ b/autogpt_platform/backend/TESTING.md@@ -138,7 +138,7 @@ If the test doesn't need the `user_id` specifically, mocking is not necessary as#### Using Global Auth Fixtures-Two global auth fixtures are provided by `backend/server/conftest.py`:+Two global auth fixtures are provided by `backend/api/conftest.py`:- `mock_jwt_user` - Regular user with `test_user_id` ("test-user-id")- `mock_jwt_admin` - Admin user with `admin_user_id` ("admin-user-id")diff --git a/autogpt_platform/backend/backend/api/features/builder/routes.py b/autogpt_platform/backend/backend/api/features/builder/routes.pyindex 7fe9cab189..15b922178d 100644--- a/autogpt_platform/backend/backend/api/features/builder/routes.py+++ b/autogpt_platform/backend/backend/api/features/builder/routes.py@@ -17,7 +17,7 @@ router = fastapi.APIRouter()-# Taken from backend/server/v2/store/db.py+# Taken from backend/api/features/store/db.pydef sanitize_query(query: str | None) -> str | None:if query is None:return querydiff --git a/autogpt_platform/frontend/CLAUDE.md b/autogpt_platform/frontend/CLAUDE.mdnew file mode 100644index 0000000000..b58f1ad6aa--- /dev/null+++ b/autogpt_platform/frontend/CLAUDE.md@@ -0,0 +1,76 @@+# CLAUDE.md - Frontend++This file provides guidance to Claude Code when working with the frontend.++## Essential Commands++```bash+# Install dependencies+pnpm i++# Generate API client from OpenAPI spec+pnpm generate:api++# Start development server+pnpm dev++# Run E2E tests+pnpm test++# Run Storybook for component development+pnpm storybook++# Build production+pnpm build++# Format and lint+pnpm format++# Type checking+pnpm types+```++### Code Style++- Fully capitalize acronyms in symbols, e.g. `graphID`, `useBackendAPI`+- Use function declarations (not arrow functions) for components/handlers++## Architecture++- **Framework**: Next.js 15 App Router (client-first approach)+- **Data Fetching**: Type-safe generated API hooks via Orval + React Query+- **State Management**: React Query for server state, co-located UI state in components/hooks+- **Component Structure**: Separate render logic (`.tsx`) from business logic (`use*.ts` hooks)+- **Workflow Builder**: Visual graph editor using @xyflow/react+- **UI Components**: shadcn/ui (Radix UI primitives) with Tailwind CSS styling+- **Icons**: Phosphor Icons only+- **Feature Flags**: LaunchDarkly integration+- **Error Handling**: ErrorCard for render errors, toast for mutations, Sentry for exceptions+- **Testing**: Playwright for E2E, Storybook for component development++## Environment Configuration++`.env.default` (defaults) → `.env` (user overrides)++## Feature Development++See @CONTRIBUTING.md for complete patterns. Quick reference:++1. **Pages**: Create in `src/app/(platform)/feature-name/page.tsx`+ - Extract component logic into custom hooks grouped by concern, not by component. Each hook should represent a cohesive domain of functionality (e.g., useSearch, useFilters, usePagination) rather than bundling all state into one useComponentState hook.+ - Put each hook in its own `.ts` file+ - Put sub-components in local `components/` folder+ - Component props should be `type Props = { ... }` (not exported) unless it needs to be used outside the component+2. **Components**: Structure as `ComponentName/ComponentName.tsx` + `useComponentName.ts` + `helpers.ts`+ - Use design system components from `src/components/` (atoms, molecules, organisms)+ - Never use `src/components/__legacy__/*`+3. **Data fetching**: Use generated API hooks from `@/app/api/__generated__/endpoints/`+ - Regenerate with `pnpm generate:api`+ - Pattern: `use{Method}{Version}{OperationName}`+4. **Styling**: Tailwind CSS only, use design tokens, Phosphor Icons only+5. **Testing**: Add Storybook stories for new components, Playwright for E2E+6. **Code conventions**:+ - Use function declarations (not arrow functions) for components/handlers+ - Do not use `useCallback` or `useMemo` unless asked to optimise a given function+ - Do not type hook returns, let Typescript infer as much as possible+ - Never type with `any` unless a variable/attribute can ACTUALLY be of any typediff --git a/autogpt_platform/frontend/src/lib/autogpt-server-api/types.ts b/autogpt_platform/frontend/src/lib/autogpt-server-api/types.tsindex 2d583d2062..74855f5e28 100644--- a/autogpt_platform/frontend/src/lib/autogpt-server-api/types.ts+++ b/autogpt_platform/frontend/src/lib/autogpt-server-api/types.ts@@ -516,7 +516,7 @@ export type GraphValidationErrorResponse = {/* *** LIBRARY *** */-/* Mirror of backend/server/v2/library/model.py:LibraryAgent */+/* Mirror of backend/api/features/library/model.py:LibraryAgent */export type LibraryAgent = {id: LibraryAgentID;graph_id: GraphID;@@ -616,7 +616,7 @@ export enum LibraryAgentSortEnum {/* *** CREDENTIALS *** */-/* Mirror of backend/server/integrations/router.py:CredentialsMetaResponse */+/* Mirror of backend/api/features/integrations/router.py:CredentialsMetaResponse */export type CredentialsMetaResponse = {id: string;provider: CredentialsProviderName;@@ -628,13 +628,13 @@ export type CredentialsMetaResponse = {is_system?: boolean;};-/* Mirror of backend/server/integrations/router.py:CredentialsDeletionResponse */+/* Mirror of backend/api/features/integrations/router.py:CredentialsDeletionResponse */export type CredentialsDeleteResponse = {deleted: true;revoked: boolean | null;};-/* Mirror of backend/server/integrations/router.py:CredentialsDeletionNeedsConfirmationResponse */+/* Mirror of backend/api/features/integrations/router.py:CredentialsDeletionNeedsConfirmationResponse */export type CredentialsDeleteNeedConfirmationResponse = {deleted: false;need_confirmation: true;@@ -888,7 +888,7 @@ export type Schedule = {export type ScheduleID = Brand<string, "ScheduleID">;-/* Mirror of backend/server/routers/v1.py:ScheduleCreationRequest */+/* Mirror of backend/api/features/v1.py:ScheduleCreationRequest */export type ScheduleCreatable = {graph_id: GraphID;graph_version: number;diff --git a/docs/platform/contributing/oauth-integration-flow.md b/docs/platform/contributing/oauth-integration-flow.mdindex dbc7a54be5..f6c3f7fd17 100644--- a/docs/platform/contributing/oauth-integration-flow.md+++ b/docs/platform/contributing/oauth-integration-flow.md@@ -25,7 +25,7 @@ This document focuses on the **API Integration OAuth flow** used for connecting### 2. Backend API Trust Boundary- **Location**: Server-side FastAPI application- **Components**:- - Integration router (`/backend/backend/server/integrations/router.py`)+ - Integration router (`/backend/backend/api/features/integrations/router.py`)- OAuth handlers (`/backend/backend/integrations/oauth/`)- Credentials store (`/backend/backend/integrations/credentials_store.py`)- **Trust Level**: Trusted - server-controlled environmentdiff --git a/docs/platform/ollama.md b/docs/platform/ollama.mdindex 392bfabfe8..ecab9b8ae1 100644--- a/docs/platform/ollama.md+++ b/docs/platform/ollama.md@@ -246,7 +246,7 @@ If you encounter any issues, verify that:```bashollama pull llama3.2```-- If using a custom model, ensure it's added to the model list in `backend/server/model.py`+- If using a custom model, ensure it's added to the model list in `backend/api/model.py`#### Docker Issues- Ensure Docker daemon is running: