Group task configuration under settings

[puemos]

Problem

The primary navigation is becoming crowded with setup and configuration destinations that are used much less often than core workflows.

The navigation should prioritize daily actions—creating tasks, searching, reviewing the inbox, and using the command center. Configuration that is typically completed once or revisited occasionally should live in Settings, where it remains discoverable without competing with frequent work.

Why: Separate doing work from configuring how work gets done. This keeps the main navigation focused while giving task and agent configuration a clear home.

Changes

• Replace the separate Agents, Skills, and MCP servers navigation entries with one Configure entry that opens Settings with Agents selected.
• Group Settings by concern: Account, Workspace, Configure, Experience, Integrations, and Application.
• Place Agents, Skills, MCP servers, Claude Code, and Self-driving together under Configure.
• Make Settings the canonical home for Skills and MCP servers while preserving legacy URLs through redirects.
• Preserve existing configuration behavior and full-height pages, and consistently fall back from categories unavailable on the current host.

The information architecture follows one rule:

• Navigation: destinations and actions used regularly
• Settings: setup, customization, integrations, and lower-frequency configuration

Screenshots

How did you test this?

• Focused settings visibility tests
• Biome checks on touched files
• pnpm --filter @posthog/ui typecheck
• git diff --check

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

---

Created with PostHog Code

[trunk-io]

😎 Merged successfully - details.

[github-actions]

React Doctor found 1 issue in 1 file · 1 warning.

1 warning

src/features/settings/components/SettingsPanel.tsx

• ⚠️ src/features/settings/components/SettingsPanel.tsx:166 Chained array iterations js-combine-iterations

_{Reviewed by React Doctor for commit 7438f5a.}

[veria-ai]

Medium: AI approval gate bypass

A signed-in organization member awaiting admin approval can open Settings, select Agents, and use “Run setup agent,” which calls taskService.createTask with workspaceMode: "cloud" and executionMode: "auto". Prevent this category and its agent actions from rendering in the pre-router settings dialog until AI data processing has been approved.

[puemos]

Confirmed: the pre-router approval screen can open the shared Settings panel, and this PR newly exposes the Agents setup action there. This commit does not address that approval-state behavior, so I am leaving the thread open rather than marking a valid concern resolved.

[veria-ai]

PR overview

This pull request groups task-related configuration into the Settings experience, including settings content for agent setup and task execution options. It adds or exposes UI paths such as the Agents settings area and setup-agent action from the settings page.

There is one open security concern: users who are signed in but still awaiting AI data-processing approval can reach the Agents settings flow and start an automatic cloud setup task. That creates a concrete approval-gate bypass for agent actions, though the impact appears limited to this pre-approval task execution path. No issues have been addressed yet, so the PR still needs a guard to hide or block these settings actions until approval is complete.

Open issues (1)

• Medium: AI approval gate bypass — packages/ui/src/features/settings/components/SettingsPageContent.tsx:57

Fixed/addressed: 0 · PR risk: 6/10

[k11kirky]

Automated review — findings inline.

[puemos]

/trunk merge