Question 1

How do I authenticate Voxy with GitHub?

Accepted Answer

GitHub uses Bearer token. You generate the credential in the GitHub dashboard and store it as a vault reference; Voxy never holds the literal secret and never sends it to the browser. The credential is attached server-side when a confirmed action runs.

Question 2

What can I do in GitHub by voice?

Accepted Answer

This page exposes 6 GitHub actions generated from its OpenAPI spec: createIssue, createPullRequest, mergePullRequest, createRelease, getRepo, deleteRepo. For example, you can say things like “create an issue with owner <owner> and repo acme/web”.

Question 3

Which GitHub actions need confirmation?

Accepted Answer

3 of the 6 actions are classified destructive or costly and are gated behind a deliberate click: mergePullRequest, createRelease, deleteRepo. Voxy shows a read-back of exactly what it will do, and nothing runs until you click confirm.

Question 4

Is operating GitHub by voice safe?

Accepted Answer

Yes — safety is the whole point. A spoken word never executes a destructive action. Every irreversible or costly GitHub call (like mergePullRequest) requires an explicit on-screen confirmation, and destructive detection runs at 100% recall, so nothing dangerous is silently executed.

Question 5

Do I need a GitHub API key to try the demo?

Accepted Answer

No. The demo on this page is parse-only: it understands your command, shows the parsed call and read-back, and stops at the gate. It never calls GitHub and needs no keys. A key is only required when you wire Voxy to your live GitHub account.

Question 6

Does Voxy change my GitHub setup or require code?

Accepted Answer

No code and no changes to GitHub. Voxy reads the GitHub OpenAPI spec to generate the voice layer; you keep using GitHub exactly as before and add a safe voice/natural-language way to run these actions.

Action	Endpoint	Class	Why	Blast radius
`createIssue`	`POST /repos/{owner}/{repo}/issues`	read-only	read-only — safe to run without a gate	No side effect. Read-only.
`createPullRequest`	`POST /repos/{owner}/{repo}/pulls`	read-only	read-only — safe to run without a gate	No side effect. Read-only.
`mergePullRequest`	`PUT /repos/{owner}/{repo}/pulls/{pull_number}/merge`	⚠ destructive	irreversible/costly action: “merge”	Irreversible or costly side effect.
`createRelease`	`POST /repos/{owner}/{repo}/releases`	⚠ destructive	irreversible/costly action: “release”	Irreversible or costly side effect.
`getRepo`	`GET /repos/{owner}/{repo}`	read-only	read-only — safe to run without a gate	No side effect. Read-only.
`deleteRepo`	`DELETE /repos/{owner}/{repo}`	⚠ destructive	irreversible: HTTP DELETE	Permanently removes the resource.

Scheme	`Bearer token`
Header	`Authorization: Bearer <token>`
Where to get it	Create a token / API key in the API's dashboard, then store it in your vault.
How Voxy stores it	As a vault reference (`keyring:voxy/github`) — never the literal secret. The gate and execution run server-side; the secret never reaches the client.

Make GitHub voiceable.

What you can say to GitHub.

Every write, classified.

Connecting to GitHub.

Questions about GitHub by voice.

Give GitHub a voice.
Keep the safety.