You are viewing limited content. For full access, please sign in.

Discussion

Discussion

Some feedback on Smart Chat

posted on October 29 • Show version history

Starting with a positive: when Smart Chat does what you want its amazing. 

Every time you more forward with a positive outcome it's very encouraging. Any step back feels like 5 steps back. 

When I use smart chat with the intent to use agent mode I get: Tip: It looks like you're trying to perform repository actions. Switch to agent mode... Most times this is when I use Smart Chat in agent mode, switch folders (it defaults to ask mode?), and I write my prompt. Either stay in agent mode or provide a stronger visual cue on what mode I am in. 

Easy human solution: make sure you're in Agent mode. But it's not very clear. And if SC knows I am trying to perform repository actions (because you just said that to me), give me a one click 'continue in agent mode'. 

 

I get these often:

I'm sorry, I've encountered an error and cannot answer questions at this time. If the error persists, please clear your chat history and try again.

Anyone who uses mainstream AI almost never gets these. And after repeated asks and the error keeps coming up, people who are not all-in on AI are going to say it just doesn't work. 

Sometimes when I get the error, the agent still did what I wanted it to do even though it showed an error. The only way to know if it worked (or if it didn't) is to do manual checks to see if it completed.

 

(And add Smart Chat to the Post topics)

7 0
replied on November 11

Anthony,

Thank you for the detailed feedback, and for the kind words about when Smart Chat gets it right.

Ask vs. Agent mode: You're not the only one who has run into this, and you've made some good points. These are all things we're looking at as we rework that experience:

  • Changing the default to Agent
  • Merging the two modes into one

 

The error message: We've been looking into what causes that error and have made several improvements to Smart Chat since then. Please try the same kinds of requests again. You're right that the worst case is when the error appears but the action actually finished, which leaves you checking by hand. We're looking at that case specifically.

If you still get the error, please open a Support ticket and include roughly when it happened and what you asked. That lets us find those requests in our logs and work with you directly.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.