Feature Spec: Full Drive Integration Model

1. Problem Statement

Legionis currently exposes only the Legionis workspace folder in its file explorer. Users can see context/, deliverables/, and their workspace subfolders, but nothing else from their Google Drive. This creates a walled garden that contradicts the product's core promise: your files, your cloud, your control.

The result is friction. Users who want an agent to review a strategy doc from last quarter, analyze a spreadsheet from a shared folder, or reference a contract buried three levels deep in their Drive must leave Legionis, find the file in Google Drive's native UI, copy its content, and paste it into the chat. That workflow is the opposite of superpowers. It feels like a downgrade from using Drive natively.

The decision is clear: open the entire Drive to the user inside Legionis, let them drag any file into a conversation, manage files anywhere in their Drive, and restrict agents to writing only in the Legionis workspace. The user is the host. Legionis is the guest. The guest should not rearrange the furniture.

2. Decision

The Model

Full Drive browsing. Users navigate their entire Google Drive freely within the Legionis file explorer. My Drive root is the top level. The Legionis workspace folder is visually pinned and highlighted, but it is one folder among many.

Drag and drop into chat. Users drag files from the file explorer into the chat input area. The system reads the file content and injects it into the agent's context. Any file in the user's Drive is eligible.

Full file management. Users can move, rename, create folders, and delete files anywhere in their Drive from within Legionis. Standard file operations. No restrictions.

Agent write boundary. Agents create new deliverables exclusively in the Legionis workspace folders (context/, deliverables/, and subfolders). This is the single hard constraint. Agents can read anything the user shares with them, but they cannot write outside the workspace.

Why This Model

The Drive belongs to the user. Legionis adds intelligence to it. A restricted file browser feels like a downgrade from native Drive. This model makes Drive feel like it gained superpowers: the same familiar space, but now you can pull a file into a conversation and an agent acts on it immediately.

This directly reinforces two core differentiators:

USP #1 (Cloud Storage Connectivity): The Drive integration is not a feature. It is the architecture.
USP #6 (Full Data Ownership): Users manage their own files. Agents write to a designated workspace. The boundary is clean and verifiable.

US-1: Browse Full Drive

As a Legionis user with a connected Google Drive, I want to see my entire Drive in the file explorer, so that I can find and access any file without leaving Legionis.

Acceptance Criteria:

Given I have connected Google Drive, when I open the file explorer, then I see My Drive root with all top-level folders and files.
Given I click a folder, then its contents load and display with standard file/folder icons.
Given the Legionis workspace folder exists, then it appears pinned at the top of the explorer with a distinct visual indicator (Legionis icon or highlight color).

US-2: Drag File into Chat

As a user working with an agent, I want to drag a file from the explorer into the chat input, so that the agent receives the file's content as context for its response.

Acceptance Criteria:

Given I drag a supported text file onto the chat input area, then a visual drop indicator appears (highlight border, "Drop to attach" label).
Given I drop the file, then a file attachment chip appears in the chat input showing the file name and size.
Given I send the message with the attached file, then the agent's response reflects awareness of the file's content.
Given I attach multiple files (up to 5), then all file contents are included in the agent's context.

US-3: Manage Files Anywhere

As a user organizing my Drive, I want to rename, move, create folders, and delete files from within Legionis, so that I do not need to switch to the Google Drive web app for file management.

Acceptance Criteria:

Given I right-click a file or folder, then a context menu appears with Rename, Move, Delete, and (for folders) New Folder options.
Given I select Rename, then the name becomes editable inline.
Given I select Move, then a folder picker dialog appears showing my Drive structure.
Given I select Delete, then a confirmation dialog appears before the file is moved to Drive trash.

US-4: Agent Reads Attached Files

As a product manager using the @pm agent, I want to attach a competitor's analysis document and ask the agent to review it, so that the agent can produce a competitive assessment based on the actual document.

Acceptance Criteria:

Given I attach a file and type "Review this competitive analysis," when the agent processes the request, then the agent's context includes the full file content.
Given the attached file is a Google Doc, then the system exports it as plain text before injecting into context.
Given the file exceeds 100KB of text content, then the system truncates with a notice: "[Truncated: showing first 100KB of {filename}]".

US-5: Agent Write Boundary Enforced

As a user concerned about data integrity, I want agents to only create files in the Legionis workspace folder, so that my personal Drive structure is never modified by an AI without my direct action.

Acceptance Criteria:

Given an agent calls writeFile or editFile, when the target path resolves to a location outside the Legionis workspace folder, then the operation is rejected with an error: "Write operations are restricted to the Legionis workspace."
Given an agent calls readFile with a file ID from any location in Drive, then the read succeeds (no boundary restriction on reads).
Given the workspace folder ID is ws_folder_123, then all agent write targets must resolve to descendants of ws_folder_123.

US-6: Locate Workspace Quickly

As a user with a large Drive, I want the Legionis workspace folder to be visually prominent and always accessible, so that I can navigate to agent deliverables with one click regardless of where I am in my Drive.

Acceptance Criteria:

Given the file explorer is open, then the Legionis workspace folder appears in a pinned section at the top, above the general Drive tree.
Given I click the pinned workspace entry, then the explorer navigates directly to the workspace folder.
Given I am deep in another folder, then the pinned workspace entry remains visible and clickable.

US-7: Drag from Outside Workspace

As a user with files scattered across Drive folders, I want to drag a file from any folder (not just the workspace) into chat, so that agents can work with my existing documents regardless of where they are stored.

Acceptance Criteria:

Given I navigate to a non-workspace folder (e.g., "Shared with me" or "Projects/Q1"), when I drag a file to chat, then the attachment works identically to workspace files.
Given the file is owned by someone else (shared with me), when I drag it into chat, then the system reads it using my Drive permissions and includes the content.

4. Functional Requirements

FR-1: Full Drive Browsing

ID	Requirement
FR-1.1	The file explorer root is the user's My Drive, not the Legionis workspace folder.
FR-1.2	The Legionis workspace folder is pinned at the top of the explorer in a visually distinct "Workspace" section with the Legionis icon.
FR-1.3	Folder navigation is lazy-loaded: contents are fetched on expand, not preloaded.
FR-1.4	The explorer supports pagination for folders with 200+ items (Drive API `nextPageToken`).
FR-1.5	File and folder entries display: name, icon (by MIME type), and modified date.
FR-1.6	The explorer supports "Shared with me" as a navigable section below My Drive.
FR-1.7	Google Workspace files (Docs, Sheets, Slides) display their native icons and are browsable but not directly editable inline. They can be dragged into chat for reading.

FR-2: Drag-and-Drop File Attachment

ID	Requirement
FR-2.1	Files in the explorer are draggable. The drag preview shows the file name and icon.
FR-2.2	The chat input area is a valid drop target. On drag-over, it displays a visual indicator (blue border highlight, "Drop file to attach" overlay).
FR-2.3	On drop, the system creates a file attachment chip in the chat input with: file name, MIME type icon, and a remove button (x).
FR-2.4	The file is NOT downloaded on drop. Content is fetched on message send to avoid unnecessary API calls.
FR-2.5	Maximum 5 files per message. Attempting to add a 6th displays: "Maximum 5 files per message."
FR-2.6	Supported file types for content injection: plain text, markdown, JSON, CSV, TSV, Google Docs (exported as text), Google Sheets (exported as CSV).
FR-2.7	Unsupported file types (images, PDFs, binaries) display in the chip but inject a metadata-only reference: "[Attached: {filename}, {mimeType}, {size}. Content not extractable as text.]"
FR-2.8	Per-file content limit: 100KB of extracted text. Files exceeding this are truncated with a notice appended to the content.

FR-3: File Management Operations

ID	Requirement
FR-3.1	Right-click (or long-press on mobile) on any file or folder in the explorer opens a context menu.
FR-3.2	Context menu options for files: Open (preview), Rename, Move to, Delete, Copy Link.
FR-3.3	Context menu options for folders: Open, Rename, New Folder, Move to, Delete.
FR-3.4	Rename: inline edit with Enter to confirm, Escape to cancel. Calls `files.update` with new `name`.
FR-3.5	Move to: opens a folder picker dialog. On confirm, calls `files.update` with `addParents` (new parent) and `removeParents` (old parent).
FR-3.6	Delete: confirmation dialog ("Move {name} to trash?"). On confirm, calls `files.update` with `trashed: true`.
FR-3.7	New Folder: creates a new folder inside the selected folder. Inline name input, default "Untitled folder".
FR-3.8	All management operations are available everywhere in Drive, not restricted to the workspace.
FR-3.9	Optimistic UI updates: the explorer reflects the change immediately, rolling back on API failure with an error toast.

FR-4: Agent Write Boundary

ID	Requirement
FR-4.1	Agent tools `writeFile` and `editFile` enforce that the target resolves to a descendant of the workspace folder (`workspaces.driveFolderId`).
FR-4.2	The boundary check occurs in the tool execution layer, not in the Drive API wrapper. This ensures all agent code paths are covered.
FR-4.3	If an agent attempts a write outside the workspace, the tool returns an error string: "Write denied: agents can only create files in the Legionis workspace. Target path: {path}."
FR-4.4	The agent's system prompt includes an explicit instruction: "You can read any file the user shares with you, but you can only write to the Legionis workspace folder."
FR-4.5	User-initiated file management (FR-3) is NOT subject to this boundary. Users manage their entire Drive freely.

FR-5: Agent File Reading

ID	Requirement
FR-5.1	A new agent tool `readDriveFile` accepts a `fileId` parameter (not a workspace-relative path) and returns the file content.
FR-5.2	`readDriveFile` works for any file the user's Drive credentials can access, regardless of location.
FR-5.3	When a user sends a message with attached files, the chat route fetches each file's content via `readDriveFile` and prepends it to the agent's context as a system message block.
FR-5.5	The existing workspace-relative tools (`readFile`, `writeFile`, `editFile`, `listDirectory`, `glob`, `grep`) continue to work unchanged for workspace operations.
FR-5.6	Google Workspace files (Docs, Sheets, Slides) are exported before reading: Docs to plain text, Sheets to CSV, Slides to plain text.

5. UX Specifications

5.1 File Explorer: Full Drive with Pinned Workspace

+-----------------------------------------------+

FILE EXPLORER                            [x]


+-----------------------------------------------+



WORKSPACE
+-- [L] Legionis Workspace          (pinned)
+-- context/
+-- deliverables/

─────────────────────────────────

MY DRIVE
+-- [>] Clients/
+-- [>] Finance/
+-- [L] Legionis Workspace
+-- [>] Marketing/
+-- [>] Projects/
+-- [>] Shared Resources/
strategy-2026.md
budget-template.xlsx

SHARED WITH ME
+-- [>] Partner Docs/
+-- [>] Board Materials/


+-----------------------------------------------+


WORKSPACE
+-- [L] Legionis Workspace (pinned)
+-- context/
+-- deliverables/

─────────────────────────────────

MY DRIVE
+-- [>] Clients/
+-- [>] Finance/
+-- [L] Legionis Workspace
+-- [>] Marketing/
+-- [>] Projects/
+-- [>] Shared Resources/
strategy-2026.md
budget-template.xlsx

SHARED WITH ME
+-- [>] Partner Docs/
+-- [>] Board Materials/

Notes:

[L] = Legionis icon (amber accent, distinct from folder icon)
[>] = collapsed folder arrow
The Workspace section is always visible at the top, separated by a divider.
The Legionis workspace also appears in its natural position under My Drive (not hidden).
Sections collapse independently.

5.2 Drag-and-Drop into Chat

+-----------------------------------------------+

CHAT


[User]: Review this competitor analysis
[PM]: I'd be happy to review it. Could you
share the document?



+-----------------------------------------------+



Drop file to attach 
~~~ (blue dashed border) ~~~ 


+-----------------------------------------------+
After drop:
+-----------------------------------------------+



[competitor-analysis.md] [x]

Type your message...                [Send]


+-----------------------------------------------+

CHAT

[User]: Review this competitor analysis
[PM]: I'd be happy to review it. Could you
share the document?


[competitor-analysis.md] [x]

Type your message... [Send]

Notes:

The drop zone activates when a file is dragged over the chat input area.
File chips are small, inline, and dismissible with the [x] button.
Multiple chips stack horizontally, wrapping to a second line if needed.

5.3 File Management Context Menu

+-----------------------------------------------+

MY DRIVE

+-- [>] Projects/
+-- Q1-strategy.md
+-- competitor-d Open 
Rename 
Move to... 
Delete 
Copy Link 


+-----------------------------------------------+

Notes:

Context menu appears on right-click (desktop) or long-press (mobile).
Menu items have icons (eye for Open, pencil for Rename, folder-arrow for Move, trash for Delete, link for Copy Link).
Menu disappears on click outside or Escape.

5.4 Agent Response with Attached File Reference

+-----------------------------------------------+

CHAT


[User]: Review this and give me feedback
[competitor-analysis.md]

[PM]: Looking at the competitor analysis
you shared, I see three things worth
calling out.

First, the pricing comparison on page 2
understates our BYOT advantage...

I've saved my detailed review to:
deliverables/competitor-review-2026-02.md


+-----------------------------------------------+

CHAT

[User]: Review this and give me feedback
[competitor-analysis.md]

[PM]: Looking at the competitor analysis
you shared, I see three things worth
calling out.

First, the pricing comparison on page 2
understates our BYOT advantage...

I've saved my detailed review to:
deliverables/competitor-review-2026-02.md

Notes:

The attached file appears as a chip in the user's message bubble.
The agent references the file naturally, by name.
The agent writes its deliverable to the workspace (deliverables/), not to the user's personal folders.

5.5 Move To Dialog

+-----------------------------------------------+

Move "budget-v2.xlsx" to:


+-----------------------------------------------+



My Drive
+-- [>] Clients/
+-- [v] Finance/
+-- 2025/
+-- 2026/     <-- (selected, highlighted)
+-- [>] Projects/

[ New Folder ]


+-----------------------------------------------+

[ Cancel ]  [ Move Here ]


+-----------------------------------------------+


My Drive
+-- [>] Clients/
+-- [v] Finance/
+-- 2025/
+-- 2026/ <-- (selected, highlighted)
+-- [>] Projects/

[ New Folder ]

6. Technical Requirements

6.1 API Route Changes

Route	Current	Change
`GET /api/drive/files`	Lists workspace folder contents by path	Add `mode` query param: `mode=workspace` (default, existing behavior) or `mode=drive` (lists by Drive folder ID). When `mode=drive`, accept `folderId` param instead of `path`. For root, use `'root' in parents`.
`GET /api/drive/files/[id]`	Reads file by Drive file ID	No change needed. Already supports any file ID. Remove the "verify belongs to workspace" comment and the intent behind it.
`GET /api/drive/files/content`	Reads file by workspace-relative path	No change needed. Continues to serve workspace-relative reads.
NEW `PUT /api/drive/files/[id]`	N/A	Rename a file: accepts `{ name: string }`. Calls `files.update`.
NEW `PATCH /api/drive/files/[id]/move`	N/A	Move a file: accepts `{ newParentId: string, oldParentId: string }`. Calls `files.update` with `addParents`/`removeParents`.
NEW `DELETE /api/drive/files/[id]`	N/A	Trash a file: calls `files.update` with `{ trashed: true }`.
NEW `POST /api/drive/files`	N/A	Create a new folder: accepts `{ name: string, parentId: string, mimeType: "application/vnd.google-apps.folder" }`.
NEW `POST /api/drive/files/export`	N/A	Export Google Workspace file as text: accepts `{ fileId: string, exportMimeType: string }`. Returns plain text content. Used for Docs/Sheets/Slides attachment.

6.2 Component Changes

Component	Current	Change
`file-tree.tsx`	Shows workspace root only. Fetches from `GET /api/drive/files?path=/`.	Redesign to show two sections: (1) Pinned Workspace section fetching workspace root, (2) Full Drive section fetching `GET /api/drive/files?mode=drive&folderId=root`. Lazy-load children on folder expand.
`file-item.tsx`	Renders file/folder with expand/collapse.	Add: (a) drag handle via HTML5 Drag and Drop API, setting `dataTransfer` with `fileId`, `fileName`, `mimeType`. (b) Right-click handler for context menu. (c) Visual distinction for Legionis workspace items (amber accent).
`file-preview.tsx`	Markdown preview panel for workspace files.	Extend to handle any Drive file. Fetch content via `GET /api/drive/files/[id]` for non-workspace files. Handle Google Workspace exports.
NEW `context-menu.tsx`	N/A	Floating context menu component. Positioned at right-click coordinates. Options: Open, Rename, Move to, Delete, Copy Link. Triggers corresponding API calls.
NEW `move-dialog.tsx`	N/A	Modal dialog with folder tree browser for selecting move destination. "New Folder" button at bottom. Confirm/Cancel actions.
NEW `file-drop-zone.tsx`	N/A	Wraps the chat input area. Handles `onDragOver`, `onDragLeave`, `onDrop` events. On drop, extracts `fileId` from `dataTransfer`, creates attachment chip. Manages attachment state (array of `{ fileId, name, mimeType }`).
NEW `file-attachment-chip.tsx`	N/A	Inline chip component: file icon + name + remove button. Displayed in chat input area above the text field.

6.3 Agent Runtime Changes

Area	Current	Change
Chat route (`src/app/api/chat/route.ts`)	Accepts `{ messages, agentId }`.	Accept additional field `attachments: Array<{ fileId: string, name: string, mimeType: string }>`. For each attachment, fetch content (via Drive client), build context block, prepend to model messages as a system message.
Tool: `readFile`	Reads by workspace-relative path.	No change. Continues to resolve paths within workspace.
Tool: `writeFile`	Writes by workspace-relative path.	Add boundary enforcement. Before calling `workspace.writeFile()`, verify the resolved target is a descendant of the workspace folder. Reject with error string if not.
Tool: `editFile`	Reads then writes by workspace-relative path.	Same boundary enforcement as `writeFile`. The read portion has no restriction; the write-back must target workspace.
NEW Tool: `readDriveFile`	N/A	New tool definition. Parameters: `fileId: string`. Description: "Read a file from the user's Google Drive by its file ID. Use this for files the user has attached to the conversation." Calls Drive API directly (not workspace path resolver). Handles Google Workspace export.
System prompt	No mention of Drive access boundaries.	Append to L1 (base) system prompt: "File access: You can read any file the user attaches or shares (using readDriveFile). You can only write files to the Legionis workspace folder (using writeFile and editFile). Never attempt to modify files outside the workspace."
ToolContext	Contains `workspace`, `userId`, `agentId`, `provider`, `apiKey`, `workspaceId`.	Add `driveClient: drive_v3.Drive`	null for direct Drive access by `readDriveFile`. Add `workspaceFolderId: string`	null for boundary checks.

6.4 Drive Workspace Class Changes

Area	Current	Change
`DriveWorkspace` constructor	Takes `rootFolderId` (workspace folder).	No change to the class itself. The workspace abstraction remains scoped to the workspace folder. The new `readDriveFile` tool bypasses this class and uses the Drive client directly.
`PathResolver`	Resolves paths relative to workspace root.	No change. Path resolution for workspace operations stays the same.
NEW `DriveExporter`	N/A	Utility class in `src/lib/drive/exporter.ts`. Handles Google Workspace file export: `exportAsText(drive, fileId, mimeType) => string`. Maps: `application/vnd.google-apps.document` to `text/plain`, `application/vnd.google-apps.spreadsheet` to `text/csv`, `application/vnd.google-apps.presentation` to `text/plain`.

6.5 Database Changes

No schema changes required. The existing file_references table can optionally cache non-workspace file metadata for performance, but this is not required for the initial implementation. The workspaces.driveFolderId field already stores the workspace boundary reference needed for FR-4.

7. Security and Privacy

7.1 Permission Model

Actor	Read Scope	Write Scope
User (via explorer)	Entire Drive (My Drive + Shared with me)	Entire Drive (rename, move, delete, create folder)
Agent (via tools)	Any file the user attaches or references by file ID	Legionis workspace folder and its descendants only
Legionis backend	Only files accessed during active requests. No background scanning or indexing.	Only workspace folder (for initialization and agent writes).

7.2 Data Handling

No server-side storage of Drive file content. File content is fetched on-demand, streamed to the agent as context, and discarded after the response. Legionis servers never persist Drive file content.
File metadata caching. The file_references table caches file IDs, paths, and MIME types for workspace files. Non-workspace file metadata may be cached in-memory during a session but is not persisted to the database.
Token security. Drive OAuth tokens are encrypted at rest (driveAccessToken, driveRefreshToken in the workspaces table). Token refresh is handled automatically by the Drive client. Refreshed tokens are re-encrypted before persistence.
No cross-user access. Each user's Drive client is scoped to their own OAuth credentials. There is no mechanism for one user to access another user's Drive files through Legionis.

7.3 What Agents Cannot Do

Write, edit, move, rename, or delete files outside the Legionis workspace folder.
Access Drive files that the user's Google account cannot access (permissions are inherited from Google Drive).
Store or transmit file content to any destination other than the LLM provider the user has configured (BYOT).
Browse the user's Drive autonomously. Agents only see files that the user explicitly attaches to a conversation or that exist in the workspace.

7.4 Boundary Enforcement Implementation

The agent write boundary is enforced at two layers:

Tool layer (primary). The writeFile and editFile tools check that the resolved file ID is a descendant of workspaceFolderId before executing the write. This is a hard gate.

System prompt (advisory). The agent's system prompt explicitly instructs it to only write to the workspace. This reduces the frequency of boundary-rejected calls, but is not relied upon for security.

Layer 1 is the security boundary. Layer 2 is a UX optimization to avoid wasted API calls.

8. Success Criteria

#	Criterion	Measurement
SC-1	User can browse their full Drive and navigate to any folder within 3 clicks from explorer root.	Manual QA: navigate to a 3-level deep folder.
SC-2	User can drag a text file from any Drive folder into chat and the agent's response references its content.	End-to-end test: drag file, send message, verify agent context.
SC-3	User can rename, move, and delete files anywhere in Drive via context menu. Operations reflect in Google Drive's native UI within 5 seconds.	Manual QA: perform operation in Legionis, verify in Drive.
SC-4	Agent write to a path outside the workspace is rejected with an error.	Automated test: mock agent writeFile call targeting a non-workspace path, assert rejection.
SC-5	Agent can read any attached file regardless of its Drive location.	End-to-end test: attach file from "Shared with me," verify agent receives content.
SC-6	Google Docs, Sheets, and Slides are exportable as text when attached to chat.	Automated test: attach each Google Workspace type, verify text extraction.
SC-7	File explorer loads the Drive root in under 2 seconds on a typical Drive (fewer than 500 root-level items).	Performance benchmark with test account.
SC-8	The Legionis workspace folder is always visible and accessible with one click from the pinned section.	Manual QA: verify pinned section is persistent across navigation.

9. Out of Scope

The following are explicitly excluded from this feature:

Item	Rationale
Inline editing of Google Docs/Sheets/Slides	Google Workspace files have their own editors. Opening them in a new tab (via Copy Link) is sufficient.
Real-time Drive sync / file watching	Polling or push notifications for Drive changes are a performance risk. Users refresh the explorer manually.
Agent-initiated file moves or renames	Agents write deliverables. File organization is the user's domain. If needed later, it would require explicit user approval per operation.
Shared Drives (Google Workspace enterprise)	Shared Drives have different API semantics (`supportsAllDrives`, `driveId`). Supported in a future iteration if enterprise demand warrants it.
Offline access or local caching	Legionis is online-first. No offline Drive browsing.
Binary file content injection	Images, PDFs, and other binary files cannot be injected as text context. Metadata-only references are included. Multimodal support (image analysis) is a separate feature.
Drag from desktop to chat	Only in-app drag from the Legionis file explorer is supported. Desktop file drag would require a different upload mechanism.
Search across Drive	Full-text search within the Drive explorer is not part of this spec. The existing `glob` and `grep` tools work within the workspace. Drive-wide search is a future enhancement.

10. Open Questions

#	Question	Owner	Target Date
OQ-1	Should the "Shared with me" section be a top-level section in the explorer, or nested under My Drive? Google Drive treats it as a separate view.	Yohay	Before implementation
OQ-2	For Google Sheets with multiple tabs, should we export all tabs as CSV or only the first? Multiple tabs could produce large payloads.	Yohay	During implementation
OQ-3	Should we add a "Pin" action to the context menu so users can pin frequently-used non-workspace folders to the top section alongside the Legionis workspace?	Yohay	Post-MVP enhancement decision
OQ-4	Rate limiting on file management operations: should we throttle rapid renames/moves to avoid hitting Google Drive API quotas (1,000 queries per 100 seconds per user)?	Engineering	During implementation

Appendix: File Inventory

Files to Create

File	Purpose
`src/components/explorer/context-menu.tsx`	Right-click context menu for file management
`src/components/explorer/move-dialog.tsx`	Folder picker dialog for move operations
`src/components/chat/file-drop-zone.tsx`	Drop target wrapper for chat input
`src/components/chat/file-attachment-chip.tsx`	Inline file attachment display
`src/tools/read-drive-file.ts`	New agent tool for reading any Drive file by ID
`src/lib/drive/exporter.ts`	Google Workspace file export utility
`src/app/api/drive/files/[id]/move/route.ts`	Move file API route
`src/app/api/drive/files/export/route.ts`	Google Workspace export API route

Files to Modify

File	Change
`src/components/explorer/file-tree.tsx`	Two-section layout (pinned workspace + full Drive), lazy loading by folder ID
`src/components/explorer/file-item.tsx`	Drag handle, right-click handler, workspace visual distinction
`src/components/explorer/file-preview.tsx`	Support non-workspace files via file ID fetch
`src/app/api/drive/files/route.ts`	Add `mode=drive` support, folder ID navigation, pagination
`src/app/api/drive/files/[id]/route.ts`	Add PUT (rename) and DELETE (trash) handlers
`src/app/api/chat/route.ts`	Accept `attachments` array, fetch content, inject into context
`src/tools/write-file.ts`	Add workspace boundary check before write
`src/tools/edit-file.ts`	Add workspace boundary check before write-back
`src/tools/index.ts`	Export `readDriveFile`
`src/lib/agent/runtime.ts`	Add `readDriveFile` to `allTools`, pass `driveClient` and `workspaceFolderId` in context
`src/lib/drive/resolve-workspace.ts`	Return `driveClient` and `workspaceFolderId` alongside workspace
`src/lib/workspace/types.ts`	Extend `ToolContext` with `driveClient` and `workspaceFolderId`

MY DRIVE
+-- [>] Projects/
+-- Q1-strategy.md
+-- competitor-d	Open
	Rename
	Move to...
	Delete
	Copy Link

Feature Spec: Full Drive Integration Model

1. Problem Statement

2. Decision

The Model

Why This Model

3. User Stories

US-1: Browse Full Drive

US-2: Drag File into Chat

US-3: Manage Files Anywhere

US-4: Agent Reads Attached Files

US-5: Agent Write Boundary Enforced

US-6: Locate Workspace Quickly

US-7: Drag from Outside Workspace

4. Functional Requirements

FR-1: Full Drive Browsing

FR-2: Drag-and-Drop File Attachment

FR-3: File Management Operations

FR-4: Agent Write Boundary

FR-5: Agent File Reading

5. UX Specifications

5.1 File Explorer: Full Drive with Pinned Workspace

5.2 Drag-and-Drop into Chat

5.3 File Management Context Menu

5.4 Agent Response with Attached File Reference

5.5 Move To Dialog

6. Technical Requirements

6.1 API Route Changes

6.2 Component Changes

6.3 Agent Runtime Changes

6.4 Drive Workspace Class Changes

6.5 Database Changes

7. Security and Privacy

7.1 Permission Model

7.2 Data Handling

7.3 What Agents Cannot Do

7.4 Boundary Enforcement Implementation

8. Success Criteria

9. Out of Scope

10. Open Questions

Appendix: File Inventory

Files to Create

Files to Modify