Stay in Visual Studio 2026
Keep Codex close to Solution Explorer, your editor, and the code you are changing.
Codex support for Visual Studio 2026
Bring the Codex AI coding agent into the IDE where your C# and .NET work already happens. iolys connects to the Codex CLI while keeping solution context, sessions, tool activity, and permissions visible in Visual Studio 2026.
Provider access
Sign in through the Codex CLI with the account and plan you already use. When your ChatGPT plan includes Codex access, iolys lets you bring that route into Visual Studio 2026 instead of requiring a separate pay-as-you-go API setup.
Codex for .NET developers
Best for: Agentic refactors, repository-wide changes, code review, debugging, and implementation work across .NET solutions.
Keep Codex close to Solution Explorer, your editor, and the code you are changing.
Switch to or from Codex without adopting another conversation interface.
Review tool calls, target files, and permission requests before sensitive work runs.
Connect Codex
Install and authenticate the Codex CLI.
Add Codex as a provider in iolys.
Choose your Codex model and start from the active Visual Studio 2026 solution.
Yes. iolys connects the Codex CLI to a provider-independent workspace built for Visual Studio 2026.
Not necessarily. The Codex CLI can use eligible account-based access; API-key options remain available when that is the route you prefer.
Yes. Provider switching is a core iolys workflow, so your Visual Studio 2026 experience remains consistent.
Keep your active solution, provider access, and development workflow.
Get iolys for Visual Studio 2026