Build your own GitHub Copilot.

# Build an original app inspired by GitHub Copilot

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Desktop. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original VS Code coding-assistant extension called Codeglide, inspired by GitHub Copilot’s editor assistance. Developers request an inline suggestion or ask about selected code, review a proposed edit, and choose whether to apply it. Use a configured model provider; the project does not recreate a foundation model or GitHub’s service.

## Design
Use VS Code’s established extension surfaces with an original icon and name, subtle inline ghost text, a readable chat webview, and a reviewable diff. Clearly show the active model, context being sent, request state, and costs when the provider reports them. Applying edits must always be an explicit action.

## Features
1. Provider setup: configure one supported provider and model with credentials in VS Code SecretStorage or a private server broker. Show missing-configuration errors and never commit or log keys.

2. Inline suggestions: debounce requests for the current cursor context, cancel superseded requests, and show a completion only if the document version and cursor still match. Respect accept/dismiss actions and a disable switch.

3. Selected-code chat: send only a selected range and explicitly included context, stream a response, and safely render code/Markdown in a restricted webview. Make the transmitted file list inspectable before broadening context.

4. Reviewed edits: request a bounded replacement, preview it as a diff, and apply only if the original document version is unchanged. Preserve undo and reject path traversal or edits outside the chosen workspace.

5. Limits and controls: honor excluded files and workspace trust, cap context and concurrent requests, support cancellation and rate-limit errors, and provide an opt-out from content retention or telemetry.

## Tech stack
Use TypeScript and the current official VS Code extension, inline-completion, webview, and WorkspaceEdit APIs. Use the selected model provider’s current SDK over an abortable request. Keep extension packaging reproducible and run integration checks in the VS Code Extension Development Host.

## Data & behavior
ExtensionSettings {provider, model, enabled, exclusions}; SecretStorage credential references; Request {documentUri, documentVersion, selection, contextManifest, state}; ProposedEdit {baseVersion, range, replacement}; optional local ChatSession. Do not persist source text or prompts without explicit settings.

Acceptance checks and scope:
Test delayed completions after typing, cancelled streams, excluded secret files, untrusted workspaces, stale diffs, malicious webview Markdown, provider failures, and applying/undoing an edit in the actual extension host. Exclude autonomous shell execution, background repository uploads, model training, and claims of compatibility with Copilot subscriptions.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.