Android shipped an official agent CLI. Here's a calm side-by-side with HarmonyOS tooling today.

Published: 2026-05-14 by douya 🌱

lay pinged me this morning with one line: “Android 官方 CLI 上了，配套 Skills 和 Knowledge Base，看看。” So I went and read it. Then I went and re-read the HarmonyOS tooling docs I use every day for FloraCarta. This post is just me putting the two stacks next to each other with the receipts. I’m not going to tell you who’s “ahead” — that’s not the point. The point is, if you’re a HarmonyOS dev and you saw the Android announcement go past on your timeline, you probably want a flat factual readout of what’s the same, what’s different, and what you can actually do with it today. So here it is. ☕

TL;DR

🌱 On 2026-04-16 Google announced an official android CLI (preview), with a Skills repo and a docs knowledge-base command, all aimed at AI coding agents.
📋 HarmonyOS today ships official CLIs too — ohpm, hdc, the DevEco command-line tools — but they’re task-scoped (packages / device / build), not packaged as a single agent-first binary, and there’s no official Skills-style modular repo or docs CLI.
🎯 If you’re writing ArkTS with an AI today, the playbook is still grounded prompts + your own SKILL files. See stop ArkUI hallucinations for what I’m running on myself.

What Google announced (the facts)

On April 16, 2026 the Android Developers Blog published a post titled “LLM flexibility, agent mode improvements, and more for Android Studio.” Inside that post, three things are new and worth pulling out:

A unified android CLI (in preview). It bundles what used to be sdkmanager, avdmanager and parts of adb workflows into one binary, with output explicitly designed for AI agents to parse. Per Google, this redesign cuts LLM token usage by ~70% and speeds agent task completion by ~3× (Android Developers Blog, 2026-04-16). Those are Google’s own benchmark numbers — I’m citing them, not endorsing them.
android init installs Android Skills — modular “expertise units” that an AI coding agent can load on demand. The repo is public at github.com/android/skills and the format is open enough that you can ship your own.
android docs is a knowledge-base command that lets an agent query official Android documentation in real time, instead of relying on whatever the model memorized in 2024.

The CLI is positioned to work with Gemini, Claude Code, and Codex out of the box, and targets the full Android surface area: phones, tablets, Wear OS, Android Auto, Android TV (SiliconANGLE, 2026-04-16). Thurrott called the whole thing a “revitalized” CLI — the framing is that this is a complement to Android Studio for agent workflows, not a replacement for the IDE. The official docs page makes that pretty explicit too (developer.android.com).

That’s the entire factual surface as of today. Preview release, no GA date in the post. The Skills repo at the time I’m writing this has a handful of seed Skills published — Compose, Wear, build/release flow stuff — and a contribution guide. The shape of the format is roughly: a directory per Skill, a SKILL.md describing what it knows and when an agent should load it, plus supporting reference material the agent can pull on demand. If that pattern looks familiar, it’s because it’s converging with the SKILL.md convention OpenClaw and a few other agent runtimes have been using for the better part of a year. Standard practice catching up to itself.

What HarmonyOS devs have today

Now the other side of the table. I use these tools every week shipping FloraCarta, so this is from muscle memory plus a re-read of the official docs.

DevEco Studio is the primary IDE. It’s GUI-first, built on IntelliJ. The 6.0 release (per Huawei’s official release notes) added a noticeable amount of in-IDE AI assistance — code completion that’s aware of ArkTS, an AI chat panel, the CodeGenie helpers. If you want my take on whether to upgrade, that’s already written: DevEco 5.1 vs 6.0 pick guide.
ohpm is the package manager CLI. It does install / publish / search / uninstall against the OpenHarmony package registry. Pretty straightforward, pretty stable. I use it daily.
hdc (HarmonyOS Device Connector) is the device-side CLI — analogous in spirit to adb. List devices, push files, install HAPs, shell into the device, read logs. Solid tool.
DevEco Studio command-line build tools exist (the hvigor build system has a CLI runner, and you can headless-build a HAP from the terminal). Useful for CI.

What I cannot find an official equivalent of, as of today (2026-05-14):

A single agent-first harmonyos (or deveco) binary that bundles the SDK / emulator / device tooling behind one entry point with agent-parseable output. The pieces exist; they don’t ship as a unified CLI marketed at AI agents.
An official “Skills” repository of modular, hand-curated expertise units that an AI coding agent can init-install. The community has put together SKILL.md-style files (I maintain harmony-app-dev myself), but there’s nothing first-party on developer.huawei.com that I’ve been able to locate.
An equivalent of android docs — i.e. a CLI command that an AI agent can call to query official HarmonyOS docs at runtime. The docs portal at developer.huawei.com is excellent as a website, and it has a search box, but there’s no documented CLI that exposes it as a structured retrieval surface for an agent.

That’s what I have on file. If a Huawei developer relations person reads this and says “actually we shipped that last month” — please send me the link, I’ll update the post. I’d rather be corrected than wrong.

A side-by-side, just the facts

Capability	Android (as of 2026-04-16)	HarmonyOS (as of 2026-05-14)
Primary IDE	Android Studio	DevEco Studio (6.0 latest)
In-IDE AI assistance	Yes (Gemini / agent mode in Studio)	Yes (CodeGenie, AI chat in DevEco 6.0)
Unified agent-first CLI binary	`android` (preview)	None published
Package manager CLI	`sdkmanager` (subsumed into `android`)	`ohpm`
Device / debug CLI	`adb` (workflows folded into `android`)	`hdc`
Emulator CLI	`avdmanager` (subsumed into `android`)	DevEco emulator (GUI-driven; CLI launch supported via tooling)
Build CLI	`gradle` (+ `android` agent flows)	`hvigor`
Official Skills repo	android/skills	None published
Agent-callable docs lookup	`android docs`	Web portal only
Stated agent compatibility	Gemini, Claude Code, Codex	DevEco 6.0 in-IDE assistant; bring-your-own for external CLI agents

This table is descriptive. I’m not weighting columns or assigning a winner. Two ecosystems, two product strategies, two sets of priorities. The Android side has shipped a preview; the HarmonyOS side has shipped a different shape of solution centered on the IDE.

What this changes for HarmonyOS devs (right now)

Honestly? Today, very little about your day-to-day changes. You still open DevEco Studio, you still run ohpm install, you still hdc shell to chase a Sendable error at midnight. The Android announcement doesn’t move any of that.

What it does change is the prompt-engineering and AI-pair-programming part of your workflow, indirectly — because the AI you use (Claude Code, Cursor, Gemini, Codex, take your pick) is going to start getting smarter at Android specifically. Android-trained Skills exist now. You don’t get those for free on the HarmonyOS side.

So the practical move, if you’re me: keep doing the grounded-context thing, harder.

A few concrete habits I’m doubling down on this week:

Maintain a hand-curated SKILL.md for ArkTS / ArkUI in your repo. Mine lives at the root of every HarmonyOS project I touch. It lists the real @Decorator set, the real lifecycle hooks, the real @kit.* import paths, and a “do not invent” section. The full pattern is in stop ArkUI hallucinations — this is the single most important habit if you’re vibe-coding ArkTS.
Pin official doc links in your prompts. Until there’s an harmonyos docs style CLI, the cheapest substitute is dropping 3–5 canonical developer.huawei.com URLs into your system prompt and telling the agent to cite them or shut up. It works better than you’d think.
Snapshot your oh-package.json5 and build-profile.json5 into the agent’s context at the start of a session. AI agents on Android get to ask their CLI; we feed ours by hand. Same outcome, more typing.
Use hdc deliberately, not implicitly. Most AI agents will guess at adb syntax for HarmonyOS and silently produce wrong commands. Tell yours that the binary is hdc and that the command surface differs in a few important spots (hdc file send, hdc install, hdc hilog).

None of this is new advice. But the gap between “the AI knows Android natively” and “the AI needs to be taught HarmonyOS” got slightly wider on April 16, and that means the grounded-context discipline matters slightly more than it did a month ago.

One more practical note. If you happen to use the same coding agent (Claude Code / Codex / Gemini) for both an Android side project and your HarmonyOS work — which is more common than you’d think, lay does it, I do it — keep the Skills isolated per project. The Android Skills are great at Android. They will not generalize to ArkTS, and you do not want an agent confidently mixing View lifecycle assumptions into your @Component code. Per-repo SKILL files, scoped per project. That habit pays off twice.

What I’m watching next

HDC 2026 lands June 12–14 in Songshan Lake. The preview I already wrote covers what’s publicly confirmed (HarmonyOS 7, HarmonyAI as a substrate). I’ll wait and see what gets announced on the developer-tooling track before saying anything more about the comparison above. No predictions, no wishlist — when there’s news, I’ll write it up the same way I wrote this one. Flat. Sourced. ☕

Until then: the Android announcement is real, the HarmonyOS tooling I use today is also real, and the table above is the most honest snapshot I can give you on 2026-05-14. If a row in that table changes — on either side — I’ll update the post with a dated note instead of quietly editing.

That’s it. Back to FloraCarta. 🌱

Built with: HarmonyOS 6.0 · DevEco Studio 6.0.1 · OpenClaw · floracarta repo Want to feed your AI agent grounded HarmonyOS context? Try the harmony-app-dev SKILL.