Spring 2026 Roadmap

Scope of Work

This document serves as both the project roadmap for Open Parachute and the Scope of Work for ATLAS Creative Technology & Design at CU Boulder.

Student

Aaron Gabriel

Program

ATLAS, CU Boulder

Advisor

Kurt Smith

Meeting Cadence

Biweekly

Final Presentation

April 22, 2026

Repository

github.com/OpenParachutePBC

Vision

Parachute is an open-source personal AI platform built around a simple premise: instead of you learning the system, the system learns you.

We're building two entry points into one coherent system—connected by an intelligent graph database that gives everything shared memory.

Parachute Daily is a journaling app with gentle AI integration—daily reflections, weekly synthesis, pattern detection. Hosted service, accessible price point, designed for the 90% of people who want to think better without running a server. Read the full vision →

Parachute Computer is the full agentic platform—Claude Code for your entire life, not just your codebase. It combines Chat with deep context, Daily journaling, and Brain (your personal knowledge graph) into one integrated system that runs on your machine, with your data, under your control.

The two products connect through a seamless upgrade path: months of Daily journals flow into Parachute Brain, which bootstraps a system that already knows you the moment you switch.

Progress This Semester

Since the semester started in mid-January, 200+ pull requests merged across the repository have transformed Parachute from an early prototype into a near-launch platform. Here's the arc:

January: Foundation

• Built a multi-agent daily system with reflection agents and a content-scout that processes journal entries
• Added API key authentication for multi-device access
• Shipped local voice transcription using Sherpa-ONNX with Parakeet models—works fully offline on macOS and Android
• Built a CI/CD pipeline with code signing, notarization, and automated DMG builds for macOS distribution
• Designed the product architecture and wrote the Modular Architecture PRD—the design document that shaped the rebuild
• Published this documentation site at openparachute.io

February: The Big Build

• Completely rewrote the server as Parachute Computer—12,800+ lines of new code in under two weeks
• Built the module system: brain, chat, and daily as independent modules with SHA-256 hash verification
• Implemented three trust tiers (full / restricted / sandboxed) with Docker container isolation for untrusted sessions
• Built Telegram and Discord bot connectors with a per-user pairing and approval flow
• Created the parachute CLI for install, daemon management, config, diagnostics, module management, and updates
• Added workspaces—named capability scopes that control which tools, MCPs, and models are available per session
• Built the unified Flutter app with an adaptive multi-panel layout (mobile / tablet / desktop)
• Decomposed large monolithic files into focused services—chat_service.dart went from 2,059 lines to 9 focused files
• Built the event-driven hooks system for extending behavior at every lifecycle point

March: Graph as Core Infrastructure

• Dissolved Brain as a standalone module—graph database became core infrastructure connecting all of Parachute
• Complete brain system redesign: memory feed UI, MCP Cypher tools, graph-native entity system
• Unified projects and conversation schema into a single coherent graph
• Built chat system prompt modes (converse / cocreate) with skills pipeline
• Shipped container file browser—full end-to-end with symlink support
• Hardened Daily: durable audio staging, offline sync fixes, graph-native agent definitions (Callers & Cards)
• Extracted orchestrator phase methods, context system cleanup, WAL corruption fixes
• UI polish across the app—approaching internal launch readiness

What Exists Today

Parachute Computer (Server)

• AI orchestration server (Python/FastAPI) wrapping the Claude Agent SDK with session management and streaming
• Three trust tiers—full access, restricted, or sandboxed in Docker containers—so you control what AI can touch
• Graph database as core infrastructure—an intelligent knowledge graph connecting journals, conversations, and entities across the entire system
• Modular architecture: brain, chat, and daily ship as independent modules with hash verification
• Workspaces that scope what tools, MCPs, and capabilities are available per session
• Telegram, Discord, and Matrix bot connectors with per-user trust and a pairing approval flow
• Multi-agent workspace teams—agents that spawn and coordinate sub-agents within your system
• MCP server for session and journal search, workspace operations, inter-agent messaging
• A real CLI (parachute) for install, daemon management, config, diagnostics, module management, and updates
• Event-driven hooks for extending behavior at every lifecycle point

Parachute App (Client)

• Unified Flutter app with Chat, Daily, and Brain tabs
• Adaptive layout: single-panel on mobile, dual-panel on tablet, three-panel on desktop
• Voice journaling with local Sherpa-ONNX transcription (works fully offline)
• Brain—memory feed UI, entity browser, and Cypher query tools backed by the graph database
• Chat redesign with two-phase streaming and polished session management
• Workspace picker, model selection, trust level controls, bot session management
• CI/CD pipeline with macOS code signing and notarized DMG builds

Project Objectives

• Launch Parachute Daily—a standalone hosted journaling app with AI reflections, bringing the core Parachute experience to a much wider audience
• Ship Parachute Computer to real users—open-source launch to the Claude Code community, Learn Vibe Build graduates, and beyond, building on the Regen Hub foundation
• Complete the Daily → Brain → Chat loop—journals feeding the knowledge graph, which enriches every conversation over time
• Design and build a hardware pendant—collaborating with Marvin Melzer to create a wearable device for always-on voice capture
• Grow an open-source community—launch publicly, get to 100+ active users
• Find a revenue path—Parachute Daily subscriptions and hosted Computer options; identify a model that reaches $1,000 MRR by April 22
• Maintain modular foundations—ship fast while keeping architecture decisions that support long-term extensibility

Architecture

Success Metrics (April 22, 2026)

Timeline

Revenue Path

Open source is the growth engine, not a constraint. Parachute Computer is free for self-hosters. Revenue comes from making the experience easier for people who don't want to run infrastructure—and from a simpler product built for a wider audience.

• Parachute Daily subscriptions—the entry point for most users. Hosted journaling with AI reflections at an accessible price. Simple tiers: sync, daily AI reflections, richer weekly synthesis. This is where the majority of revenue comes from at scale.
• Hosted Parachute Computer—a managed service for power users who want everything without running a server. Higher-margin, lower-volume.
• Hardware pendant—wearable voice capture device, in development with Marvin Melzer. Future revenue stream once prototyping is complete.

The upgrade path is the flywheel: Daily users build months of journal context, then upgrade to Computer where Brain ingests their history and immediately knows them. Retention compounds on both sides.

Early 2026 focuses on real users and real usage. Revenue experimentation follows once usage patterns show which path has the most pull. Target: a path to $1,000 MRR identified by April 22.

Stretch Goals

• Community modules—third-party modules that extend Parachute Computer
• Multi-provider AI—beyond Claude: Gemini, local models, other providers through the modular agent system