---
title: "Delete Application"
description: "Documentation for Delete Application Command in ZeyOS SDK CLI"
canonical_url: "https://www.zeyos.com/sdk/application-management/zeysdk-delete"
markdown_url: "https://www.zeyos.com/ai/guide/sdk/application-management/zeysdk-delete.md"
section: "sdk"
authority: "guide"
language: "en"
source_repository: "zeyos/sdk-v2"
source_path: "docs/application-management/zeysdk-delete.md"
source_revision: "a99897af74253b4dc5af6fecb9301cea0ae18e27"
---

# Delete Application

The `delete` command permanently deletes your ZeyOS application from the current instance.

```bash
zeysdk delete [options]
```

**Options**

| Option | Description |
|--------|-------------|
| `-f, --force` | Skip deletion confirmation prompt |
| `--verbose` | Show detailed output |

**Process**

1. **Validation**
   - Checks that the command runs inside a linked app
   - Loads `.zeysdk/sync.json`
   - Verifies required instance and app identifiers

2. **Confirmation**
   - Prompts before deleting the remote application
   - Stops when deletion is not confirmed
   - Uses verbose output for additional progress details

3. **Deletion**
   - Sends the delete request to the current instance
   - Removes the application from the platform
   - Reports the final deletion result

**Examples**

```bash
zeysdk delete
zeysdk delete --force
zeysdk delete --verbose
```

**Error Handling**

| Error | Description | Resolution |
|-------|-------------|------------|
| Missing sync.json | sync.json file not found | Ensure you are in an app directory |
| Invalid sync.json | Missing required keys | Verify sync.json has id and url |
| API error | Server communication failed | Check connection and permissions |

**Warning**

Delete permanently removes the application from the current instance.

**Notes**

- Delete acts on the currently linked instance
- Local files are not a substitute for a remote backup
- Use `zeysdk whoami` before deleting if you are unsure which instance is active
- Consider `zeysdk predelete` when you need a reversible operational state first
- `--force` skips confirmation and should be used carefully

**Best Practices**

- Create a snapshot before destructive changes
- Confirm the active instance before deleting
- Notify affected users before removing production apps
- Keep a record of the app ID and instance for audit purposes