Rename, move, and duplicate

What this is for

Rename changes how an artifact is identified, Move changes which workspace governs its access, and Duplicate creates an independent copy.

When these actions are available

Rename and Duplicate are available from the artifact actions. Move applies between workspaces in the same team when you can access the artifact in the source workspace and place it in the destination workspace. A cross-team transfer is a copy workflow, not a workspace move.

Rename

Open the artifact actions, choose Rename, and enter the new display name. The artifact URL, workspace, files, and History stay the same, so existing links keep working.

Move between workspaces

1. Open the artifact actions and choose Move.
2. Select a destination workspace in the current team.
3. Review who can reach the destination before confirming.
4. Complete the move, switch to the destination workspace, and verify the artifact opens there.

The destination workspace's access list applies after the move. People or agents with only source access may lose visibility, while destination members may gain it. You need sufficient permission in both workspaces; a denied move is terminal until a workspace manager changes access.

Duplicate

Choose Duplicate, name the copy, and select its destination workspace. The copy has a new URL and its own History from that point. It does not stay synchronized with the original and does not inherit chat history or a custom domain.

You can also duplicate a specific version from History when you want the earlier state alongside the current artifact. Use Restore instead when the earlier version should become current in the original artifact.

Ask your agent or use the CLI

A connected agent can duplicate into a reachable workspace when it has the required capability. A reachable workspace is one the agent can access. A capability is permission for the requested action. Give the agent the source artifact identifier, which is the ID for that artifact, and the destination workspace ID. Then verify the returned artifact in that workspace.

Duplicate this AgentGrid.io artifact into workspace <workspace-id> and call the copy "Q4 draft".

For current CLI syntax, see The Anima CLI.

Limits and recovery

• A workspace move stays inside one team. For another team, duplicate or export and import a copy.
• Moving changes access scope but does not create a second artifact.
• Duplicating consumes artifact capacity, and repeating it can create another copy. After a timeout, list the destination before retrying.
• If the destination is missing, verify the active team and your workspace grant.
• Folders are not part of this workflow; use workspaces, names, filters, and pinning to organize work.

Related pages

• Workspace access
• Find an artifact
• Version history

Questions and answers

Does renaming break existing links? No. The same artifact URL, workspace, files, and History remain.

Who can see an artifact after it moves? The destination workspace’s access list applies, so source-only collaborators may lose access and destination members may gain it.

Is a duplicate kept in sync with the original? No. It has a new URL and separate History, and it does not inherit chat history or a custom domain.

What should I do after a duplicate timeout? Check the destination workspace before retrying because repeating the operation may create another copy.

Operation model

Preconditions

Discover the active team and reachable workspaces. A reachable workspace is one the current identity has permission to access. For Move, require enough access in both source and destination. For Duplicate, require source read access, destination create access, and artifact capacity. Do not infer a workspace ID from an artifact URL.

Human UI route

A human opens the artifact actions and selects Rename, Move, or Duplicate. Move and Duplicate require a destination-workspace decision. The human must review the destination audience when a move may expose the artifact to different people or agents.

Agent and CLI route

Use the source artifact identifier, meaning the ID for that artifact, and an explicit destination workspace ID for a destination-aware duplicate. For exact current syntax, follow The Anima CLI. After the operation, list or open the returned artifact and verify its workspace and URL.

Do not claim that an agent can make a human-only access decision. A workspace manager must resolve a missing source or destination grant.

State and permission rules

• Moving changes workspace scope, not artifact identity.
• The destination workspace's grants apply after a move; source-only identities may lose visibility.
• A workspace move stays inside one team. A different team requires a copied or re-imported artifact with separate History.
• Duplicate does not synchronize with the original and does not copy chat history or a custom domain.
• Duplicating a historical version preserves that version as a new artifact. Restore changes the original's current state instead.

Failure and verification

Verify a rename by reopening the same URL, a move by opening the artifact from the destination workspace, and a duplicate by reading the new artifact ID and confirming its destination.

Related pages

• Workspace access
• Version history
• Troubleshooting

Questions and answers

Which identifiers are required for duplication? Use the source artifact ID and an explicit, discovered destination workspace ID.

How are the three operations verified? Reopen the same URL for rename, open the artifact in the destination for move, and confirm the new artifact ID and workspace for duplicate.

Which decision remains human-controlled? A human must choose the destination and approve any access-scope change; a workspace manager resolves missing grants.

When must duplication not be retried immediately? When the response is lost. List the destination first because repeating the operation can create another artifact.