[Due for payment 2026-09-04] Home - Task is not created in Concierge after sending [] task from Concierge prompt box

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.61-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #98336
Email or phone of affected tester (no customers): jsoidjnosndjoijsi@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Other

Action Performed:

1. Go to staging.new.expensify.com
2. Go to Home.
3. Enter [] task on Concierge prompt box and send the message.

Expected Result:

Task will be created.

Actual Result:

Task is not created in Concierge after sending [] task from Concierge prompt box.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7242817_1787697637952.5.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7242817

Issue Owner

Current Issue Owner: @ZhenjaHorbach

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/e5bd8acc079d9265c5bbb732c6c6594fcd824e6d941776321fe8944bf1ec5dab

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #98336

[melvin-bot]

@puneetlath @ZhenjaHorbach you have been assigned to this deploy blocker because you reviewed the offending PR: #98336

[melvin-bot]

@adamgrzybowski you have been assigned to this deploy blocker because you authored the offending PR: #98336

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[MelvinBot]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #98336 - "[Home Page] Add Concierge prompt box to home For You section" by @adamgrzybowski (High confidence)
Related Issues: #94497 (feature request the PR implemented)

Recommendation: ROLL FORWARD

The new Home "For You" Concierge prompt box sends its text through a code path that calls addComment directly and never runs the [] task markdown detection that the normal composer performs, so [] task posts a plain message instead of creating a task. Reverting would remove the entire 40-file feature; a targeted fix (add task-syntax detection to the prompt box send path) is far smaller and safer.

Assigned: @adamgrzybowski (PR author), @ZhenjaHorbach and @puneetlath (approving reviewers) — already assigned
Labels: No changes. DeployBlockerCash kept (Frontend bug, App deploy blocked). No DeployBlocker present. Not reproducible on production (new feature), so the App blocker must stay.

📋 Detailed Analysis

Evidence

• PR [Home Page] Add Concierge prompt box to home For You section #98336 introduces the entire ConciergePromptBox feature (new file, 266 lines) and merged 2026-08-25, landing in the current staging deploy checklist Deploy Checklist: New Expensify 2026-08-25 #99466. The bug is staging-only and "N/A in production" because the prompt box does not exist in prod — the symptom is native to this PR.
• The prompt box's send handler calls askConcierge(value), which routes to useAskConcierge → addComment(...). There is no branch that inspects the text for the [] task markdown syntax, so the message is always sent as a plain comment.
• By contrast, the canonical composer submit path (useComposerSubmit.validateAndSubmitDraft) matches the text against CONST.REGEX.TASK_TITLE_WITH_OPTIONAL_SHORT_MENTION and, on a match, calls createTaskAndNavigate(...) instead of addComment. The new entry point never replicates this, which is exactly the missing behavior the reporter observed.

Verification

• Affected send path (calls addComment, no task detection): ConciergePromptBox.tsx#L116-L122 → useAskConcierge.tsx#L32-L50.
• Reference implementation that the prompt box omits (the [] task → createTaskAndNavigate branch): useComposerSubmit.ts#L110-L161.
• Task-detection regex used by the working path: CONST/index.ts#L5347 (TASK_TITLE_WITH_OPTIONAL_SHORT_MENTION).
• Confirmed PR [Home Page] Add Concierge prompt box to home For You section #98336 modifies useAskConcierge.tsx and adds ConciergePromptBox.tsx (both in the affected send path); merge date aligns with first report.

Root Cause

useAskConcierge.askConcierge unconditionally forwards the trimmed input to addComment. The [] task capability is not a property of Concierge or the backend — it is implemented on the frontend inside the composer's submit logic (useComposerSubmit), which runs TASK_TITLE_WITH_OPTIONAL_SHORT_MENTION and diverts matching messages to createTaskAndNavigate. Because the new prompt box built a parallel send path that skips that detection, [] task never becomes a task.

Suggested targeted fix: before calling addComment, have the prompt box send path (in useAskConcierge / ConciergePromptBox) run the same TASK_TITLE_WITH_OPTIONAL_SHORT_MENTION check and call createTaskAndNavigate with parentReport = the Concierge target report, mirroring useComposerSubmit.ts#L110-L161. Extracting that block into a shared helper reused by both submit paths would prevent future drift.

---

view run