What's New in StateDock

Shipped a complete Agent status board and its integration with the global overview in Global Cockpit (PWA): 1. The top Workspace Overview now includes a global "Connected Agents" summary card that smooth-scrolls straight to the board when clicked; 2. Shipped a dual-view toggle between "List" and "Grid", defaulting to the more detailed and legible List view: - ⚡ Working agents: show a live pulsing halo, the owning project badge and name, the current task number and full title, a status readout ("⚡ Executing task"), and buttons that jump directly to the task or project; - 🟢 Idle and ready agents: clearly labeled "🟢 Idle and on standby (ready for work at any time)", showing Ready task pills queued for pickup or the most recently delivered task records, plus the last heartbeat time; 3. Strengthened Agent identity resolution across clients (supporting /auth/agents profiles, standalone tokens from /auth/mcp-clients, and claim/assignment/completion records across all tasks); 4. Added complete English and Chinese i18n strings with type safety; 5. Built and deployed the full package to production at statedock.dev and app.statedock.dev.

1. `pnpm --filter @statedock/web build` passed, including packaging and SSR prerendering of all 12 routes; 2. The full `pnpm test` suite passed: 104 unit and integration tests, 100%; 3. `pnpm deploy:online` deployed successfully; Worker Current Version ID: b76ee4eb-9189-42bf-aaa1-5c3049ff535d.

Refresh the browser to see the new global Agent board and the List view.

1. Created and initialized the apps/chrome-extension project in the monorepo, targeting the Chrome Manifest V3 architecture and the Vite build system. 2. Configured the full MV3 permission set, icon guidelines (native 16, 32, 48, 128 px slices), and a multi-entry architecture (Popup, Side Panel, Options, Service Worker). 3. Implemented the quick floating popup (400×560px): - Quick capture: one-line idea capture saved in a single click, with the active tab's title and URL captured as context. - Waiting cards: blocked or decision-pending tasks are highlighted and pinned to the top, with the ability to type a reply directly in the popup and resume execution (Ready) in one click. - An overview of Working tasks and global task flow. - Quick links to open Chrome's native Side Panel and the Web App. 4. Implemented the native Chrome Side Panel: a persistent docked panel for browsing the web alongside tasks, with cross-project task filtering, search, and card expansion. 5. Implemented the background Service Worker: scheduled polling and status detection that lights up a red badge count and a system notification when tasks await decisions; a right-click menu for pages and selected text to save into StateDock. 6. Implemented the Options page: switch between the official cloud (passwordless Cookie auth) and a private deployment on Docker / Cloudflare (Token auth). 7. Added the `pnpm extension` and `pnpm extension:build` commands at the repository root along with detailed development and testing documentation.

1. `tsc --noEmit && vite build` in apps/chrome-extension succeeded, producing popup.html, sidepanel.html, options.html, background.js, manifest.json, and correctly sized icons. 2. The full automated test suite (104 tests via `pnpm test`) passed.

Open Chrome and go to chrome://extensions/, enable "Developer mode", click "Load unpacked", and select the apps/chrome-extension/dist directory to pin it to the toolbar; verify with local development or against statedock.dev.

Implemented and deployed the optional Code Reference for Task Handoff; also updated the StateDock and Docker open-source projects along with the StateDock plugin Skills and handoff documentation.

`pnpm typecheck` and the build check passed; Cloudflare D1 migration 0027 was applied and the production Worker was deployed as version 0aa7362d-2045-4101-bc60-9e4e2c6ecafb; the live get_instance_info works, and the deployed MCP accepts codeReference. The open-source project typechecks passed; plugin validate, build, pack, zip, and Harness build passed.

PRs awaiting review and merge: StateDock https://github.com/statedock/statedock/pull/1; Docker https://github.com/statedock/statedock-docker/pull/1; plugin https://github.com/statedock/statedock-plugins/pull/1. Plugin 0.1.1 is prepared but not yet released. MCP clients still showing the old parameter documentation need to refresh the connection or tool definitions. The main repository's recorded HEAD is bb95aac332cd63035c39f375f9b941005a920ceb on branch main with a dirty working tree; that HEAD therefore does not mean uncommitted changes are included.

Updated the StateDock Skill's pre-execution self-check flow: agents first verify the task objective, status, project and identity, relevant decisions, and the execution environment; anything they can resolve from records, the codebase, and tools they handle themselves, and they only ask when there is a genuine conflict, missing authorization, or a decision that requires the user. Also updated the English and Chinese operating guides and the self-hosted rules, and deployed the website Skill and Agent onboarding guide to production.

The production build and deployment succeeded, Worker version 744c777b-954d-4e15-b7c5-6fd95f94ca51. Live https://statedock.dev/skill.md returns 200 and includes the new self-check rules, and https://statedock.dev/agent.md includes the matching onboarding rules. The canonical and website Skill source files match, documentation examples were checked one by one, and the relevant changes passed whitespace checks.

The currently installed Codex user-level Skill copy is not replaced automatically by website deployments; to have future sessions load the new rules, update that copy from the live site and reload the Skill or start a new conversation.

1. Added public/robots.txt, explicitly allowing all public landing pages and documentation routes (/, /zh, /workflows, /blog, /doc, /more-fun, /privacy, /terms) while blocking sensitive API, OAuth, and admin paths, and declaring the Sitemap location. 2. Refactored prerender-workflows.mjs: it now generates a standards-compliant sitemap.xml per Google's rules (with lastmod, changefreq, priority, and multilingual xhtml:link alternate mappings), and provides full SSR HTML prerendering plus complete Canonical/Alternate/OG/Twitter SEO metadata for the English and Chinese home pages, workflow pages, blog and article pages, documentation pages (/doc), and the portfolio (/more-fun). 3. Enhanced i18n context route detection to support the /zh Chinese home page root route. 4. Updated DocPage and MoreFunPage so they run safely under SSR and serve complete documentation content directly, greatly improving search-engine indexing weight for the core docs.

1. The @statedock/web build ran static prerendering and sitemap generation locally with success, validating all 12 entries and their alternate mappings. 2. The full automated test suite (104 tests via `pnpm test`) passed. 3. Production deployment (`pnpm deploy:online`) succeeded, and curl checks confirmed that https://statedock.dev/sitemap.xml, https://statedock.dev/robots.txt, and https://statedock.dev/zh all return 200 with prerendered static HTML and complete multilingual metadata.

Go to Google Search Console (GSC) and submit the sitemap URL: https://statedock.dev/sitemap.xml, and use the URL inspection tool to test how https://statedock.dev/ and https://statedock.dev/zh are crawled.

The website Skill has been synced to the English canonical version and is now served on the production site.

Website repository commit c417bea (2026-10-14) contains the English update and is on origin/main; live https://statedock.dev/skill.md now returns English content that matches apps/web/public/skill.md exactly.

No additional implementation needed.

1. Fully refreshed the copy in the homepage Open-source Self-hosting section: - Updated the top lede: the former "Docker is coming next" now states clearly that both the Cloudflare and Docker versions are fully open source and ready to deploy. - Updated the Docker card status: the status badge was upgraded from "Coming soon" to "Available now" with a green checkmark. - Updated the Docker card body copy: it now states clearly that the single container ships with a built-in SQLite architecture, needs no external database or email service, starts with a single Docker CLI or Docker Compose command, and is fully tested and ready out of the box. - Buttons and links: the secondary "Follow Docker development" button was upgraded to a solid primary call-to-action, "Docker deployment guide", linking directly to the statedock-docker repository and README. 2. Bilingual support and SSR prerendering alignment: the English and Chinese versions were updated together, and the static HTML prerendering and Service Worker were packaged in sync.

1. Unit test validation: `pnpm test` passed all 104 tests. 2. Type checking and frontend compilation: `pnpm --filter @statedock/web typecheck` and build passed cleanly, completing MDX compilation, home page SSR static prerendering, and SW manifest generation. 3. Production deployment: `pnpm deploy:online` successfully published the static assets and the Cloudflare Worker to statedock.dev.

The production environment is live (version ID: 35d74481-3bd7-4a7d-85c9-ca2d285e8b63). Visit the homepage at https://statedock.dev/ or https://statedock.dev/zh and scroll to the open-source self-hosting section to see the new Docker available-now card and deployment guidance.

1. Substantially slimmed down the left sidebar: removed the vertically space-consuming project sub-menu (Overview, Tasks & Plans, Documents, Activity Log, Settings, Collaborators), leaving 100% of the sidebar's vertical space to "Global Cockpit + 📥 Inbox + workspace project list (with search and tri-state boxes)" and solving the crowding when there are too many projects. 2. Introduced a top horizontal secondary tab bar (Header Horizontal Sub-nav): inside a project, a horizontally scrolling tab strip now sits below the header in the main view, presenting Overview, Tasks & Plans (with a task-count badge), Documents (with a document-count badge), Activity Log (with a log-count badge), plus Settings and Collaborators action buttons, styled in line with Linear/GitHub. 3. Automatic hiding in global views: when in Global Cockpit or the global notifications view, the project-level horizontal nav hides automatically, keeping the interface clean.

1. Unit tests and bilingual alignment checks: `pnpm test` passed all 104 tests. 2. Type checking and production build: `pnpm --filter @statedock/web typecheck` and build passed with no errors. 3. Production deployment: `pnpm deploy:online` successfully deployed the static assets and Cloudflare Worker to statedock.dev and app.statedock.dev.

The production environment has been built and deployed (version ID: fc5b1bfc-d0b2-4532-8289-776daa5e7254). Refresh in the browser or PWA client to try the new layout with the fully freed-up left sidebar and the horizontal tab bar at the top of the main view.

1. Moved the Inbox to the front and highlighted it: the Inbox entry and its undistributed count now appear permanently in the Global Cockpit's top KPI area, with one-click access to triage; in the left sidebar the Inbox is pinned to the top with a badge showing the number of unprocessed tasks. 2. Project status micro-boxes (ProjectStatusBoxes): added phone-icon-style tri-state indicator boxes emphasizing Working (blue/green breathing indicator), Ready (cyan/purple ready indicator), and Plan (a prominent red/rose awaiting-planning indicator), while Done is fully silenced and no longer competes for attention. 3. Projects Hub and quick search: the Global Cockpit page now offers a dedicated card matrix and a quick search box supporting instant filtering by project name or slug, with one-click "All / Working / Has ready / Has planning" filter switching; the left sidebar also gains a live search box whenever there are more than 5 projects. 4. Global data sync optimization: lightweight per-project task caches and version comparison are maintained per workspace, keeping the sidebar and cockpit micro status boxes and Inbox counts in sync at second-level latency.

1. Unit tests and end-to-end checks: `pnpm test` passed all 104 tests, and the English and Chinese i18n keys are 100% aligned and verified. 2. Type checking and frontend compilation: `pnpm --filter @statedock/web typecheck` and build passed cleanly, completing the production bundle, SSR static prerendering of MDX blog posts and workflows, and Service Worker asset manifest generation. 3. Production deployment verified: `pnpm deploy:online` successfully deployed the static assets and Cloudflare Worker to app.statedock.dev / statedock.dev.

The production environment is live (version 158fa184-ce24-40a8-8646-841dae73e802). Refresh directly in the browser or PWA client to try the new Global Cockpit and sidebar. Any feedback on visual details or interaction preferences can be tuned quickly.

Fixed the live MCP instance information incorrectly reporting itself as local, and deployed the current website content as authorized.

85 website and live tests, the full build, and type checking passed; the production direct connection and both existing connections return the correct origin, MCP URL, and remote; the website Blog, skill, and health checks all succeeded.

Deployed version a59a0235-cdff-4d80-a7d2-06a0d1b4e9a4. The OAuth test environment regression passed, and the plugin status flow after real authentication can continue to be accepted; nothing was pushed to Git.

Published the English and Chinese drafts provided with the task as separate MDX articles, preserving the original arguments and factual boundaries, and cross-linked the English and Chinese posts.

The production build passed; validation for empty content directories, missing frontmatter, slug conflicts, and invalid MDX passed; a browser check confirmed the website listing and the direct English and Chinese detail pages work. English: https://statedock.dev/blog/manage-outcomes-not-agents; Chinese: https://statedock.dev/zh/blog/manage-outcomes-not-agents. Final production deployment version 502b3cf7-9996-4e93-a1b7-6faa0a5a7a1e.

The website now ships a static MDX blog: bilingual listing and direct detail pages, article metadata and hreflang, sitemap entries, and author notes. The production build and live page verification passed; deployment version 502b3cf7-9996-4e93-a1b7-6faa0a5a7a1e. The first bilingual article is tracked separately as statedock-107.

The English StateDock Skill has been synced to the open-source specification and repository, preserving the security boundary that self-hosted Agents obtain rules from their current instance's `/skill.md`, and pushed to main (commit 7c5c3ab). Verification: The export overlay and the manifest SHA-256 match the open-source repository files; the English files contain no Chinese characters. Notes: The full 271-file export verification was blocked by pre-existing source drift in `apps/web/index.html`; only the Skill files were pushed this time, and other workspace changes were not included in the commit.

The website's `/skill.md` is now the complete English canonical version, and browser garbled text was fixed via UTF-8 response headers. Verification: With cache-bypass parameters, the live file displays as readable English; the Worker TypeScript check and Cloudflare deployment preflight passed, and it was released to statedock.dev and app.statedock.dev. Notes: No database changes were needed.

Published a public, read-only English mirror of the statedock-dev project at https://statedock.dev/demo and added a homepage entry. The demo serves a sanitized static snapshot of 106 project records; production D1 was not modified. Verified the deployed page loads anonymously, shows project counts and task detail, and has no editing/account controls. Type check and production build passed; deployed Worker version b493cce7-bd95-45e6-aa0f-d2df5259a774 while preserving the existing production backend.

established an independent, fully self-contained Docker open-source Monorepo at /Volumes/DevData/run-projects/statedock-docker. Implemented an All-in-One single-container service architecture based on Node.js 22 + SQLite WAL; added a one-time Setup Token secure activation mechanism (to prevent public-internet admin squatting); implemented online atomic SQLite hot backup (VACUUM INTO); mounted a streaming Streamable HTTP /mcp endpoint for direct Coding Agent connections; provided a production-ready multi-stage Dockerfile, a compose.yaml with integrated Caddy automatic HTTPS, and complete documentation.

ran the full build and test suite (pnpm build && pnpm test), covering the core state machine, REST API, stdio MCP, and newly written Docker-specific unit tests (Setup Token security cycle, online atomic SQLite hot backup, HTTP streaming /mcp endpoint); all 22 test cases passed, with zero errors and zero warnings.

in the P1 phase, docker compose startup and Let's Encrypt certificate verification can be performed on a real public VPS; memory and connection behavior will be further tuned based on test feedback. The code changes are ready in the local workspace and can be committed and pushed to the statedock/statedock-docker remote repository at any time.

Reopened https://app.statedock.dev/ in Chrome; the homepage, signed-in state, and project list load normally, and the current observation is that the service has recovered. Cloudflare cross-check: app.statedock.dev is still bound to statedock-online, the most recent Worker deployment version shows no new changes with an error rate of 0, and Page Rules is 0. Both MeshWrite records SD-000229 and SD-000230 are fully updated to DONE with summaries explicitly noting they were not deployed, so this was not caused by either of those code releases going live. The issue shown in the screenshot corresponds to a failure when the Web Service Worker navigation fetch encounters a redirect; the current SW implementation does indeed have this fragile path. Since the incident recovered on its own and does not currently reproduce, the redirect source cannot be determined from the requests at the time, and no code was changed or release reissued.

the admin console is now deployed independently and the admin entry point is restored; same-domain API calls and the existing admin verification are preserved, and the marketing site and user app continue to work normally. Verification: build, type, and forwarding tests pass; online admin assets load correctly, and unauthenticated and cross-origin requests are rejected. Notes: the interface after a real admin sign-in has not yet been accepted; the independent deployment config has been synced to the actual project but not pushed to Git.

the marketing site hero now reads Agents come and go. Tasks remain., with the Chinese positioning, subheadline, and description filled in, and the page title and description updated. The open-source self-hosting entry point is preserved, and the explanation of Agent maintenance records sits below.

build, translation consistency, static page, and release checks pass; desktop, 390px/320px mobile, language switching, and the open-source link were checked, and the live copy plus the original documentation/workflows are normal. The production backend remains byte-identical.

the marketing site source has been synced to the actual repository but not pushed to Git. Headlines wrap naturally on narrow screens.

the marketing site published the main on-demand reporting workflow, covering daily, weekly, and monthly reports plus cross-project rollups; switchable and copyable report prompts are provided in Chinese and English, an entry point was added to the homepage, and it is positioned ahead of the English mirror.

task and summary read capabilities were verified; the production build, static pages, and release checks pass. Desktop/mobile layout, bilingual prompt switching, step illustrations, and copy feedback were checked; live pages and existing documentation are normal, and the backend remains byte-identical.

reports are generated by an external AI reading already-recorded content, and the prompts require stating the date, permission scope, and record gaps; no scheduled jobs, automatic sending, or native reporting were added. The page examples contain no real user task data.

the Cloudflare open-source repository is now set to public. A prominent bilingual open-source self-hosting section with source and deployment guide entry points was added below the homepage hero, and it is made clear that Docker is currently only a public preview and not yet installable. The homepage HTML and description now also surface the open-source information directly.

the committed version and a scan of the 13-commit history pass, and the repository and guide are accessible without signing in; the production build, static pre-generation, and release checks pass, and desktop/mobile plus Chinese and English display were verified. The marketing site is live, existing documentation and app reads are normal, and the production backend remains byte-identical.

Cloudflare currently uses the deployment guide to configure resources, email, and secrets and is not advertised as one-click install; Docker will be switched to a deployment entry once an actually installable version is ready. Other uncommitted local changes were not pushed.

the homepage now consolidates three core collaboration flows, and a bilingual Workflows page was published with interactive illustrations, connection requirements, capability boundaries, extended usage, and an FAQ.

the production build, bilingual consistency, static SEO, and release packaging checks pass; desktop and mobile layout, step switching, the FAQ, keyboard operation, and the live Chinese and English pages were verified. The marketing site, documentation, sitemap, and anonymous sign-in reads are normal, and the production backend is byte-identical to pre-release.

new material is clearly marked as illustrative; MCP capabilities in mobile chat clients depend on account and version and were not advertised as a verified end-to-end demo. The marketing site source was synced back to the actual repository but not pushed to Git.

the marketing site /doc now reads from a unified bilingual Markdown documentation source, with fixed cross-language section anchors, and the machine-facing compatibility paths /doc.md, /agent.md, /setup.md, and /skill.md are preserved. The Vite and Worker release scripts, the open-source export manifest, and the Cloudflare and Docker READMEs have been synced to the same documentation structure; the marketing site docs are deployed.

the marketing site frontend production build, Worker dry-run, 271-file open-source export validation, and self-hosted frontend Vite bundle all pass. The live /doc HTML and Markdown dual modes plus /doc.md, /doc.zh.md, /agent.md, /setup.md, and /skill.md all return 200, and the Markdown endpoint content type is correct; the live scripts include Chinese and English loading and stable Cloudflare/Docker anchors.

full type checking and Worker dry-run for the Cloudflare self-hosted repository are blocked by its existing missing Core export: tasks.ts references readyQueueClaim and readyQueuePredicate, but the current Core build does not export those two symbols, so no self-built test was deployed this round. The Tabbit runtime could not create a browser page, so visual checks were not completed. The open-source and Docker README changes are prepared in the local repository but have not been committed or published to GitHub.

the marketing site added bilingual Discord and X community entry points and presents plan entitlements and current pricing in a clear Free/Pro comparison table. Pricing reads the Stripe active configuration shared with checkout; the upgrade entry opens plan selection directly. Free/Pro entitlements are described according to the existing server-side limits, and MCP connections and the Agent identity queue are explicitly listed in both tiers.

all 4 billing regression tests pass; the online service TypeScript check and the Web production build pass; the Cloudflare Worker dry-run passes. Deployed to statedock.dev, and the live production page shows US$2.99 monthly and US$19 yearly (47% off), with the plan table, Discord, and X links confirmed visible. Worker version 3f1f87ee-ab26-4936-8455-ea133cbefa64.

nothing pending. Marketing site pricing updates with the Stripe active Price configuration used at checkout.

established a reusable unified task card covering the task list, Dashboard In Progress/Ready/Planned/Recent Outcomes, the cross-project overview, and the Capture page. Cards consistently show title, status, assigned identity, completer, summary, and updated time, and adapt to container width. Only In Progress, Ready, and Needs Input use a light status background; Planned, Completed, and Dropped use a neutral background.

the Web TypeScript check and the production builds for the main site and test pass; the open-source export validation passes. Changes were pushed to open-source main (commit 121b8d1) and deployed to statedock.dev and test.statedock.dev. After refreshing the actual StateDock pages, overview cards were confirmed to show assigned identity, completer, and the unified card content structure.

no client configuration changes required; refresh the StateDock page to see them. Card summaries show 1-3 lines at most depending on the width of their section.

the completion card, recent completions overview, and detail view now show the actual completer; the detail view provides identity type and ID. This is identified from the server-side activity record of the last explicit Done action, not inferred from the assigning or claiming identity; ordinary content edits preserve the original completer, while reopening and completing again updates it. Legacy records with no clear evidence show Not recorded. Released to the main site and test and synced to open-source main commit 7ba53d0.

85 application tests pass, plus Cloud completer regression and identity/Ready checks; type checks, builds, release, and dependency boundary checks pass for both editions. Browser verification covered Agent, human, legacy not-recorded, and detail ID cases. Live reads confirm 93 is harness and 94 is Codex with their corresponding identity IDs. The query index migration and deployment succeeded for both editions, and the open-source export is rebuildable.

refresh the page to see it. Historical tasks with no completion action records will not have their ownership guessed or rewritten.

every Ready card in the overview now shows the assigned identity name, for example Codex or Harness; when none is specified it explicitly shows Unassigned. The identity comes from the task assignment record, loading or unavailable states show the corresponding message, and it refreshes when the identity changes. Released to the main site and test, synced to open-source main commit 343bfb6.

type checks and builds pass for both editions, and the open-source release and dependency boundary checks pass. Browser previews in Chinese and English verified the Codex, Harness, and unassigned scenarios; deployment to the main site and test succeeded and the live sites load the new assets.

this shows the task's Assigned Identity; the agent's own identity in execution instructions is still determined by the actual MCP credentials.

a test task with no actual development content. The user confirmed in person that this task verifies Agent assignment and Ready queue isolation.

get_instance_info confirms agentId is 7391d5cb-88d4-4f9b-b1cd-fe8b0484521a; list_ready_tasks(mode="mine") confirms the task's assignedAgentId matches this agent and claimedAgentId is empty; the user explicitly authorized marking it Done.

none. Agent assignment and Ready isolation verification passed.

status selection and filtering now use full-block status background buttons with the inner small pills removed; task cards use a very light status background while keeping plain text status, and the selected card uses a clear border. Colors were unified across the six statuses and adapted to the page's light/dark themes. Released to the main site and self-built test, synced to open-source main commit 6260087.

type checks, both edition builds, formatting, and open-source release boundary checks pass. Browser verification covered the six card backgrounds, selected state, light/dark switching, and the Ready filter keeping only the matching cards; buttons were confirmed to have no nested pills. Deployment to the main site and test succeeded and the live sites load the new assets; the open-source export is rebuildable.

a pure UI adjustment, so task status, identity assignment, and claim rules follow the existing behavior.

identity management, task assignment, queue isolation, and the OAuth fix are synced to open-source main, and the marketing site documentation and Skill are updated. The self-built test.statedock.dev is also upgraded to the same commit ac8ae45, completing migrations 0024 and 0025 and clearing system cache assets.

the earlier 84 application tests, 3 release scans, and fresh instance verification pass. This round's test remote migration check found no pending migrations; the browser shows the new identity and Ready queue documentation; Cloudflare deployment records confirm version 94797166-d392-4cd3-9b22-ecf6c43f8b21 is taking 100% of traffic. A restore point before the upgrade was recorded.

old Tokens on the test instance must be bound to an identity, and old OAuth connections must be reauthorized with an identity selected; after updating the corresponding instance Skill, you can claim your own Ready tasks. The deployment management API returned 504 at one point, but the upgrade was confirmed successful via deployment records.

Ready task assignment per Agent Identity and MCP claim-queue isolation are complete, with support for identity management, Token binding, and OAuth identity selection; fixed shared OAuth clients revoking each other's authorization. This round unifies the interface wording around Identity: Add Identity, Identities, Assign to identity, Identity, keeping Agent Identities and Unbound; the copy was aligned across task assignment, filtering, and the authorization page, and added a note that an identity does not create or run an AI Agent. Released to the main site.

The previous full 102-test suite passed. For this copy change, Web/Online type checks, Web build, 4 OAuth tests, and the deployment precheck all passed; browser checks of the English/Chinese UI and the 390px mobile layout showed no horizontal overflow; production confirmed loading the new bundle index-DkCn3qCi.js. Production version 0dfa9c39-2711-41d2-9683-7d52d7aa2334.

Existing identities and Token bindings remain in effect. Multiple connections bound to the same identity share that identity's task queue.

Published a public English preview of the Docker edition, clearly stating the in-development status, planned capabilities, and how it differs from the existing Cloudflare deployment path; it contains only an announcement, with no image, deployment script, or release-date commitment. Repository: https://github.com/statedock/statedock-docker

The public API confirms the repository is public, Issues are enabled, and it contains only a README; the public content matches the commit, and the preview is readable in a logged-out browser.

The Docker implementation is tracked as a separate task. The main project and its self-hosting documentation are currently not publicly accessible, and the preview notes that access depends on the main project's release status; the main project's visibility was not changed.

Fixed the scroll conflict between the task list and the task detail: on desktop the two panes now scroll independently, and reaching a boundary no longer drags the outer page along; on mobile the page keeps natural full-page scrolling. Deployed to both the main site and the private open-source test build.

Both frontend builds passed. Using virtual tasks in a real browser, the list and detail were verified to scroll independently without boundary bleed-through, and the 390px mobile layout showed no horizontal overflow.

Refresh the main site or test to check; no other uncommitted user work was touched.

Built-in multi-device Web Push is live, fixing the 502 on the main site's test push and syncing the self-hosted test build. Users confirmed receiving notifications with the PWA fully closed on iPhone and with the PWA closed in Brave on PC, so no separate external channel such as Bark is needed for everyday use. Automated verification passed; Android and notification-tap navigation were not tested separately.

Added an English demo to More Fun's Feature Universe: translated 78 task titles/summaries, 8 modules, and the interactive UI, keeping the Chinese version; the page language now switches the demo and real preview images together. The English version states the translation source, and task numbers, dates, evidence, and acceptance boundaries are preserved. Fixed horizontal scrolling on narrow screens caused by a decorative glow in the English demo. Commit 245159d, released to the site.

Type checks, production build, and deployment precheck passed. Verified that all 78 task identities/dates/statuses, 76 summaries, and module evidence links match, with no Chinese leftovers in the English files. Real-browser checks covered task search, summary expansion, module browsing, Chinese/English demo and preview switching, and no horizontal overflow at 390px; both language demos were confirmed online. Deployment version 78fec49d-268b-4278-8656-89b731e227dc.

Visit https://statedock.dev/more-fun?lang=en for the English case; switch to Chinese for the original. The case is still a static snapshot from the original generation date.

More Fun is now a case showcase that presents outcomes first and prompts second. The first real case is the Feature Universe provided by a user, explorable interactively with the original prompt, plus dates, Agent, input scope, and a public redaction note; the existing prompts were kept and completed with 13 categorized idea entry points. Deployed to the main site.

The site build and release precheck passed, and the Chinese/English catalog check confirmed 13 independent working entry points with the original five prompt groups fully preserved. Browser checks covered copying, categories, no mobile overflow, and the embedded module demo; the live real outcome and its matching prompt were verified.

Only Feature Universe currently has a real generated outcome; other cards are explicitly labeled as prompt ideas. New cases can follow the existing standalone-asset and case-catalog structure.

The site's Chinese and English positioning is now unified around human Todos continuously maintained by Agents, keeping the original visuals and interactive demo, adding the step where a human confirms Ready, and aligning the narrative across team, notifications, handoff, and footer. Released to the main site.

The site build, translation-consistency check, and release precheck passed; the live Chinese and English Hero and Ready examples were reviewed, and mobile layout, the five-stage switching, and keyboard operation were verified.

Continuous maintenance assumes an Agent is connected and configured with working rules; Ready does not automatically wake an Agent.

Added "Copy Ready execution command" to the main site and the open-source edition, so the overview and task pages can hand work to an Agent without selecting a number. The command locks in the server-provided instance address and project UUID, claims Ready items one by one, delivers after verification, ends on an empty queue, and sets Waiting when blocked. The Skill now states the user-authorized idle-claim rules and adds no scheduler. Ready status and the security migration were synced and pushed to the open-source repository, deployed to the main site and test, and the currently installed Codex Skill was updated too.

83 tests on the main site and 65 tests each in the open-source edition and the actual test directory passed; type, module-boundary, open-source cleanliness scan, and release checks passed. Browser checks covered the copy entry point, the fully instance/project-bound command, and no mobile overflow. The test data backup upgrade drill and migration passed with historical data intact; the live resource hashes on both sites match the builds, and the instance address and Skill contract are published.

Refresh the PWA to use it. Agents must reload the Skill/connection to refresh the cached READY state; scheduled wake-ups or remote control remain the responsibility of the existing Agent host, and no scheduled task was created or GitHub visibility changed this round.

Planned/Ready statuses and per-project Ready claim queues are complete, with Telegram/Inbox staying Planned by default; also fixed the project-overview misalignment after adding a Ready item, restoring the two-column layout with in-progress/Ready/Planned on the left and recent outcomes/materials on the right, and redeployed the main site.

82 status tests passed and the historical data upgrade drill passed. The layout fix build passed; a multi-task browser check confirmed the desktop two columns are top-aligned, mobile is single-column with no horizontal overflow, and live resources match the fixed build.

Refresh the PWA to see it. Scheduled automatic execution is not enabled, and the open-source test instance was not updated.

Completed the Cloud operations console and deployed https://admin.statedock.dev. Built with Tailwind/shadcn + React and clearly split into Overview, Users, Project Metadata, Subscriptions and Redemption Codes, Notifications, and Audit Log; the frontend pages/components and backend routes/service/repository are layered. Supports disabling/restoring users, revoking sessions and Agent authorizations, and creating/disabling redemption codes, with a required reason for sensitive changes recorded atomically in the audit log. An admin email allowlist, strict same-origin checks, and blocking of logins/API/OAuth/bot access for disabled accounts protect admin accounts; projects expose metadata only. Commit ce92860.

All 80 tests passed; frontend and backend builds, type checks, module boundaries, and the deployment dry-run passed. An isolated browser verified menus, tabs, redemption-code operations, audit, pagination, retention of unsubmitted filters, and the mobile modal. After backing up the production database, migration 0022 was applied, ADMIN_EMAILS was configured, and version d9a51e95-5266-4ee5-9489-fbf5389cf567 went live. The online HTTPS login page and assets return 200, build asset hashes match, and anonymous admin API calls return 401/no-store; the app main site keeps the already-released statedock-80 optimization.

Please use sovsov@gmail.com to complete a real email-code login in the console and accept the production data pages. This round did not perform production acceptance actions with real impact, such as disabling accounts or using redemption codes; the first version of notifications provides status viewing only, and disabling a user does not automatically cancel their Stripe subscription. The open-source repository and test instance were not changed.

Pages no longer re-download all project data every 5 seconds. A single shared sync request (reading just a few count rows) now determines which project's data type changed and refreshes only the changed parts; in the background the page drops to once per minute and syncs immediately on return; notifications and task reviews/feedback no longer poll separately. Tasks from other projects load only when the Global Cockpit is opened. Unchanged data no longer triggers a full-page re-render. The server adds migration 0021 (project revision counters, maintained automatically by triggers on every write path) and the /api/sync endpoint.

73 automated tests passed, including 6 new ones (trigger granularity, member visibility isolation, diff and backoff logic); Web and Worker type checks, formatting, and boundary checks passed. Based on code estimates, an idle foreground tab drops from roughly 50-80 requests/minute to about 6, and about 1 in the background. Not yet measured in a real browser or against production D1.

Before deploying, run migration 0021 against the live database, then deploy the frontend and Worker (reversing the order makes the frontend receive a 404 from /api/sync and fall back to a full refresh). After deploying, watch one round of real request volume. The open-source edition needs migration 0021 and the frontend changes synced into the export overlay.

The official main site now wraps long text in the MCP credential dialog, handles narrow-screen layout and scroll constraints, and restores the Token deletion endpoint. Revocation is limited to the owner and immediately blocks that Token from further access. Deployed to both official domains.

67 tests, Worker type checks, and the isolated release precheck passed; with fabricated over-long data, dark-mode desktop and mobile widths showed no horizontal overflow. The new frontend content on both live domains matches the build, the deletion endpoint now enforces authentication, and health is normal.

Refresh https://app.statedock.dev/?ui=a2d3f27 to accept; no real user Token was revoked.

The self-hosted edition now pauses workspace and task-detail polling while in the background and syncs immediately on return; slow requests are merged automatically, post-action refreshes are queued and re-read, and other-project caches expire based on real read time. Notification receiving stays independent. Deployed to test.

62 tests, the frontend build, type, format, dependency-boundary, and release checks passed; the live frontend matches the new build and the health endpoint is normal.

Test page switching, task actions, and cross-project updates at https://test.statedock.dev/?ui=b8768d9. The repository stays private; polling is still used and no load testing was done.

The self-hosted release overhaul is complete. Re-review confirmed deploy:core was removed and the difference between the self-hosted and Cloud skills is documented; the documentation route now streams assets directly, dropping response rewriting and duplicate headers, using a 60-second private browser cache while preserving format differentiation. The latest fixes were synced and deployed to test.

58 tests, Worker type, boundary, and release checks passed. Alternating requests for HTML and Markdown at the same live URL returned correct formats and cache headers; the connection guide, health, and OAuth addresses checked out.

Visit https://test.statedock.dev/?ui=0e573f0 to continue testing. The repository stays private.

The self-hosted edition is now fixed to an admin email allowlist: unknown emails receive no verification code and cannot register, and project invites cannot bypass admission; projects stay isolated and admins get no private-project privileges. Disabled users are immediately blocked from login and MCP, the Chinese and English admin UI and upgrade notes were updated, and the test instance was deployed.

55 automated tests and build checks passed; on test.statedock.dev, a real A→B→C invite chain, project isolation, and continued invalidation of old credentials after disable/restore all passed. A backup was taken before migration, temporary data was cleaned up, and existing accounts and projects were preserved.

Visit https://test.statedock.dev/?ui=01a3068 to test. Accounts created by old project invites need an admin to approve their email before they can log in; the repository stays private and the official Cloud was not changed.

Completed multi-instance onboarding and credential revocation fixes, and continued correcting the misaligned credential modal — long text no longer stretches the grid, the copy button sits on its own row, and narrow screens scroll vertically. Deployed to the test instance.

The previous 50 automated tests passed; this round's frontend build and type checks passed. Real-browser checks confirmed no horizontal overflow at 1280px desktop and 390px narrow widths, and the test-domain version link loads the fixed frontend.

View the new build via https://test.statedock.dev/?ui=28640c9. The parameterless homepage still hits the old edge cache, and the current login credential lacks cache-purge permission; the version link is verified working. Switching instances still requires reconnecting the Agent.

Pulled fresh from the private repository and deployed a standalone demo instance at https://test.statedock.dev, with real admin email login and instance management confirmed by the user. Fixed the missing Core build in the cacheless deployment, completed the self-hosted email and asset naming guide, and corrected the Webhook test message link; fixes pushed to main, commit a3c7ebd.

48 regression tests passed; deployment packaging after removing build artifacts, plus type, format, and boundary checks, passed. Real shared projects and tenant isolation, API Token MCP, OAuth PKCE/refresh/revocation, standard MCP continuation of the OAuth plan, attachments and member permission revocation, signed Webhook completion notifications, and remote D1/R2 backup with local restore all passed. Test accounts, projects, and temporary receivers were cleaned up, the admin was retained, and the site is healthy.

The instance defaults to invite-only registration, and the repository remains private. The ntfy public service delivered test messages, but subsequent events are limited by the shared egress daily quota; the retry queue was verified and acceptance used our own Webhook completion notifications. Telegram/Discord/Bark require separate test credentials and did not reuse the production bots. Actual third-party product UI connections and public release remain open for further acceptance. Personal deployment config and restricted-permission backups are kept in the test directory and excluded from Git; the official Cloud instance was not modified.

The private open-source repository main branch is now a clean single initial commit cfa3e0b; the first commit no longer contains the marketing site code, while the app and usage docs keep their previously verified content.

After checking the remote's old version, a history update used a pinned version and pushed successfully; the new history has only one commit with 227 files and no marketing site files. The Git application tree matches exactly the version that previously passed 48 tests, and the working tree is clean.

The repository is still a private candidate. Going forward, the new initial commit is the baseline; before going public, run real login, Agent OAuth, and notification acceptance on an independent remote instance.

Completed F01–F15 code audit remediation: split large files and service responsibilities, hardened project permissions and concurrent writes, unified error handling and bilingual behavior, filled in Waiting history, added persistent notification retries and storage cleanup, and improved formatting, dependency boundaries, and CI. Backed up the production database, applied migrations 0016–0018, and deployed to statedock.dev / app.statedock.dev, version 9ed0fbc3-ae17-4786-beaf-20ffa9e30dc8.

All 66 regression tests passed; build, frontend/Worker type, format, dependency boundary, and deployment package checks passed. An isolated instance completed task editing, Waiting switching, and notification UI regression. The online database is healthy, and OAuth metadata, new static assets, and the English login page were verified.

The user is performing UI and real notification channel acceptance; notifications are delivered at least once, so retries may duplicate. The first open-source release will be discussed separately.

Completed the pre-open-source code structure review, producing 15 prioritized issues, service boundary recommendations, and a phased cleanup plan. Focus areas confirmed problems with permissions, concurrent updates, and integration behavior when configuration is missing; no product code was changed and nothing was deployed this round.

Scanned 127 source and style files and parsed all 121 TypeScript files; the existing 55 tests passed, and Web and Worker type checks passed. On a separate in-memory database, reproduced a member renaming a project, concurrent overwrite at the same version, and task creation without a signature when Discord has no public key configured.

Address permissions, atomic updates, and integration authentication first, then tidy up the backend services, notifications, and frontend components. A formal security audit, browser interaction testing, and open-source license/history secret checks still need to be done separately.

Fixed mixed Chinese and English in the project member invite modal: the Owner description, invite help, "you" label, join date, Pro hint, and invite/remove/leave error messages now all follow the interface language. Deployed to production.

Type checks and the production build passed; the English member modal has no leftover Chinese strings, and the Chinese and English error strings match and cover every member API error code. The online new assets match the build. Deployment version 24bffb7b-e168-46d8-a94a-c9bbb7d8fd0b.

No write tests were performed for real invite or remove actions.

The browser message center and Telegram, Discord, Bark, and ntfy notifications now all show "project slug-task number · task title". Webhook gained the same readable fields while keeping the global number and task link for compatibility. Deployed to production.

All 55 tests passed, including five-channel and browser consistency, Chinese titles, and special-character escaping; build, type checks, and pre-deployment checks passed. The production new assets match the local build and the app entry returns HTTP 200. Version cac3e766-2427-4c7a-94b1-b159271142db.

New notifications use the unified format, but previously sent external messages are not rewritten; real-device delivery was not confirmed one by one, though channel formatting was verified via simulated sends.

The first version of the homepage is deployed to statedock.dev: the visuals and interactive demo are retained, with new coverage of shared projects, the ChatGPT→Codex workflow, and Free/Pro benefits, plus stronger messaging on unified notifications and cross-Agent handoff. Type checks, the production build, 4 frontend tests, and pre-deployment checks passed; the online homepage, docs, and app entry work, and the new assets match the build. Deployment version 45202347-c396-40f4-814f-b06c0c62c483. Visual acceptance, real screenshots, and verification of live subscription amounts are still pending.

Built and launched the official StateDock English how-to and reference documentation (https://statedock.dev/doc and /doc.md). The docs are concise and practical, serving both human developers and AI Agent queries: detailed coverage of quick start, local Agent MCP setup, ChatGPT Web OAuth 2.1 connection, core collaboration rules (collaborators get full read/write access on joining, while only the creator retains management and delete rights), the task and plan lifecycle protocol, unified project slot rules (Free allows 2 slots; Pro is unlimited with up to 10 collaborators per project), the multi-channel private notification mechanism, and FAQ troubleshooting. Also implemented adaptive response serving: CLI/Agent access returns plain Markdown while browsers get an interactive docs page, fully tested and deployed to production.

All 53 automated integration tests passed; production was verified end-to-end with curl and a browser, returning HTTP 200 with exactly the expected format. Production deployment version 3f94c142-2985-4d93-b2b1-c51016244c13.

The docs page is live in production and reachable at https://statedock.dev/doc (human UI and Agent Markdown dual mode) and https://statedock.dev/doc.md. If a Chinese or other language version is needed later, a language switcher can be added to the page.

Investigated and located the issue of a collaborator's project list not showing shared projects: after checking the production database and multi-user session data, the collaborator successfully added to the project by the primary account is byteyellow@gmail.com, while the second browser window in the user's screenshot is still signed in as yellowaistudio@gmail.com, the account used for yesterday's subscription test. Since the two accounts have different emails, the latter correctly returns 0 projects under project tenant permission isolation. Also fixed the gateway routing fallback logic for obtaining context in the edge environment and added full-flow integration tests for preset collaborator verification-code login and project list sync, then deployed.

All 53 automated integration tests passed, and the production build and Cloudflare Workers deployment succeeded.

In the second browser window the user can choose either 1) sign out and sign in with the invited email byteyellow@gmail.com, or 2) add the current test account yellowaistudio@gmail.com as a collaborator from the primary account, which will immediately show the StateDock shared project in the sidebar.

Updated the Pro paywall benefit copy: added the complete benefit list to the BillingModal and the multilingual strings, including "Unlimited active projects (Free is limited to 2 slots, including self-created and invited projects)", "Invite full-access collaborators (up to 10 per project; Free cannot invite)", and "Multi-channel instant alerts pushed concurrently (Bark / Telegram / Discord / ntfy / Webhook)". Also confirmed and documented the collaborator private notification and full read/write mechanism.

The full test suite and TypeScript type checks all passed; the Cloudflare production deployment is live.

You can click upgrade to Pro in the Web UI or try private notification setup in settings.

Implemented a unified project slot quota: Free users previously only had self-created projects counted, and now the total slots of all active projects in their personal project list (self-created + joined as collaborator, capped at 2) count toward one limit. If an invitee is a free user with full slots, the invite is blocked immediately on the inviter's side with a prompt that they must upgrade to Pro or leave an existing project; invited users are also subject to the total slot limit and cannot create projects after already having 2. This closes the loophole where a single Pro account could pull in unlimited free members to freeload projects, creating a natural viral conversion path.

All 53 automated tests passed (covering combined self-created + invited slot counting, over-limit blocking, and the full lifecycle of creating/inviting again after leaving a project frees a slot); TypeScript type checks passed; deployed to the Cloudflare production environment.

You can test inviting a free user and creating projects in the Web UI to see the slot-limit prompts.

Completed StateDock's minimal multi-user project sharing (a full-access collaborator mechanism built on the creator/Owner). The creator can invite collaborators directly by email, and once they join, invitees get full read/write and Agent collaboration rights on all tasks, plans, and docs in that project (no complex granular permissions); invited users cannot invite others or delete the project. Project sharing is a StateDock Pro selling point: Free users cannot invite collaborators, and Pro users can invite up to 10 collaborators per project. Also completed outbound notification integration, the multilingual interface, the project management modal, and leave/remove member functionality, with the full test suite passing and deployment to production.

All 52 unit and integration tests passed, including permission isolation, plan quotas, lifecycle events, and multi-collaborator read/write; the production D1 migration ran successfully and Cloudflare Workers plus the Web frontend deployed successfully.

You can test inviting a real email in production or the Web app to experience team collaboration.

Unified the OAuth authorization page and flow to full management permissions (mcp:read and mcp:write). The authorization page no longer offers a confusing granular checkbox list; instead it clearly shows a full management permission card and grants the complete read/write scope by default in both the form and the backend, letting ChatGPT Web read projects, create requirement tasks (Planned), update progress, and record notes.

All 51 tests passed; built and successfully deployed to production (Version: dde196dd-3f46-436e-925d-df3aa0408acd); the verification endpoint now returns the default full authorization.

When ChatGPT Web connects to StateDock it receives full read/write management permissions by default, so users can create tasks by simply chatting with ChatGPT on the web (for example, "save the plan we just discussed to StateDock") without worrying about read-only limits.

Set run_worker_first: true for static assets in wrangler.jsonc so requests like /oauth/* are always handled by the Worker first, preventing Cloudflare Assets' SPA mechanism from intercepting them and incorrectly returning the marketing homepage. Also added no-store cache control to the /oauth authorization endpoint, excluded /oauth from the Service Worker and frontend routing, and ensured form submission fully preserves the redirect context.

All 51 unit tests passed; built and successfully deployed to production (Version: 5c1d9eb3-fbaf-4f15-a2ee-773213f2aad8); a live production request with browser headers now correctly returns the StateDock authorization sign-in card HTML with no-store cache control, completely eliminating the landing page behavior.

Please click connect again in ChatGPT Web (or refresh the previously stuck authorization page); the page will immediately show the StateDock sign-in verification card (or go straight to the ChatGPT authorization consent card if already signed in), and after you confirm, it will redirect back to ChatGPT to complete the MCP connection.

Integrated the official @cloudflare/workers-oauth-provider v1 to add OAuth 2.1 authentication to StateDock Remote MCP. Supports RFC 8414, RFC 9728, PKCE S256, and CIMD/DCR, ships an /oauth/authorize authorization page, scopes mcp:read and mcp:write per tool with securitySchemes, and keeps sdm_ API keys fully backward compatible with zero interruption through resolveExternalToken.

51 tests pass, covering metadata discovery, unauthenticated 401 challenges, legacy API key read/write with tenant isolation, PKCE authorization code exchange for tokens, mcp:write privilege escalation blocking, ChatGPT creating Planned tasks, and token renewal and revocation. In production, the discovery endpoint and 401 challenge behave as expected.

You can add Remote MCP in ChatGPT Web (https://statedock.dev/mcp) and create Planned tasks after signing in and authorizing; existing clients need no changes.

Established and implemented the Task Language Alignment Principle: a task's title, body, blocker reasons, delivery records, and result summary strictly match the language the Agent uses to communicate and report to the user. Core services plus the MCP submit_handoff and pause_task tools now adapt Chinese and English labels and separators automatically, and both the batch execution instructions and all documentation standards (AGENTS.md, SKILL.md, agent.md) now include the full principle.

TypeScript build and all 47 automated tests pass, and the production deployment succeeded.

Deployed to production and synced across all platform skills and configuration rules, so every future Agent integration records tasks in the conversation's language.

Fixed the duplicate Inbox icons and hard-coded Chinese label in the PWA sidebar and the global project list, which now adapt between Chinese and English (Inbox / 收集箱). Also fixed Chinese window titles appearing in English environments for the app and web, wiring up complete internationalization support.

TypeScript type check is clean, all 47 automated tests pass, and the production deployment is complete.

Live in production. If the PWA is already installed on your phone or desktop, refresh or reopen it to pick up the latest version.

Fixed an issue where clicking a project in the left sidebar while on the notification settings or global pages did not return to the project view. Clicking any project (including the currently selected one or switching to a new one) now switches back to the project Overview automatically, closing the settings dialog and the mobile drawer at the same time. The project dropdown in the top header now supports the same behavior.

TypeScript type check passes, all 47 automated tests are green, and the production build was successfully released to Cloudflare Workers.

The fix is live. You can verify the instant return by clicking any project name in the left sidebar from the message center.

Completely rebuilt the message center from a dialog into a standalone three-column workbench page: a left column for channel navigation (Bark, Discord, Telegram, ntfy, Webhook, in-app alerts), a middle column listing configured endpoints (endpoint name, linked-project badge, live counts, and an add button), and a right column for detailed settings (endpoint credentials, project binding, event preference toggles, instant test, and delete). Reachable in seconds from the sidebar, the top navigation bell, and keyboard shortcuts.

Frontend and Worker TypeScript type checks pass, all 47 unit tests plus API integration tests are green, and the production build was successfully released to Cloudflare Workers.

The three-column message center workbench is officially live. Try adding endpoints, filtering by project, and running instant tests on each channel across different devices.

The Bark and ntfy notification channels now fully support multiple endpoints and multi-project binding, and the Telegram chat list now shows project badges and independent preferences as well. With that, all five notification channels — Discord, Webhook, Telegram, Bark, and ntfy — now share one unified experience, each supporting multiple configurations, precise project-level filtering, and instant testing.

TypeScript type checks pass (Web and Online), all 47 end-to-end unit tests and API tests are green, the remote D1 tables migrated smoothly, and the production build and Cloudflare Workers release succeeded.

Multi-endpoint management and project linking are now deployed across all channels. Combined with overseas promotion and per-channel feedback, we can further expand advanced push templates and frequency controls.

In-app notifications now show a 5-second auto-dismiss countdown with pause on hover, and notification settings include a toggle for in-app floating alerts. Message channels (Discord and Webhook) now support linking multiple endpoints to projects: you can pick a target project or a global push when creating and managing a channel, and the connection card clearly shows the linked project badge.

The full test suite and build pass, and the production Cloudflare Workers and frontend assets were deployed successfully.

Additional multi-endpoint channels such as Telegram can be bound later as needed.

Completed the site-wide English-first and end-to-end multilingual fixes, including the index.html page title, meta description, and lang attribute; refined the PWA manifest and the offline page; made document.title switch instantly with the bilingual state; and refactored the notification event system, browser push, batch command templates (BatchExecution), attachment uploads (Attachments), standalone checks and feedback (TaskFollowUp), and the Stripe subscription dialog (BillingModal), completely eliminating Chinese text suddenly appearing on the home page or in dialogs in the default English mode.

Full type check pnpm typecheck reports 0 errors; all 47 automated unit tests pass (including Chinese and English bilingual cases); the production build completed and was successfully released to Cloudflare Workers via pnpm deploy:online (statedock.dev and app.statedock.dev).

The site and console now deliver a fully English-first experience with smooth, stable language switching, and are ready for formal promotion and trials with overseas developers.

The marketing site (Landing Page + More Fun page and all subcomponents) now fully supports Chinese and English internationalization. Overseas visitors see English-first by default, while Chinese browsers or users who have chosen Chinese see Chinese; a persistent LanguageToggle in the navigation supports localStorage persistence and URL ?lang= overrides; and the interactive walkthrough, multi-project notifications, 10 playbook ideas, and 5 real-world Prompts are all natively bilingual.

Type check pnpm typecheck reports 0 errors; all 47 unit tests pass; the production bundle and Cloudflare deployment are live.

Next up is multilingual support for the PWA console (workspace, dialogs, settings) and the Agent onboarding guide.

The marketing site officially launched the More Fun page (fun ideas and playbook showcase), covering 10 Agent playbook ideas with category filters, 5 high-quality real-world Prompts (with one-click copy and expected-outcome notes), a visual showcase of Feature Atlas and Developer Playbook artifacts, and the core idea threaded throughout that "Done is not the end, but a project asset and the starting point for the next project"; the full test suite passes and the page is deployed to production.

Shipped a single-source-of-truth plan quota center (TIER_CONFIG) that fully delivers Free and Pro benefits: Free is limited to 2 active projects and 1 notification channel, and exceeding a limit triggers the upgrade flow and opens the BillingModal, while Pro supports unlimited projects and multi-instance linking across all channels; the full automated test suite passes and the production deployment is complete.

On top of the agreed shared-Todo marketing site, added notification examples for pushing multiple projects forward at once, five alert channels, and a concrete walkthrough of the same task being read and independently reviewed by B after A finishes it.

Frontend type check, production build, and diff review pass; desktop and 390px mobile previews pass, and the notification descriptions match the actual event settings.

The local preview is updated and the code is written back to the real repository; this round of marketing site changes has not yet been committed or deployed.

1. Built a lightweight local redemption code operations service in apps/admin on Hono, supporting direct connections to the live production D1 database (Remote) or the local dev database (Local); 2. Included a complete dark-mode web console (http://localhost:3002) offering quick preset templates, single and batch generation, one-click copy/export as newline-separated or CSV output, full query and filtering, void and delete, and real-time traceability of redemption history; 3. Added a minimal one-command pnpm admin launcher at the repository root.

apps/admin builds and type checks independently; endpoints start and pass curl verification (successfully pulling live codes such as LAUNCH2026 from the production D1); all 42 automated tests pass at 100%.

Run pnpm admin locally to open the visual management panel at http://localhost:3002.

1. Implemented a single authoritative membership status and ledger architecture, abstracting a unified isUserPro determination service and the extension-and-accumulation calculateNewPeriodEnd logic; 2. Created the D1 migration 0013_redemption_codes.sql (supporting exclusive one-time codes and campaign multi-use codes), and shipped the POST /api/billing/redeem redemption endpoint with safeguards against double redemption and over-redemption; 3. Provided the CLI code-issuing script scripts/create-redemption-code.ts; 4. Wired instant redemption and extension-expiry display into the BillingModal frontend.

All 42 automated tests and the global TypeScript type check pass at 100%; the production D1 migration succeeded with the public beta code LAUNCH2026 seeded; the frontend and Cloudflare Worker production deployments are live and verified with curl.

Live in production. You can enter a redemption code in the subscription dialog in the console at any time, or use the script to generate campaign gift codes in bulk.

1. Added the STATEDOCK_PRICE_LOOKUP_KEYS constant and the resolveStripePriceId dynamic resolution cache in stripe.ts, supporting statedock-pro-monthly ($2.99/month) and statedock-pro-yearly ($19.00/year); 2. The checkout endpoint in billing-routes.ts now accepts an interval ('monthly' | 'yearly') or lookupKey and can create Checkout sessions automatically without hard-coded price IDs; 3. The subscription endpoint exposes the plans list for frontend display and billing selection.

All 38 unit tests pass at 100% (covering dynamic lookup key resolution and monthly/yearly Checkout request generation); the production Worker deployed successfully.

Continue discussing the Free vs. Pro permission control strategy and the frontend upgrade flow.

1. Added guidance for forced injection of workspace rules (AGENTS.md / CLAUDE.md / .cursorrules) in agent.md / setup.md, so Agents write the rules automatically during setup, fixing silent session auto-resume and task creation issues; 2. Built a lightweight Stripe payment core in apps/online based on Web Crypto (Checkout Session generation, hosted Customer Portal redirect, Webhook HMAC-SHA256 signature verification, and duplicate-event protection); 3. Completed the Cloudflare D1 subscription data table migration (0012_billing_subscriptions.sql) and deployed to production.

All 38 automated tests passed at 100%; the Cloudflare D1 production database remote migration succeeded; the production Worker (statedock.dev / app.statedock.dev) was published successfully and verified with live requests.

Next step: discuss the specific Free vs. Pro permission split criteria, interception mechanisms, and frontend interactions.

Refined the TodoDemo interactive demo on the website so it truly matches the actual StateDock PWA and the latest protocol: including natural task numbering web-app-24 (SD-000024), the full state machine flow (PLAN, WORKING, WAITING, DONE), proactively suspending and pushing to your phone when hitting a technical decision blocker (the WAITING blocker alert card), and the three-part structured delivery card after completion (🛠️ Changes, ✅ Verification, 📌 Notes); the card includes a real "copy Agent prompt" interaction.

All 34 unit and build tests passed at 100%, and the build was successfully deployed to production.

Improved website routing for both local and online environments: running pnpm web locally and visiting the root path / now shows the new website by default (no need to manually add /?view=landing); clicking "Open StateDock" goes straight to /?view=app to enter the console; added smooth scrolling for the new website anchors (#example, #notifications, #get-started), and added a link back to the website in the sidebar.

All 34 unit and integration tests passed, the local build produced no errors, and the release was successfully deployed to production.

Completed the responsibility cleanup and committed the current deployable version (7213b3b), with a successful production release. The 34 tests, type checking, build, and deployment pre-checks all passed; the health endpoints and static asset checks for both production domains passed, and unauthenticated access boundaries behaved correctly. Deployed version 6fe73cc9-dfd7-47f3-a137-5f78d4fa5754; local operation logs were not included in the commit, and the Git commit has not yet been pushed to the remote.

Launched automated self-configuration guide URLs for AI Agents (https://statedock.dev/agent.md and /setup.md), covering environment introspection, Skill download and location, MCP configuration templates for various clients, automatic repository binding, and protocol self-checks; also added a one-click "copy Agent instructions" feature to the MCP credential management dialog in the Web console.

All 32 automated tests passed, live curl checks confirmed that https://statedock.dev/agent.md and /setup.md return 200 text/markdown, and the Cloudflare Production release completed successfully.

Standardized the three-part structured delivery Handoff contract (Changes, Verification, Notes), provided the submit_handoff MCP tool and API endpoint, and highlighted the structured parsing plus one-click template fill-in in the Web detail and list cards.

All 32 automated tests passed, including the submit_handoff integration tests and MCP tests; the full build and Cloudflare Production deployment completed successfully.

Implemented claim_next_task (atomic takeover of the pending queue) and pause_task (recording a blocker suspension and triggering external push notifications) in Core, the API, and the MCP Server, and established working guidelines in SKILL.md.

Implemented the resume_project tool in Core, the API, and the MCP Server, supporting high-density recovery of project goals, in-progress tasks, blocker reasons, the last completed delivery, and the next batch of to-dos in a single atomic call, and updated the SKILL.md guidelines.

Implemented a zero-friction Inbox requiring no input commands and one-click cross-project task classification, supporting automatic plain-text capture into the Inbox and smooth migration; production deployment is complete.

Implemented the primary/subdomain architecture split: statedock.dev serves as the official Landing Page for promotion and navigation, while app.statedock.dev serves as the PWA and Web workbench console; enabled cross-subdomain cookie session sharing and smart path redirection.

Implemented a generic outgoing Webhook channel with HMAC-SHA256 signature verification, event filter preferences, connectivity testing, and production deployment.

Implemented two-way Slash Commands interaction and account binding in Discord (/todo, /doing, /plan, /done, /summary, /review, /projects, /use, /link), with Ed25519 signature verification and instant card replies; the D1 migration is complete and the release is live in production.

Integrated the cross-platform ntfy push channel into the unified reminder settings, supporting configuration of the official ntfy.sh or self-hosted service Topic, an optional Auth Token, and connectivity testing; the full regression suite passed, and the database migration and application have been deployed.

Added the full set of two-way query commands to the Telegram Bot (/todo, /doing, /review, /done, /summary, /help), supporting quick queries for a specified project or the default project; all 21 regression tests passed and the release is live.

Consolidated desktop entry into the quick-capture note and removed the redundant new-task button; restructured the overview layout to highlight pending items and show current work more compactly; fully upgraded the PWA icons and SVG assets to a dimensional brand logo and completed the production deployment.

Shipped a safe-area fix for the iOS top navigation and project drawer, and enlarged the tap targets for mobile buttons. Builds and menu and theme interactions under a simulated iPhone safe area all pass; still needs a recheck on a real iPhone PWA.

Shipped a fix for the scheduled sync that was clearing form drafts; "Jot down an idea" now feeds into quick notes uniformly, and the ideas-to-discuss list is retained. Builds pass, and input is confirmed to persist after a sync.

Shipped mobile quick capture, a fixed-order execution entry point for tasks, standalone checks, and feedback on the same task. 21 regressions, type checks, mobile-size interactions, and live MCP verification all pass; the real-device PWA and Telegram images still need hands-on testing.

Added multi-select, ordering, and fixed-numbered execution instructions for tasks awaiting scheduling, with explicit pause-on-blocker behavior and no auto-claiming of newly added tasks. The interface builds and the sequencing rules tests pass, shipping with this release.

Implemented quick capture on the mobile home screen, screenshot attachments, and explicit project selection in Telegram, with entries defaulting to PLAN. Builds, type checks, and attachment API regressions pass, shipping together with this release.

Unified the rules for direct execution, mobile staging, pause-on-blocker for fixed batches, and standalone checks, and updated the usage guide and the current skill. The online version is updated with this release.

Reminder settings now use a vertical channel list on the left, showing only the current channel on the right, with a green check for configured connections. Switching preserves entered content, and mobile uses a narrow menu with independent scrolling. Shipped.

Shipped unified reminder preferences: Bark, Telegram, and Discord can be selected per project and event, defaulting to completion and needs-attention reminders. Notifications open the corresponding task directly, with support for testing and pausing connections.

Added Bark reminders and fixed failures when sending online, with support for saving the address, enabling or disabling them, and sending test notifications.

Implemented the cross-project Global Cockpit Dashboard: it brings together in-progress tasks and recently delivered results across all projects, supports one-click jumps straight to the matching project board, and offers global access from the sidebar, mobile bottom navigation, and Cmd+K. Tests pass and it is deployed live.

Fixed native browser push and in-app toasts still showing the old SD-xxxxxx format, unifying them on project-native numbering (for example statedock-18). The full test suite passes and the change is deployed live.

Implemented a global Cmd+K command palette and keyboard shortcut system: search and jump to tasks instantly, switch across projects, press N to create a task quickly, and trigger it from the top bar.

Added a "Copy Agent prompt" button to the top bar of the goal board detail page in the Web console, generating a standardized instruction in one click (for example, "Please read StateDock task statedock-xx, start implementation, and sync status") that is copied on click.

Implemented two-way Telegram interaction: sending a message or /plan to the bot automatically creates a to-discuss idea (PLAN) in StateDock and returns a confirmation card; sending /status retrieves the currently in-progress tasks at any time.

Fixed an issue in the Cloudflare Worker where async pushes were cancelled before the response closed; Telegram notification tests now succeed.

Task IDs have been upgraded across the board to natural project numbering (e.g. statedock-12), with smart resolution that accepts statedock12, statedock#12, SD-12, and the original numeric IDs. The interface and Telegram notifications now display the new format.

Real-time Telegram Bot notifications and account linking are implemented and live. You can start linking Telegram with one click from the cockpit, and tasks automatically push a system notification whenever their status changes.

The notification system now uses standard PWA Service Worker native push, with notificationclick handling to wake and focus the app, so the desktop system notification center shows a banner that takes you straight to the relevant task in one click.

The web cockpit was fully rebuilt on React 19 and shadcn/ui, fixing narrow-screen mobile layout and sidebar cramping. A mobile bottom navigation bar and drawer menu were added, giving both desktop and phone a polished, no-line-wrap power-user experience.

Fixed an issue where an empty notification container covered the entire screen on mobile, making all taps unresponsive. Deployed to statedock.dev and verified bottom navigation, goal details, back navigation, and the new task sheet at a 390×844 viewport.

Deployed the mobile-first StateDock PWA to statedock.dev; on phones it supports install guidance, bottom navigation, project switching, single-page browsing/editing, and safe-area layout. Build and live health/static asset checks passed.

Published the canonical StateDock skill at https://statedock.dev/skill.md, documented the update prompt, and verified HTTP 200, Markdown content type, and an exact match with the repository source.

Added an English newcomer guide covering the product, local setup, architecture, contribution workflow, database changes, and production boundaries; linked it from the README.