One Week, Two Platforms, 74 Commits

February 18, 2026. A Tuesday. By the following Monday, we’d pushed 74 commits across two repositories, shipped two major version bumps, added an entirely new platform, and introduced a cloud/local architecture that changed how the desktop app works.

None of this was planned as a single sprint. It just happened.

The mobile story: iOS in four days

LikeClaw Mobile had been Android-only since launch. The Flutter codebase was theoretically cross-platform, but “theoretically” is doing a lot of heavy lifting in that sentence. iOS needs provisioning profiles, a different billing system, platform-specific sign-in, and a bundle ID that Apple actually approves.

On Friday, Feb 21, the iOS platform support branch merged. 36 commits in the mobile repo that week. The highlights:

• Apple Sign-In with a post-login email linking flow. Apple doesn’t always share your real email, so we built a screen that lets you link one for cross-platform access. It’s skippable, but we warn you.
• Apple Store in-app purchases mirroring the existing Google Play billing. The billing screen detects your platform and uses the right service. Android flow didn’t change at all.
• New app icons and bundle ID — ai.likeclaw.mobile instead of the old development identifier.
• Font sizes and line spacing reworked for better readability across both platforms.
• API migration from the legacy likeclaw.aiwayz.com domain to api.likeclaw.ai.

The version went from 1.1.1 to 1.1.4 in seven days. Three version bumps. Each one a releasable build.

The desktop story: cloud meets local

The desktop app had a bigger architectural shift. Until this week, it was local-only — your machine, your API keys, your agents. That changed on Wednesday, Feb 19, when the cloud/local mode infrastructure landed.

38 commits in the desktop repo. One day alone — February 19 — had over 30 of them. Here’s what shipped:

• Authentication using the dashboard-v2 auth system (email + 6-digit code, JWT tokens).
• Cloud/local toggle in the header. Cloud mode routes sessions through our server API. Local mode runs agents on your machine with OpenRouter.
• Workspace file sync between local and cloud storage.
• Background task cards with live polling, showing agent work in real-time.
• VFS file browser — a virtual filesystem panel for browsing, uploading, and sharing files.
• Interactive questionnaire tool — agents can now ask structured questions during local mode sessions.
• Unified model selection — same model picker works in both cloud and local modes.
• Remote tool proxy — cloud-only tools like web search are now available in local mode through a server proxy.
• Space-themed dark mode redesign with new gradient backgrounds and sidebar styling.
• Bash tool for local mode command execution, complete with a terminal-style UI.
• macOS notarization through a custom process.

Version 0.3.0 shipped on Friday with all of it.

The shared pieces

Some changes landed in both repos simultaneously:

Skills catalog. Both mobile and desktop got a browsable skills catalog with download counts and star ratings on each skill card. The “Add to workspace” button works the same way on both platforms. Mobile initially had a more complex flow and simplified it to match desktop by Sunday.

API migration. Both apps moved from the old likeclaw.aiwayz.com endpoint to api.likeclaw.ai. On desktop, the app auto-migrates your saved server URL on startup. On mobile, the default was updated in the environment config.

Claude writing code. Nearly every commit in both repos this week includes Co-Authored-By: Claude Opus 4.6. We’re using our own agents to build the product they run on. The mobile repo also added a Claude Code GitHub Actions workflow — Claude now picks up issues, writes fixes, and opens PRs automatically.

What we learned

Parallel shipping is possible when the backend is shared. Mobile and desktop are separate codebases with separate teams, but they talk to the same API. When the API is stable, both can move independently without stepping on each other.

Platform-specific work is the bottleneck. The actual features — skills catalog, billing, auth — took a day or two each. Apple provisioning profiles, notarization, and store review are what ate the rest of the time. The code was ready before the platforms were.

30 commits in a day sounds chaotic. It wasn’t. Each commit was small, focused, and independently deployable. The cloud mode infrastructure on desktop was built as a stack of incremental changes — auth first, then session management, then workspaces, then tools. Each commit worked on its own.

The next week will be quieter. Stabilization, bug fixes, and getting the iOS build through Apple review. But the foundation is in place: LikeClaw runs on Android, iOS, macOS, and the web. Same agents, same skills, same sandbox. Four surfaces, one platform.