For the complete documentation index, see llms.txt. This page is also available as Markdown.

Gates

Operator conversations that have stopped to wait for your answer.

Gates lists the Operator conversations you started that ended on a question for you. An agent working for you needed a decision, and nothing moves until you answer.

Select Gates in the top bar. The page describes itself exactly: "Conversations you started that have stopped to ask you something. Open one to answer it." It is in both Console and Control Center, and the two are independent: Console's Gates lists only Console Operator conversations, and Control Center's lists only Governance Operator conversations.

The Gates page in Console, listing one request: Add Dashboard Page with Key Metrics, asked by App Builder Agent, Requested 11 mins ago, with an arrow to open it
A request waiting on you, and the agent that asked.

What each request shows

Part
What it tells you

Title

The conversation it came from, for example Add Dashboard Page with Key Metrics

Agent

Who is asking, for example App Builder Agent

Requested

How long it has waited, for example Requested 11 mins ago

Select a request, or its arrow, to open the conversation at the question. A request from another project opens in that project. The page refreshes on its own while it is open, so new requests appear without reloading. Switch between list and grid with the icons at the top right.

Only your requests appear here, and only you can answer them. A conversation you started waits for you, not for a colleague who happens to open it.

Answer a request

In the conversation, the question sits in a card above the composer, naming the agent that asked:

An Operator conversation with a question card from App Builder Agent: There are two apps named ToDo List App in your project. Which one would you like to update? Two numbered options follow, then an Answer in your own words… field with a paperclip and a Skip button
Pick an answer, write your own, attach a file, or skip.
  • Pick a numbered answer, when the agent offers choices.

  • Write your own in Answer in your own words….

  • Attach a file, when the agent asks for one, such as a brand guide or a spreadsheet. A question that offers numbered answers doesn't take a file.

  • Skip, to let the agent carry on without an answer.

Once you answer, the request leaves Gates and the work continues.

Notes and limitations

  • An unanswered request holds up the work. A conversation that ends on a question waits until you answer. Check Gates when something you started hasn't finished.

  • Requests are per space. Console's Gates doesn't show Control Center conversations, and the other way round.


Maintained by Abhishek Paul AI-assisted, human-approved

Last updated

Was this helpful?