René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Support interactive input variables (${input:...}) for plugins in GitHub Copilot CLI","articleBody":"### Describe the feature or problem you'd like to solve\n\nGitHub Copilot CLI currently has no support for interactive input variables (for example, ${input:...} in .mcp.json). This makes it difficult for plugins to securely prompt users for values such as API keys, URLs, or other configuration at runtime, reducing compatibility with existing MCP configurations.\n\n### Proposed solution\n\nIntroduce an interactive input mechanism for Copilot CLI similar to VS Code's ${input:...} support.\n\n- Support resolving ${input:...} variables when a Copilot CLI session starts, prompting the user for required values.\n\n- Provide a dedicated CLI configuration section (similar to Claude Code's userConfig https://code.claude.com/docs/en/plugins-reference#user-configuration) where plugins can declare user-configurable parameters that are prompted interactively and made available during execution.\n\nFor example:\n\n```json\n{\n  \"inputs\": [\n    {\n      \"id\": \"github_token\",\n      \"type\": \"password\",\n      \"description\": \"GitHub Personal Access Token\"\n    }\n  ]\n}\n\n```\n\n### Example prompts or workflows\n\n_No response_\n\n### Additional context\n\n_No response_","author":{"url":"https://github.com/Sozhan308","@type":"Person","name":"Sozhan308"},"datePublished":"2026-07-07T05:39:52.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/4042/copilot-cli/issues/4042"}