AnswerPath
AnswerPath
Changelog
  • Docs
  • Changelog
  • Feature requests
  • Support portal

AnswerPath changelog

New Company OS & AnswerBank Add Q&A

New Company OS & AnswerBank Add Q&A

Company OS: a new guided workspace

Company OS ships as a new guided journey for building out your company's operating model. A visual skill tree maps the path through each level, and every level opens into its own workspace with an artifact form, completion validation, and a per-level AI coach chat that helps you work through the material.

Each workspace is backed by its own data model for artifacts, coach messages, and curriculum config, with authentication and workspace isolation enforced through Supabase RLS. When you're ready to share progress, you can export the entire journey as a markdown zip bundle for use outside the app.

Answer Bank: manual entries and ownership

You can now add answers to the Answer Bank by hand, view each entry on its own detail page, and link it to an owner and a source. New owners get an email the moment they're assigned an entry.

Improvements

  • Roles now map to Curator, Collaborator, and User, aligning permissions with how teams actually work.

  • You can refine an answer immediately after generating it, without starting a new request.

  • Onboarding includes clearer wayfinding so new users can find their next step faster.

  • OpenAI quota-exceeded errors now show distinctly from generic rate-limit errors, making it clear when a request failed due to plan limits rather than throttling.

  • The Teams Q&A bot now surfaces as a banner alongside Slack instead of competing for the same space.

  • The sign-in page now fills the full viewport width so the auth card centers correctly on all screen sizes.

  • Usage telemetry has been removed.

Fixes

  • Pending invites now show up correctly, and colleague invites and invite emails work again after a 404 regression.

  • Saving to a project no longer fails silently; errors now surface properly.

  • Deleting an organization now completes cleanly after a foreign-key issue in the audit trigger was fixed.

  • Confidence scores are now calculated on one consistent scale across the app, instead of two conflicting ones.