Menu
Undo the last Amp update if something went wrong
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Extract and track commitments from meeting notes - who promised what to whom, with deadlines and status tracking.
Route tasks to Pi for comparison testing. Toggle Pi mode or run specific commands through Pi.
View and manage Pi-built extensions synced to Amp. Shows available tools, commands, and sync status.
Review proposed actions surfaced by the B-1 Activation Engine. Gathers recent signals, extracts candidates, ranks them, drafts artifacts, and captures the user's response per offer. Standalone — does not modify /daily-plan.
Configure AI model options - budget cloud models (save 80%+) and offline mode (use Amp without internet)
Check your AI model configuration - see what's set up, current model, credits remaining
| name | amp-rollback |
| description | Undo the last Amp update if something went wrong |
Restores Amp to the version before your last update. Use this if something broke after updating.
When to use:
Safe to use: Your notes, tasks, and projects are never at risk.
A. Verify Git repository
Run: git --version
If Git not found:
❌ Git not detected
Rollback requires Git. Your data is safe, but automated rollback isn't available.
**To manually restore:**
1. If you have a backup folder, copy your data back
2. Or re-download Amp and copy your folders (00-07, System/)
[Show manual restore guide]
B. Check for backup tag
Run: git tag | grep backup-before
If no backup found:
❌ No backup found
Looks like you haven't updated recently, or the backup wasn't created.
Your current version: v1.3.0
Options:
[Download previous version manually]
[Cancel]
C. Identify what version to restore to
Run: git tag | grep backup-before | tail -1
Example: backup-before-v1.3.0 means restore to before v1.3.0 update.
🔙 Rollback Amp Update
You're about to restore Amp to the version before your last update.
Current version: v1.3.0
Will restore to: v1.2.0 (last backup)
**What happens:**
✓ Amp features restored to v1.2.0
✓ Your notes, tasks, projects stay as they are
✓ Any new skills from v1.3.0 will be removed
**This is safe:**
• Your data folders (00-07) are not affected
• Your configuration (user-profile, pillars) stays
• You can update again later if you want
[Confirm rollback]
[Cancel]
Before rolling back, save any uncommitted changes:
💾 Saving current state...
Run:
git add .
git commit -m "Auto-save before rollback to v1.2.0" || true
Create a "before rollback" tag in case they want to undo the rollback:
git tag before-rollback-$(date +%Y%m%d-%H%M%S)
✓ Current state saved
🔄 Rolling back to v1.2.0...
Run:
git reset --hard backup-before-v1.3.0
This restores all Amp files to the state before update.
Note: User data folders (00-07) remain untouched because:
git reset only affects tracked filesA. Remove dependencies from newer version
📦 Cleaning up...
Run:
npm install
pip3 install -r requirements.txt
This ensures dependencies match the older version.
B. Remove migration markers (if exist)
rm -f .migration-v*-complete
rm -f .migration-version
✓ Rollback complete! Now testing...
Quick checks:
Verify version in package.json:
cat package.json | grep version
Check key files:
03-Tasks/Tasks.mdSystem/user-profile.yaml.claude/skills/daily-plan/SKILL.mdTest user profile loads:
Read System/user-profile.yaml
If all pass:
✅ Rollback successful!
If issues:
⚠️ Rollback completed but found an issue
[Details]
Your data is safe. You may want to:
[Report this issue]
[Try rolling back again]
[Continue anyway]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✅ Rolled Back: v1.3.0 → v1.2.0
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Amp restored to: v1.2.0
Your data: All preserved (notes, tasks, projects)
You're back to the version from before your last update.
**What now?**
• Everything should work as before
• You can try updating again later with /amp-update
• If issues persist, try /setup to verify configuration
**Want to report what went wrong?**
[Open issue on GitHub] — Help improve future updates
If user rolled back by mistake and wants to go forward again:
Did you roll back by mistake?
We saved your state before rollback. You can restore it:
[Restore to v1.3.0] — Undo this rollback
[Stay on v1.2.0] — Keep rollback
If user chooses restore:
RESTORE_TAG=$(git tag | grep before-rollback | tail -1)
git reset --hard $RESTORE_TAG
If Git not available or no backup tags:
📥 Manual Rollback Method
To restore an older version without Git:
1. **Download your desired version:**
For v1.2.0:
https://github.com/hemory/amp/releases/tag/v1.2.0
Click "Source code (zip)"
2. **Copy your data:**
From CURRENT Amp, copy to DOWNLOADED Amp:
✓ System/user-profile.yaml
✓ System/pillars.yaml
✓ 00-Inbox/
✓ 01-Quarter_Goals/
✓ 02-Week_Priorities/
✓ 03-Tasks/
✓ 04-Projects/
✓ 05-Areas/
✓ 07-Archives/
✓ .env (if exists)
3. **Replace folders:**
• Move current Amp folder to trash (or rename to amp-old)
• Rename downloaded folder to 'amp'
• Open in Cursor
4. **Verify:**
Run /setup to check everything works
[See version history] — All Amp releases
[Copy instructions]
What rollback restores:
What rollback preserves (doesn't touch):
What you might lose:
Likely MCP servers need restart:
Your task data is unchanged. What might look different:
Your actual tasks are safe. Check 03-Tasks/Tasks.md directly - everything is there.
Yes, if backups exist:
git tag | grep backup-before
Shows all available backups:
backup-before-v1.1.0
backup-before-v1.2.0
backup-before-v1.3.0
To rollback to specific version:
git reset --hard backup-before-v1.1.0
But easier: tell /amp-rollback which version you want, and it handles it.
To avoid needing rollback:
Read release notes before updating
/amp-whats-new firstUpdate during low-stakes time
Test after updating
/daily-planKeep regular backups
/amp-update - Update to latest version/amp-whats-new - Check what's available/setup - Verify Amp configurationRollback should be:
User confidence: "I can try updates knowing I can undo them instantly"
No shame in rolling back: Updates should improve things. If they don't for you, rolling back is the right choice. Help us by reporting what went wrong.
Update System/usage_log.md to mark Amp rollback as used.
Analytics (Silent):
Call track_event with event_name amp_rollback_completed and properties:
restored_versionThis only fires if the user has opted into analytics. No action needed if it returns "analytics_disabled".