Code Deck

A desktop app for keeping local development projects, launch commands and IDE shortcuts in one place.

What CodeDeck does

• Keep local projects in one searchable dashboard
• Open projects in the correct IDE
• Run and stop development commands
• Create projects from built-in or custom templates
• Start complete multi-project workspaces

The current interface is in German. This README uses the exact German button names where that makes the app easier to find.

Download

Download the latest version from GitHub Releases.

If CodeDeck saves you time, consider starring the repository.

Where everything is

Area	Where to find it	What it is for
Project search	Search field at the top	Searches names, paths, tags, frameworks and branches
Favorites	Favoriten filter and star on each card	Keeps frequently used projects at the top
Add a project	Neues Projekt	Creates a starter project or adds an existing folder
Scan folders	Ordner scannen	Looks below a base folder for Git repositories and known project files
Project actions	Details on a project card	IDE, terminal, commands, Git status and project settings
Running commands	Prozesse in the top bar	Live output, status, history and stop buttons
Multi-project setup	Workspaces in the top bar	Starts several project actions together
App configuration	Einstellungen in the top bar	IDE commands, templates, theme, folders and import/export

Documentation

For a detailed explanation of every page and feature, see the full user guide:

Open the Code Deck documentation

Guides

• Dashboard
• New Project
• Project Details
• Processes
• Workspaces
• Settings

Adding projects

Click Neues Projekt on the dashboard. There are two modes.

Create a new project

Choose Neues Projekt erstellen and select a starter:

• Empty project
• Node.js
• Node.js with TypeScript
• React with Vite
• Spring Boot with Maven and Java 21
• Python
• Rust CLI
• one of your own local templates

Then enter the project name and the parent folder. Code Deck shows the final path before it creates anything. Git initialization is optional.

Dependencies are not installed automatically. For example, a generated React project still needs pnpm install or npm install afterwards.

Add an existing project

Choose Vorhandenen Ordner hinzufügen and select the project directory. Code Deck checks common files such as:

.git
package.json
Cargo.toml
pom.xml
build.gradle
pyproject.toml
go.mod
Dockerfile

Detected package scripts are added as command suggestions. The project files themselves are not changed.

Scan a projects folder

Use Ordner scannen when you already have many repositories below one folder, for example:

C:\Users\you\Projects

The scan lists likely projects first. You decide which ones are added.

Project details

Open Details from a project card.

The detail view contains the project-specific functions:

• Open in … starts the preferred IDE configured for the project
• Terminal öffnen opens a terminal in the project directory
• Ordner öffnen opens Explorer, Finder or the Linux file manager
• Status aktualisieren scans frameworks, scripts, Docker files and Git data again
• Commands stores commands such as pnpm dev, mvn test or cargo run
• Git status shows the current branch, changed-file count and latest commit
• project name, description, tags, favorite state and preferred IDE can be edited here
• archiving hides the project from the normal dashboard without deleting its files

A command always runs with the project folder as its base directory. A custom working directory and environment variables can also be saved per command.

Processes and logs

Starting a command opens the Prozesse panel. It stays available from the top bar afterwards.

Each run shows:

• project and command name
• running, successful, failed or stopped state
• start time and process ID when available
• stdout and stderr output
• a stop button for active processes

Finished entries can be removed from the history without touching the project.

Workspaces

A workspace is useful when one task needs several projects, for example a frontend, API and local browser URL.

Open Workspaces, create a workspace and add actions. Supported actions are:

• open a project in an IDE
• open a terminal
• open the project folder
• run a saved or custom command
• open a URL

Actions can run in parallel or in sequence. Start runs the complete workspace; Stop all stops processes that were started by that workspace.

Settings

Open Einstellungen in the top-right corner.

Editors and IDEs

Each editor has a name and a command template. Examples:

VS Code:       code "{projectPath}"
Cursor:        cursor "{projectPath}"
IntelliJ IDEA: idea "{projectPath}"
WebStorm:      webstorm "{projectPath}"

Available placeholders:

{projectPath}
{projectName}

Keep {projectPath} in quotes so paths containing spaces work correctly.

Terminal and default folder

You can set:

• the default folder used by project dialogs and folder scans
• a custom terminal launch command when automatic terminal detection does not fit your setup

Leaving the terminal command empty uses the platform-specific default.

Custom project templates

Under Eigene Projektvorlagen, select a local folder and save it as a reusable template. When the template is used, Code Deck copies its files into the new project folder.

Generated or repository-specific folders such as these are skipped:

.git
node_modules
target
dist
build

Appearance and backups

Settings also contains:

• light, dark and system theme
• JSON export of projects, editors, workspaces and settings
• JSON import with confirmation before the current configuration is replaced
• an option to run the onboarding again

Imported commands are marked as untrusted and require confirmation before their first run.

Keyboard shortcuts

Shortcut	Action
Ctrl/Cmd + K	Focus project search
Ctrl/Cmd + N	Open the add-project dialog
Esc	Close the active dialog

Installation

Download a build from GitHub Releases.

Platform	Package
Windows	.msi or setup .exe
macOS	.dmg
Linux	.AppImage or .deb

Code Deck does not require an account or a server. The app configuration stays on the local machine.

Running from source

Requirements

• Node.js 24
• pnpm 10.33 or newer
• stable Rust toolchain
• the Tauri system dependencies for your operating system

Development

pnpm install --frozen-lockfile
pnpm tauri:dev

Frontend only:

pnpm dev

The frontend-only version is useful for UI work, but filesystem dialogs, process execution and IDE launching require the Tauri app.

Checks and build

pnpm build
cargo check --manifest-path src-tauri/Cargo.toml
pnpm tauri:build

Tauri writes platform packages below:

src-tauri/target/release/bundle/

Linux packages

On Ubuntu or Debian:

sudo apt-get update
sudo apt-get install -y \
  libwebkit2gtk-4.1-dev \
  libappindicator3-dev \
  librsvg2-dev \
  patchelf

On macOS, install the Xcode command-line tools:

xcode-select --install

On Windows, install Microsoft C++ Build Tools with the Desktop development with C++ workload.

Project structure

CodeDeck/
├── src/
│   ├── app/                  # Main application state and actions
│   ├── features/
│   │   ├── onboarding/       # First-start guide
│   │   ├── processes/        # Process list and logs
│   │   ├── projects/         # Cards, creation, scanning and details
│   │   ├── settings/         # Editors, templates and app settings
│   │   └── workspaces/       # Workspace editor and runner
│   └── shared/
│       ├── components/       # Shared modal, icons and toasts
│       ├── lib/              # Storage, templates and Tauri bridge
│       └── types/            # Shared TypeScript models
├── src-tauri/
│   ├── src/                  # Rust commands and OS integration
│   ├── capabilities/         # Tauri permissions
│   └── tauri.conf.json       # Window and bundle configuration
├── docs/screenshots/         # Images used in this README
├── .github/workflows/        # CI and release workflows
├── CHANGELOG.md
└── CONTRIBUTING.md

Local data and command safety

Code Deck reads project metadata but does not silently rewrite source files.

Commands are only started after a click. They run with the permissions of the signed-in operating-system user, so the same care applies as when running a command manually in a terminal.

Only import configurations and custom templates you trust.

Releases

Before creating a release, keep the version in these files identical:

package.json
src-tauri/Cargo.toml
src-tauri/tauri.conf.json

Then create and push the matching tag:

git tag -a v0.2.0 -m "Code Deck v0.2.0"
git push origin v0.2.0

The release workflow builds the platform packages and creates a GitHub release draft for review.

Current plans

The next useful additions are:

• SQLite storage instead of browser-backed local storage
• better Git actions such as fetch and pull
• Docker Compose controls
• port and process overview
• update notifications
• workspace templates
• a command palette

Contributing

For a small change, create a branch such as:

feature/project-icons
fix/windows-terminal-launch

Before opening a pull request, run:

pnpm build
cargo check --manifest-path src-tauri/Cargo.toml

More details are in CONTRIBUTING.md.

License

See LICENSE.