mohio

Mohio Roadmap

This roadmap is user-facing. It outlines Mohio’s current direction and planned phases. It is a planning document, not a fixed delivery contract.

Current Focus

Mohio is currently focused on validating the core workflow for a lightweight team knowledge workspace:

• capture ideas quickly
• turn rough documents into structured knowledge
• review important changes clearly
• keep shared documentation easy to publish and track

Phase 1: Core Workspace

The first milestone is a usable foundation for a bring-your-own-AI, Markdown-based team wiki that works with Codex and Claude Code.

Planned focus areas:

• personal scratchpad for quick document capture
• Markdown-based wiki pages for shared knowledge
• AI proposals from connected tools that suggest new pages, edits, and links
• reviewable diffs before shared content changes
• snapshots and visible history for page-level changes
• explicit publish flow for shared updates

Automatic Sharing & Versioning

Objective: Simplify the commit messaging system, automate workspace syncing, and refine the layout to keep the interface as clean and non-technical as possible.

1. Updated Commit Heuristics (The “Pulse”)

Trigger a Git commit on the following events. Every single commit will use the exact same message schema: Snapshot: [ISO-Date].

• Idle Pulse: After 3 minutes of inactivity following a change.
• Context Switch: Immediately when the user switches to a different document.
• Assistant Dispatch: Immediately before a message is sent to the AI assistant (to ensure the AI has the latest context).
• Safety Guard: Immediately before Rename, Delete, or merging incoming changes.
• Lifecycle Guard: Immediately when the app loses focus and immediately before app exit.

2. Fully Automated “Publishing” (Sharing)

The concept of “Unpublished” files is removed. Sharing is now a background process linked directly to the heuristics.

• Auto-Sync: Every time a commit is created by the heuristics above, Mohio will automatically push the changes to the Git remote.
• Left Sidebar: Remove the Unpublished documents tab entirely. The file tree should just be a clean list of the team’s documents.
• Right Sidebar: UI Copy Change: Rename the right sidebar’s History tab to Versions.
• Manual Sync Control Placement: Place the manual Sync status control at the top right of the application layout. It should be aligned to the right of the main panel, sitting immediately to the left of the icon used to hide the right panel. Even though syncing is automatic, users should be able to force an immediate push if they are about to close their laptop or need someone to see a change right now.

Definition of Done

• All Git commits use the uniform Snapshot: [ISO-Date] format.
• Commits are triggered before sending messages to the assistant.
• The Unpublished view is removed from the left sidebar.
• Commits automatically trigger a git push in the background.
• The manual sync control is correctly positioned to the left of the “Hide Right Panel” icon.
• The right sidebar tab is labeled Versions.

Git v2

• Create a git repository in the background for each workspace to track changes and support collaboration (users should not need to interact with Git directly).
• When the user clicks Sync and there is no remote git repo, prompt the user to connect a remote git repository (GitHub, GitLab, Bitbucket, or custom).
• The user can decide to login with their github ceredentials and select a repository to connect to, or they can choose to create a new private repository for the workspace.
• The user can open a remote git repository directly from the start screen and choose to connect it to the workspace.

Semantic Summaries (The “Secret Sauce”)

Since you have a “technical” person, use a small LLM call (or a simple regex) to look at the diff before committing. Instead of auto-save, use a summary:

• If 1 line changed: Update (Small edit)
• If 20+ lines changed: Update (Major revision)
• If headers changed: Update (Restructured document)

Phase: Private and Shared Documents

• Clarify the split between private documents and shared documents.
• Private documents support quick capture and early drafting.
• Shared documents capture structured knowledge for team use.
• Private documents remain user-only until shared.
• Shared documents are visible to workspace collaborators.
• Private documents are listed by recency in a flat list.
• Shared documents stay organized in a folder hierarchy.
• Users can promote private documents into shared documents when ready.
• The left panel should expose clear navigation between private documents and shared documents.
• Sorting options should include modified time, created time, and name where appropriate.
• New private documents should keep predictable timestamp-based naming for fast recall.

Phase: Canvas

Text based canvas for freeform document-taking, brainstorming, and visual organization.

• support for basic shapes, connectors, and text boxes
• fixed grid layout with drag-and-drop positioning
• fixed sized elements and spacing for simplicity

Phase: Real Time Collaboration

Real Time collaboration and change awareness features to support team workflows.

• real-time collaborative editing with presence indicators
• inline comments and discussions
• change notifications and activity feed
• version history and rollback
• user mentions and notifications
• shared editing sessions and live cursors

Phase: Internal Tools From Documented Knowledge

Once the core workspace and collaboration workflows are stable, Mohio should grow beyond ad-hoc AI code generation into a dependable internal-tool builder for small teams.

Planned focus areas:

• turn documented procedures and requirements into structured internal tool proposals
• ground generated software changes in existing workspace documentation, not only prompts
• help users define workflows, data shapes, UI requirements, and acceptance criteria from business context
• produce reviewable implementation plans and code changes with clear traceability back to source documents
• support minimal IT teams with safer iteration, validation, and handoff workflows
• make internal tools easy to version, review, and distribute through Mohio and the existing Git ecosystem

Phase: Mobile and Workflow Expansion

After the desktop-first experience is solid, Mohio can expand the companion workflows that matter most away from the main workspace.

Planned focus areas:

• mobile capture for new documents and ideas
• mobile reading for team documentation
• lightweight proposal review on smaller screens
• faster discovery of workspace knowledge

Phase: Shared Storage and Workspace Connectivity

Once the core local-first workflows are mature, Mohio can expand to support shared storage providers for teams that already organize documents in external file platforms.

Planned focus areas:

• Google Drive workspace support
• OneDrive workspace support
• clear handling of shared-folder document structure
• reliable sync-aware file change detection
• clear product language for connected versus purely local workspaces
• safe handling of publishing, checkpoints, and review flows across shared storage backends

Ongoing Exploration

• When should a document update an existing page versus create a new one?
• How much AI explanation is needed for users to trust a proposal?
• What is the right balance between local navigation and global orientation?
• Which collaboration signals matter most early: comments, mentions, or change notifications?

Out of Scope for the Initial Release

• real-time collaborative editing
• database-style workspace features
• heavy rich media workflows
• enterprise-grade permissions and compliance
• fully automatic AI publishing
• graph view as the primary interface

This site is open source. Improve this page.