A Windows desktop product currently in development
Project Workspace
A local-first Windows desktop product currently in development, designed around explicit safeguards, controlled process boundaries and dependable local behaviour.
Project facts
- Relationship
- A Windows desktop product currently in development
- Status
- In development
- Platform type
- Local-first Windows desktop application
- Technologies
- C#, .NET, WPF, XAML
- Current stage
- Currently in development
- Capability
- Native Windows workflow software
Selected capabilities
Project Workspace remains in active development. The capabilities shown here are implemented or substantially implemented parts of the local-first workspace model, with future browser, terminal and release ideas deliberately kept out of this public list.
Local Project Workspaces
A native Windows shell keeps each project's tasks, files, browser context and working notes organised around the active project.
- - Project dashboard and workspace navigation
- - Persistent local project state
- - General Workspace plus named projects
Project Library for Files, Folders and Repositories
Users can link the working files, folders and repositories a project depends on without moving or deleting the originals.
- - Safe metadata links to local resources
- - Open With, VS Code and Windows default launch options
- - Missing-path visibility
Virtual Project Folders and Bulk File Linking
Many local resources can be organised into project-specific virtual folders, with review before bulk linking.
- - Virtual project folders
- - Bulk file review before linking
- - Duplicate and missing-path handling
Task and Next Action Planning
Goals, milestones and the next concrete action stay visible inside the workspace.
- - Tasks, goals and milestones
- - Blocked, overdue and completed states
- - Next-action replacement guard
AI Context Bundle Builder
Structured local context documents can be prepared and combined into a copyable bundle for external AI workflows.
- - Standard markdown context documents
- - Shared General Workspace context
- - Local preview and copy flow
Reviewed Command Workflows
Project commands sit behind review and safety checks before they can be sent to a visible terminal process.
- - Review-required command imports
- - Secret and destructive-command checks
- - Execution records for reviewed commands
Local Backup, Restore Staging and Diagnostics
Local app state is protected through validated backups, staged restore checks and diagnostics that avoid private outputs by default.
- - Checksum validation for backups
- - Staged restore before active data changes
- - Privacy-conscious diagnostics export
The intended problem
Project Workspace is being built as a local-first Windows desktop application. The present work focuses on creating a dependable base for managing project context on the local machine, rather than making broad claims about finished capability.
It is separate from CommandDeck. Where CommandDeck focuses on command and terminal workflows, Project Workspace is being designed around a wider local workspace model.
Why a native Windows stack
The application uses C#, .NET, WPF and XAML. A native Windows stack is appropriate for a product that needs careful local behaviour, explicit process boundaries and a desktop experience that can deal responsibly with files, project context and local actions.
That choice reflects the importance of dependable local operation rather than a desire to turn every problem into a web application.
Design boundaries
The product is currently being developed around explicit safeguards and controlled process boundaries. That means the underlying structure matters before the public proposition can be widened.
Because the detailed end-user proposition is still being verified, this page uses careful wording: intended to, being designed to and currently being developed around.
Current status
Project Workspace is in development. No release timing, pricing, beta availability, integrations, cloud synchronisation or completed feature set is claimed.
What this work demonstrates
- - native Windows development
- - local-first product thinking
- - explicit process and command boundaries
- - honest handling of in-development work
Have a workflow that needs careful improvement?
If a process in your business needs clearer systems, a focused tool or a better way of working, start with the operational problem.