Projects
A project groups imported programs and their analysis state. A local project and a server-backed repository are different storage choices; a server is not required for one person’s analysis.
Choose the project type
Section titled “Choose the project type”| Type | Use | Setup |
|---|---|---|
| Non-shared | Local investigation, learning, isolated experiments | Choose a directory and project name |
| Shared | Multiple analysts working through a Ghidra Server repository | Existing server access and repository permissions |
Create either through File → New Project in the upstream Project window. Creating a project closes the current one and can prompt you to save modified work. VERIFY the corresponding menu labels in your Opcodex version.
A practical structure
Section titled “A practical structure”Group by investigation and keep original samples separate from the project database:
research/ samples/ # originals and hashes notes/ # observations, hypotheses, provenance projects/ # application-managed project state exports/ # dated, explicitly generated outputsUse program names that distinguish builds and architectures. Avoid modifying application-managed project files with a text editor. Close the application before making a filesystem-level backup, and test restoration with disposable data.
Sharing and compatibility
Section titled “Sharing and compatibility”Server use requires the correct host, port, authentication, and permissions. It is not an AI endpoint. VERIFY Opcodex server compatibility and project migration against a specific release before opening important work in a newer build. Keep a backup before any format upgrade.
Recent-project improvements and workspace restoration are product work in progress; this guide does not promise a new restore interface.
Next: Import a program.
Source: Creating a Project.
Adapted from the Ghidra documentation (Apache 2.0).