Questions, approvals and Apply cards

When your agent needs something from you, it asks on a card in the conversation: in its direct message, or in the work item’s thread it’s working in. You can answer from your computer or your phone. Only you can answer your agent’s cards; colleagues in an item’s thread see them read-only, with “Waiting for Kelly”.

There are four kinds of cards:

• Question cards, when the agent needs a decision.
• Tool approvals, before it runs a command or changes a file.
• Apply cards, for changes to your projects that it proposes.
• Handoff cards, when it asks to pass part of its work to another of your sessions.

The question and tool approval cards come from the buildit plugin in Claude Code. See Connect a Claude Code session.

Question cards#

When Claude asks you something, its questions arrive as one card, up to 4 questions at a time, instead of in the terminal.

Answer it#

• The card shows one question at a time, with “Question 2 of 3” and page dots.
• Each choice has its description beside it (under it on a phone). Some questions let you pick several.
• To answer in your own words, type in the field under the choices. It takes up to 2,000 characters.
• When a question takes one choice, tapping it moves on by itself. With several choices or your own answer, tap Next. Back returns to the previous question.
• After the last question, Review your answers lists them all. Tap one to change it, then tap Send.
• A card with just one question sends as soon as you pick (or on Send, for several choices or your own answer).

Every question needs an answer. Your answers go back to Claude together, and it carries on.

After you send#

The card folds to one row per question, with its answer, and “Answered” with the time. Tap a row to see the full question again.

• In your direct message, only you see your answers.
• In an item’s thread, everyone in the thread sees your answers once you send them.

If you don’t answer#

A question waits 60 minutes. Then the card closes and Claude is told nobody answered, so it makes a safe assumption and says which, or stops and says what it needs.

To close a question yourself, press and hold it on a phone, or right-click it on a computer, and choose Dismiss question. Claude is told the same way.

Tool approvals#

When Claude Code would ask you before it runs a command, changes a file or uses another tool, it also asks you in buildIt.social on a card. The first answer wins, whether it’s on the card or in the terminal.

What the card shows#

• Everyone who can read the thread sees only which tool the agent wants and who asks: “Claude wants to use Bash”, and the subagent when one asks.
• Only you see the details: Claude’s description of the call and each part of it (the command, the file and its new content, the text an edit replaces), as plain text. Long values fold, with Show all and Show less.
• Details are shown only while you’re online, and they’re deleted 7 days after the card ends.

Your answers#

• Approve runs the call. For a Bash or PowerShell command, the app first asks Run this command?, showing the command and where it runs; tap Run it.
• Allow for this session appears when Claude Code suggests a rule for the rest of the session, and the card shows the rule’s words, such as “Allow Bash commands starting with “npm test” for the rest of this session”. It approves this call and the rule. There’s never an “always allow”.
• Deny tells Claude no. It won’t retry the call, and asks you what to do instead.

Approve only what you can see in full#

You can approve in the app only what you can read in full. Two kinds of cards offer only Deny:

• “Part of this is hidden because it looks like a credential. Answer in the terminal, or deny.” Passwords, keys and tokens are hidden before anything leaves your computer, so the card can’t show you exactly what would run.
• “Too long to check here. Answer in the terminal, or deny so Claude splits it.” A Bash or PowerShell command that was too long to show in full.

Either way, answer in the terminal, or deny it and Claude splits the command or keeps the credential out of it.

Where approvals go#

• The session’s own approvals go to your agent’s direct message.
• An item’s helper asks in that item’s thread.

If nobody answers within 60 minutes, the card expires and Claude is told no. The card also closes if the session ends, if the item is taken from your agent, or if tool approvals are switched off.

Turn them off#

In your agent’s details, turn off Tool approvals in buildIt.social: the sessions then ask only in their terminal. In Claude Code, the buildit plugin’s settings (/plugin) also have Tool approvals in buildIt.Social and Approval wait (minutes).

Claude Code asks for approval only in modes that ask. In auto mode, when edits are accepted automatically, or for tools you’ve already allowed, nothing is carded.

Apply cards#

Some changes never happen in one step: deleting, moving or bulk-editing items, archiving a status, changing workflows, work types, fields or labels, and drafts of new items or of changes to items (such as the ones you ask for from a button in the app). For these, your agent posts an Apply card: a preview of exactly what would change, with Apply and Cancel.

• The card names the change (“Delete an item”, “Create items”, “Change items”...), the project, a summary and the items, up to 20 and then “…and 12 more”.
• Apply asks Apply this change? first. Then buildIt.social makes the change itself, as you through your agent. The agent can’t apply it on its own.
• Cancel closes it. Nothing changes.

The card then shows what happened: Applied., Cancelled. Nothing changed., or Not applied: the items changed since this preview. if someone changed the items after the preview. A card for new items lists their keys once applied; tap one to open it.

An Apply card stays open 60 minutes, or 24 hours when it answers something you asked for from a button. After that it shows Expired. Nothing changed.

Show all#

On a Create items or Change items card, Show all opens everything the change holds: each item, new or with its key, its fields (such as “Priority: Medium → High”), labels added and removed, links, and the full description. It opens as a sheet on a phone and a dialog on a computer.

Replace instead#

When your agent drafts a description for an item that already has one, the draft is added to the end of the description. If you’d rather replace the old text, tap Replace instead. The app asks Replace the description? (“The current text is removed.”) before it applies.

Where Apply cards appear#

• A change your agent proposes while chatting goes to its direct message.
• In an item’s thread, a change within that item’s project appears in the thread; anything wider goes to the direct message.
• A card that answers a button, such as Turn into items with my agent, appears where you asked.

Colleagues see Apply cards in shared threads with “Waiting for Kelly’s approval.”, and can’t apply them.

Waiting for your answer#

While any card waits for you, your agent’s direct message shows Waiting for your answer in the list and at the top of the conversation, and the thread with the card shows it too. You also get a notification. See Notifications from your agent.