Reducto Office

View saved version →

---
name: onboarding
description: First-run setup for Reducto Office. Checks the connection to the user's Reducto account and helps them sign in if needed.
---

# Set up Reducto Office

Reducto Office connects to the user's Reducto account. Use the account they intend to use for their documents; do not instruct them to select Reducto's internal organization or assume that they are a Reducto employee.

## Check the connection

1. If `list_files` is available, call it.
2. A successful response confirms the connection, even if the file list is empty. Tell the user the account is connected. Offer to open a blank document with `open_editor`, or continue the document task they already requested.
3. If the tools are unavailable, guide the user to enable or connect Reducto Office in their host. If the call specifically reports an authentication or authorization problem, guide them through sign-in using the supported connection flow:
   - ChatGPT: Settings → Apps → Reducto Office → Connect.
   - Codex app: Settings → MCP servers → Reducto Office → Authenticate.
   - Codex CLI: `codex mcp login reducto-office`.
   Host labels can vary; use the connection or authentication control shown for Reducto Office.
4. Sign-in happens in the browser. Ask the user to sign in with their intended Reducto account and complete the authorization flow. Do not claim that external-account access is supported until the server has actually authorized the account.
5. After sign-in, call `list_files` again. Confirm setup only if it succeeds. If tools are still unavailable, ask the user to return to the host and confirm that the connection is enabled before retrying.

## Handle problems

- Do not treat network errors, service failures, or other unrelated errors as proof that sign-in is required. Explain the reported problem accurately and suggest a retry when appropriate.
- If authorization fails after sign-in, explain the returned access problem. Do not tell the user to join Reducto's internal organization, invent account eligibility rules, or repeatedly send them through the same sign-in flow. Direct them to Reducto Office support at https://office.reducto.ai/support if the problem persists.
- Do not create or change documents merely to test authentication. `list_files` is the connection check.
- Never ask for passwords, access tokens, client secrets, or authentication codes in the conversation.

View saved version →

---
name: reducto-office
description: Edit Word (.docx), PowerPoint (.pptx) and Excel (.xlsx) files in Reducto Office, a live editor the user watches and types into. Use when the user wants to write, revise, redline or format a document, build or change a slide deck, or fill or format a spreadsheet, or opens or attaches one of these files.
---

# Reducto Office

Reducto Office shows a live Word document, PowerPoint deck or Excel workbook in the conversation. Your edits appear while the user watches, and the user can type in the same file.

## Start

- A file the user opens with Open in → Reducto Office arrives through `open_document`. The editor shares its `fileId` once it loads; use that, and do not call `open_editor` for it.
- A .docx, .doc, .pdf, .pptx or .xlsx the user attached in ChatGPT: call `open_editor` with `file` set to the attachment. A .doc or .pdf becomes a Word document; check a converted PDF's layout before you edit.
- For a new file, call `open_editor` with `kind`: `docx` (the default), `pptx` or `xlsx`. It shows a blank file. A blank deck has no slides yet.
- To show a file from a link (`…/d/<id>`) or `list_files`, call `open_editor` with `fileId`.
- Show each file once. The editor shows every `exec` live, and each `open_editor` call opens another copy of it. Do not open the file's links in a browser.
- To show the user their files or the Reducto Office home, call `open_home`. Never open office.reducto.ai in a browser: the user is not signed in there.
- `list_files` lists the user's files for you.
- A local file (Codex CLI): call `create_file`, upload the file with `curl -sfT <path> '<uploadUrl>'`, then call `open_editor` with its `fileId`.

## Save to disk

With a shell: the open result has a download link. Run its `curl` command to write the current file over the local one. The link expires in 15 minutes; `open` with `fileId` returns a new one without another editor. Never look for tokens or credentials.

Without a shell (ChatGPT, Claude): tell the user to use Export in the editor.

## Edit

1. Call `read_guide` with the file's `kind` once before the first `exec`. It has the API and recipes for that kind.
2. Call `exec` with `fileId`, `agent` (your name, for example "chatgpt"), `intent` (a few words the user sees) and `code` (JavaScript against the live file).
3. `code` gets `doc` for Word, `presentation` for PowerPoint and `workbook` for Excel. They follow the Office.js object model without `run`, `sync` or `load`.
4. Read before you write: `readPage()` or `text()` in Word, `renderPage(n)` for a slide, `renderRange(sheet, range)` for cells.
5. Make small edits in each call. The user sees each change as it lands.

## Rules

- If a result starts with "Note:", someone else changed the file. Read it again before you edit content you saw earlier.
- Use tracked changes when the user asks for a redline or review of a Word document.
- Do not paste the file back into the conversation. The user sees it in the editor.
- The editor tells you where the user is: in Word, the caret's line or the selected text; in a deck, the slide and the selected shape ids; in a workbook, the sheet, range and active cell, with the cell values. "This", "here" and "these cells" mean that place. Use the ids and addresses it gives you in exec.