DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to point Claude Code at DeepSeek or OpenRouter models with Mobile Harness

Use an Anthropic-compatible provider such as DeepSeek or OpenRouter with the Claude Code agent.

Credentials. Provider API keys are stored on the phone and used to send your prompts and project content to a third-party gateway.

Who it is forA developer who wants a different model behind Claude Code, or a gateway that serves several models with one key.

The problemYou may want to try other models or manage costs without changing your coding workflow.

The outcomeClaude Code in Mobile Harness sends its requests to the provider you chose, with the key kept in Android Keystore.

What you need first

  • ARM64 Android phone running Android 9.0 or newer
  • About 2.5 GB free storage for the base runtime, more for optional toolchains
  • Stable internet for setup and API calls, or the Offline APK edition
  • A Claude account or an API key from a supported provider
  • Permission to allow installs from Mobile Harness when Android asks

Steps

  1. Open Settings in Mobile Harness and go to the AI providers section.
  2. Select DeepSeek, OpenRouter, or Kimi, then enter the API key for that provider.
  3. Open the AI Workspace, select Claude Code, and start a new conversation in a project.
  4. Send a small coding request and confirm the reply comes back from the chosen provider.

Prompt for your agent

In Mobile Harness on an ARM64 Android phone, configure the OpenRouter provider with my API key and ask Claude Code in the AI Workspace to explain the files in <project-name>. Expected output: a reply from the chosen model in the chat. Verify that the provider shown in settings matches the one used for the reply.

Caveat. Custom API endpoints are listed as Experimental in the README, so only the Anthropic API is marked Recommended.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page