Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Access to local Android devices

Open
#4,168 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, github-actions

Research direction

Look at how self-hosted runners are configured in the GitHub Copilot app codebase, particularly around resource permissions and ADB integration. Investigate existing Android testing workflows and cloud agent architectures. Determine what 'minimal permission runners for specified resources' entails and how local device access can be securely exposed to cloud agents.

Written by the indexing model from the issue text.

Description

triage
Feature summary

I want to access local Android devices connected via ADB through cloud.

What problem are you trying to solve?

Developing on Android requires testing on actual hardware. I can do this in CLI via adb, but having a way to do so for cloud agents is nice.
I am thinking of connecting self-hosted runners, but setup is complex.
Accessing local resources for some test should be common to other dev workflows, so it would be nice if GitHub Copilot App can facilitate it.

Proposed solution

You already have self hosted runners for various OSs. Maybe the app can setup minimal permission runners for specified resouces.

Workflow impact

Android developers. Things like MS Teams integration also requies cloud agents, so enabling local resource access for cloud agents would help those.

Installation context

No response

Additional context

No response

Dominant language
No language data
Stars
2.1k
Forks
157
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/app

All issues in github/app

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.