Developer Workflow

Not just stored

Password managers stuff developer resources into a "secure note" text box - a title and a blob of content, with no fields and no structure. Nokuo is different: entry, import, export, copy, and use are all built for developers.

Structured entry

Each resource type has its own field template, not a blob of text:

API key: key, secret, expiry, scope
Database: host, port, db, user, password, sslmode
SSH: private key, port, user, host address
Code snippet: language, tags, content

Enter by field, and you can search and copy by field. No more hunting through a text blob to find which part is the password and which is the port.

Structured resource preview in the workspace

Bulk import

Import is not a single path. The main entry points are workspace packages, official templates, password-vault CSVs, structured config files, and direct paste recognition.

1. Choose an import source

The wizard starts by picking the entry point, then decides how to parse the file.

2. Read a config file or template file

.env, JSON, YAML, SSH Config, official CSV templates, and XLSX templates are all read first and parsed next.

3. Review the parsed result and resolve duplicates

The app turns file content into field cards; if it matches existing items, the review page warns about duplicates and overwrite risk before import.

4. Run the import

Once confirmed, execute the import and inspect the created, updated, and skipped counts.

5. Paste a config block

Loose config snippets do not need to be prepared as files first. Paste them directly and let Nokuo recognize them.

It works well for database connection strings, SSH config, JSON, YAML, .env blocks, and private-key fragments.

Copy a single config

Each config card has a copy menu in the top-right corner. Choose the output format for the current item, then copy it to the clipboard.

Common outputs include:

Database: connection string, .env fragment, JSON.
SSH: SSH config, SSH command, .env fragment, JSON.
API keys, AI configs, websites, panels, accounts, and object storage: .env fragment or JSON.
Code snippets, certificates, and DevAccess entries: plain text, YAML, .env, or JSON.

This is per-item copy, not a full export.

Export a project

Project-level export starts from the workspace toolbar's "Export environment variables" action. It works on the whole project aggregate, not on a single item.

1. Open the export panel

The panel first aggregates every exportable config in the current project.

2. Choose the output format

Switch between .env and Docker Compose. In .env mode you can also choose whether to group by config.

3. Copy or save the result

You can copy the full output or save it as a file on desktop. Docker Compose mode emits an environment: block that can be dropped into a compose file.

Move a workspace package

If you need to migrate the full dev workspace, not just one project, use the workspace package flow.

Export workspace package: generates dev-workspace-package.json with metadata and the full workspace data.
Restore workspace package: importing the JSON shows the project and item counts first, then runs a destructive restore.
This path is for full backups, device migration, or workspace transfer, not for copying individual configs.

Organized for use

Group by project: one group per project, with related resources together.
Filter by type: show only API keys, only databases, only SSH.
Tags: tag across projects (e.g. production, staging).
Quick search: by name, field value, or tag.
Recent: jump back to recently used resources.
Resource templates: start a new resource from a field template instead of from scratch.

Daily rhythm

The desktop workflow is built around "unlock when you need it, lock when you're done":

Unlock the Vault: unlock your local Vault with the master password.
Find a resource: locate it by project, type, or tag.
Copy and use: copy a field into the terminal, editor, or CI config, then drop plaintext when done.
Lock when done: lock the Vault on leave so secrets don't linger in clipboard or memory.

Security habits

Lock the Vault before stepping away.
Clear the clipboard soon after copying sensitive content.
Don't paste plaintext secrets into chat or docs; pull from the Vault instead.
Periodically review which resources are no longer in use and clean them up.