Cleaner Approvals & Stronger ICP Bootstrapping

The new project chat gets a reliability pass around tool approvals, onboarding kickoff, ICP seeding, and brand color. The result is a smoother first project handoff into the co-founder chat.

After the chat-first foundation lands, the next problem is trust. Approvals need to look clear, stay responsive, and not leave the user wondering whether an action actually happened.

We also make the first-run path more coherent. A new project should not arrive as an empty shell, so onboarding now feeds an ICP, hypotheses, and an initial chat thread that can explain what to do next.

This is the kind of polish that makes a new architecture feel less experimental. The pieces from the previous day are still new, but the handoff from setup into chat is already cleaner.

  • Project chat tool cards: tool calls now render through dedicated project-chat cards, making approvals, inputs, outputs, errors, and pending states easier to understand.
  • Reusable kickoff prompt: new projects can start with a shared kickoff prompt that asks the chat to summarize the project, surface hypotheses, and recommend first steps.
  • ICP seed derivation: projects created from onboarding can now seed active ICP data, problem hypotheses, and solution hypotheses from the lean canvas.
  • Approval handling tightened: approving or rejecting agent actions now tracks pending approval IDs, prevents ambiguous button states, and keeps the UI responsive while the mutation runs.
  • Onboarding handoff refined: after onboarding, Tracsio creates the project, generates the ICP, starts a co-founder chat thread, and routes the user directly into that thread.
  • Primary brand color updated: the global primary and sidebar colors move to the green Tracsio brand tone, with matching brand utility tokens.
  • AI chat approval bugs: the approval path for project-chat tools is cleaned up so user decisions are submitted through the right mutation and reflected in the message UI.
  • New project dialog coverage: project creation paths get tests around the chat-first handoff and seeded project state.