AIWG 2026.10.19 - Give your Flue app AIWG skills and a code reviewer

“Add AIWG to my Flue app and give it a code reviewer.” AIWG now works inside Flue apps, so your app can find a skill, ask a specialist for help and save the result in your project's AIWG folder, such as `.aiwg/reviews/`.

aiwg use sdlc --provider flue

Put AIWG into your app

Run that command from your Flue app directory. Your app gets AIWG skills, project context in `AGENTS.md`, tools for finding and reading AIWG guidance and saving artifacts, and two built-in helpers: Code Reviewer and Test Engineer. The helpers use your app's model unless you choose another one.

Start with the Node example. It shows how to connect the generated tools and specialists to an app. Deploy AIWG before starting the example, then give the running app a concrete request: “Review this change, ask Code Reviewer to check it, and save the review.” The review is saved in the project's AIWG folder, at `.aiwg/reviews/example.md`.

This integration is experimental. Its biggest limit is that it targets Node apps only; Cloudflare is outside this release. It also has no sandbox or approval hooks. The Flue guide explains the supported setup and its limits.

Conversation state uses SQLite in `.flue-state/`. Don't serve the same conversation from two running copies of your app at once. To test restarts, use `flue run` or your built app, because the development server forgets conversations when it restarts. If you cancel while a tool is working, check what actually happened before retrying: cancelling can leave a half-done change.

Get all framework rules on the first install

A fresh `aiwg use sdlc` previously needed a second run before all of the framework's rules appeared. The first run now installs them. You can start using the framework without repeating setup to recover missing guidance.

Find papers across preprint and publication years

Citation lookup now handles a preprint and its published version more carefully. A one-year difference can resolve when other details corroborate the match. An arXiv identifier alone does not settle it. When the year still conflicts, lookup asks for review and names both years. A clearly weaker alternative match also no longer blocks the stronger result.

If you are upgrading

• If a framework setup was missing rules, rerun `aiwg use sdlc` or your original framework command.
• For Flue, start with the linked example and guide. If you already have a database setup, AIWG leaves your existing database file alone.
• Keep `.flue-state/` when you want to retain Flue conversation state.

See the CHANGELOG entry for the full technical detail.