Skip to main content

Heads up: attune-gui is folding into attune-ai

Pre-fold notice. Nothing breaks today.

What’s changing

Today the dashboard ships as a standalone PyPI package:

pip install attune-gui

In an upcoming release, it becomes an install extra on attune-ai itself:

pip install attune-ai[gui]

Same dashboard, same surfaces (Living Docs, RAG search, Commands, Summaries). One package to install instead of two.

What stays the same

  • The dashboard URL, layout, and feature set.
  • Your project directory and any .help/ templates / corpus state.
  • The CLI. attune workflows continue to work unchanged.
  • Your existing attune-gui install keeps running until you choose to migrate.

When does this happen

On the v7.0 release. We’ll publish a banner here, on the homepage, and on the attune-gui PyPI page about 4–6 weeks before release day so you aren’t blindsided. The banner phrasing is deliberately non-version-specific until the v7.0 RC cuts.

Do I need to do anything now?

No. This page is a heads-up. When v7.0 ships, the steps will be:

  1. pip uninstall attune-gui
  2. pip install attune-ai[gui]

The standalone attune-gui package will continue to publish as a deprecation shim that points at the new install path, so a stale install command in a CI script won’t break overnight.

Where to follow along

  • Changelog — v7.0 release notes will land here with the exact migration steps.
  • FAQ — “What’s the difference between attune-ai and attune-gui?” updates on fold day.
  • GitHub issues — raise anything that surprises you in the migration.