Support

No. The mobile app does not have its own sign-in screen. Your account lives on the Mac, you sign in once with Google or email/password in the macOS companion app. The phone links to that account by scanning a QR code shown in the Mac app (see "How do I link my phone?" below). No email, no password, no Google account needed on the phone.

On your Mac, click the Agents At Work menu bar icon and choose Link Mobile. macOS will ask for your password or Touch ID first, so a random person at your desk can't generate a pairing code, then a QR code appears. On your phone, open Agents At Work, go through the onboarding slides, and tap Scan QR Code on the last slide. Point your camera at the Mac's QR code, done. Your phone is linked, and the communication channel's end-to-end encryption is set up, in one step.

The QR code expires after 1 hour. If you see an "expired" error, close and reopen Link Mobile from the Mac menu bar to get a fresh code.

Make sure you have scanned the QR code to link your phone (see above). The Mac companion app must be running and connected to the internet. If the Mac is running but still doesn't appear, try quitting and relaunching the macOS app.

The macOS companion app sends a heartbeat every 30 seconds. If your Mac went to sleep, lost its network connection, or the app was quit, the heartbeat stops and the mobile app shows the computer as offline. Wake your Mac and make sure the Agents At Work app is running to restore the connection.

Check that notifications are enabled for Agents At Work in your phone's Settings app. On iOS, go to Settings → Agents At Work → Notifications → Allow Notifications. On Android, go to Settings → Apps → Agents At Work → Notifications. Also confirm that the macOS app shows your session as running (not stopped).

On your new phone, open Agents At Work, go through onboarding, and tap Scan QR Code. On your Mac, click the menu bar icon and choose Link Mobile to show a fresh QR code. Scan it with your new phone, it will replace the old phone's link automatically. If prompted that "this Mac is already linked to another device," tap Continue to proceed.

Yes. Install Ollama on your Mac and pull at least one model (ollama pull qwen2.5, for example). Once Ollama is running, Agents At Work detects it automatically within about 30 seconds and adds an Ollama tab to the session picker.

Start a session from the app, pick your model and project folder, and send prompts from your phone as you would with any other agent. Because the model runs locally on your Mac, your prompts never reach a third-party AI service. No API key is required.

If the Ollama tab does not appear, click Discover Agents from the Agents At Work menu bar icon. If it still does not appear, confirm that Ollama is running with ollama list in your terminal and that at least one model has been pulled.

If sessions stop responding or a new session won't start even though Ollama appears to be running, restart the Ollama server. Run pkill ollama && ollama serve in your terminal, or quit and relaunch the Ollama desktop app. Agents At Work detects it again within about 30 seconds and the Ollama tab reappears.

Open the macOS app and click Discover Agents from the menu. This re-runs agent detection and hook installation. Make sure the agent CLI is installed and available in your $PATH. For Codex, confirm that codex_hooks = true is set in your ~/.codex/config.toml. For Gemini, confirm the GEMINI.md hooks are configured. For Grok, confirm the binary is accessible (curl installer places it in ~/.local/bin/grok, ensure that directory is in your $PATH). For Ollama, confirm it is running (ollama list should return your installed models) and that at least one model has been pulled.

This was a known bug in earlier versions where the stop status was written after each agent response turn. An "idle" status was introduced in v0.28.0 to distinguish "waiting for input" from "actually stopped." Update to the latest macOS app version to resolve it.

From your phone, open the project in the mobile app and type your message in the input field at the bottom. This forwards the message to the agent's terminal. You can also send slash commands like /restart or /stop from the same field, or use the menu in the top-right corner of the project screen.

On Mac, use the session window: click an active session in the main Agents At Work window to open the live conversation feed, then type in the text bar at the bottom and press ⌘↩ to send. The session window also lets you search the conversation and toggle Mobile or Desktop mode from its status bar. Press ↑ and ↓ in the input field to cycle through your last 10 sent prompts.

The session window is a macOS window that shows the live conversation with any active agent session, so you can follow what the agent is doing without keeping a terminal visible. Click an active session in the main Agents At Work window to open it.

From the session window you can:

• Read the live conversation feed as the agent works
• Send messages to the agent using the text bar at the bottom (⌘↩ to send)
• Navigate your last 10 sent prompts with ↑ and ↓ in the input field
• Search the conversation by keyword
• See whether the session is in Mobile or Desktop mode, and switch modes, from the status bar at the bottom
• See whether auto-approve is active (a shield badge appears in the status bar when "Yes for this session" has been granted)

The mode is determined automatically by the model you choose, no setting to toggle.

Chat mode works with any Ollama model (mistral, llama3.2, gemma2, and others). The model responds to your messages in natural language but does not access your files or run commands. Good for writing, Q&A, summarising pasted content, and planning.

Agentic mode requires a model that supports tool use, specifically the qwen2.5, qwen2.5-coder, or qwen3 families. In this mode the model can read and write files, list directories, and run shell commands on your Mac to complete multi-step tasks. Before doing anything potentially destructive, it pauses and asks for your approval, either as a tap-to-approve card on your phone or inline in the Mac session window. You can approve once, approve for the whole session, or deny.

See the Ollama modes section in the tutorial for a model-by-model comparison and RAM requirements.

Agents At Work encrypts your conversation content, including prompts, agent responses, tool-call summaries, and project paths, with AES-256-GCM on your Mac before it reaches Firebase. Only your devices hold the encryption key; Firebase and AnswerSolutions never see your data in plaintext.

The encryption key is established automatically during the QR scan that links your phone to your Mac. There is no separate encryption setup step: scanning the QR code handles both authentication and key exchange in one go. The key is stored locally on both devices and is never transmitted to our servers.

Yes. Sign in with the same account on all your Macs and each will appear as a separate computer in the mobile app after you scan its QR code. The number of Macs you can connect depends on your subscription tier:

• Personal: 1 Mac
• Pro: up to 5 Macs

All Macs must be signed in with the same email address so the mobile app can show them all in one list.

Unlink this phone: Open the Agents At Work mobile app, go to Settings → Unlink this Phone. This removes the phone's connection to your Mac account and clears local data from your device. Your Mac account and data are not deleted.

Delete your account: Account deletion is done from the macOS companion app. Open Agents At Work on your Mac, go to Sign Out / Uninstall in the menu, and follow the on-screen instructions. Alternatively, email support@answersolutions.net and we will process your deletion request within 30 days.

Note: subscription billing is managed by Apple or Google. Deleting your account does not automatically cancel an active subscription. Cancel through the App Store or Google Play first to avoid further charges.