Start, Progress and Wrap up are the everyday shortcuts. Use the other commands when you need them; you do not need every command each time.
This guide includes updates that have not been released yet. Features available to download depend on the published version.
Commands are entry points. Behind them, the tool keeps work context, organizes file connections and applies relevant working rules. You give requirements and feedback; the AI handles reading, execution, checks and saving.
The handoff keeps the current goal, your corrections, completed work and outstanding items. Important choices and reasons are recorded, while older work records are organized for later reference. The AI reads the full handoff at startup and task-relevant material as needed, without loading all history each time. Unsaved content must not be treated as remembered.
For an article, research, a webpage or document organization, simply state your goal. The AI checks the audience and tone, sources, actual program results, or file purposes and permissions as appropriate. External tools must be verified before use; unavailable connections cannot be reported as successful reads or writes.
Enter shortcuts in your project’s AI conversation, not in the terminal. Claude Code, Gemini CLI and Antigravity CLI use /; Codex uses $, or selection through /skills.
Pick up where you left off
/handoff-kit-startThe AI reads the full handoff, tells you where things stand and what remains, then waits for your task. On first use, with no goal yet, it adds a short welcome.
To continue immediately, add “continue the current goal”. If the handoff is incomplete or contains an important contradiction, the AI must say so instead of claiming it has resumed.
/handoff-kit-start continue the current goalSee the whole project
/handoff-kit-progressOpens this project’s dashboard: current work, outstanding items, history and connections between important documents.
The page updates when records are saved. Unsaved conversation changes do not appear. Viewing it does not change the project.
Finish this conversation
/handoff-kit-closeThe AI saves what is done, what remains, any problems and where to resume, then checks and reports whether the handoff was saved.
You can wrap up unfinished work. “Saved” does not mean the whole project is complete, and wrapping up grants no extra permission to upload or publish.
Get help getting started
/handoff-kit-onboardThe AI explains the tool in your language and helps you start with your own goal, asking only for information that matters.
This teaches you how to use the tool. It does not reinstall it or mark unfinished work as complete.
Find the right shortcut
/handoff-kit-helpLists the available commands and what each one does.
Showing the menu does not start work or check the project. You can still describe tasks in everyday language.
Help the next AI find an important file
/handoff-kit-alignAdd a file name. The AI checks whether the file is registered, when it should be read, and whether anything is duplicated or missing.
For example, “handoff-kit-align docs/plan.md”. With no file named, it lists possible gaps and suggestions first; edits wait for your approval of the scope.
/handoff-kit-align docs/plan.mdKeep a working preference for next time
/handoff-kit-rememberAdd the requirement after the shortcut. The AI saves it in the appropriate place in this project so it can be found for relevant work next time.
For example, “handoff-kit-remember Reply in Traditional Chinese from now on”. If no requirement is given, the AI asks first. Do not save passwords or secret keys as working preferences.
/handoff-kit-remember Reply in Traditional Chinese from now onCheck whether the tool is installed correctly
/handoff-kit-checkChecks this project’s handoff tool files and shortcuts, and explains anything missing or incorrect.
It only checks; it does not repair or upgrade. Passing does not mean the AI has read the full handoff or that your work is complete.
Get the latest released version
/handoff-kit-updateChecks the official npm download service. If a newer release exists, it upgrades this project and checks the result. If already current, it only checks. For controlled candidate testing, pass the general registry explicitly on the same npx --registry <loopback> … invocation, so the CLI launched by npx inherits it for the update check. A .npmrc readback is setup metadata, not proof of inheritance, and a direct Node run is insufficient.
It runs only when you invoke it, not on a background schedule. Connection failures, unclear versions or conflicts with custom content stop the update with an explanation. It does not force overwrites or downgrade.
You can also say “Start Agent Handoff” or “wrap up”. Describe your task in everyday language; the AI works out the necessary steps and checks, asking when key information or your decision is needed.
Use handoff-kit-progress to see where the project stands, what remains and how it got here.
Actual interface screenshot; Atlas is a fictional example. Select the image to enlarge it. Each project shows its own records.
The page updates automatically when the AI saves records. Asking the AI to open it and saving records use some tokens; viewing, filtering and subsequent page updates do not make further AI calls. Unsaved work does not appear.
Dashboard help →Open your project folder in your AI tool and paste the sentence below. The AI confirms the folder, installs or upgrades, then checks the result. You do not choose the installation commands.
Read https://adamchanadam.github.io/agent-handoff-kit/agent-handoff-kit-ai-install.en.html and install or upgrade Agent Handoff Kit in this project folder.
You need an AI tool with read and write access to your project folder, plus Node.js 18 or later. Web chat without folder access is not supported; ask the AI to check if unsure. Use the same sentence for older versions or existing AI work files.
Check that your AI has opened the right project, then reopen its conversation. Gemini CLI also supports /commands reload. If entries are still missing, give the AI the setup sentence on this page to check or repair installation. Installed files do not mean a tool has reloaded its menu; visibility and invocation must be checked in your tool.
Open the same project folder in the new tool. When changing computers, first transfer the full project and handoff files, then use Start. The tool does not automatically sync computers or copy unsaved chats.
The AI keeps your custom content, explains what needs attention and merges only the scope you approve. Identical files stay unchanged; only confirmed unmodified official shortcuts update automatically. After an interruption, ask the AI to follow recovery instructions rather than deleting protective files or reinstalling over them.
Shortcuts and handoffs live in this project. The tool refuses installation into shared AI settings, and each project needs its own setup. Merely discovering a shortcut does not mean you have asked the AI to run it.
Before deleting important data, uploading, publishing or changing access, the AI must still explain the effects and obtain the required approval. The tool’s checks cannot guarantee an AI will never make a mistake; failed reads, missing information and incomplete checks must be clearly reported.