Workspace
Home and project hub
Home, Projects, and a code-first workspace provide the reported navigation foundation.
THE ROADMAP
Growing with intention.
The current foundation, the next careful steps, and the longer view. A working inventory, not a release schedule.
LATEST SUPPLIED REPORT · OCT 19, 2026
What these labels mean ↗0.9.5 reported released.
0.9.6 is in development and QA. 1.0 is intended as a private beta, with no announced dates or access.
THE COMPLETE INVENTORY
Find the part you care about.
All 102 features in the inventory
Reported present
C development
Native new-project flow
Create a C starter directly in CENTER with a clear project name and location.
C development
One-click Run
Configure, build, and run a C project from one primary action, with advanced controls available separately.
C development
Failed-build protection
The reported C workflow prevents a failed build from running a stale executable.
C development
Readable editing and panels
Compact tabs, project tree, indentation, and bottom output panels keep code in focus.
Reliability
Durable saves and recovery
C drafts survive restarts. Documents use a local crash journal and Archive checkpoints, with recovery refinements continuing in QA.
C development
Interactive run console
Keep program output and keyboard input inside CENTER with clear running, finished, and error states.
C development
Clickable compiler diagnostics
Navigate from a compiler error to the relevant source location.
Terminal
Integrated terminal
Use the reported terminal panel alongside code and build output.
Git
Git workspace and account panel
Git changes, staging, commits, history and branches are available alongside account and sync status.
Git
Git history and branches
Diffs, history, branches, commits, stash, remotes, fetch, pull and push are reported implemented.
Git
Optional automatic commits
Offer an explicit, configurable auto-commit mode with readable history and a way to review changes.
Workspace
Return to the same working state
Restore open files, cursor positions, panel layout, and project context after navigation or restart.
Reliability
Owned-process stop and clean close
Terminal process trees are cleaned up on close. Run/stop wording and release-specific behavior continue through QA.
Toolchains
CENTER-managed C compiler
CENTER includes WinLibs GCC for its C workflow, reported released in 0.9.1.
Toolchains
Managed CMake and Ninja
CENTER includes CMake and Ninja for configuring and building C projects.
Toolchains
Bundled Git
CENTER provides its own Git when needed, as part of the reported native tooling release.
Toolchains
Guided tool setup and repair
Show what is ready, what is missing, why it matters, and the smallest supported repair action.
Toolchains
Pinned tool versions and provenance
Track tool versions, verified sources, integrity information, and relevant license terms.
Toolchains
Clean-host acceptance
Prove the supported C workflow on a clean target machine before describing it as self-contained.
Toolchains
Path and environment resilience
Handle supported long paths, spaces, shell quoting, and competing host toolchains predictably.
Toolchains
Toolchain profiles per project
Let a project declare its toolchain and build configuration to reduce machine-to-machine surprises.
Archive
Notes, files, and folders
The existing Archive foundation organizes notes, code, files, and nested folders.
Archive
Simpler Archive navigation
Folder creation, renaming, moving and starring respond immediately, with drag-and-drop organization and desktop file intake.
Archive
PDF import foundation
Local PDF importing exists; supported cloud-streaming paths need separate compatibility evidence.
Archive
GoodNotes Auto Backup import
Read-only Google Drive access locates GoodNotes Auto Backup PDFs and refreshes imported notebooks while CENTER is open.
Archive
Watched PDF folders
A chosen-folder PDF watch foundation exists; robust replacement, offline recovery, and clear watch controls still need qualification.
Archive
Offline and cloud-file states
Explain files that are online-only, unavailable, still downloading, or usable offline.
Archive
Clear import errors and retry
Keep failed imports visible, explain the cause, and make a safe retry straightforward.
PDF workspace
Continuous PDF reading
The reported reader supports continuous pages, search, zoom, and page navigation.
PDF workspace
Fast large-document reading
Keep rendering and caching bounded while making long textbooks responsive.
PDF workspace
Remember the reading position
The PDF reader remembers where reading stopped. Additional file-replacement and recovery edge cases remain a testing concern.
PDF workspace
Dock references beside code
Attach Archive folders to a project and dock or float their PDF, note and code references. Projects remember their reference layout.
PDF workspace
Multiple PDF workspaces
Keep more than one document open and move between references without losing context.
PDF workspace
Pinned notes and code links
Pin relevant notes and connect a PDF page or note to a source file or project.
Archive
Backup, export, and restore
Give notes and attachments clear backup/export paths with tested restoration and conflict preservation.
Embedded
Managed MSP430 tool kit
CENTER includes its own MSP430 kit for the supported embedded workflow.
Embedded
CCS project intake
Existing Code Composer Studio projects can open in CENTER. Version-specific and unusual project configurations still need qualification.
Embedded
MSP430FR2355 project setup
Create an MSP430 project for the supported MSP430FR2355 workflow.
Embedded
In-app embedded builds
Build MSP430 programs inside CENTER and inspect compiler and linker output.
Embedded
Flash a supported target
Flash the supported MSP430 target through the supported LaunchPad setup; driver and hardware prerequisites apply.
Embedded
LaunchPad driver setup
The supported LaunchPad workflow includes a one-time USB driver step. Broader readiness diagnostics remain a possible refinement.
Embedded
Embedded debugging
Breakpoints, watchpoints, stepping, call stack, variables, registers, memory, disassembly and Console output are reported implemented.
Embedded
Serial monitor
Bring serial input/output into the workspace for supported boards and lab workflows.
Embedded
Workshop projects and references
Organize embedded templates, board references, notes, and experiments around a practical workshop.
Embedded
Board configuration profiles
Save a project’s supported target, probe, connection, and build configuration to reduce repeated setup.
Onboarding
Private-beta access
CENTER accounts already exist. The invitation process and access arrangements for a future private beta remain to be defined.
Onboarding
First-run setup
Guide a new user from launch through tools, workspace selection, and a successful first run.
Quality
End-to-end workflow testing
Test real C, Archive, PDF, Git, terminal, and supported embedded workflows in the packaged app.
Quality
Focused bug and usability pass
Resolve friction and quality-of-life issues before broadening the product further.
Updates
Signed release foundation
Signed, staged releases with an installed smoke test are reported established. Every new build still needs its own acceptance evidence.
Updates
Predictable updates and rollback
Offer clear update status, preserve work, and verify recovery from an unsuccessful activation.
Brand
CENTER identity
The golden orbit and charcoal-and-gold visual language identify CENTER independently of its founder.
Brand
Motion and accessibility refinements
Color schemes, text-size controls and reduced motion are reported implemented. Wider keyboard, contrast and accessibility testing remains ongoing work.
Support
Reviewable troubleshooting packet
Let a user inspect and share a minimal diagnostic packet while excluding credentials and unnecessary content.
Support
Tester feedback and known limitations
Provide a lightweight feedback route and an honest supported-configuration and known-issues view.
Sync
Automatic cross-device project sync
Keep approved desktop and laptop project data aligned without manual copy-paste workflows.
Sync
Cross-device Archive sync
Accounts sync supported notes, PDFs, files, folders and code items while CENTER is open. Files above 50 MB remain local.
Sync
Visible sync state
The Account tab shows sync status, a Sync now action and information about what syncs.
Sync
Offline edits and reconnect
Allow useful offline work and reconcile it safely when the next connection becomes available.
Sync
Preserve diverging edits
Edits made on different computers are preserved; reference-note conflicts ask the user which version to keep.
Sync
Explicit device pairing
Connect only selected devices and folders with understandable pairing and removal controls.
Sync
Separate updates from user-data sync
Keep software delivery and project/Archive synchronization visibly distinct.
Sync
Selective sync and storage limits
Choose which projects or documents stay on a device and see the resulting storage use.
Editor
C and C++ language intelligence
Add completion, symbols, navigation, and diagnostics for C and later C++ after the underlying language service is ready; prior deferral was not permanent exclusion.
Editor
Formatting and static analysis
Offer readable formatting and analysis tools with reviewable changes.
C development
Test runner and memory checks
Run project tests and supported memory-analysis tools with clear, actionable results.
C development
Native debugger
Add an integrated debugging experience after basic run and process control are dependable.
C development
Templates and build profiles
Support reusable starters and debug/release configurations while keeping the simple path simple.
C development
Build records
Retain useful build configuration and outcome context for diagnosis and reproducibility.
Documents
CENTER Documents
A document editor with ribbon tools, numbered equations, paginated views, comments, tracked changes, footnotes, recovery and PDF/Word/Markdown/HTML/text export.
Languages
Python workspace
Add Python project creation, environments, execution, and output as a later language expansion.
Integrations
PyCharm handoff
Support an optional PyCharm workflow without making that IDE a requirement for CENTER.
Languages
MATLAB integration
Explore a licensed MATLAB workflow after the core class and embedded needs are satisfied.
Integrations
VS Code integration
Add an optional VS Code handoff or integration after the native experience is solid.
Integrations
CLion handoff foundation
An installed-CLion handoff and sample execution were user-reported; this does not prove portable CLion support.
Serana
Optional Claude or ChatGPT assistance
AI provider choice replaces the earlier Serana-branded panel. Assistance is off by default and never sends on its own.
Serana
Refine optional assistance
Improve the optional assistant experience while preserving explicit choice and clear information-sharing controls.
Serana
Project-scoped code and error context
Offer reviewable selected code, diagnostics, and project context without repetitive manual copying.
Serana
Review assistant changes
Show suggested patches with diffs and accept/reject controls before changes are applied.
Serana
Optional local-model support
Explore local assistance where practical, with clear capability and resource limits.
Collaboration
Internal project chat
Discuss work in the relevant project with a clear record of participants and shared content.
Collaboration
Shared project files
Share selected files and documents with explicit membership and permissions.
Collaboration
Live collaborative editing
Explore shared presence and concurrent editing with recoverable history and offline behavior.
Collaboration
Review and handoff workflow
Keep proposed changes, discussion, and approval attached to the work they concern.
Portability
Portable SSD workspace
Carry the workspace, selected tools, and data on an external SSD for supported computers.
Portability
Drive detection and automatic sync
Recognize an approved connected drive while CENTER is running and reconcile selected data safely.
Portability
Portable offline operation
Continue working without internet when required tools, data, and valid licenses are available locally.
Portability
Optional Linux VM environment
Explore a self-contained Linux working environment where the host supports virtualization.
Portability
Fast-host and USB hardware workflows
Use suitable host resources and supported USB passthrough for demanding or hardware-connected work.
Portability
Offline key and recovery model
Design an offline-capable unlock and recovery model before relying on encrypted portable storage.
Portability
Leave-no-trace ambition
Minimize intentional host writes and document residual traces; zero host traces cannot be guaranteed.
Portability
Portable host readiness check
Explain compatibility, available storage, driver, USB, policy, and administrator constraints before setup.
Security
Optional encrypted local vault
Explore an encrypted workspace vault with established cryptography and a deliberate recovery design. This is a future direction, not a claim about current data protection.
Security
Expanded sync encryption model
Explore additional user-controlled encryption with explicit key ownership and recovery limits. This does not describe or certify the present transport and storage protections.
Security
Tamper-evident components
Extend integrity checks across supported app and tool components without claiming immunity from modification.
Security
Minimized host exposure
Reduce unnecessary caches and sensitive temporary data while acknowledging operating-system and compromised-host limits.
Security
Team data protections
Develop appropriate project permissions, membership controls, revocation, and protections for shared work.
Security
Security and privacy dashboard
Make encryption state, connected devices, shared projects, and diagnostic sharing understandable.
Security
Independent security review
Review the threat model and critical storage, sharing, and recovery paths before strong security claims or wider release.
Workspace
Detachable and multiple windows
Detach editors and documents into separate windows, including multi-monitor layouts, while retaining consistent save state and navigation.
Archive
Reliable watched-PDF updates
GoodNotes notebook refresh and rename tracking are reported implemented. Continue testing partial writes, unavailable cloud files, reconnects and replacements.
No features in this view.
Try a broader search, or start again with every item.
Understand the status labels
Reported present
Reported present: seen in prior reports or product context; not a certification of the latest release.
In development
Current work: implementation or qualification is still in progress.
Planned
Planned: an established direction or requested capability with no delivery date.
Aspirational
Aspirational: a longer-term ambition requiring feasibility work.
Proposed
Proposed: a new supporting idea for consideration, not an established commitment.
Planning areas & readiness gates
These groupings and dependencies describe a suggested plan, not sequential release promises. Some work overlaps.
01Make everyday C feel effortless
A fast, calm workspace where creating, editing, running, and recovering a C project feels natural.
Ready when
- New and existing C projects complete an edit-save-run cycle in the target app.
- A failed build never launches an older executable; stopping work touches only owned processes.
- Unsaved work survives expected navigation, close, and recovery paths.
Depends on: Starting foundation
Browse this planning area ↗02Make the tools self-contained
Deliver supported compiler, build, and Git tools through CENTER without requiring a separate full IDE.
Ready when
- A supported clean Windows machine builds and runs the starter with CENTER-managed tools.
- Paths with spaces and supported long paths, interrupted setup, and missing tools produce useful outcomes.
- Every distributed component has checked provenance, integrity, and redistribution terms.
Depends on: Make everyday C feel effortless
Browse this planning area ↗03Make Archive dependable and connected
Bring class notes, PDFs, and code together with reliable imports, fast reading, and understandable storage.
Ready when
- Local and supported cloud-backed PDF imports work with explicit offline and unavailable states.
- Large-document reading remains responsive and returns to the correct place.
- Backup and recovery are demonstrated without silently losing or replacing material.
Depends on: Make everyday C feel effortless
Browse this planning area ↗04Complete the embedded workbench
Build toward a real MSP430FR2355 workflow inside CENTER with explicit hardware and licensing boundaries.
Ready when
- A representative MSP430FR2355 project builds with the supported TI toolchain.
- Flashing and debugging are validated on named hardware and driver configurations.
- Unavailable drivers, permissions, licenses, and disconnected hardware are explained before operations proceed.
Depends on: Make the tools self-contained; Make Archive dependable and connected
Browse this planning area ↗05Prepare a thoughtful private beta
Polish the C, Archive, and embedded experience until a few invited testers can use it with little help.
Ready when
- A new tester can set up, create a project, import a PDF, and understand a failed build.
- Accounts, recovery, privacy controls, and update rollback are tested for the alpha scope.
- Known limitations and supported configurations are explicit; critical data-loss or release-integrity defects block the release.
Depends on: Make the tools self-contained; Make Archive dependable and connected; Complete the embedded workbench
Browse this planning area ↗06Make work follow the user
Connect project and Archive data across approved devices while keeping offline work and conflicting edits safe.
Ready when
- Two-device edits, offline reconnect, conflict resolution, and interrupted transfer preserve both versions.
- The interface distinguishes app updates from project and Archive synchronization.
- Users can see, pause, recover, and export their synchronized data.
Depends on: Prepare a thoughtful private beta
Browse this planning area ↗07Grow the engineering workspace
Add deeper development tools and additional languages without overwhelming the core experience.
Ready when
- Each language has a documented supported workflow and reproducible starter project.
- Editor intelligence, debugging, testing, and external-tool handoff are independently qualified.
- Optional integrations respect licenses and do not become mandatory dependencies for the core C workflow.
Depends on: Prepare a thoughtful private beta
Browse this planning area ↗08Explore assistance and collaboration
Build collaboration around projects, documents, and reviewable assistant context with clear sharing boundaries.
Ready when
- Shared work has explicit membership, access controls, attribution, and recoverable history.
- Concurrent edits and reconnects are tested before live collaboration is relied upon.
- Assistant context sharing is visible, scoped, revocable, and separated from approval to apply changes.
Depends on: Make work follow the user; Grow the engineering workspace
Browse this planning area ↗09Carry a personal engineering workspace
Explore a portable SSD and optional Linux environment that can move between supported hosts.
Ready when
- Physical-drive disconnect, reconnection, and interrupted writes are tested with recovery.
- Supported host, USB, virtualization, performance, license, and administrator requirements are documented.
- The portable workflow does not claim universal compatibility or a trace-free host.
Depends on: Make work follow the user; Grow the engineering workspace
Browse this planning area ↗10Mature the protected workspace
Develop stronger encryption, integrity, recovery, and team protections against an explicit threat model.
Ready when
- Encryption, key recovery, access revocation, and tamper responses receive specialist review.
- Claims are tested against a defined threat model and distinguish trusted from compromised hosts.
- A lost key, lost device, or interrupted update has a documented and tested recovery outcome.
Depends on: Make work follow the user; Explore assistance and collaboration; Carry a personal engineering workspace
Browse this planning area ↗The boundaries of the roadmap
- Keep C, Archive, and embedded usefulness ahead of optional expansion.
- Security and privacy foundations apply from the first stage; the final stage describes deeper protections, not permission to defer basics.
- No fixed dates, universal compatibility, admin-free driver installation, or trace-free operation are promised.
- Respect third-party licenses, redistribution terms, supported operating systems, and host policies.
- Treat account login, project-data sync, Git remotes, and app updates as distinct systems.
- Current local files are unencrypted; future encryption is an aspiration until implemented and reviewed.
- A roadmap is product planning, not a claim that the latest application release is complete.
- The detailed dependency order is a suggested plan; established near-term priorities are distinguished from proposed sequencing.