Workspace organization
Keep the workspace tidy: group related work into folders, rename as projects evolve, and move objects where they belong. These tasks lean on folder-list to find ids and the folder/workspace functions to make changes.
Set up and rename a project folder
Goal — Create a home for a new initiative, then rename it once the project name is settled.
Example prompt
"Create a folder called Q3 Onboarding at the top level. … Actually, rename it to Onboarding 2026 — we're reusing it next year."
Functions used
folder-create— createsQ3 Onboardingat org root.folder-list— finds the folder's id.folder-rename— renames it toOnboarding 2026.
What you get — A single folder, renamed in place (its contents and location are untouched).
Reorganize: move a tool into the right folder
Goal — A tool was created at the root by accident; move it into its project folder.
Example prompt
"Create a folder Support Automations, then move the ticket-summarizer tool into it."
Functions used
folder-create— createsSupport Automations.tool-create— (if the tool doesn't exist yet) createsticket-summarizer.folder-list— resolves both the folder id (dir_…) and the tool id (tool_…).workspace-move— moves the tool (kind: tool) into the folder.
What you get — The tool now lives inside Support Automations. The same pattern works for agents, tables, workflows, and subfolders — only the kind changes.
Higento guards against mistakes here:
workspace-moveinfers the object kind from the id prefix, and refuses to move a folder into one of its own subfolders.
Find and open the right object
Goal — Jump straight to an object's editor without hunting through the UI.
Example prompt
"Open the invoice-parser agent so I can review its prompt."
Functions used
folder-list— locates the agent and its id.workspace-navigate— opens the agent editor (kind: agent).
What you get — The workspace navigates to the object's editor (agent, tool, workflow, table, or knowledge base) or folder view.