Wingware
Wing Tips: Introducing AI Agents in Wing Pro 12
Wing Pro 12 integrates your choice of AI coding agent: Claude Code, Codex, Antigravity, Copilot, Cursor, goose, OpenCode, or any other agent that supports the Agent Client Protocol. You can use Wing to queue agent requests, manage their execution, and review and audit each completed task before committing changes. Wing also gives the agent tools for code analysis, unit testing, debugging, and version control, in a way that reduces both elapsed time and token use.
This Wing Tip is part of a series of Wing Tips on working with AI agents in Wing.
Shown above: The Tasks Manager running three queues on the Tasks tool's Execute tab, beside one queue's session in the AI Agent tool.
Setup
To get started:
- Install or upgrade to Wing Pro 12.
- Install the agent you want to use, and get an account or API key for it if you don't already have one. Setting Up an AI Agent lists what each agent needs. For sustained use, a subscription is generally much cheaper than paying for usage on an API key.
- From the Project menu, choose New Project, check Set Up for AI Agent, choose your agent, enable the autonomous task manager for easier implementation workflow, and select an existing or new directory and Python environment. If you already have a Wing project, just open it and choose Set Up for AI Agent from the Project menu.
- Set your new or existing project up in a revision control repository. You can use an agent without it, but Wing's task review features won't work. Even a local git repository (in the same directory as your sources) will work. Ask the agent for help with setup.
Your First Session
Type a request into the AI Agent tool and press Enter -- or add it as a task in the Tasks tool, which queues the work and lets you review it before committing. For example:
- "Can you write, run, and fix unit tests for the new user registration dialog?"
- "Let's change how this works so it uses a .jsonl file instead."
- "Find out why the dashboard sometimes shows yesterday's data, and propose a fix."
The agent reads the relevant files, makes edits, and reports back.
Shown above: Choosing a queue for a task from its Q menu, which also sets the run mode (such as Plan).
If the result isn't quite right, follow up in the same session -- for example "good, but please add a regression test that would have caught this". The agent has the context of the previous turn and refines accordingly.
Where to Next
Once you are comfortable working with one agent, you can turn on the Tasks Manager to have agents carry out a series of tasks on their own, while you write tasks, answer questions, look over the problems agents find in the Plan tab's Incoming view, and review the results. When to take that step is up to you. See the Wing Tip on autonomous development for how to get started.
The other Wing Tips in this series look more closely at:
- The Tasks tool as a way to manage one or more AI agents.
- Autonomous development with the Tasks Manager.
- Reviewing and accepting the agent's edits.
- Using unit tests to keep code quality high and simplify the review process.
- Fixing code warnings with the agent, in place or in bulk.
- Best practices for getting reliable results.
Beyond the Tasks tool, Wing also offers one-click FIX actions for exceptions, failing tests, and code warnings, plus AI actions in the editor to explain, review, or optimize code -- see Autonomous Development with AI Agents for the full picture.
Further Reading
Wing's AI agent integration has a lot of features, but you don't need to understand all of them to get started. When in doubt, ask the agent!
See also Autonomous Development with AI Agents and AI Agent-Assisted Development in Wing's documentation.
That's it for now! Next time we'll take a closer look at the Tasks tool.
As always, please don't hesitate to email support@wingware.com if you run into problems or have any questions.