-
Notifications
You must be signed in to change notification settings - Fork 1
Project Settings
Sia edited this page May 31, 2026
·
1 revision
The project overview page (/projects/{id}/overview) has a Project settings
card for renaming three things.
Editable at any time. Updates the name column only — no files or IDs change.
Editable only while the project is idle (no console turn in progress and no build running). On change the server:
- Updates the project's
package_namein the database. - Renames the keystore files in
/home/vibe/keystoresfrom<old>.keystore(and-debug.keystore,-keystore.properties,-admob.properties) to the new package prefix, rewriting thestoreFilepath inside the properties. - Sends a rename task to the console so Claude updates the code:
namespaceandapplicationIdinbuild.gradle.kts, thesrc/main/java(andkotlin/test/androidTest) directory structure, allpackage/importdeclarations,AndroidManifest.xml, and any signing references.
Watch the console while Claude performs the refactor, then build to confirm.
The project ID is the workspace folder name and the database primary key, so this is the heaviest change. Editable only while the project is idle.
On change the server:
- Terminates any live console session (the process holds the old folder as its working directory). The conversation history is preserved in the database and reappears in the renamed project's console.
- Moves the workspace directories:
<root>/<id>,.vibecoder/<id>, and the project keystore directory. - Migrates the database primary key in a single transaction — inserts the new
project row, repoints
project_idin every child table (builds, artifacts, uploaded files, conversation turns, build schedules, webhook secrets, prompt automation runs, notification events), then deletes the old row. If the DB step fails the filesystem move is rolled back.
The new ID must match [a-z0-9][a-z0-9._-]{0,63} and must not already exist.
General Chat / chat ghost projects cannot be renamed.