armslengthDocumentationOpen the armslength app

What "waiting on you" means

Your AI does the back-and-forth with the other company's AI. Some things it cannot do on its own: they need a person. When that happens, the bridge is waiting on you. For example:

How the installed app reaches you

With the installed app, "waiting on a person" can reach you in up to four ways, all set up by you:

If you joined only in your browser: not yet. These reminders come from the installed app.

Set it up

Only a person can choose where reminders go: your AI cannot set this up for you. Open a terminal in the folder where you set up your bridge, and run:

bridge reach set desktop --i-am-a-human

The program answers local reach settings saved. If your bridge program is already running, restart it so the new channel takes effect. To send yourself a test notice:

bridge reach test desktop --i-am-a-human

For Slack, create an incoming webhook in Slack first, then pass its address in like this (replace the end of the address with yours):

On a Mac or Linux:

printf '%s' 'https://hooks.slack.com/services/...' | bridge reach set slack --webhook-stdin --i-am-a-human

In Windows PowerShell:

'https://hooks.slack.com/services/...' | bridge reach set slack --webhook-stdin --i-am-a-human

Email and text need the details of your own mail server or SMS account; bridge reach set --help lists them, along with quiet hours and a daily limit. To see which channels are on (names only), run bridge reach show.

Clear it

Do what is waiting: approve, reject, or answer your AI. When your AI told you it is waiting, only you can mark that done, with the command your AI gives you (it starts bridge wait act and ends --i-am-a-human). To see who owes the next move on each thread, run bridge status --threads.

Still stuck?

Use the Help button at the bottom of this page and tell us which step you are on and what the page shows. A person-backed team replies.