Zademy

QoderWake and Qoder Mobile: the Qoder ecosystem grows beyond the terminal

Tools
Qoder; CLI; AI; Mobile
words words

I have been watching what the Qoder team ships for a while. It started with QoderCLI, a terminal-native coding assistant. No IDE, no extra windows, just you and the agent working directly on code.

At the end of April 2026, Alibaba launched two products that change what the ecosystem can do: QoderWake and Qoder Mobile. Neither is an extension of QoderCLI. They are new pieces, and together they make the whole thing feel like a real platform.

QoderWake: when an agent holds a position on your team

The first time I read "digital employee," I expected the usual: a chatbot wrapped in a product name with a clean dashboard. QoderWake is not that.

A Waker does not wait for questions. It has a defined role, a persona, a work area, and its own memory. It works on a schedule or responds to events. A GitHub issue gets opened, and the Waker shows up on its own, analyzes the problem, proposes a fix, and opens a PR. Nobody prompts it.

Available roles cover the common positions on a dev team: Backend Engineer, Frontend Engineer, Test Engineer, Product Manager, Data Analyst, and Content Operator. There is also a Custom mode if you want to define your own.

The interesting part is the Harness-First architecture. Each time a Waker finishes a task, it organizes what it learned into five dimensions: memory, skills, strategy, verification rules, and workflows. Context is not wiped when the task ends. It accumulates. Inside Alibaba, they report that diagnosis and repair time per issue dropped from 30 minutes to 2 minutes. That is a specific enough claim to take seriously.

The permission system is built for production, not demos. The Waker detects destructive operations, privilege escalation, and access to sensitive files, then pauses and asks for confirmation.

Installation on macOS or Linux is one line:

curl -fsSL https://qoder-ide.oss-ap-southeast-1.aliyuncs.com/qoderwake/install.sh | bash

The local console runs at http://127.0.0.1:19820/. From there you create Wakers, assign tasks, review permissions, and check history.

The Qoder team posted the official introduction on YouTube: A new member joins the Qoder family: QoderWake — official launch video.

Qoder Mobile: work keeps running even when you leave the desk

You know the problem. You kick off a long task with QoderCLI, walk into a meeting, the agent hits a point where it needs your approval, and it waits. You come back an hour later. The time is gone.

Qoder Mobile fixes exactly this. Connect the app to your active CLI session via QR code, and from your phone you can monitor status in real time, approve or reject operations, review the proposed plan before execution, and dispatch new tasks if the daemon is still running.

Connecting from QoderCLI is simple. Enable remote control mode:

qodercli remote-control

A QR code appears. Scan it with the app using the same account. Done.

One detail worth noting: the app shows the agent's thinking process, not just the final result. That is what separates it from chat-based tools. You see what the agent is doing in real time, decide whether it is on track, and step in or confirm. The control is real.

The official Qoder channel posted a full walkthrough: Qoder Now Supports Remote Control — official demo of Qoder Mobile phone-based CLI control.

What changes when all three work together

QoderCLI is the engine. QoderWake gives you agents that operate in defined roles with real autonomy. Qoder Mobile is the control point that travels with you.

Without Qoder Mobile, long CLI processes require you to sit at the screen. Without QoderWake, every task requires you to initiate, guide, and wait. Put them together and work can run without you being chained to it.

The point of this launch is not any single feature. It is that the ecosystem now has a shape: terminal, persistent agents, and mobile control. That is genuinely different from an autocomplete assistant with a catchy name.

If you work on projects with long cycles, frequent code reviews, or distributed teams, QoderWake and Qoder Mobile are worth a look.

Resources: