Upload work from other AI tools

Publish reports and visualizations exported from other AI tools with SecondPage's toolbar and Notes working.

3 min read

Reports and visualizations exported from other AI tools sometimes include strict outer security rules or wrapper pages that block SecondPage's toolbar and Notes. When you upload a Page in the app or publish one through an agent, SecondPage checks the HTML and adjusts supported exports so review tools work. For basic upload steps, see Create your first Page.

What SecondPage handles

Most HTML files publish exactly as uploaded. When an export's outer page has security rules that would block the toolbar and Notes, SecondPage recognizes and repairs three kinds:

  • Codex visualization exports. SecondPage adjusts only the outer page's security rules and leaves the visualization inside untouched.
  • Cursor shared canvases saved from the browser as a complete webpage. SecondPage puts a minimal outer page around the untouched report.
  • Single-frame exports from any tool, where the file is one sandboxed frame inside an otherwise empty page. SecondPage relaxes only the outer page's rules.

Your uploaded files are never rewritten. SecondPage keeps your original files intact, stores the checked copy separately, and serves that copy when someone opens the Page. Every repair is tested in an isolated browser before the Page is published.

This check runs both when you use Upload in the app and when a connected agent creates or updates a Page. See Publishing flow for how agents handle publishing.

What happens during publishing

While SecondPage checks your files in the app, the upload dialog shows Checking compatibility and finishing publication....

If a file cannot be published with a working toolbar and Notes, the dialog shows an alert and the button changes to Choose corrected files. There is no option to skip the check. The message names the file and the problem, says Nothing was published; an existing Page keeps its current version., and ends with a hint on what to change.

The message says the file...What to do
is not valid UTF-8 HTMLExport the report as UTF-8 HTML and upload it again.
is too large or complex to check safelyExport a smaller standalone HTML report.
is missing its embedded report fileUpload the HTML with its complete companion folder, or upload the complete ZIP export.
contains an embedded report that does not match the uploadExport the complete report again and upload the fresh files together.
could not be verified with working toolbar and NotesTry exporting again. If the same export still fails, contact SecondPage support with the file name.
has security rules that block the toolbar and NotesAsk the tool that created the file to export only the finished report as a standalone HTML page. Do not remove security protections to force publication.
uses an embedded export structure that cannot be repaired safelyRe-export the Codex report as a standalone HTML page while keeping the embedded report's sandbox and security rules.
uses an export structure that cannot be repaired safelyExport the report as a standalone HTML page with all its companion files.
could not be checked because SecondPage’s verification service is temporarily unavailableClick Try again in a few minutes. You do not need to change or re-export your files.

What agents see

Connected agents go through the same verification check when creating or updating Pages. When a file cannot be published, the tool call returns review_controls_incompatible along with recovery instructions. If the verification service cannot be reached, the tool call returns import_verification_unavailable so the agent can retry without changing the files. See Publishing flow for details on handling these errors.

Size and complexity limits

Very large or deeply nested HTML may be too large to check safely, even when the total upload fits within your plan. For standard file and Page size limits, see Page capacity.

Still have a question?

Ask in your own words, or write to us at support@secondpage.cc.

Email us