[BUG] Desktop Code tab: /workflows works but /deep-research & ultracode can't initiate a run (workflows toggle ON)

Resolved 💬 2 comments Opened Jun 3, 2026 by esuds Closed Jul 9, 2026

Summary

On the Claude desktop app's Code tab, dynamic workflows are enabled (toggle ON, /workflows opens), but there is **no way to start a workflow**: /deep-research is missing from / autocomplete, the ultracode keyword doesn't highlight/trigger, and /effort doesn't offer ultracode. The identical account works fully in the standalone CLI.

Environment

  • Claude desktop app: 1.10628.2
  • Bundled Claude Code runtime: 2.1.161 (macOS, Apple Silicon)
  • Workflows enabled: /config Dynamic workflows toggle = ON; account flag tengu_workflows_enabled = true
  • Web search: enabled

Steps to reproduce

  1. Open a Code tab session in the desktop app.
  2. Run /workflows → opens fine (the run manager works).
  3. Type /no /deep-research in the command list.
  4. Type ultracode at the start of a prompt → no highlight, no trigger.
  5. Run /effort → does not offer ultracode.

Expected

Parity with the CLI: /deep-research <question> available, and ultracode / /effort ultracode initiate a workflow.

Actual

The workflow manager (/workflows) and the toggle are present, but no initiation entry point exists in the desktop Code-tab session. The same account + provider + config surfaces /deep-research and ultracode correctly in the standalone CLI on runtime 2.1.162 (direct Anthropic). So initiation appears unwired specifically in the desktop session harness, independent of the toggle and the account flag.

Possibly related

  • #63498 — dynamic-workflows toggle vs. gate reading different sources
  • #63957 — workflow keyword trigger dismissals on macOS
  • #40495 — Cowork/agent-mode settings resolution gaps

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗