feat: add settings import/export functionality by coderGtm · Pull Request #734 · WordPress/ai

coderGtm · 2026-06-16T08:32:42Z

What?

Closes #191

This PR implements the ability to export and import non-sensitive AI configuration settings and introduces a dedicated AI section in WordPress Site Health.

Why?

Allowing users to move AI configurations between environments (e.g., staging to production, multi-site etc.) improves the developer experience. By excluding sensitive credentials from the export, we ensure security while maintaining portability. The Site Health integration provides administrators with a quick overview of the plugin's status and credential health.

How?

REST API: Created includes/REST/Settings_IO_Controller.php to handle GET /ai/v1/settings/export and POST /ai/v1/settings/import.
Security: Implemented SENSITIVE_PATTERNS filtering to ensure API keys, tokens, and secrets are never exported or overwritten during import.
Site Health: Added includes/Admin/Site_Health.php to provide debug information (version, enabled features, credential status) and a status test for connectivity.
UI/UX:
- Added "Export settings" and "Import settings" to the AI settings menu in routes/ai-home/stage.tsx.
- Implemented a confirmation modal for imports.
Tests: Added comprehensive integration tests in tests/Integration/Includes/REST/Settings_IO_ControllerTest.php and tests/Integration/Includes/Admin/Site_HealthTest.php.

Use of AI Tools

AI assistance: Yes
Tool(s): GitHub Copilot
Model(s): Claude Sonnet 4.6, GPT-4o
Used for: Authoring the codebase exploration, UI components, and the integration test suite.

Testing Instructions

Navigate to AI Settings.
Open the kebab menu (three vertical dots) in the top right.
Click Export settings. A JSON file containing your current toggles and developer configurations (but no API keys) should download.
Toggle several features to different states.
Click Import settings in the menu and select the previously downloaded file.
Confirm the prompt "This will overwrite existing AI settings."
Verification: The UI should update immediately to reflect the imported settings without a page refresh.
Navigate to Tools > Site Health.
In the Status tab, verify the "AI Plugin" test results.
In the Info tab, verify the "AI Plugin" section contains correct metadata about your setup.

Screenshots or screencast

Menu Items:

Confirmation prompt before completing import:

Changelog Entry

Added - Import/Export functionality for non-sensitive AI settings.
Added - AI-specific Site Health integration and status tests.

github-actions · 2026-06-16T08:32:57Z

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: coderGtm <gautam23@git.wordpress.org>
Co-authored-by: dkotter <dkotter@git.wordpress.org>
Co-authored-by: jeffpaul <jeffpaul@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

coderGtm · 2026-06-18T10:40:32Z

The failing JavaScript quality check is due to a conflict between eslint and typescript. While eslint prefers dot notation, typescript complains about it (TS4111). Should I suppress the eslint error?

dkotter · 2026-06-18T14:52:30Z

The failing JavaScript quality check is due to a conflict between eslint and typescript. While eslint prefers dot notation, typescript complains about it (TS4111). Should I suppress the eslint error?

We do have a number of these that we already ignore with inline statements so I think that's fine

…to feature/import-export-config

dkotter

Overall this looks really good, left a few comments. In addition, an E2E test here would be nice to verify the import/export options are available

dkotter · 2026-06-23T15:27:38Z

+				),
+				'description' => sprintf(
+					'<p>%s</p>',
+					__( 'At least one AI connector has credentials configured and is ready to use.', 'ai' )


So this isn't entirely accurate. The has_ai_credentials function will tell us if a Provider has credentials set but doesn't tell us if the credentials are valid. We do have a new is_connector_configured function that we could use here instead

dkotter · 2026-06-23T15:33:31Z

 	content: string;
 }

+/** Shape of an AI settings export payload (matches the PHP schema). */


So this file is already really large so if we can extract out any of these new functions into individual component or hook files, that would be great

dkotter · 2026-06-23T15:37:41Z

+	 *
+	 * @var list<string>
+	 */
+	private const SENSITIVE_PATTERNS = array( 'api_key', 'token', 'secret', 'credential', 'password', 'auth' ); // phpcs:ignore SlevomatCodingStandard.Classes.DisallowMultiConstantDefinition


Worth adding just key to this list?

Also risk here if there's a setting named author, I think that gets matched due to auth

dkotter · 2026-06-23T15:39:19Z

+				continue;
+			}
+
+			update_option( $option_name, $value );


Slight risk here since we don't run any sort of validation or sanitization

And would be nice to capture this in a test, ensuring if someone passes in data that is the wrong type (i.e. we expect a boolean for a certain field and someone passes in string) that the data is either sanitized properly or rejected

dkotter · 2026-06-23T15:40:02Z

 				( new Dashboard_Widgets( $registry ) )->init();
 			}

+			// Register Site Health integration (always, not just in admin).


Does this need to load everywhere or could we scope this to the admin only?

coderGtm · 2026-06-25T11:52:40Z

Thanks @dkotter for reviewing this. I will work on the feedback over the days and request a review again.

feat: add settings import/export functionality

2683599

coderGtm and others added 2 commits June 16, 2026 14:11

docs: remove emdashes

d32f36a

Merge branch 'develop' into feature/import-export-config

e6b3b14

coderGtm marked this pull request as draft June 16, 2026 09:26

coderGtm and others added 2 commits June 18, 2026 13:34

Merge branch 'develop' into feature/import-export-config

b8b1ef9

lint: fix coding standard errors

38643d0

coderGtm and others added 5 commits June 19, 2026 16:37

lint: suppress eslint dot notation error

31d35ad

fix: ensure option names are consistently treated as strings

cb58b9e

Merge branch 'develop' into feature/import-export-config

b1f0a0a

fix: ensure option names are consistently treated as strings

bcdbfc4

Merge remote-tracking branch 'origin/feature/import-export-config' in…

73048bd

…to feature/import-export-config

coderGtm marked this pull request as ready for review June 19, 2026 12:34

dkotter assigned coderGtm Jun 23, 2026

dkotter requested changes Jun 23, 2026

View reviewed changes

dkotter added this to the Future Release milestone Jun 23, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat: add settings import/export functionality#734

feat: add settings import/export functionality#734
coderGtm wants to merge 10 commits into
WordPress:developfrom
coderGtm:feature/import-export-config

coderGtm commented Jun 16, 2026 •

edited by github-actions Bot

Loading

Uh oh!

github-actions Bot commented Jun 16, 2026

Uh oh!

coderGtm commented Jun 18, 2026

Uh oh!

dkotter commented Jun 18, 2026

Uh oh!

dkotter left a comment

Uh oh!

dkotter Jun 23, 2026

Uh oh!

dkotter Jun 23, 2026

Uh oh!

dkotter Jun 23, 2026

Uh oh!

dkotter Jun 23, 2026

Uh oh!

dkotter Jun 23, 2026

Uh oh!

dkotter Jun 23, 2026

Uh oh!

dkotter Jun 23, 2026

Uh oh!

coderGtm commented Jun 25, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

coderGtm commented Jun 16, 2026 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What?

Why?

How?

Use of AI Tools

Testing Instructions

Screenshots or screencast

Changelog Entry

Uh oh!

github-actions Bot commented Jun 16, 2026

Uh oh!

coderGtm commented Jun 18, 2026

Uh oh!

dkotter commented Jun 18, 2026

Uh oh!

dkotter left a comment

Choose a reason for hiding this comment

Uh oh!

dkotter Jun 23, 2026

Choose a reason for hiding this comment

Uh oh!

dkotter Jun 23, 2026

Choose a reason for hiding this comment

Uh oh!

dkotter Jun 23, 2026

Choose a reason for hiding this comment

Uh oh!

dkotter Jun 23, 2026

Choose a reason for hiding this comment

Uh oh!

dkotter Jun 23, 2026

Choose a reason for hiding this comment

Uh oh!

dkotter Jun 23, 2026

Choose a reason for hiding this comment

Uh oh!

dkotter Jun 23, 2026

Choose a reason for hiding this comment

Uh oh!

coderGtm commented Jun 25, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

coderGtm commented Jun 16, 2026 •

edited by github-actions Bot

Loading