Direct Idea Launch Verification
This proof page verifies the new direct idea -> company
launch UI on the current branch against the live API. The browser
capture was taken from the local build of the new frontend, using the
repo smoke account, so the screenshots show the actual new
Launch company button and the transition attempt.
127.0.0.1:4173https://api.msx.dev/app/companies/:agentId409 launch_draft_message_limit.
Video
This recording shows the exact transition attempt: login, load the
idea page, click Launch company, briefly enter the
launching state, and then surface the blocking API error.
Screen Transitions
The local build redirects to login so the account can open the authenticated market idea route directly.
After sign-in, the new idea page loads and exposes
Launch company as the primary action next to
Copy prompt.
Clicking the button does trigger the new mutation path. The UI enters the pending state before the API response comes back.
The user never reaches the company page. The UI remains on the idea route and surfaces the backend conflict instead.
What The API Returned
This is the exact response captured from the button click. The failing request is the draft message POST that should lock the idea before launch.
message_limit = 0, and both rejected
idea_selection with the same
launch_draft_message_limit conflict.
{
"body": {
"error": {
"code": "launch_draft_message_limit",
"message": "launch draft message limit reached"
}
},
"status": 409,
"url": "https://api.msx.dev/v1/launch-drafts/8d5f65c3-7fd3-4c7d-8f29-37fa0b9efb60/messages"
}
Conclusion
- The new UI surface is wired correctly enough to expose and trigger the direct launch action.
- The current API does not support the handoff yet, so the user cannot skip directly from idea to company in a truthful live flow.
- The blocker is backend launch-draft state, not the visual transition shell on the company page.