Roadmap

A few of the planned enhancements include (not in any specific order):

• Improve the coverage of the Excel object model, especially with formatting and charting.

• Allow to use multiple Python modules.

• Add the ability to switch from Pyodide to a full Python installation on a backend server such as Azure functions.

• Integrate Git version control.

• ✅ - Scripts: Scripts don’t allow to interact with Excel’s calculated values. This means that you currently can’t trigger an Excel calculation in a script and use its result in the same script.

• ✅ Allow to use a Jupyter notebook instead of a normal Python file.

• ✅ Improve code completion and code navigation.

• ✅ Allow to change the Pyodide version.

• ✅ Optionally allow to store the Python code externally like Office Scripts do.

• ✅ Add AI coding support similar to Excel’s Copilot.

• ✅ Make it easy to work with a set of scripts/funcs across workbooks, similar to how Personal Macro Workbook works in VBA.

• ✅ Add an interactive Python terminal.

• ✅ Introduce trusted documents concept similar to VS Code.

• ✅ Enable access to local files.

• ✅ Add a secure way to deal with secrets (environment variables).

• ✅ Allow to run scripts from buttons on the Excel sheet.

• ✅ Scripts: Currently, the content of the whole workbook is transferred to the Python runtime even if it’s not required. This makes scripts slow when the workbook is very big.

• ✅ Add dark mode.

• ✅ Custom functions: add support for streaming functions

• ✅ Custom functions: add support for object handles.