Requests

Before you start#

• You need the permission Register requests in the project to write a request, Comment to discuss one, and Take decisions to answer the analysis or close a request. See roles and permissions.
• The automatic analysis of a request needs an external intake agent that the person who operates the installation has configured and enabled. Without it your request is saved and waits.

Write a request#

1. Open the project and choose Requests. The heading is "The original request comes first."
2. Choose New request. The form opens as its own page, titled Record a request: "Write what you need in your own words. Intake reads the code and prepares a formal definition from it."
3. Fill in:
   • Title, up to 160 characters.
   • What should change?, up to 5,000 characters. "Write in any language. The original text is kept exactly as submitted."
   • Source or conversation reference, which starts as platform. Use it to say where the ask came from.
4. Choose Record request. Cancel goes back to the list.

Expected outcome: the request opens at its own address with a reference such as R-1, in the state Waiting for intake, and an analysis is queued.

The form carries this warning, which is a fact about the installation and not an error: "Automatic intake needs a permanent worker, provider trigger and verified remote MCP connection. Requests remain saved while these are disconnected."

Without the permission the form is disabled and says "You do not have permission to register requests in this project."

References such as R-1#

Every request gets a short reference that is unique inside its project: R-1, R-2, and so on. Approved requirements get D-1, and batches get B-1. A reference belongs to one record for its whole life and is never reused, because nothing in Delegate deletes records. Use it in conversation and in the Search box of the list, which matches the reference and the title.

Follow the analysis#

The list shows each request with its state, who registered it and when. State filters it; the filter is remembered when you come back from a request.

Answer a question#

When a request Needs your answer, the question is stated at the top of its page, above everything else: "Intake asked something it needs before it can propose a definition. Your answer returns the request to analysis."

1. Read the question under Analysis, questions and answers in the Record panel if you need the full exchange.
2. Write Your answer.
3. Choose Answer and continue intake.

Expected outcome: "Saved.", and the request goes back to analysis. This needs Take decisions. A comment is not an answer: the Discussion panel says so itself, "A comment is discussion. It does not change the request, answer a tracked question or approve anything."

Edit your request, keeping the original#

Only the person who registered a request can edit it, and only while it is Waiting for intake, Needs an answer or in Human evaluation.

1. On the request, under The request as it was written, open Edit your request: "The first submission is kept. Your change is recorded as a new revision, with what changed and when."
2. Change Title or What should change?, and optionally say What changed.
3. Choose Save revision.

Expected outcome: the page shows "Revision 2", and Record gains "2 revisions of the request", where the first words stay readable next to the current ones. The original submission is never rewritten.

Discuss a request#

In Discussion, write Your comment and choose Add comment. Comments from people, from agents and from an imported source are labelled Person, Agent and From the source system and are never mixed.

Close or separate a request#

With Take decisions, the Record panel offers two disclosures while the request is still open:

• This request contains more than one ask separates it into two requests that each go through analysis: "Each part becomes its own request and goes through intake separately. This original stays exactly as written."
• Dismiss this request closes it with a Reason for dismissing and, optionally, Repeats an earlier request. "A dismissed request keeps its original text and history, leaves the intake queue and creates no requirement."

Import a request from another system#

Manual import appears only when you may Configure the project; otherwise the page says "Importing records into this project needs permission to configure it. Ask a workspace administrator."

"An import preserves the source author and time beside your own. It approves nothing, starts no agent and does not close the source record."

1. Open Manual import. Choose what you are importing: A request, A comment or An intake outcome.
2. Fill in the source: Source system (for example github), Source identifier, Address of the source record, Author recorded by the source and Time recorded by the source (for example 2026-09-19T15:04:00Z).
3. For a request, fill in Title to display (at most 160 characters; a longer one goes in Full source title) and Text as the source holds it.
4. Choose Show what this would do. The preview says one of "This would create a new record.", "This would update a record that is already here." or "Nothing would change."
5. Choose Apply this import.

Expected outcome: the request exists with a line such as "Written by {author} in {provider} and imported here." Importing the same Source identifier again writes nothing new; if the source text changed, it records a new revision. "Importing never presents you as the author."

Analyze several requests together#

In Batches, Group requests lets a person with Take decisions choose at least two requests that are waiting for analysis, name the batch and ask for one joint analysis. "Each request keeps its own state, questions and definition." A request whose analysis already reached an agent cannot be grouped.

Limits#

Next action#

When the state reaches Human evaluation, continue with Review and planning.

Related: Work status vocabulary · Delegate recovery · Supported limits