Bring your work from other AI tools to Glass

Overview

Early Access. For access information, see Request access to Glass.

You can bring useful context from Claude, Claude Code, Codex, ChatGPT, and other AI tools into Glass: your preferences, ongoing work, reference files, and reusable instructions. Start with the work you want to continue, rather than copying your entire history or recreating your old tool's environment.

Step 1: Gather context from your current AI tool

Choose a workflow you use often, such as preparing meeting briefs or writing weekly updates. Gather the preferences, instructions, source files, and decisions that make that workflow useful.

Choose Open in Claude or Open in ChatGPT, then review and send the draft there. For Codex, Claude Code, or another tool, use Copy prompt, paste it into that tool, and review it before sending. If a link does not fill the draft, use the copy option instead. Opening or copying a prompt does not import anything into Glass.

For a coding assistant, review the instruction and skill files you already maintain, such as CLAUDE.md, AGENTS.md, or SKILL.md. Start with the instructions and references for your chosen workflow, not dependencies, caches, or an entire working directory.

Step 2: Bring reviewed preferences into Glass

Review the handoff before pasting or uploading it into Glass. Remove secrets, outdated details, and anything you are not allowed to transfer. Declining a later memory save does not undo sharing the material in a chat.

Open Glass and use your private space for personal preferences. If setup opened a memory-import chat, use that chat; otherwise, start a private chat and explain what you want Glass to remember. For example:

Here are my reviewed preferences from another assistant. Summarize the lasting preferences you propose to remember, then wait for me to choose. Save only the preferences I approve as personal memory, and show me what you saved. Keep space-specific material separate.

Check the saved summary and correct anything that is wrong. These are instructions for Glass to follow, not a separate technical approval control.

Step 3: Continue ongoing work in a Glass space

For an active project, bring a short handoff with its goal, decisions, source links, open questions, and next task. Use a summary to continue an old conversation rather than expecting its original chat history to appear in Glass.

Keep a separate brief for each workstream. Review the proposed summary and choose which original files to include; leave out outdated or unnecessary material. Before transferring, check the handoff against your choices and resolve anything missing rather than assuming it was included.

In Glass, use a space you can work in or ask Glass to help create one for the workstream. Before adding sensitive material or inviting teammates, review who can read Glass chats and files. Files saved to a space follow that space's access, not just the audience of the chat that created them.

Try this prompt:

Help me continue this work in this space. Read the attached handoff and references. Summarize the goal, decisions, open questions, and next steps. Flag missing or conflicting information. Save the reviewed brief as a Markdown space file, then help me with [next task].

If you cannot create a space or save a file there, continue in a chat you can use and ask the space owner to review your access.

Step 4: Reuse skills and instructions in Glass

Try the workflow in Glass before bringing over its skill. If the result already meets your needs, skip the extra instructions. Keep only methods you still rely on, including when to use them, required inputs, steps, and the expected result.

Review the instructions and required reference files. Remove secrets and identify dependencies on local files, scripts, or connected tools. Check whether the intended space already has instructions you can reuse. Compare them with your current version before creating another copy.

Use Save and reuse instructions in a Glass space to save, reuse, and refine the reviewed instructions.

Do not assume an uploaded skill gives Glass the same tools, credentials, local paths, or behavior as your previous assistant. Ask it to identify what needs adapting before using the workflow. Keep copies in other tools up to date separately rather than assuming they stay synchronized.

If your instructions live in GitHub, provide the repository and file link and connect an account with the required access. Glass's GitHub access is limited by both the connected account and the repositories available to the installed GitHub app; a link alone does not grant access.

Step 5: Reconnect apps in Glass and test a familiar task

Set up the apps your workflow needs through Glass plugin connections. Review the account and requested permissions. Your old assistant's connections are not a substitute for Glass setup. If an app is not enabled for your company, ask your Glass admin to review it or provide approved source material yourself.

Before testing in the destination space, review its plugin access. A personal connection alone does not establish access there. If an account is missing, ask the account owner to review sharing for that space or use approved source material.

Run the task in an ordinary chat before scheduling it or using it to send anything. For example:

Use the handoff and saved instructions to draft [result]. Check the source facts and identify missing access or information. Keep the result here for review; do not send messages, change records, or create an automation.

Compare the result with what you need, check the sources, and refine the instructions. Do not rely on a draft-only prompt instead of checking Glass access boundaries.

Step 6: Recreate scheduled work in Glass

After the task works in chat, follow Create and manage Glass automations to review the configuration before creating it. Creation activates scheduling.

For each schedule you choose to replace, prepare the Glass instructions and check account access and approvals before turning off the old schedule. Choose a cutover time and a manual fallback if a delivery cannot be missed.

Turn off the selected old schedule and confirm it is off before creating the Glass version. Preserve its full instructions, schedule, timezone, delivery settings, and intended space. Check the first Glass run's actual output and delivery. If it fails, pause the Glass schedule before restoring the old one or handling the task manually, so both do not run.

Running an automation manually is real execution, not a dry run: it can send messages or make changes. Use an ordinary chat for draft-only review first.