# DevDb for VS Code: Project-Aware Database Browsing and Editing

> DevDb is a TypeScript VS Code extension that detects many project database setups and exposes local database browsing and editing without requiring users to write a connection. Its strongest fit is development work inside Laravel, Rails, Django, AdonisJS, Prisma, Drizzle, DDEV, Supabase, Docker Compose, and related projects.

**damms005/devdb-vscode** — A zero-config VS Code database extension with affordances to aid development and debugging.

- Repository: https://github.com/damms005/devdb-vscode
- Website: https://marketplace.visualstudio.com/items?itemName=damms005.devdb
- Stars: 1,455 · Forks: 38
- Language: TypeScript
- License: MIT
- Published: 2026-10-16 · Updated: 2026-10-16 · Language: en
- Canonical page: https://hysenlabs.com/projects/damms005-devdb-vscode

## Why DevDb belongs in a Project Workspace

DevDb addresses a specific gap between application development and database administration. A developer working in a VS Code project usually has framework configuration, environment variables, container definitions, or ORM files already present, but still has to connect a separate database client manually. DevDb reads those project-level signals and presents detected databases in a DevDb panel. The README says it does this for Laravel, Rails, Django, AdonisJS, DDEV, Supabase, Prisma, Drizzle, `docker-compose`, Wrangler, and `DATABASE_URL` setups.

The target user is a developer who needs to inspect records while modifying application code. The panel supports row filtering, value editing, setting `null`, and deleting rows. It also provides navigation from code context: `Cmd+K Cmd+G` goes to a table, and a context-menu command can open the table at the cursor. The README also documents generating Laravel factories from real data, explaining MySQL queries, and exporting data as JSON or SQL.

This is not a general database administration console by design. Its value comes from placing database work beside the files and frameworks that define the application. The extension also supports Cursor and Windsurf, according to the project description, although the installation instructions focus on VS Code-compatible environments.

## What Zero-Config Detection Actually Covers

The central mechanism is project-aware detection rather than a universal connection wizard. Based on the repository layout and README, the extension activates for workspaces containing `.devdbrc` or when VS Code recognizes PHP, JavaScript, or TypeScript. Its capabilities indicate that DevDb runs project tooling such as `php artisan` and `rails`, and reads project database configuration. That explains why the extension declares that untrusted workspaces are unsupported.

Detection covers several connection styles rather than only local files. The documented datastore table lists SQLite, MySQL, MariaDB, PostgreSQL, SQL Server, MongoDB found through zero-config detection, and local Cloudflare D1 as Free features. The same table places remote MySQL, MariaDB, PostgreSQL, MongoDB, and Supabase Cloud behind Pro. Redis, Valkey, ClickHouse, DuckDB, Neon, pgvector search, remote Cloudflare D1, Turso or libSQL, and DynamoDB are also listed as Pro capabilities.

The distinction matters when evaluating adoption. A project can use a supported database engine and still fall outside the free feature set if the connection is remote or the datastore belongs to the Pro list. The README does not document every framework-specific detection rule or the precedence between multiple configuration sources. Teams should therefore inspect the detected result in the panel rather than assume that a database will appear.

## Opening and Editing Data in the DevDb Panel

Once a database is detected, the panel becomes the interface for inspecting and changing records. The README documents filtering rows, editing values, setting `null`, deleting rows, and saving changes. Keyboard commands for `Cmd+Z`, `Cmd+Y`, and `Cmd+S` correspond to undo, redo, and save on macOS. These operations are useful for small development corrections, such as reviewing a newly created record or changing a field while reproducing application behavior.

DevDb also connects database browsing to the editor. The Go to Table command uses `Cmd+K Cmd+G`, while the Open Table at Cursor action uses the table context associated with the current code location. The documented editor features extend this path with Laravel factory generation, MySQL query explanation, and JSON or SQL export. The README does not specify transaction behavior, bulk editing limits, confirmation dialogs, or the exact conflict handling when multiple editors or processes modify the same row, so those details require verification in the linked documentation or through actual use.

For MCP clients, the project provides a separate integration point. Claude Code, Cursor, Windsurf, and other MCP clients can read the schema and run queries through a localhost-only server with a token. The server is read-only by default. This creates a controlled path for agent access, but it also means that enabling broader query access changes the security boundary and should be evaluated separately from ordinary panel use.

## Installing DevDb and Opening a Local Database

The README directs users to install DevDb from the VS Code Marketplace or Open VSX. After opening the project, VS Code asks whether the workspace can be trusted. Trust is required because the extension reads project configuration and runs project tooling. The documented requirement is VS Code 1.90 or later, with support stated for macOS, Windows, Linux, Alpine on x64 and arm64, and Linux armhf.

The first-use sequence is short. Open DevDb with the documented shortcut, then select the detected database under `Local Databases`. The commands below are copied from the README, so the platform-specific shortcuts are kept separate.

```bash
# macOS: open the DevDb panel
Cmd+K Cmd+D
```

```bash
# Windows and Linux: open the DevDb panel
Ctrl+K Ctrl+D
```

After the panel opens, click the database under `Local Databases`. The expected first result is a list of detected local databases, followed by the tables DevDb exposes for the selected database. If detection fails, the README calls for a `.devdbrc` file and explains that typing `devdb` reveals snippets. The file can contain passwords, so the project explicitly says to add it to `.gitignore`.

The repository contribution instructions use Bun for extension development:

```bash
bun install
bun run test-services
```

The README instructs contributors to press `F5` to test the extension in VS Code after making changes. It also states that all tests must pass. The UI code is not public, which limits the scope of external contribution to the extension core.

## Configuration, Credentials, and Upgrade Cost

Automatic detection removes the need to create a connection in the common case, but it does not remove configuration risk. `.devdbrc` is the documented fallback when DevDb cannot find a database. Because it may contain passwords, the README instructs users to add it to `.gitignore`. The project does not document rotation, secret storage, or redaction behavior for that file in the README or the repository files described there, so credentials should be treated as sensitive project data rather than ordinary editor settings.

The free and paid boundaries affect upgrade planning. Local SQLite, MySQL, MariaDB, PostgreSQL, SQL Server, detected MongoDB, and local Cloudflare D1 are marked Free. Remote database access, SSH tunnels, direct TLS connections, MongoDB remote access, Supabase Cloud, Redis or Valkey, ClickHouse, DuckDB, Neon, pgvector, remote D1, Turso or libSQL, and DynamoDB are marked Pro. DevDb Pro is described as a one-time payment for a lifetime license. That is a product licensing statement, not a guarantee about future compatibility or support.

The repository identifies the project as MIT licensed, while `package.json` points to `LICENSE.txt` through `SEE LICENSE IN LICENSE.txt`. That distinction is worth checking before redistribution or commercial integration. Upgrade effort is not quantified by the README. The recent release list shows `v4.0.1` on 2026-10-02, following `v3.0.9` on 2026-05-14 and `v3.0.8` on 2026-05-12. The last push was on 2026-10-14, so the project is not archived, but the README does not define a formal support policy for older versions.

## DevDb Compared with a Separate Database Client

The practical alternative is a standalone database client that asks the developer to select an engine, enter a host, choose a port, and manage credentials before browsing data. DevDb takes a different approach. It starts from the project already open in the editor, detects database setup from framework and deployment files, and places the resulting database panel beside the code.

That difference favors repeated local development tasks. It can remove repeated connection setup and connect table navigation to editor context. It also reduces the need to move between a code editor and a separate administration window when the task is inspecting a record or opening a table referenced by application code.

A standalone client remains the better fit when database administration is the primary job. DevDb's documented feature table concentrates several remote and specialized datastore options behind Pro, while its workspace integration requires a trusted project and includes project tooling execution. The README does not present DevDb as a replacement for server administration, backup management, or arbitrary database operations. Its scope is editor-side development and debugging.

## Practical Boundaries of DevDb

The first limitation is feature segmentation. A developer with a remote PostgreSQL server, Redis instance, ClickHouse database, or DuckDB file may need the Pro edition according to the README's table. Local support does not imply equivalent support for every remote or specialized deployment. The project description also separates ordinary panel access from remote connections, SSH tunnels, TLS, and MongoDB capabilities.

The second limitation is trust. DevDb declares that untrusted workspaces are unsupported because it runs project tooling and reads database configuration. Opening a repository can therefore involve more than displaying a static view of files. The README does not describe a granular trust prompt for each detected configuration source, so repository owners should be aware that the extension expects the workspace to be trusted before using its project-aware behavior.

The third limitation is documentation depth. The README names `.devdbrc` and links to external documentation, but it does not provide a complete configuration schema, error taxonomy, transaction model, or rollback procedure. The project is not archived, and the last push was on 2026-10-14, yet maintenance status alone does not answer those product questions. For a production database, the absence of a documented rollback path is especially important.

## Conclusion

Adopt DevDb when database access is part of day-to-day work in a supported local project and you want an editor-side panel with automatic detection. Do not choose it as a substitute for a dedicated database administration client when you need Pro-only remote services, specialized datastores, or operations outside the documented feature set. Verify first that your datastore is included in the Free column, that the project configuration is detected, and that any credentials in `.devdbrc` are excluded from version control.

## FAQ

### How do I install DevDb in VS Code?

Install DevDb from the VS Code Marketplace or Open VSX. The README states that VS Code 1.90 or later is required, then directs you to open the project and trust the workspace.

### How does DevDb find my database?

DevDb reads project configuration and supports detection for setups including Laravel, Rails, Django, AdonisJS, DDEV, Supabase, Prisma, Drizzle, `docker-compose`, Wrangler, and `DATABASE_URL`. If detection fails, the README says to add a `.devdbrc` file.

### Can DevDb edit and delete database rows?

Yes. The README documents filtering rows, editing values, setting `null`, deleting rows, undo, redo, and save through `Cmd+Z`, `Cmd+Y`, and `Cmd+S` on macOS.

### Does DevDb support remote databases and Redis?

Remote MySQL, MariaDB, PostgreSQL, MongoDB, and Supabase Cloud are listed under Pro. Redis and Valkey are also listed as Pro features, as are several other specialized datastores.

### Can MCP clients query my database with DevDb?

The README says Claude Code, Cursor, Windsurf, and other MCP clients can read the schema and run queries. The MCP server is localhost-only, uses a token, and is read-only by default.

## Sources

- [damms005/devdb-vscode on GitHub](https://github.com/damms005/devdb-vscode)
- [License: MIT](https://github.com/damms005/devdb-vscode/blob/main/LICENSE)
- [Project website](https://marketplace.visualstudio.com/items?itemName=damms005.devdb)
- [README](https://github.com/damms005/devdb-vscode/blob/main/README.md)
- [Releases](https://github.com/damms005/devdb-vscode/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/damms005-devdb-vscode