Skip to content

feat(settings): merge the Developer page into Settings > Developer - #24810

Merged
iamwhatever merged 1 commit into
mainfrom
feat/merge-developer-page-into-settings
Oct 28, 2026
Merged

iamwhatever merged 1 commit into
mainfrom
feat/merge-developer-page-into-settings

Conversation

@iamwhatever

@iamwhatever iamwhatever commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: The developer tools live in one place, Settings > Developer, with no Developer Mode switch in front of them.

Today the tools are split. Settings > Developer holds a Developer Mode switch and the feature previews. Turning the switch on adds a separate Developer page to the left rail with Logs, System, Telemetry, Storage, MCP Management, Memory, Config, Debug tools and Archive. A reader must find the switch, then a second page. The same switch also hides the chat side panel's Logs, Context and Crew log views, and the desktop app's View > Toggle Developer Tools item.

Why it matters

A person debugging a problem has to know a hidden switch exists before they can see logs or system metrics. Docs, tips and the doctor's MCP hint each had to explain "turn on Developer Mode first". One home in Settings removes that step and the explanation.

Not a goal

  • The server's KIROCREW_DEV_MODE setting and per-app dev mode (/api/apps/{name}/dev). They are separate switches and stay as they are.
  • Changing what any internals page shows. Each page renders the same component it did on the Developer page.
  • Moving /logs or the other standalone pages.

What changed (motivation → approach → change)

Before After
Settings > Developer: one pane A page list: Feature Previews first, then the nine internals pages
Left rail Developer row (behind the switch) Gone
Developer Mode switch Gone
Side panel + Logs / Context / Crew log Always offered
Desktop View > Toggle Developer Tools Always shown
/developer?tab=<page> Redirects to /settings/developer/<page>

The approach reuses the Settings SubNav that Chat, Display and Notifications already use, so the page list, the phone drill-in and path deep links behave the same way. DeveloperPanel.tsx renders the pages; DeveloperPage.tsx is only the redirect. It keeps every other query param (plane, highlight), forwards agent-backend to Agent Harness as before, and matches the route's own trailing-slash and case rules.

Without the switch there is nothing for a gate to guard, so the developer_mode guide gate, the shell.developer location, the page.developer palette entry, useDevMode / useDeveloperMode, and their catalog strings are removed. Search and find_ui now point at settings.tab.developer and its settings.sub.developer.* pages. App.tsx drops the phone rail row, and uiLocations/conditions.ts with uiLocations/areas/shell.ts drop the gate and location. In-app links, curated tips (data/tips_curated.json), the doctor's MCP hint (doctor_checks/mcp.py), the find_ui blocker wording (mcp_guide.py, dashboard/guide_runs.py), the utils/previewFlags.ts comments and agent docs use the new paths. The i18n/locales/en.json catalog and its translations lose the removed strings and the tab description no longer says "Developer mode". The generated settings registry, ui index and guide plans, the GUI user-test catalog, and the owning specs (learn-cron-dashboard.md, metrics.md, kas-auth.md, feature map) follow the new layout.

Backwards compatibility

Compatible: every old /developer?tab=<page> link lands on the same page under Settings, and /developer?tab=agent-backend still reaches Agent Harness.

Reader: website/src/hooks/useDevMode.ts:useDevMode -- chat -- removed with its only caller, pages/chat/SidePanel.tsx, which no longer gates diagnostics
Reader: website/src/shell/nav/developerMode.ts:useDeveloperMode -- chat -- removed with its only caller, shell/appShell.tsx; the rail row it fed is gone
Reader: website/src/lib/uiPrefs.ts:DURABLE_PREF_KEYS mc-dev-mode -- chat -- dropped from backup; the frozen PRE_ROSTER_KEYS list keeps it by design, and a restored profile carrying it is ignored (App.mobileSingleTopbar.test.tsx, AppRootCoverage.test.tsx)
Reader: website/src/guide/guidePredicates.ts:GUIDE_GATE_EVALUATORS developer_mode -- chat -- no plan names the gate after regeneration; an unknown id reads unmet (liveRegistry.test.tsx)
Reader: src/kiro_crew/ui_index.py:AREAS developer -- subagent -- anchors move to page.logs, page.webhooks, page.projects; test_find_ui.py, test_find_ui_shell.py
Reader: src/kiro_crew/docs/ui-index.generated.json shell.developer / page.developer -- subagent -- regenerated; "developer page" terms resolve to settings.tab.developer (test_find_ui_shell.py)
Reader: website/src/components/commandPalette/providers/pagesData.ts:EXTRA_PAGES developer -- chat -- removed; Settings search lists the tab and its pages (pagesProvider.test.ts)
Reader: website/electron/app-menu.js devtools-toggle -- app -- built visible; an older desktop shell still gets setDevMode(true) at boot (app-menu.test.js, AppRootCoverage.test.tsx)

Tests

  • DeveloperPanel.test.tsx: the page list order, path navigation, and that no Developer Mode switch is drawn.
  • previewSurfaces.test.tsx: the redirect for Feature Previews (rings the section), another page, kept params, trailing slash, mixed case and an unknown tab. Removing the route-matching guard fails the trailing-slash and mixed-case cases.
  • DeveloperPanel.defaultCrewmateHighlight.test.tsx and DeveloperPanel.lazyGraph.test.tsx: the default-mate deep link and the lazy memory graph on their new pages.
  • sidePanelAddMenu.test.tsx, ContextBreakdownPanel.test.tsx: diagnostics offered whatever Terminal does; group ids stay fixed.
  • Guide, find_ui and gate tests (GuideLayer.uiShow.test.tsx, test_guide_select_gate.py, test_guide_ui_find.py, test_guide_ui_show.py) use the terminal and Mates preview gates in place of the removed one.
  • settingsCoverage.test.ts, deadKeys.test.ts, uiPrefs*.test.ts, gui_user catalog tests, app-menu.test.js.

Determinism: the 53 changed frontend test files passed 3 runs in a row (1067 tests each). Under --sequence.shuffle, DeveloperPanel.lazyGraph.test.tsx reads its import count once at load, so it passes in any order (5 shuffled runs). Three files still go red in some shuffled orders: the crew is preview-gated end to end block of previewSurfaces.test.tsx, sidePanelBrowserTabs.test.tsx and sidePanelPinsTab.test.tsx. The same reds reproduce under shuffle on unmodified origin/main, and this PR touches none of those test bodies.

Manual verification

Built website/dist and drove it with headless Chromium against stubbed /api/** (desktop 1400x900 light and dark, phone 390x844): the page list, Feature Previews, System, Config, the old /developer?tab=logs link, and the rail with an old mc-dev-mode=1 value all render as shown below.

Screenshots / video

Feature Previews, light and dark. The rail has no Developer row:

Settings > Developer, Feature Previews, light
Settings > Developer, Feature Previews, dark

The old link /developer?tab=logs lands on the Logs page:

Old Developer link lands on Settings > Developer > Logs

The chat side panel's + menu (Logs, Context, Crew log now in its diagnostics group for everyone) is not shown: the stubbed-API harness cannot open a chat session, so /chat renders its error card. sidePanelAddMenu.test.tsx renders the real menu and asserts those three rows and the three-group, two-separator layout.

System, Config, phone list, rail with the old key set

System page
Config page
Phone: the page list
Rail with mc-dev-mode=1: no Developer row

Related Issues

Closes #24797

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

@iamwhatever
iamwhatever requested review from a team and KiroCrewCaptain as code owners October 27, 2026 08:39
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 27, 2026
@github-actions

github-actions Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of b6caf23048c4e4f03df689f7e5a43aada0b73e52 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing blocks: the old /developer?tab= links redirect, rendered evidence is attached, and none of the readers I checked outside the patch breaks.

Notes

  • website/scripts/capture-21058-mcp-share-refused.mjs:100 still waits for /\/developer\?tab=mcp-pool/. After the redirect the URL is /settings/developer/mcp-pool, so this capture script will time out. Several other capture scripts still set mc-dev-mode, which does nothing now. Update them here or in a follow-up.

[DESIGN-REVIEWED] b6caf23

Description read

[DESCRIPTION-READ] 3aefc5608d38b044fc27d23a935fcd6d04546d048400ee205145ee26801ccc9a

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of b6caf23048c4e4f03df689f7e5a43aada0b73e52 — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

First-Principles-Verdict: PASS

Nothing blocks. The accepted RFC rfc-developer-tools-in-settings.md on base covers every product-shape item: the switch is removed, the gated surfaces are shown to everyone, and the old links redirect.

What this change ships

Inventory (9 items) — 8 justified

Intent: put every developer tool in one place, Settings > Developer, with no hidden switch in front of it. This is an ADDITION (a move plus removing the switch).

  1. Settings > Developer becomes a page list: Feature Previews first, then the nine internals pages — justified
  2. The left-rail Developer row and its unseen dot are gone — justified
  3. The Developer Mode switch and its "Open Developer page" link are removed — justified
  4. Side panel + menu always offers Logs, Context breakdown and Crew log — justified
  5. Desktop View > Toggle Developer Tools is always shown, and older shells get setDevMode(true) at boot — justified
  6. /developer?tab=<page> redirects to /settings/developer/<page> and keeps its other params — justified
  7. The developer_mode guide gate, the shell.developer and page.developer entries, the palette page and their catalog strings are removed — justified
  8. Search, find_ui, tips, the doctor hint and the docs point at the new paths — justified
  9. All nine internals pages now load lazily, where before only the memory graph did — undeclared

[FIRST-PRINCIPLES-REVIEWED] b6caf23

Description read

[DESCRIPTION-READ] a2ca3b31ac5d8b35c338adc529bd5b0b0d575901c089af0b1724af96d6ceb713

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ✅ PASS (a BLOCK with no Trigger and no Outcome does not block)

UX-level review of b6caf23048c4e4f03df689f7e5a43aada0b73e52 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

UX-Verdict: PASS

cannot evaluate: missing a screenshot of the chat side panel's + menu, which now shows a Logs / Context / Crew log group to every user. That menu is opened in daily chat use, and nobody has looked at what it looks like with the new group.

Evidence gaps

  • Side panel + menu, diagnostics group now always shown (SidePanelAddMenu.tsx drops the devMode filter from newMenuSections). No screenshot shows it, and the PR says so: "is not shown: the stubbed-API harness cannot open a chat session". A unit test asserting the rows does not show how the three-group, two-separator menu reads to someone who never turned on Developer Mode. To close: attach a screenshot of the open + menu in a real or seeded chat session.
  • Desktop View > Toggle Developer Tools, now always visible (app-menu.js builds it visible; appShell.tsx calls showNativeDevTools() on mount). No screenshot shows it. To close: attach a screenshot of the desktop app's View menu.

Notes

  • Every desktop shot (shot-01, shot-02, shot-07) opens on Developer, but the Developer row in the Settings column is scrolled out of view under "More below", so nothing in that column is highlighted. The blind reader said: "If I closed this page I wouldn't know how to get back." Now that the left-rail Developer row is gone, this is the only way in, so scroll the active Settings row into view when the page loads.
  • On the Feature Previews page the "Developer Tools" heading sits above the "Feature Previews" heading. The reader couldn't tell whether "Automatic cards for all sessions" counts as a preview. Rename that heading after what it controls, for example "Session cards".

[UX-REVIEWED] b6caf23

Description read

[DESCRIPTION-READ] 207868a60737cc0074938583e957f35c9c130ef797bffd0a5f4a9bd603031d91

That sha256 names everything this verdict read: the PR description, plus the 10 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed b6caf23048c4e4f03df689f7e5a43aada0b73e52 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] b6caf23

Verdict parsed from the review's SHA-scoped output markers for commit b6caf23048c4e4f03df689f7e5a43aada0b73e52.

False positive or not applicable? A repository writer can comment:
/ai-review override fable b6caf23048c4e4f03df689f7e5a43aada0b73e52 false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of b6caf23048c4e4f03df689f7e5a43aada0b73e52 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] b6caf23

False positive or not applicable? A repository writer can comment:
/ai-review override gpt b6caf23048c4e4f03df689f7e5a43aada0b73e52 false-positive: <reason, 20 to 500 characters>

@iamwhatever

iamwhatever commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor Author

self-added: yes
mechanism: Settings > Developer SubNav

  • span=f18b095dfa87 Existing setting deep links lose their target on narrow screens

Rebutted: disproportionate, as this lane's own adjudication found (harm LOW, downgraded).
Every link the app builds carries the page: registry and manual entries have params.sub (settingsRegistry.gen.ts, settingsManual.ts), and settingsPath turns it into /settings/developer/<page>.
Only a hand-saved /settings/developer?highlight=… opened below 760px shows the page list first; one tap on Feature Previews reaches the switch. Nothing is lost.
A highlight-to-page translation layer for every SubNav tab is new mechanism this PR's goal does not need.

@iamwhatever

iamwhatever commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor Author
  • span=5f78099786d1 product-shape change without accepted RFC

needs-a-decision: the RFC is #24818 (docs/request-for-change/rfc-developer-tools-in-settings.md, status accepted), recording the product owner's decision of 2026-10-26 to move the tools into Settings > Developer and remove the switch.
It lists all five surfaces mc-dev-mode gates and the ruling for each: the rail row goes, the side-panel Logs / Context / Crew log rows and the desktop DevTools item stay for everyone.
@iamwhatever: please review and merge #24818; this PR then rebases onto it and the gate re-runs. No override will be posted by the agent.

@iamwhatever
iamwhatever force-pushed the feat/merge-developer-page-into-settings branch from dc6a984 to 55ffa4c Compare October 27, 2026 09:02
@iamwhatever

iamwhatever commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor Author

self-added: yes
mechanism: doctor MCP hint wording

  • span=7ce5198e53bc assert "Developer Mode does not need" in out

fixed in 55ffa4c: the stale assertion now checks the new pointer, Settings > Developer > MCP Management, on whitespace-collapsed output so wrapping cannot split it, and asserts Developer Mode is gone from the hint.
Swept test/ for other assertions on removed Developer Mode wording: none (remaining hits are Windows symlink "Developer Mode", unrelated).

@iamwhatever

Copy link
Copy Markdown
Contributor Author

UX lane note (PASS, "cannot evaluate" the side panel + menu): the stubbed-API capture harness cannot open a chat session, so /chat renders its error card instead of the panel. The menu itself is covered by website/src/test/sidePanelAddMenu.test.tsx, which renders the real SidePanel and asserts Logs and Context breakdown are offered, with three groups and two separators. The PR body's Screenshots section says the same.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 27, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=2300c225ae48 product-shape change without accepted RFC: Developer Mode removal and Developer page relocation

needs-a-decision: the RFC is #24818 (docs/request-for-change/rfc-developer-tools-in-settings.md, status accepted), the product owner's decision of 2026-10-26 covering both the Developer Mode removal and the Settings > Developer consolidation.
It lists the five surfaces mc-dev-mode gates and rules on each, including the side-panel diagnostics rows and the desktop DevTools item shown to everyone.
@iamwhatever: merge #24818 and this PR rebases onto it; the agent posts no override.

@iamwhatever
iamwhatever force-pushed the feat/merge-developer-page-into-settings branch from 55ffa4c to 3b0e84e Compare October 27, 2026 09:34
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 27, 2026
@iamwhatever
iamwhatever force-pushed the feat/merge-developer-page-into-settings branch from 3b0e84e to bb4a075 Compare October 27, 2026 09:55
@iamwhatever

Copy link
Copy Markdown
Contributor Author

self-added: yes
resolution: removed DebugToolsTab search entry

  • span=01d1ca4b1cb2 Scroll inspector search loses its highlight during a cold load

fixed in bb4a075: removed the DebugToolsTab.tsx entry from PANEL_TAB_MAP and panelRoots, so the Scroll inspector is no longer a Settings search result and no highlight-only deep link to it exists. Registry and ui index regenerated.
This also restores main's rule that the debug overlay stays out of Settings search (First Principles item 5).

@iamwhatever

Copy link
Copy Markdown
Contributor Author

self-added: yes
mechanism: lazy internals pages

  • span=3d3eafbe51ea New Config lazy-boundary wait retains the short default deadline

fixed in bb4a075: the wait now has an explicit LAZY_PAGE_TIMEOUT_MS = 5000 with a comment naming the ConfigPage lazy import it awaits.
Class swept: the same bound and comment cover DeveloperPanel.lazyGraph.test.tsx (memory-graph, and a log-viewer wait that replaces a bare await Promise.resolve()).

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=9f8e9ebfdaf5 deleted pin reversed without mention — item 5

fixed in bb4a075: the debug tools stay out of Settings search. The DebugToolsTab.tsx extractor entries are removed and its header again says the overlay is deliberately not indexed by gen-settings-registry.mjs; it lives on Settings > Developer > Debug tools.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=47b894d086bd product-shape change without accepted RFC — items 1, 3, 4

needs-a-decision: the RFC is #24818 (docs/request-for-change/rfc-developer-tools-in-settings.md, status accepted), the product owner's decision of 2026-10-26, covering the Developer Mode removal, the side-panel diagnostics rows and the desktop DevTools item.
@iamwhatever: merge #24818 and this PR rebases onto it; the agent posts no override.

@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=4225ef21bbde product-shape change without accepted RFC — items 1–4

needs-a-decision: the RFC is #24818 (docs/request-for-change/rfc-developer-tools-in-settings.md, status accepted), the product owner's decision of 2026-10-26 covering the Developer Mode removal, the Developer page merge into Settings, and the always-shown diagnostics rows and DevTools item.
@iamwhatever: merge #24818 and this PR rebases onto it; the agent posts no override.

@iamwhatever
iamwhatever force-pushed the feat/merge-developer-page-into-settings branch from bb4a075 to d771d14 Compare October 27, 2026 10:23
@iamwhatever

Copy link
Copy Markdown
Contributor Author
  • span=a07d27147181 product-shape change without accepted RFC: Developer Mode removal and Developer page merge

needs-a-decision: the RFC is #24818 (docs/request-for-change/rfc-developer-tools-in-settings.md, status accepted), the product owner's decision of 2026-10-26 covering the Developer Mode removal, the Developer page merge into Settings, and the always-shown diagnostics rows and DevTools item.
@iamwhatever: merge #24818 and this PR rebases onto it; the agent posts no override.

@github-actions github-actions Bot removed the readiness: checking Automated validation is still running label Oct 27, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor Author

Rebased onto main adb562f, which now carries the accepted RFC from #24818 (docs/request-for-change/rfc-developer-tools-in-settings.md). Conflicts resolved: docs/feature-map/README.md (kept main's new context_turn_detail / turn= text, reapplied this PR's Developer Mode removals) and ui-index.generated.json (regenerated). Also removed a stale mock of the deleted useDevMode hook from main's new sidePanelAllTabs.test.tsx. New head 8befe1b. Locally: tsc, i18n:check, check_feature_map pass; changed backend tests 554 passed; changed frontend tests 54 files / 1081 tests passed; settings + side-panel suites 143 files / 2205 tests passed.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Oct 28, 2026
@iamwhatever
iamwhatever enabled auto-merge (squash) October 28, 2026 08:14
@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Oct 28, 2026
Settings > Developer becomes a SubNav: Feature Previews first, then the
logs, system, telemetry, storage, MCP Management, memory, config, debug
tools and archive pages. The Developer Mode toggle, the rail Developer
row and its unseen dot are removed; the side-panel diagnostics views
and the desktop DevTools menu item are always offered. /developer?tab=
links redirect to /settings/developer/<page>.
@iamwhatever
iamwhatever force-pushed the feat/merge-developer-page-into-settings branch from 8befe1b to b6caf23 Compare October 28, 2026 12:54
@iamwhatever

Copy link
Copy Markdown
Contributor Author

Rebased onto main to clear conflicts with #19661 (MCP sharing). Resolutions: the 13 locale catalogs keep this PR's removal of developerPage.tabs.mcpPool.description (main reworded it, but its only reader was the old Developer page tab list; en-XA regenerated with i18n:pseudo); settingsCoverage.test.ts keeps this PR's Settings > Developer wording and adds main's new McpManagementHero.tsx in the same wording. New head b6caf23. Locally: tsc, i18n:check, check_feature_map pass; changed backend tests 554 passed; changed frontend tests 55 files / 1102 tests passed; settings + side-panel + McpManagement suites 148 files / 2337 tests passed.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: passed Eligible automated validation passed for the current revision merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Oct 28, 2026
@iamwhatever
iamwhatever merged commit eceb35e into main Oct 28, 2026
111 checks passed
@iamwhatever
iamwhatever deleted the feat/merge-developer-page-into-settings branch October 28, 2026 16:00
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 28, 2026
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.

Merge the Developer page into Settings > Developer and remove the Developer Mode switch

2 participants