Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The official date is October 19, 2026, without an exact time or time zone. This article’s October 14 publication does not mean retirement has happened.
- /migrate-workflows scans global and workspace legacy directories, generates SKILL.md and appends .bak to originals. Review the generated files.
- Workspace and global skills have different locations. Scanning a global directory does not establish that every migrated result works across projects.
- A same-name skill takes precedence. Restoring the old Markdown alone may not restore behavior, and a backup cannot keep the legacy format executable after retirement.
What stops October 19, and what can replace it?
Both official documents name October 19, 2026. The migration guide says legacy directories then cease to be indexed or executable through slash commands. It gives no exact time, time zone or account-specific implementation details.
This concerns legacy Markdown workflows in Antigravity IDE. Google says instructions for a new workflows system will follow; skills are an available alternative that packages instructions and supporting files in a directory. That does not establish that the future system has launched.
First identify the file behind each command
Legacy workspace files use .agents/workflows/<name>.md; global files use ~/.gemini/config/workflows/<name>.md. Inventory the commands your team actually uses, their files, dependent scripts and intended projects. Back up the files and their supporting resources.
Start with a workflow that organizes local notes rather than deploying or paying for anything. For example, suppose /review-notes only summarizes changes: record which files it should read and what it should produce. This is an unexecuted trial scenario for comparing intent.
What should you inspect after /migrate-workflows?
Run /migrate-workflows in Antigravity 2.0 chat. The documented process scans both legacy locations, parses metadata and instructions, creates .agents/skills/<workflow-name>/SKILL.md and archives originals with a .bak suffix. The guide says new skills become immediately active for slash commands and autonomous agent use, so perform the migration in a disposable project first.
Review the file differences before relying on the result. Check names, descriptions, step order, paths and permission boundaries, then locate each supporting script and reference. A completed conversion command is not proof that every workflow behaves correctly.
Pay particular attention to previously global workflows. The automatic output shown is workspace-local, whereas global skills use ~/.gemini/config/skills/<name>/SKILL.md. The guide does not explain automatic preservation of global scope; verify it rather than inferring reach from the scan.
How can manual migration preserve behavior?
Create a same-name folder in the intended workspace or global skills directory and place the instructions in SKILL.md. Use standard name and description metadata. Describe the task and when to use it; a vague label such as “useful tools” does little to distinguish its purpose.
Initially preserve the original sequence, checkpoints and stop conditions. Put long references in references/ and helper scripts in scripts/, with actual relative paths in the instructions. The official guide contains complete file examples. Recheck references when splitting one file into several.
The command name still works: which file runs?
Skills in either supported location can use /<name>. A skill wins over a legacy workflow with the same name. In a disposable project, inspect the loaded instructions, step order and result before wider adoption; the familiar command name alone tells you little.
For instance, if the old process summarizes changes and then waits for human confirmation, retain that stop in the skill. Compare each expected step instead of trusting a final “done.” Deployment, deletion and external writes still require their existing permissions.
Why does a .bak file not guarantee rollback?
A backup preserves content, not permission to execute the retired format. Before October 19, stop a faulty skill before restoring and checking the old command. Leaving a same-name skill in place can keep the new version active even after the old Markdown returns.
After retirement, renaming the backup cannot be promised to restore execution. Use it to repair the skill or temporarily follow the instructions manually. The future workflows conversion process, minimum version, pricing and individual account outcome require their own official confirmation.
Sources
Frequently Asked Questions
Will automatic migration relocate all my scripts?
The guide specifies scanning, parsing, SKILL.md generation and archiving. It does not guarantee that every external script or absolute path is copied and repaired. Compare the resource inventory with the output, correct missing references, then use a disposable verification scenario.
Should I distribute the workspace skill to every teammate?
First confirm its paths, scripts and permissions fit the shared project. Synchronizing a file does not establish that each person has reviewed it, can execute it or has permission for external actions. Keep private credentials out of skills and version control.
Can I rely on an older tutorial that says November 1?
Both official documents read for this article give October 19, 2026. Recheck those original pages when another tutorial differs, and plan against the current official date. No exact time or time zone is published, so do not invent a conversion.