azure-workspace

byOrion Photo

## THE THESIS Every app exists because humans can't do something fast enough. - Email exists because you can't deliver messages by hand - Excel exists because you can't calculate 10,000 rows in your head - Jira exists because you can't remember 500 tasks across 20 people - Chrome exists because you can't visit 100 websites simultaneously - CRM exists because you can't remember 10,000 customer interactions **What if ONE AI could do ALL of it — and remember everything, learn from everything, and get better every time?** Not by integrating with apps. Not by being a chatbot that answers questions. Not by being a task runner that disappears after completion. By being the PLACE where all your work happens. The AI does the work. The workspace ORGANIZES the work. The knowledge ACCUMULATES. The system LEARNS. You DIRECT and REVIEW. **We're building IntelliFish — an open-source AI agent where:** - You type what you need in natural language - AI agents execute it (browser automation, desktop control, data extraction, form filling, research) - Results are AUTOMATICALLY organized into a living workspace - Knowledge compounds — run 100 is smarter than run 1 - Everything is searchable, shareable, exportable, schedulable - The AI remembers your preferences, your projects, your entities, your patterns - Zero vendor lock-in — self-hosted, open source, your data stays yours **The workspace IS the product. Not the chat. Not the agents. The WORKSPACE.** --- ## WHAT WE'VE ALREADY BUILT (real, working code — 30K+ lines) ### Agent Engine (working, tested) - 10 parallel browser agents with live CDP video streaming - DuckDuckGo self-healing when pages block the agent - BrightData residential proxy on every agent - Stealth fingerprinting (UA rotation, WebGL spoof, timezone match) - Smart Loop V2: lightweight navigation (512 tokens) + full-power extraction (4096 tokens) - Progressive extraction — data saved at EVERY step, crash-resilient - 5-dimension quality scoring on every agent output (goal adherence, completeness, freshness, depth, content quality) - Cross-agent intelligence bus — parallel agents share discoveries in real-time - Site memory — agents learn per-site cookie selectors, data locations, navigation patterns - UNIVERSAL_EXTRACTION_MANDATE — structured V11 intelligence schema - SearXNG dynamic source discovery — 20+ sources per query in real-time ### Frontend (91 components, 87 pages built) - AG-UI chat interface with GenUI cards (approval, progress, results, error) - Live multi-screen browser streaming (watch all agents work simultaneously) - Intelligence report page with findings, entities, traceability, export - Workspace page with artifacts, entities, entity graph, canvas, timeline, search - Full sidebar navigation (Chat, Templates, Jobs, History, Settings, Help) ### Database - PostgreSQL with workspace tables: artifacts, entities, relationships, facts, canvas_items - Intelligence runs table with full audit trail - Workspace builder that auto-populates after every agent run ### Export - ZIP package: PDF + Excel + PPTX + JSON + per-agent source reports + SHA-256 manifest + audit trail --- ## THE QUESTION I NEED ANSWERED **How do I design a workspace that makes every other app unnecessary?** Not a dashboard. Not a project management tool. Not a knowledge base. Not a CRM. Not a task tracker. ALL OF THEM. In ONE place. Powered by AI agents that do the work automatically. --- ## WHAT I NEED PERPLEXITY TO RESEARCH (go DEEP, latest April 2026) ### 1. THE WORKSPACE AS OPERATING SYSTEM How would you design a workspace that functions as a personal operating system for all knowledge work? Not a file system. Not a database. A LIVING SYSTEM where: - AI agents are first-class citizens alongside humans - Every piece of information is connected to every other piece - Knowledge grows automatically from agent work - The system LEARNS what you care about and surfaces it - Tasks generate themselves from findings - Alerts trigger themselves from changes - Reports compile themselves from accumulated data What does this look like? What patterns exist? What's been tried? What failed? What would WORK? Investigate: - Notion's "connected workspace" concept — what makes it sticky? What's missing for AI agents? - ClickUp's "everything app" approach — what works? What's bloated? - Obsidian's "second brain" with bidirectional linking — why do developers love it? - Linear's opinionated design — why is it 10x better than Jira despite having fewer features? - Superhuman's speed — what makes a workspace feel FAST? - Arc browser's "spaces" — how does spatial organization help? - Figma's multiplayer — what makes real-time collaboration work? - Apple's ecosystem integration — what makes everything "just work" together?

LandingChatLogin
Landing

Comments (0)

No comments yet. Be the first!

Project Tasks19

#1

Implement Theme & Structure

To Do

As a user, I want all existing scaffold pages (home, login, signup, welcome, dashboard/overview, dashboard/ai-assistant, dashboard/settings) to visually match the mock-design pages exactly. This includes applying the color palette (#1A1D2E background, #2E3447 surface, #F5F7FA text, #06B6D4 cyan accent, #A3A8B8 muted), typography, spacing, and layout structure from all designed pages. Remove any pages not required by the user flows or design specs. This task must be completed independently before any other UI work begins.

AI 75%
Human 25%
High Priority
2 days
Frontend Developer
#2

Build Landing Page

To Do

As a user, I want to view the Landing page (v2 design) that showcases the azure-workspace product, allows solo developers and freelancers to explore the demo, and leads them to login or sign up. Implement the Living Workspace Garden concept with dynamic growth animations, interactive knowledge graph preview, agent activity visualization (glowing orbs), micro-interactions on hover, and time-based color transitions. Reference the existing Landing (v2) JSX design.

Depends on:#1
Waiting for dependencies
AI 90%
Human 10%
High Priority
2 days
Frontend Developer
#3

Build Login Page

To Do

As a user, I want to sign in to azure-workspace via the Login page (v2 design) with email/password authentication. The page serves as the entry point for Solo Developer, Project Manager, Freelancer, Small Business Owner, and Enterprise Team personas. It links to the signup flow and redirects to the Dashboard on success. Implement using the Login (v2) JSX design with the dark theme and cyan accent.

Depends on:#1
Waiting for dependencies
AI 90%
Human 10%
High Priority
1 day
Frontend Developer
#4

Build Dashboard Page

To Do

As a user, I want to view the Dashboard page (v1 design) that shows daily briefings summarizing overnight AI agent activity, scheduled run results, active task stats, and predictive insights. It is the first page seen after login for all personas. Supports navigation to Jobs, Workspace, Chat, and Settings. Implement using the Dashboard (v1) JSX design with responsive widgets and glassmorphism styling.

Depends on:#1
Waiting for dependencies
AI 88%
Human 12%
High Priority
2 days
Frontend Developer
#5

Build Chat Page

To Do

As a user, I want to use the Chat page (v2 design) to type natural language commands for AI agents to execute tasks such as browser automation, data extraction, research, and form filling. The page displays real-time agent activity feeds, GenUI cards (approval, progress, results, error), and live multi-screen browser streaming. Used by Solo Developer, Freelancer, and Small Business Owner personas. Implement using the Chat (v2) JSX design.

Depends on:#1
Waiting for dependencies
AI 85%
Human 15%
High Priority
2 days
Frontend Developer
#6

Build Workspace Page

To Do

As a user, I want to use the Workspace page (v1 design) as the central hub for viewing the interactive knowledge graph, browsing artifacts, reviewing findings, exploring entity relationships, searching entities, viewing timelines, and reviewing insights. Used by all personas. Implement the 3D-feel graph with pulsing connections, node previews on hover, and canvas/timeline tabs. Reference the Workspace (v1) JSX design.

Depends on:#1
Waiting for dependencies
AI 85%
Human 15%
High Priority
3 days
Frontend Developer
#7

Build Jobs Page

To Do

As a user, I want to use the Jobs page (v1 design) to monitor active and scheduled AI agent tasks, view agent activity logs, schedule automated monitoring tasks for recurring workflows, and see real-time status of running jobs. Used by Project Manager, Enterprise Team, and Small Business Owner personas. Implement using the Jobs (v1) JSX design with real-time status indicators and radar-ping alert styling.

Depends on:#1
Waiting for dependencies
AI 88%
Human 12%
High Priority
2 days
Frontend Developer
#8

Build Settings Page

To Do

As a user, I want to use the Settings page (v1 design) to configure notification preferences, manage user permissions and workspace configurations, and customize workspace behavior. Used by Freelancer (Configure Notifications) and Enterprise Team (Manage Permissions) personas. Implement using the Settings (v1) JSX design with tabbed sections for notifications, permissions, and workspace config.

Depends on:#1
Waiting for dependencies
AI 88%
Human 12%
Medium Priority
1.5 days
Frontend Developer
#9

Build Export Page

To Do

As a user, I want to use the Export page (v1 design) to download results and reports in multiple formats (PDF, Excel, JSON, PPTX, ZIP with audit trail and SHA-256 manifest). Used by Solo Developer (Download Results), Freelancer (Download Results), Project Manager (Share Report), Small Business Owner (Share Report), and Enterprise Team (Download Audit Report) personas. Implement using the Export (v1) JSX design.

Depends on:#1
Waiting for dependencies
AI 88%
Human 12%
Medium Priority
1.5 days
Frontend Developer
#10

Implement Dashboard API

To Do

As a user, I want to use the backend API to retrieve daily briefing summaries, agent activity stats, scheduled run results, and real-time workspace metrics for the Dashboard page. Implement FastAPI endpoints: GET /api/dashboard/briefing, GET /api/dashboard/stats, GET /api/dashboard/activity-feed using PostgreSQL workspace tables.

Depends on:#4
Waiting for dependencies
AI 80%
Human 20%
High Priority
2 days
Backend Developer
#11

Implement AI Chat API

To Do

As a user, I want to use the backend AI API to submit natural language commands, receive real-time streamed responses from AI agents, and view execution progress via SSE. Implement FastAPI endpoints: POST /api/chat/command, GET /api/chat/stream/{session_id}, using LangChain for agent orchestration and Litellm for LLM routing across GPT, Claude, and Gemini models.

Depends on:#5
Waiting for dependencies
AI 75%
Human 25%
High Priority
3 days
AI Engineer
#12

Implement Workspace API

To Do

As a user, I want to use the backend API to retrieve artifacts, entities, relationships, canvas items, and timeline data for the Workspace page. Implement FastAPI endpoints: GET /api/workspace/artifacts, GET /api/workspace/entities, GET /api/workspace/graph, GET /api/workspace/timeline, GET /api/workspace/search with PostgreSQL tsvector full-text search and pgvector similarity search.

Depends on:#6
Waiting for dependencies
AI 78%
Human 22%
High Priority
2.5 days
Backend Developer
#13

Implement Jobs API

To Do

As a user, I want to use the backend API to create, monitor, schedule, and cancel AI agent jobs. Implement FastAPI endpoints: GET /api/jobs, POST /api/jobs/schedule, GET /api/jobs/{job_id}/status, DELETE /api/jobs/{job_id}, with real-time status updates via SSE and PostgreSQL intelligence_runs audit trail.

Depends on:#7
Waiting for dependencies
AI 78%
Human 22%
High Priority
2 days
Backend Developer
#14

Implement Export API

To Do

As a user, I want to use the backend API to generate and download export packages in PDF, Excel, PPTX, JSON, and ZIP formats with SHA-256 manifest and audit trail. Implement FastAPI endpoints: POST /api/export/generate, GET /api/export/{export_id}/download supporting all formats.

Depends on:#9
Waiting for dependencies
AI 75%
Human 25%
Medium Priority
2 days
Backend Developer
#15

Implement Settings API

To Do

As a user, I want to use the backend API to read and update notification preferences, user permissions, and workspace configurations. Implement FastAPI endpoints: GET /api/settings, PUT /api/settings/notifications, GET /api/settings/permissions, PUT /api/settings/permissions with role-based access control for admin vs regular users.

Depends on:#8
Waiting for dependencies
AI 78%
Human 22%
Medium Priority
1.5 days
Backend Developer
#16

Implement Self-Organizing Engine

To Do

As a user, I want the backend AI engine to automatically organize workspace content by detecting patterns across agent runs (e.g., grouping 10 Tesla-related runs into a Tesla project), creating relationship links between related findings, identifying action items from results, and surfacing user preference-based insights. Implement using LangChain agents with PostgreSQL artifact/entity tables.

Depends on:#12#11
Waiting for dependencies
AI 70%
Human 30%
Medium Priority
3 days
AI Engineer
#17

Implement Knowledge Graph Engine

To Do

As a user, I want the backend to build and maintain a temporal knowledge graph using PostgreSQL pgvector, tracking relationships between artifacts, entities, and facts over time. Implement graph construction from agent outputs, relationship scoring, and vector similarity search for the Workspace page's interactive graph visualization.

Depends on:#12
Waiting for dependencies
AI 72%
Human 28%
Medium Priority
3 days
Data Engineer
#18

Implement Real-Time Activity Feed

To Do

As a user, I want to see real-time AI agent activity in the Dashboard and Chat pages via a live activity feed showing agent status, discoveries, and progress. Implement Valkey pub/sub → SSE → React pipeline with FastAPI SSE endpoints and Zustand state management on the frontend for zero-latency updates.

Depends on:#11#10
Waiting for dependencies
AI 75%
Human 25%
High Priority
2 days
Backend Developer
#19

Integrate Frontend with APIs

To Do

As a user, I want all frontend pages (Dashboard, Chat, Workspace, Jobs, Settings, Export) to be fully connected to their backend APIs using React Query for data fetching, Zustand for state management, and optimistic updates for instant-feeling UI. Implement keyboard shortcuts for power users (Linear-style) and ensure full-text search works across 100K+ artifacts.

Depends on:#18#14#11#15#13#10#12
Waiting for dependencies
AI 80%
Human 20%
High Priority
3 days
Frontend Developer
Landing design preview
Login: Sign In
Dashboard: View System Stats
Settings: Manage Permissions
Jobs: Monitor Agent Activity
Workspace: View Knowledge Graph
Workspace: Search Artifacts
Export: Download Audit Report