> ## Documentation Index
> Fetch the complete documentation index at: https://cogno.studio/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Answer decisions on mobile

> Get the decisions your work is waiting on as cards and answer them in place, without opening the chat.

When the AI needs a decision from you to keep the work moving, a **Decisions needed** card arrives. It says what the decision is, why it is needed, and what answering moves forward. You can approve, choose or type an answer right on the card, without opening the chat.

Questions from Cogno appear in the Desktop Task conversation first. If a question
remains unanswered for about a minute, it also appears here and can notify your
phone. Answering on Desktop before then removes the need for a mobile response.
The same question also appears above the existing message box in its Task chat.
Answer there or choose × to ignore it; either action removes the pending card
from Home.
The Task chat shows one question at a time. **Hold** puts it aside so you can
answer the next one. Open held questions again to return to their saved drafts.
In Task chat, sending an answer hides the question immediately while delivery
finishes. If delivery fails, the question returns with **Retry** for the same answer.

## Before you start

Sign in and select the Workspace the request belongs to. Answering needs your current access.

Mobile answers requests from attended local Task Sessions. Other requests show why they cannot be answered here and offer no answer. A request that needs a provider sign-in shows **Mobile sign-in recovery is not connected yet.**

## Answer a card

Home shows only your decisions, as a stack of cards. When nothing is waiting on you, Home shows a single record button. Your tasks, Captures and Settings are in the sidebar, opened with the button at the top left or by swiping sideways anywhere outside the cards. Work through them from the top, one at a time. Tapping a notification opens its card directly.

An approval (allow or decline) is decided by swiping or with the buttons.

| Action | Swipe | Button |
| - | - | - |
| Allow | Right | ○ |
| Decline | Left | × |
| Hold | — | Clock |

Any other card is answered on the card itself. Below it there is only the clock (Hold), and it does not swipe.

* Tapping an option sends that answer at once.
* A card with several questions is sent with **Send answer** once each has an answer.
* A typed answer is written in the same message box as a task's chat, at the bottom of the card, and sent with its send button.

**1. Read the card**

Read the title, the context, the permission scope and the **Answering this:** line. An approval card also shows the exact tool input read from the machine. **Show details** adds the longer explanation, and **Open the conversation** takes you to the chat it came from.

**2. Answer**

Allowing stays closed until the exact tool input is on the card; swiping right before then springs the card back and says why. For three seconds an answer or a decline can be taken back with **Undo** at the bottom of the screen; then it is sent. Leaving the app sends it at once.

## Hold a card

Press the clock button. Holding is not an answer: it moves the card to the back and shows the next one. The request's expiry and permission scope do not change.

* **Undo** right after brings it back.
* Touch and hold the clock button, then choose **Remind me in an hour** or **Remind me at 6 PM**, to be reminded at that time. Holding alone never notifies you again.
* When the waiting cards are done, an **All caught up** card appears. Swipe it to go through what you held. A card you hold again there waits until the next pass.
* New cards always come before held ones.

With VoiceOver, allow, decline and hold are in an approval card's actions.

## After you answer

The card shows **Answer sent** at once. It changes to **The work continued** once Engine has applied your answer and continued the work. Answering alone is never shown as continued.

| Shown | Meaning |
| - | - |
| **Answer sent** | Core saved your answer; Engine has not applied it yet. |
| **Answer applied · checking the work continued** | Engine applied it and the continuation is being confirmed. |
| **The work continued** | Engine confirmed the work continued. It does not mean the work is finished. |
| **The answer could not be applied** | The request was canceled, expired or replaced before your answer took effect. |

## Troubleshoot

If the tool input cannot be read, check that the machine is online and press **Retry**. **Decline** stays available. Tool input is held only on the open screen and cleared when the app goes to the background.

If another device answered first, the card shows what is true now. Switching accounts never carries one account's requests or notification actions into another.

## Related docs

* [Control execution access](/docs/execution-access.md)
* [Use Task Sessions](/docs/task-sessions.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.