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

Add typed AuthError variants once the runtime distinguishes auth-missing/invalid/unreachable

Open
#1,209 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
rust

Research direction

This work is blocked on github/copilot-agent-runtime#7485; start by reading that runtime issue and locating the SDK's existing Error/Rpc mapping, since no SDK file is named here. Once distinct wire codes exist, map them to AuthErrorKind and preserve unknown codes as Rpc, then verify src-tauri/src/error.rs:115-120 and handlers/auth.rs::emit_copilot_cli_auth_issue no longer require string matching or the connectivity workaround.

Written by the indexing model from the issue text.

Description

enhancement

Context

Companion to github/copilot-agent-runtime#7485 — the runtime today returns identical generic -32603 internal_error payloads for "no token," "invalid token," and "network unreachable." Once the runtime adds distinct codes (e.g., -32001 AuthMissing, -32002 AuthInvalid, -32003 AuthUnreachable), the SDK should expose them as a typed enum so consumers don't string-match.

Proposed shape

pub enum Error {
    Rpc { code: i32, message: String, data: Option<Value> },
    // ...
    Auth(AuthErrorKind),  // new
}

pub enum AuthErrorKind {
    /// No token configured. User needs to sign in.
    Missing,
    /// Token rejected by CAPI (401/403). User needs to reauth.
    Invalid,
    /// Transport failure talking to CAPI. Retry, don't reauth.
    Unreachable { cause: String },
}

The SDK can map known runtime codes to Error::Auth(...) and leave anything else as Error::Rpc { ... }.

What this lets consumers delete

In Copilot Desktop today (src-tauri/src/error.rs:115-120) we string-match three magic phrases:

pub fn is_copilot_auth_failure(&self) -> bool {
    let message = self.to_string().to_ascii_lowercase();
    message.contains("not authenticated")
        || message.contains("authenticate first")
        || message.contains("no authentication info available")
}

Plus the connectivity-tracker workaround in handlers/auth.rs::emit_copilot_cli_auth_issue whose only job is to second-guess whether the runtime's "not authenticated" really means "not authenticated" or "couldn't reach the auth service." Both go away with typed variants.

Dependencies

Blocked on the runtime change (github/copilot-agent-runtime#7485). No useful SDK work to land before the runtime distinguishes the cases on the wire.


  Generated via Copilot (Claude Opus 4.7) on behalf of @tclem

Dominant language
Java
Stars
10.5k
Forks
1.5k
Avg merge
1d 9h
Merged PRs (30d)
130

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/copilot-sdk

All issues in github/copilot-sdk

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.