FAWALY SUPPORT

From installation to your first reviewed task.

Need help? Email support@daxow.com with your app version and a short description. Never send keys, passwords, verification codes or private source files.

1. Install the right package

Fawaly is coming soon to the Mac App Store and is not available for download yet. macOS 14 or later is required. When it is released, install the app from the Mac App Store, then follow the in-app setup for the internal execution engine that real delegation needs. Fawaly is the only app icon you use; all setup and settings stay inside it.

2. Activate the engine deliberately

In Fawaly, open the engine setup, review the proposed connection and background setup, and confirm. If the Store edition needs a companion package, follow the linked instructions from inside Fawaly; do not look for a second engine app to open. If macOS asks to allow background activity, complete that approval in System Settings. Return to Fawaly when the engine status is ready. Full Disk Access, screen recording and Accessibility control are not required to connect assistants.

3. Connect your primary agent and one assistant

In Agent connections, choose Claude Code or Codex. Review and approve tool registration and delegation instructions separately. Open a fresh client session; in Claude Code use /mcp and check that fawaly is connected. Installing an available tool does not guarantee the agent invokes it on every message.

In Assistants & plans, choose the provider you actually use. Use the guided service and plan picker: for MiniMax M Plan (Go, Explore, Build or legacy Token Plan), choose MiniMax · M Plan. Open the linked Subscription Key page, paste the key in the secure field, then choose Connect & check. The endpoint and model are prefilled. Kimi Code, Z.ai/GLM, DeepSeek, Ollama and LM Studio have their own supported connection paths. The app helps you choose the right coding-plan, API or local-tool setup. A chat subscription alone does not prove coding/API compatibility. Paste keys only into the secure connection field. Do not send them to support.

Check authentication and available quota, then choose the model and priority.

To put MiniMax first: in Delegation rules, use Choose first assistant, select MiniMax and its model, choose This task type or All task types, review the preview and press Make first. If it is not connected yet, Connect MiniMax opens its guided setup from the same chooser.

New tasks use the updated order; active tasks keep their original assistant. If it is busy, independent work in a separate workspace can use the next eligible idle assistant. Conflicting workspaces or a fully busy crew must wait or return a clear refusal. A green saved-setup badge is not proof of a successful generated task.

4. Run one small task and review it

Use a temporary sample project. Ask the primary agent to delegate one bounded task through Fawaly with a subscription or local assistant. Keep metered fallback disabled unless you explicitly want it. Match the Fawaly task ID and assistant/model to Tasks & reviews. Have your agent read the changed files and rerun checks before recording Accepted, Needed fixes or Rejected. Completed means the worker finished, not that it passed review.

Can I close the app?

Yes, after setup you can close the Fawaly interface. The internal execution engine handles delegation independently. Keep your coding-agent session open, and keep the Mac awake and online during a task. Fawaly is the single visible app for managing connections, settings and work history.

How do I know it is connected?

Ask your primary agent to check Fawaly status and its assistant roster; this checks tools without generating a model task. Then explicitly request a small delegation, match its task ID, assistant and model with Tasks & reviews, and have the primary agent inspect the result and record a review. A saved connection or a finished worker alone is not proof of accepted work.

Try it without an account

Open Settings → Demo mode. The banner identifies isolated simulated data. No real model calls or real keys are used. Turn Demo off to return to real setup. Demo completion is not proof your account is connected.

Permissions, limits and updates

Keychain access is contextual to saving/reading keys. Notifications are optional. Select the project when needed and review the execution scope before opening wider access. Local budgets stop future starts; they are not a provider-side billing reservation. Unsupported balances are unavailable, not zero. Optional iCloud settings sync is experimental; keys, work logs and paid-fallback permission remain local.

The Store UI updates through the App Store. The internal engine may use a separate signed installer; no public automatic-update feed is currently advertised. Quit/update only after active tasks finish. Back up your local configuration before manual recovery. Uninstalling the UI does not automatically delete engine/provider tools, backups or iCloud data. Contact support for scoped removal guidance.