$ show nokodo-labs/os1
OS1 (nokodo) is a full-stack AI-powered collaborative platform combining autonomous agents, deep research, real-time collaboration, and extensible tooling in a self-hostable workspace. The system features a modular architecture with FastAPI/Python backend, Svelte 5 frontend, and separate admin console, communicating via REST API, WebSocket, and Redis pub/sub. Core capabilities include AI agent construction with tool integration (web search, code execution, file operations), persistent memory system with vector search, real-time document editing, and comprehensive resource management (threads, notes, files, projects, calendars, reminders). The platform emphasizes extensibility through plugin systems for tools, filters, and hooks, with production-ready deployment via Docker Compose.
The LLM identified 5 files worth highlighting for reuse:
Universal ID generation system creating sortable, prefixed IDs (user_, agent_, thread_, etc.) with embedded timestamps. Provides collision-resistant, lexicographically sortable identifiers that enable efficient database indexing and type safety. The implementation demonstrates non-obvious skill in balancing uniqueness, sortability, and type information in a compact string format.
Abstract base classes defining standardized interfaces for AI services (chat models, embeddings, vectorstores, rerankers) with provider-specific implementations. Enables seamless swapping of AI providers (OpenAI, Anthropic, Ollama, etc.) through dependency injection. Demonstrates sophisticated abstraction that handles varying provider APIs while maintaining consistent SDK contracts.
Tag-based Redis caching layer with automatic invalidation via pub/sub messages. Allows caching of API responses with fine-grained invalidation based on resource types and IDs. Shows advanced cache management through Redis pub/sub for cross-worker cache consistency, preventing stale data in distributed deployments.
Modular system for managing AI conversation history through pruning, protection, summarization, and budgeting. Separates concerns into distinct modules (budgets, media, pipeline, protection, pruning, summarization) that work together to maintain context within token limits. Demonstrates comprehensive approach to a complex AI engineering problem with clear separation of concerns.
Durable event persistence system that stores events in database and fans them out via Redis pub/sub for cross-worker propagation. Combines reliability of database persistence with low-latency distribution of Redis pub/sub. Shows sophisticated handling of distributed system challenges with exactly-once delivery semantics and replay capability.