Free FoneClaw and Free Local YouTube Downloader Plugin for Android

What the Free Local FoneClaw YouTube Downloader Plugin Can Do Today

The direct answer is simple: FoneClaw is free, and the FoneClaw YouTube downloader plugin is a completely free local plugin tool for supported Android workflows. The plugin does not upload the YouTube URL to FoneClaw services. It is a plugin, not one of FoneClaw's built-in Android tools, and it gives FoneClaw a YouTube download workflow through a separate plugin package with its own tool surface: video info, download, status, and cancel.

There are two supported ways to start. You can share a supported YouTube video link from the YouTube app to FoneClaw, or you can type or paste the video URL directly into FoneClaw. In both cases, FoneClaw recognizes the URL, uses the local plugin to inspect public metadata and available formats, asks you to choose the desired option, asks for approval before the consequential download action, then starts and tracks the job. When we say automatic download in this workflow, we mean FoneClaw carries out those steps after the required choice and approval; it never means bypassing the user's format choice or approval.

The current validated workflow, based on the FoneClaw Android repository, covers signed package trust, exact format selection, explicit approval, a returned jobId, foreground execution, duplicate prevention, and 360p delivery through Android MediaStore. That is a concrete path, not a promise that every YouTube format, device, network condition, or storage behavior is already validated. Network access and mobile data use still depend on your connection and carrier plan.

Use the plugin only for videos or audio you are permitted to download, such as your own content, content with the right license, or material where you have clear permission. This article is about downloading. If your goal is playback, search, or hands-free control inside YouTube rather than saving a file, YouTube Voice Control on Android: Search, Play, and Hands-Free Actions keeps that playback intent separate from the downloader plugin workflow.

Install the Signed Plugin Through the Trusted Package Flow

Installing a downloader should begin with trust, not convenience. The validated path uses a signed GitHub-delivered package and a trusted fingerprint flow. In plain Android terms, the package identity is checked before the plugin is trusted, and installation is separate from plugin registration. A file being hosted on GitHub is not the trust decision by itself; the trusted package flow is the trust decision.

The user should see a visible plugin proposal before installation. That proposal should identify the plugin, its source, the package to install, and the expected fingerprint or trust signal. After the user accepts the proposal and the package is installed, FoneClaw still needs the plugin to register its tools before those tools are ready to use. That separation is important because a package can be installed without every tool being enabled for execution.

The plugin remains a local tool path after installation. The YouTube URL is handled by the plugin workflow on the device rather than uploaded to FoneClaw services. FoneClaw may use the free default model or a configured compatible model to understand the user's request, but the downloader work is carried by the plugin after trust, tool policy, choice, and approval are satisfied.

For plugin and skill security, the useful mental model is: source, signature, registration, tool policy, and user approval are different checkpoints. Skipping one checkpoint makes troubleshooting and trust harder. Readers who want the broader permission and package-control model can use AI Agent Skill Security Needs Phone Permission Checks, which covers skill and plugin trust beyond this YouTube-specific walkthrough.

A practical install sequence should look like this:

1. Open FoneClaw and review the YouTube downloader plugin proposal.
2. Confirm the signed package source and trusted fingerprint flow.
3. Approve installation only after the package identity matches the expected trust signal.
4. Wait for plugin registration, not just package installation.
5. Inspect the available plugin tools before starting any download.

That is the only numbered workflow in this guide because each later section owns one state transition: inspect, approve, track, cancel, and verify the result.

Inspect Public Metadata and Choose an Exact Available Format

Before any file operation, use the read-only info tool. The plugin_youtube_video_info tool is LOW risk and AUTO approval. It returns public metadata and available format choices without creating a file, using the local plugin workflow rather than uploading the YouTube URL to FoneClaw services. That first step keeps the workflow transparent: the user can confirm the title, duration, available options, and intended format before approving anything that writes data to the device.

Format choice should be exact. The downloader flow is designed around selected formats, not a vague request such as "download the best one" followed by a silent downgrade. If a format is unavailable, the right behavior is to choose from available options or stop. That matters because video, audio, quality, file size, and storage expectations are all user decisions.

A useful format review should answer four questions. Do you want video or audio? Which listed quality or format is actually available? Is the expected file size reasonable for mobile data and device storage? Is the content something you are permitted to download? The metadata step gives the user enough context to answer those questions before any external-effect action begins.

Start the Selected Download With Explicit Approval

The download itself is the action boundary. plugin_youtube_download is classified as EXTERNAL_EFFECT and REQUIRE_APPROVAL because it creates a device effect: it starts a file operation, uses network and storage resources, and may continue in the background. The user should see the selected format and the intended action before FoneClaw starts the job.

Approval should be specific. It should not be a broad permission to download anything from YouTube. The user approves this video, this selected format, this plugin tool, and this job. The tool uses the exact selected format without silent downgrade. If the requested format cannot be used, the workflow should make that visible instead of switching quality without the user's knowledge.

When the job starts successfully, the plugin returns a jobId. That jobId is the handle for status checks, diagnostics, and cancellation. It also makes the audit boundary clearer: the system can connect the user's approval to the specific background job that was started.

The validated flow uses foreground execution, which matters on Android. A foreground service gives the running download a visible system presence and reduces the chance that users mistake a background transfer for an invisible action. The flow also prevents duplicate jobs, so repeated taps or repeated agent attempts do not casually create multiple copies of the same download.

The workflow can feel automatic after approval because FoneClaw continues the task: it starts the selected job, tracks progress with the jobId, and lets the user check status. That is different from skipping approval. The user still chooses the desired option and approves the consequential action before the plugin begins the download.

For approval and evidence at tool boundaries, AI Agent Identity, Permissions, and Audit Trails for Phone Tool Governance explains why download and cancel carry different policies. The important point for this plugin is practical: metadata lookup can be automatic, but creating or stopping a device-side job deserves a clear decision.

Track, Cancel, and Diagnose a Download Job

Once a job starts, the jobId becomes the user's control handle. plugin_youtube_download_status is LOW risk and AUTO approval because it checks job state rather than changing the device. It can distinguish states such as queued, running, completed, failed, or canceled when the job data is available. That status step should be the first response when the user asks, "Is it done?" or "What happened to my download?"

Cancellation is a different kind of action. plugin_youtube_download_cancel is DEVICE_CONTROL and REQUIRE_APPROVAL because it changes the state of a running job. The user should confirm which jobId is being canceled, especially if more than one download has been started over time. Cancellation should target the known job, not a vague recent action.

Recovery needs realistic expectations. A canceled job may stop the active transfer, but cancellation and recovery need broader validation across devices. A canceled job does not guarantee that every partial artifact is removed in every storage state. A failed job does not prove the plugin is broken; it may reflect network conditions, unavailable format, storage constraints, permission state, or platform behavior.

A practical diagnostic flow is compact. Check the jobId. Read status. If queued, wait or verify network. If running, continue monitoring or approve cancellation. If completed, inspect the delivered file. If failed, review the selected format, network, storage, and permission state. If canceled, check whether any visible partial item needs user cleanup. That gives the user control without pretending every failure can be undone automatically.

Current File Delivery and What Still Needs Validation

The current validated delivery path includes 360p output through Android MediaStore. That is the precise boundary to carry forward: validated 360p MediaStore delivery, not universal support for every resolution, audio-only option, codec, file container, device, Android version, or storage layout.

MediaStore matters because it is Android's system-indexed media path. A successful validated delivery can appear through Android media handling rather than a hidden plugin-only folder. This guide does not invent a storage folder or promise identical file visibility across every gallery, file manager, or media app. The result should be verified on the device after completion.

Several areas remain broader validation topics. Available formats may vary by video. Cancellation recovery needs device and storage-state testing. Storage behavior can differ by Android version and media app. The device matrix can affect foreground execution, battery handling, and file visibility. Rights and license validation also remain a user responsibility; the plugin workflow can show choices and enforce approval boundaries, but it does not decide content rights for the user.

If your broader interest is how local Android tools fit into phone-agent work, the adjacent topic is local execution rather than this plugin alone. The FoneClaw product model keeps plugins, built-in tools, model reasoning, and Android effects distinct so users can inspect which layer is doing the work.

Use the Plugin Lawfully and With Clear User Control

Convenience should follow permission, rights, and user control. YouTube content is governed by platform terms and applicable rights. The YouTube Terms of Service should be considered alongside copyright, creator permission, local law, and the user's own rights to the content. Use the plugin for content you are permitted to download, and avoid protected or unauthorized material.

Before starting a download, verify the source video, selected format, expected size, network condition, and storage availability. During the job, keep the jobId available so status and cancellation can target the correct transfer. After completion, check the delivered file in Android media handling rather than assuming the transfer produced the expected result. FoneClaw and the plugin are free, while network usage, mobile data, and device storage still remain part of the user's Android environment.

FoneClaw can use the free default model or a configured compatible model to drive the agent conversation and planning. The plugin executes the YouTube-specific work after trust, tool policy, user choice, and approval gates are satisfied. That separation keeps the workflow clear: model reasoning helps choose the next step, the plugin performs its defined task locally, and Android shows the resulting file or job state.

For adjacent YouTube handling that does not involve saving a file, YouTube Voice Control on Android: Search, Play, and Hands-Free Actions is the related task guide. This page stays focused on the FoneClaw YouTube downloader plugin, its approval boundaries, and the current validation limits.