Key view

functional

Open a key as a view: header strip, paged value, and per-type edits that show the exact command before they run.

The key view opens a Redis key as a real view rather than a query result: a header strip with the key's type, time to live, internal encoding, memory footprint and length, the value below it in pages, and the edits the key's type allows - each one shown as the exact command before it runs. Double-click a key in the explorer, or right-click it and choose Open Value; the view opens on the key's own server and logical database, whichever tab is active. Redis Key View… in the command palette opens the same view on the active connection with a box to type a key name into.

What you see

Header strip - type, TTL (as 1h 2m plus the seconds, or no expiry), encoding, memory as the server measures it (or not measured when the server or your user cannot run MEMORY USAGE), and the length: bytes for a string, fields for a hash, elements for a list, members for a set or sorted set, entries for a stream, top-level keys for a JSON document.
The value, paged - a hash, list, set, sorted set or stream loads 1,000 fields, elements, members or entries at a time and the title says how many of the total are on screen (showing 1,000 of 48,213 fields); Load more appends the next page and Refresh reloads the key from the start. A string longer than 1 MB loads in 1 MB windows and reports its full length. A JSON document loads whole.
The selected value - click a row to see its value under the grid with the same Auto / UTF-8 / JSON / Hex / MessagePack picker the value viewer has; the choice is remembered for that key across restarts, exactly as it is when you open the key in a query tab.

Redis key view: the header strip, a paged hash with the selected field's value below it, and the Add field form showing the exact HSET before Run.

Editing by type

Type	Buttons	Command that runs
string	Edit value…	`SET key value`, with `KEEPTTL` ticked by default when the key has an expiry, so editing a value does not silently make it permanent
hash	Add field…, Edit selected…, Delete selected…	`HSET key field value` / `HDEL key field`
list	Set selected…, Push to head…, Push to tail…, Remove selected…	`LSET key index value` / `LPUSH` / `RPUSH` / `LREM key 1 value` - the form says that LREM removes by value, not position
set	Add member…, Remove selected…	`SADD key member` / `SREM key member`
sorted set	Add member…, Edit score of selected…, Remove selected…	`ZADD key score member` / `ZADD key XX score member` / `ZREM key member`
JSON	Edit document…	`JSON.SET key $ document`
stream	Entries, Groups, Consumers and Pending tabs	`XADD`, `XDEL`, `XTRIM`, `XGROUP CREATE` / `DESTROY`, `XACK`, `XCLAIM`, `XAUTOCLAIM` - see Streams and consumer groups

Every form shows the exact command it will run, updated as you type, and nothing runs until you press Run. The view carries the same guards as a query tab: a connection marked read-only, or a production connection whose writes are locked, refuses every edit and says so (unlock writes from the status-bar chip, then run); and when the connection's safety settings would make a query tab confirm a data change - an unlocked production connection, or Confirm data changes on the connection - the button turns into Confirm Run and asks for a second click on the command shown. After a successful edit the key reloads from the start, so the header and the grid show what the server now holds.

Values are bytes, never numbers. A value such as 00014, a 20-digit identifier or 1e309 is shown and written back exactly as it is stored; the view never turns a value into a number on the way through. A value that is not valid text is shown as hex, and the edit form switches to hex mode so you edit the bytes themselves; tick Value is hex yourself to enter binary bytes (ff 00 0a) for any value. Scores on a sorted set are passed to the server as the text you type.

A string longer than 1 MB is not edited in the view: load the whole value to see it, and change it with SET or SETRANGE in a query tab. Open in Query Tab on a key's menu keeps the earlier behaviour - the type's read command (GET, HGETALL, LRANGE, SMEMBERS, ZRANGE … WITHSCORES, XRANGE, JSON.GET) runs in a new tab - and Copy Command copies it.