Skip to content

docs: plan native OpenVoiceFlow Mac app - #26

Open
shimoverse wants to merge 1 commit into
mainfrom
docs/native-mac-product-plan
Open

docs: plan native OpenVoiceFlow Mac app#26
shimoverse wants to merge 1 commit into
mainfrom
docs/native-mac-product-plan

Conversation

@shimoverse

Copy link
Copy Markdown
Owner

Adds a source-grounded native Mac product and engineering plan covering Dock plus menu-bar identity, four-step onboarding, local English-only dictation, local profile/dictionary/correction learning, local Insights, Direct versus Mac App Store boundaries, native architecture, data model, phased delivery, and verification gates. The unfinished experimental scaffold is preserved only in a local stash and is not included.

@vercel

vercel Bot commented Jul 15, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
openvoiceflow Ready Ready Preview, Comment Jul 26, 2026 11:58pm

Request Review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 89768af227

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@@ -0,0 +1,376 @@
# OpenVoiceFlow Native Mac App — Product and Engineering Plan

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep internal plans out of published docs

This new plan lives under docs/, but scripts/vercel-build.mjs copies the entire docs tree to public and only excludes the top-level superpowers directory, so this working plan will be deployed as a public static asset. That conflicts with the repo guidance in AGENTS.md that “internal working docs must not live under docs/”; move it outside docs or add an explicit build exclusion before landing.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant