Sign in

Wakel

Verified: controls wakel.siChecked on 10 Nov 2026.

A private AI agent for your Mac that plans, uses your apps, and asks before anything sensitive. Arabic and English.

macOSFree trial

On 10 Nov 2026 the builder showed us they control wakel.si.

Listed by ehab,

Leave feedback

Wakel is a local-first AI agent for Mac. Connect the Claude, ChatGPT or Grok account you already have, or a free local model, then tell Wakel what you need in Arabic or English. It plans the steps and does the work on your Mac: it organises files, works inside your apps (Photoshop, Illustrator, Keynote and more), browses the web, and prepares drafts such as emails, documents and spreadsheets. It asks before sending, deleting or paying for anything, and everything it does is listed in an activity log. Your files stay on your computer. It can also work as a small team of AI employees, such as a writer, a designer or an accountant, who hand work to each other. An iPhone companion lets you follow tasks and approve steps from your phone. Free for 30 days with no card, then $25 once.

What to test

Download it free from wakel.si (30 days, no card), sign in with your Claude, ChatGPT or Grok account, then give Wakel one real task from your week, for example "Organise my Downloads folder", "Resize this design for Instagram and LinkedIn" or "Draft a polite payment reminder and show it to me first". Try it in Arabic or English. Tell me where it surprised you, where it asked too much, and where it got stuck.

Bounty
?per approved post

The bounty is what this listing pays a tester per approved post. Sign in to see it.

Download page, opens in a new tabWebsite, opens in a new tab

Free trial, then a paid plan. Testers never pay to test. If a trial asks for a card, cancel before it ends.

This app is made and run by its builder, not by TestMyBuild. We tried it once before listing it, which is not a check that it is safe, keeps working or handles your data well. Use your own judgement.

Report listing

Feedback

1 tester, on macOS

1 post, newest first
jan
Tested on macOS
Signup screenshot

I'll be honest: I came in sceptical, because "AI agent that uses your Mac" is a sentence I've heard a lot lately. This one got further than most. Story first, then fixes, then your questions.

The story
I gave Wakel the most meta task I could think of: "Please list my app on TestMyBuild." Yes, the platform you're reading this on. Web navigation is where agents usually fall flat, so I wanted to see it sweat.

The start was really good. It asked which link to use, whether to check details first or submit straight away, and warned me submitting holds 10 credits and can't be undone. I was genuinely thinking: okay, this is very good.

Then: "The browser I use for websites wouldn't open. It returned no-browser." I opened Safari and asked again. Same error. It offered to drive my Safari window instead, so I said yes. Cue new macOS permission prompts, even though I'd pressed Turn It All On. Allowed those too. It worked ~4 minutes, burned 53k tokens, opened testmybuild.app… and then politely told me to do it myself. Screen Recording was still blocked (I skipped the restart, see below) and Safari needed a developer setting.

So it planned perfectly, asked all the right questions, made it to the door… and couldn't open it.

To be fair, I also tried your example "Organise my Downloads folder." Done in under half a minute. Only one file there (the Wakel installer, of all things), so it moved nothing and offered to delete the .dmg, asking first instead of just doing it. Without a browser it's quick and sensible. But ~22k tokens to look at one file feels heavy.

WRONG / CONFUSING

1. The browser is the blocker:
Everything before execution was great, everything after needed a browser setup that didn't work out of the box.

  • Make the first web task just work, or set it all up during onboarding
  • "no-browser" means nothing to a normal user. Say what's wrong and give a one-click fix

2. The restart nobody does:
After the permissions it says you need to restart, with a friendly Continue button next to it. Of course I pressed Continue. Everyone will. That's exactly what broke Screen Recording later. Force it, or do it for me.

3. "Turn It All On" didn't turn it all on:
Loved that button. But my first real task still asked for more (System Events, screenshots, a Safari setting). If it's called Turn It All On, turn all of it on.

4. Wakel talking to itself:
One reply started with "KEEP is not right here, because my last answer needs one correction…". Looks like internal reasoning leaking into the chat.

5. I almost became Egyptian:
In English setup, the dialects (Saudi, Egyptian, Gulf) sit on the left where I start reading, so it felt like I had to pick one. In English, put English first on the left and make the dialect clearly Arabic-only.

6. Opus on High for a simple errand:
Auto model selection is nice, but it picked the most expensive setting for a simple task. Plus 22k tokens for one file. That burns people's usage. Start cheaper, step up when needed.

7. Small stuff:

  • Installer has no proper icon and shows Arabic text in an English install
  • The window is big. It feels like the main thing on my screen, not a companion
  • Download for Mac is above the fold on Chrome/Windows, but only just

Good: clean, very Apple website. I even scrolled down, which I never do because I test like someone with zero patience. Easy DMG install, email-code sign-in, connecting Claude took seconds, permission dialogs flow one after another, and no trial pop-up during onboarding. Why ask about money before I've seen anything? Exactly right.

Idea: you support multiple models. I code with Claude and Codex together and bridging them is a mess. If Wakel can be that bridge and decide who does what, I'd use it every day.

YOUR QUESTIONS

Where did it surprise you?
It asked the right questions and warned me about the 10 credits before doing anything. It refused to change a Safari security setting without my OK, and offered to delete the installer instead of just deleting it. That's how an agent should behave.

Where did it ask too much?
Permissions. Each prompt is fine alone, but after Turn It All On I still got new prompts, a restart and a developer setting mid-task. That's where the magic wore off.

Where did it get stuck?
The browser, every time. Smart enough to plan it, not set up to do it.

Note: I ran macOS in a VM, so some slowness may be on my side, and I only tested in English.

from the team
Builder's replyehab

Thank you for such a thorough and honest test. We fixed what we could, and it's live now in Wakel 0.5.34 (updates arrive by themselves).
No browser: a plain message, and setup offers a Chrome download if none is installed.
Restart: Wakel reopens itself after Screen Recording is granted.
Turn it all on: now also covers a browser that is open. Safari's developer setting stays manual on purpose, because Wakel never changes browser security settings.
The "KEEP" text no longer reaches the chat.
Setup: language first, Arabic dialects only when Arabic is chosen.
Short errands no longer start on High effort. Token use is still under review.
The installer has an icon and English text, the first window is smaller, and the site's download button sits higher.
Your Claude + Codex bridge idea is on our list. Thanks again!