Changelog

What’s new in DynoTable

1.22.0

Highlights

  • On-demand backups in the Table dialog. Settings → On-demand backups lists a table's backups, yours and DynamoDB's system backups, newest first, with name, time and size. Create backup takes one with a generated name, and its row turns from Creating… to available without reopening the dialog. Delete a backup you made after a confirm. Restoring a backup stays in the AWS console or CLI. How backups and point-in-time recovery work.

Added

  • Set the point-in-time recovery period. Pick 1 to 35 days. Shortening it asks first, because DynamoDB deletes the older restore points. Lengthening it applies directly.
  • See what survives a table delete. Delete table says what DynamoDB keeps: a system backup for 35 days when point-in-time recovery is on, otherwise the backup that is kept, otherwise that no backup or point-in-time recovery was found. You can't delete a table while one of its backups is still being created.
  • A restore point before a direct run. A bulk edit or delete that writes directly cannot be reverted. With point-in-time recovery on, the run summary shows the time to restore the table to. With it off, tick Create a backup first: the run takes a backup, then waits about a minute before it writes, so the backup holds none of its changes. The backup is kept, and billed, until you delete it.

1.21.0

Added

  • DynoTable for Intel Macs. Each release now has two signed, notarized macOS downloads: one for Apple Silicon and one for Intel. An Intel install updates in the app, the same as an Apple Silicon install. If you run the Intel build on an Apple Silicon Mac, its next update installs the Apple Silicon build for you.

1.20.0

Highlights

  • Let your coding agent read your tables. Claude Code, Codex, Cursor and other agents that run shell commands can read the DynamoDB tables and OpenSearch indices of the profiles you make available to them, through the new dynotable-cli and the DynoTable plugin for Claude Code. The agent gets JSON back and never gets your AWS credentials. It only reads: changes still stage and commit in the app, by you. Each table list, index list and query that an agent runs goes into the profile's audit log. It needs Settings → Editor integration switched on. See how it works.

Added

  • Available to agents. The profile switch Expose via MCP is now Available to agents. This one switch sets which profiles MCP clients and dynotable-cli can reach. Switch it off, and a running agent loses the profile at its next request.
  • DynoTable in Neovim. dynotable-lsp gives Neovim, and other editors that start a language server over stdio, DynoTable's completion and live errors for SQL, PartiQL and OpenSearch queries. Neovim is the tested editor.
  • Switch tabs as in a browser. ⌘⇧] (⌘}) goes to the next tab and ⌘⇧[ (⌘{) to the previous one. ⌃Tab and ⌃⇧Tab still work.

Fixed

  • PartiQL value suggestions now also appear after a quoted field name, such as "status" = ', in the app and in your editor.
  • Settings → profile → Activity now shows the newest audit entries first. Before, a long log showed only its oldest entries, and new activity did not appear.

1.19.1

Fixed

  • A SQL statement that filters on a table's key now reads only the matching items when you run it from VS Code or the AI assistant, as its query plan says, instead of scanning the whole table.

1.19.0

Highlights

  • Write and run your DynoTable queries in VS Code. The new DynoTable extension for VS Code, VSCodium, Cursor and Windsurf gives SQL, PartiQL and OpenSearch query files completion from your real tables, indices and fields, live errors with quick fixes, hover, formatting and a results panel. Press ⌘↩ to run the statement under the cursor against any profile, or ⌘⇧↩ to open it in the app. Click a table or index in the DynoTable explorer to start a query on it. Switch on Settings → Editor integration once; after that the extension starts DynoTable in the background when it needs it. Set it up.

Added

  • See the query plan before you run it. Above each statement, the editor shows whether it runs as a Query or a Scan, on which index, and roughly how many items it reads. Rename a table alias and every use of it follows.
  • Install with Chocolatey. On Windows, choco install dynotable installs DynoTable, and the package follows each release.

Fixed

  • In SQL, an attribute you select by name now comes back with the same type as in SELECT *: sets stay sets, precise numbers stay exact and binary stays binary.
  • A SQL join names each column after its table alias, such as o.orderId and c.name, so two columns with the same name no longer collide.
  • SQL results, Smart Tables and their exports show binary attributes as their real bytes instead of [object Object].
  • The OpenSearch index list no longer shows the cluster's own Query Insights record indices.
  • The AI assistant answers "which customers have no orders" questions and per-table item counts correctly.

1.18.0

Highlights

  • Stop switching to OpenSearch Dashboards to check an index. Turn on OpenSearch for a profile and DynoTable lists the domains and Serverless collections your AWS credentials can reach, in ⌘K next to your tables. Open an index like a table: search it in Lucene syntax with field and value autocomplete, narrow it with filters and a time range, and open any document in Quick View or the editor. Document edits go through Pending changes like item edits, and History reverts a commit.
  • Stop picking the GSI by hand. New table tabs start on Auto. Filter for an exact value of an index's partition key, such as status equal to PENDING, and DynoTable runs a Query on that index instead of scanning the table. Auto only picks an index that returns every column you can see. A faster index that would drop columns shows up as a hint you tap, and the tabs you already have keep the index they use.

Added

  • Conflict checks on document edits. The editor opens at once and loads the whole stored document before you can change it. On a managed domain, a commit stops with a conflict if someone changed the document after you opened it, and you rebase onto their version instead of overwriting it. Serverless collections have no version check, so their edits are last-write-wins, and the tab says so. After a commit, the edited document stays where it was in the grid.
  • Search an index by meaning. Vector fields on an index get the same vector search as a DynamoDB table: type a sentence, paste a vector, or right-click a row and pick Find similar. A sentence becomes a vector through the Bedrock embedding model you pick. In the editor a vector folds to one line until you press Show values, and Save regenerates it from the fields you bound it to.
  • Join a table to an index in SQL. The SQL Workbench and Smart Tables read OpenSearch indices next to DynamoDB tables, so one statement can join orders to the index that holds your customers, or run a GROUP BY over an index.
  • The table toolkit works on an index. Bulk edit and bulk delete, export to a file or the clipboard, import a CSV, JSON or NDJSON file, and Compare two documents.
  • Create, tune and delete indices. Pick New index in ⌘K. An index's dialog shows its mapping and per-field stats, changes replicas and the refresh interval on a managed domain, and deletes the index once you type its name. Export as code copies an index's definition as a REST request or Terraform.
  • The AI assistant and MCP clients reach your indices. They read an index's mapping, search it, run SQL across both engines and stage document changes. Nothing they do writes to an index until you commit it.
  • Choose the engines per profile. A profile uses DynamoDB, OpenSearch or both, set under Engines in its settings. A profile from an earlier version asks once when it finds OpenSearch, and stays DynamoDB-only until you say yes.
  • Filter by date range. Pick a preset such as Last 24 hours, or a custom range, on a date field. A preset slides forward each time you run the query. On a DynamoDB table, mark an attribute as a date from its column's Format menu first; the TTL attribute already counts as one.

1.17.0

Highlights

  • Join a table to itself in Smart Tables. Pick the same table on both sides of Add relationship, for example employees with managerId to employeeId, and each employee row shows their manager's columns beside their own. The joined columns get a label from the attribute (manager), and you can rename it from the relationship on the canvas.

Added

  • Self-joins in the SQL Workbench. FROM employees e JOIN employees m ON e.managerId = m.employeeId now runs. The joined side follows the same rule as any join: it must be keyed by the join attribute.
  • Self-joins in exports and the AI assistant. Exports carry the joined columns under their label, and the AI assistant can build a self-join Smart Table for you.

Fixed

  • The MCP connect snippets for Cursor, VS Code and opencode now go to your user-level settings instead of a project file you might commit, and the Claude Code command is quoted so zsh runs it as written.

1.16.2

Highlights

  • Filtered export to Amazon S3. Send the items your query matches straight to your own S3 bucket. DynamoDB writes them from the table's point-in-time recovery backup, so the export uses no read capacity on a busy table, and Activity tracks it until it lands.
  • Point-in-time recovery in the Table dialog. See whether a table can be restored and from when, and turn point-in-time recovery on or off without leaving DynoTable.

Added

  • A two-step export dialog. Pick File, Clipboard or S3 first, with 1, 2 or 3, then set only the options that destination needs.
  • ⌘↩ presses a dialog's main button. The primary button in a dialog shows the shortcut and answers it from anywhere in the dialog.
  • aws login sessions. Profiles signed in with aws login just work, and Sign in renews the session when it lapses.
  • Binary values in Plain mode. The item editor shows a binary attribute as {"B": "<base64>"} and saves it back as binary.
  • The AI assistant can export to S3. It asks before every S3 export, even in Full Auto.
  • Claude Haiku 5.5 in the AI assistant. Pick it in the model picker on Amazon Bedrock.

Fixed

  • Saving an item in Plain mode no longer turns its binary attributes into strings.
  • Sign in and Reconnect now sit at the top of the sidebar.

1.14.0

Highlights

  • Bulk edit and bulk delete. Set, remove or add to an attribute, or delete the items, across the rows you select or every item your query matches. By default the changes land in Pending changes, where you review each item's diff, commit all or some of it, and revert later from History.
  • Compare two items. Select two rows to see them side by side, read fresh from the table, with every differing attribute marked. Copy a value from one item to the other and it is staged for review like any other edit.

Added

  • Direct bulk writes for large runs. When a run is too big to review item by item, write the edits or deletes straight to DynamoDB instead, with no item limit. Safe mode only changes items that still match your query; the run shows progress in Activity and can be stopped and resumed.
  • Export a table definition as code. Turn any table, with its indexes, TTL and settings, into Terraform, AWS CDK or CloudFormation from the Table dialog.
  • Global table replicas. See, add and remove a table's replica Regions from the Table dialog.
  • Claude Sonnet 5.5 in the AI assistant. The model picker now shows the newest model of each family, with older versions under More models.
  • Readable maps in Document view. Nested maps and lists show as indented JSON, and a link takes you to that value in the JSON view.

Fixed

  • Help → Learn More now opens the DynoTable docs.
  • Staging and history stay fast with thousands of pending changes.

1.13.0

Highlights

  • Claude Opus 5.5 and GPT-6 in the AI assistant. Claude Opus 5.5, GPT-6 Sol and GPT-6 Luna appear in the model picker wherever your Bedrock region offers them. GPT-6 Luna joins the default set: it works through a join across two tables, a follow-up breakdown and the edits you ask it to stage, at one of the lowest prices in the picker.

Added

  • Instant now means no thinking for GPT models. Choosing Instant in the thinking picker for a GPT-6 or GPT-5.6 turn stops the model reasoning. Before, these models kept thinking by default and you paid for it.
  • Autocomplete uses the values it can see. When a column's stored values are known, autocomplete completes one of them instead of leaving the line blank. It still leaves it blank rather than invent a table, column or value it has never seen.

Fixed

  • Extended thinking on Claude Opus 4.7 and Opus 4.8 no longer fails with an error.
  • Autocomplete and Test connection work again with Claude Opus 4.7 and newer, and with Claude Sonnet 5.
  • A GPT-5.6 model reached through a cross-region inference profile now honors the thinking level you pick.

1.12.0

Highlights

  • Add and remove attributes without leaving the form. Document view now has an add row at the bottom: type a name, pick String, Number or Boolean, press Enter, and the new field is on the item ready to fill in. The names DynoTable has already seen on that table are offered as you type, and a known column comes with its type filled in. Hover any field to remove it, or right-click it. Lists, sets, maps and binary values are still authored in the JSON views.

Added

  • Filter on a nested attribute. The filter pill's column picker now offers the fields inside your maps — address.city, at any depth — and the filter reaches the nested value instead of matching nothing. The same paths are offered when you choose which attributes an embedding is built from, so a table whose text lives inside a map can be searched by meaning too, and a bulk import embeds from those nested fields as well. One limit up front: Export code can't yet turn a nested filter into a snippet, and says so rather than emitting a wrong one.
  • One spelling for every type. Wherever the app names a DynamoDB type — a filter's type picker, a key type in the index and create-table forms, the column header menu, the indexed-fields list, the import preview — it reads the same way, String (S), in that type's colour.
  • Exported code queries the right region. The snippet from Export code now pins the client to the region the rows on screen came from, so it can't quietly run against a different copy of the table.

Fixed

  • The query cost strip now shows compact figures (~15.5M items) instead of eight digits pushing the operation name off the edge.
  • Document view polish: the add row's type picker keeps its width whatever you choose, its Cancel is the same × the field rows use, and the helper text under a field is easier to read.

1.11.0

Highlights

  • Search a DynamoDB table by meaning. Create a vector index on the table, name the embedding model and the attributes its text comes from, and every save keeps the embedding in step with the item — no copying the table into a second database and keeping the two in sync. Then type a sentence and read the ranked results, paste a raw vector, or right-click a row and pick Find similar to search using that row's own embedding. Two honest limits up front: a new index scans the whole table before it can answer anything, so expect minutes rather than seconds, and it needs a real table — local DynamoDB has no vector search to offer. Turning your words into a vector uses the Bedrock model you configured in Settings; searching with a vector you already have does not.

Added

  • The assistant searches by meaning too. Ask it in plain language and it searches the same vector index and answers from the rows it found, so a question like "which of these articles cover retries?" doesn't have to become a query first.
  • Edit an item as a form. Document view lays an item out field by field and gives each value the control it deserves: a calendar for a date, a switch for a boolean, chips for a set or a list, a growing box for a paragraph. It suggests values from the ones already in that column, and it works on every table.
  • The editor stops printing a thousand numbers. An indexed embedding is summarised where it sits, so an item you can actually read isn't buried under floats. Press Show values when you want to see them.
  • Import can embed while it writes. Turn it on for a run and each row gets its embedding as it lands. A row that can't be embedded is still written, and counted for you, rather than dropped.
  • Attributes read as words, not wire codes. Types are named and colour-coded wherever the app lists them, the key, TTL and vector marks carry a tooltip saying what they mean, and the index forms complete attribute names from the columns DynoTable has already seen.

Fixed

  • Top K now survives switching to a different vector index instead of resetting on you.
  • Deleting a table closes every view of it, not just the tab you deleted it from, and those views no longer come back from reopen history.
  • A long attribute name no longer starves the field next to it — filter pills, pickers and dropdown options now truncate it and stay readable.
  • The model picker no longer flags a model as unavailable while it is still loading the list, and models AWS publishes only as a cross-region profile now work instead of failing with an invalid-model error.
  • The assistant no longer loses a turn when a tool reads an item containing a DynamoDB set.
  • Form polish across the app: buttons match the height of the inputs beside them, every single-line input is the same height, the table's Settings dialog closes from the corner like every other dialog, and anything clickable shows the pointer cursor.

1.10.0

Highlights

  • Import data into a table. Drop a CSV, JSON or NDJSON file onto any table — or pick one from the toolbar — and DynoTable shows you what it will write before it writes anything: every column, the type it inferred for it, and the first rows laid out in the same grid you already read your data in. Adjust whatever looks wrong, then import.

Added

  • Fix the types before you commit to them. Right-click any column in the preview to change its type or rename the attribute it lands in. A warehouse code that happens to look like a number stays text if you say so — and what you see in the preview is what gets written.
  • A bad file is caught before a single row is sent. DynoTable reads the whole file through first and lists what it found — a duplicate key, a repeated header, a value that doesn't fit the column — pointing at the row each problem came from, so you fix the file instead of cleaning up after it.
  • Exports come back exactly as they left. A JSON or NDJSON file exported in DynamoDB's own format re-imports with no type guessing and no precision lost, which makes export → edit → import a safe round trip.
  • Imports run in the background and report progress in the Activity panel next to your exports, so a large file loads while you keep working.

Fixed

  • Switching tabs no longer flashes a half-drawn toolbar before the tab you picked appears.
  • The Activity panel now tells you plainly when a run was refused or stopped, instead of leaving a progress bar that never finishes.

1.9.0

Highlights

  • Create a table without leaving DynoTable. Right-click the sidebar or hit ⌘K and pick Create table: give it a name, a partition key and an optional sort key, choose on-demand or provisioned capacity, and it opens in a tab ready to use. Combinations DynamoDB would reject — a sort key that repeats the partition key, provisioned capacity with no read/write units — are caught before anything is sent, with a message that names the problem.

Added

  • Everything about a table now lives behind a single Settings button in the table toolbar, with five sections: Overview, Indexing, Secondary indexes, Settings and AI context. One button, one place to look.
  • Overview is now a real overview: item and size estimates, the primary key, every secondary index listed inline with its keys and size, and the table's status, capacity mode, region, TTL and deletion protection at a glance. A Manage link takes you across when you want to add or remove an index.
  • Indexing gets its own section, so the build status of the field index that powers search and autocomplete sits next to the fields it has discovered — instead of competing with the rest of the table's details for room.

Fixed

  • Controls in table settings now line up. Buttons match the height of the field beside them, the capacity and TTL fields share one width, and the TTL attribute name is no longer cut off.

1.8.0

Highlights

  • Every write now has an undo. DynoTable keeps a history of every write it makes to your tables — edits, PartiQL statements, batch deletes. Open the new History tab in Pending changes to see what changed, when, and exactly what each attribute looked like before and after. Hit Revert to stage the exact inverse, review it, and commit — even for a whole batch delete. If someone else changed the item in the meantime, DynoTable tells you instead of overwriting their work.

Added

  • PartiQL INSERT, UPDATE and DELETE now go through the same review flow as item edits. The run button becomes a Stage & Commit / Stage choice: write immediately in one gesture, or hold the change in Pending changes to review the diff first. Either way the write lands in your history.
  • Statements that can't be staged are flagged while you type, with the exact part of the statement underlined and a plain explanation of what to do instead. Updates to nested attributes like profile.address.city are fully supported.
  • History groups changes by commit, shows how each write was made — an edit, a PartiQL statement (with the statement itself), the AI assistant, or a batch delete — and lets you revert a single item or the whole commit in one click.
  • Batch deletes record every deleted item in full, so "Revert all" brings them back exactly as they were.

Fixed

  • A PartiQL write could re-run in rare situations after its first execution. Writes now execute exactly once, always.

1.7.0

Highlights

  • GPT-5.6 is in the model picker. Choose OpenAI's GPT-5.6 Luna for the AI assistant alongside Claude and Nova, on any AWS profile in a US region that offers it. The model needs its own AWS Marketplace subscription — until that's active DynoTable tells you so, instead of handing you a bare authorization error.

Added

  • Two more GPT-5.6 variants, Sol and Terra, are available behind Show unverified in Settings → AI. They haven't been through the full test suite the other models have, so they stay out of the picker until you ask for them.
  • Test Connection now probes the model you actually picked, over the same connection the assistant uses — a green result means that model answers, not just that your credentials are valid.

Fixed

  • The assistant repairs a mis-capitalized table name instead of insisting the table doesn't exist. DynamoDB table names are case-sensitive; when exactly one of your tables differs only in case, it uses that one and carries on. When none match, it shows you the table names you actually have rather than retrying a dead end.
  • It no longer reports a table as missing when it simply couldn't read your table list — a permissions problem now reads as one.
  • Asking about the current tab when nothing is open sends the assistant to go find what you meant, instead of guessing a table or stopping to ask.
  • Looking up an item by a key that doesn't match now tells the assistant what was wrong with the key, so it corrects the lookup instead of reporting "not found" as fact.

1.6.0

Highlights

  • Undo a filter, not just a closed tab. Cleared the wrong pill? Switched index by mistake? ⌘Z now takes back the last filter change on the table you're looking at and re-runs the query to match — the same key that already brought back closed tabs. It knows which you meant: whichever you did most recently is what it undoes, so the safety net on closing tabs and folder rows is untouched. ⌘⇧Z puts the change back.

Added

  • Filters the AI assistant sets are undoable the same way. Ask it to narrow a table, don't like the result, press ⌘Z.
  • One filter change costs exactly one ⌘Z — typing a value is a single step to undo, not one per keystroke.
  • Undo won't run a query the Run button would refuse; if a restored filter isn't executable yet, it comes back for you to finish rather than firing.

Fixed

  • The AI assistant no longer calls rows sorted when they aren't. When a sort can't be applied to the table or index in question, it either finds one that can sort or tells you plainly the view is unsorted — instead of quietly dropping the sort and describing the rows as newest-first anyway.

1.5.0

Highlights

  • Timestamps, shown your way. Pick 24-hour or AM/PM, and choose the time zone your stored timestamps should be read in — DynoTable applies both everywhere it shows a time. They sit in Settings → Appearance, next to Theme and Language, with a live sample so you can see the effect as you choose. Switch language and everything re-formats to match.
  • See how long ago, not just when. Any column holding a date or timestamp can now be shown as a relative time — "3 days ago" instead of a full timestamp. It's a per-column choice in the column header's Format menu, offered anywhere the Date format is.

Added

  • The export dialog now offers every column the grid does. A sparse attribute you could tick in the table but not at export time is available in both places now.
  • Your export column selection is remembered instead of being dropped.

Fixed

  • Saved Workbench SQL could be lost when the app started.
  • The Welcome Screen could take over while tabs were still open, and a single unreadable tab could take the rest down with it.
  • Tables briefly claimed to be empty before their first query had run.
  • Batch delete offered to confirm a deletion that would have removed nothing.
  • The AI assistant's inline suggestions showed nothing at all with some models, and its explanations could end up inside the SQL editor.
  • The AI assistant now declines a Smart Table join when the values don't actually connect, instead of building one that renders blank.

1.4.0

Highlights

  • Closed the wrong tab? Take it back. When you're not typing in an editor, ⌘Z brings back the tab you just closed, and ⌘⇧T reopens tabs one after another. Because closing is now reversible, DynoTable no longer stops to ask you to confirm it — you just close things and carry on.
  • Open links straight from your data. ⌘-click a URL in your table (Ctrl-click on Windows and Linux) and it opens in your browser. It works in every column format, and anywhere a URL appears in the item editor.

Added

  • Dropping a tab from a folder is undoable too, and no longer asks first. ⌘Z puts it back in the same folder, in the same position. Deleting a whole folder is still final, and still confirms.

Fixed

  • "Filter" appeared in English in six languages.
  • The label on the query run control no longer gets cut off in languages where it's wider than in English.
  • The AI's suggestion to open a table or query for you now appears in your language.

1.3.0

Highlights

  • Sign in with AWS IAM Identity Center on any plan. SSO now works on the free trial and on every subscription, with no upgrade required. If Identity Center is how your company hands out AWS access, you can start using DynoTable with it straight away.
  • The AI agent works inside the item editor with you. Ask it to read the item you have open, change one field, or rewrite the whole document — including edits you haven't saved yet. It never saves on your behalf: the change lands in the editor and you decide when to commit it.

Added

  • Folders remember the tabs you close. A tab you close inside a folder stays listed there and reopens with one click, so a folder becomes a durable set of the tables you work on rather than only whatever happens to be open.
  • Close a tab or remove it from the folder, straight from the row. Hovering an open row gives you × to close it; a closed row gives you − to drop it from the folder for good. The distinction is the one you actually want once folders keep what you close.
  • Give the AI notes about a specific table. Every table gets its own notes in Table Settings — what its keys mean, which fields matter, anything you'd otherwise re-explain each session. They stay on your machine, and the agent reads them whenever you work on that table.
  • Ask the AI to start a new item for you. It can open the item editor already filled in with a draft, ready for you to review, finish, and save.

Fixed

  • The export toast now names the file you actually saved, instead of the one suggested before you chose a location.
  • Code exported for the DynamoDB Toolbox library now uses your table's real primary key on scans and index queries.
  • The active tab stays visible when you collapse the folder it sits in.
  • Switching profiles no longer risks mixing up your saved tabs and layout.
  • Buttons that start a slow action now respond the moment you click them, instead of looking untouched until the work finishes.
  • Searching for a name that matches no table no longer offers to open it ahead of the matching Create action — typing "Workbench" gets you a Workbench.

1.2.0

Highlights

  • Start your 30-day trial without a credit card. Try everything — SQL, Smart Tables, editing, and the AI agent — and decide afterwards. No card at signup, and none needed when the trial ends.
  • Workbench and Smart Tables are now part of the paid plan. The Free plan keeps browsing, PartiQL queries, filters, and export, and keeps serving read-only data to your coding agent over MCP — with no time limit. SQL joins and aggregations, saved Smart Tables, editing, and the AI agent come with a subscription. Your queries, specs, and layouts are never touched when a trial ends; they're waiting when you subscribe.

Added

  • See the query plan before you run it. When a plan is available, the Workbench preview identifies Scan versus Query and the index. The RCU estimate appears only when table metadata supports it; an ordinary partition Query shows no RCU. The editor also flags N+1 cross-table joins that would fan out into many DynamoDB reads.
  • Export your query as runnable code. Alongside the existing targets, you can now emit a ready-to-run program for the schema-first DynamoDB Toolbox library.
  • Turn AI off completely. One switch in Settings hides every AI surface — the chat, inline edit, autocomplete, and the AI entries in the command palette — for people who'd rather not have it there at all.
  • Open a table you can't list. If your role can read a table but isn't allowed to list them, type its name in the command palette and open it directly.
  • Clearer permission errors. When AWS refuses an action, DynoTable now names the exact permission you're missing instead of showing a raw error.
  • Faster full-table scans. Large scans now fetch several parts of a table at once, so results fill in noticeably sooner.

Fixed

  • Sending a chat message now always scrolls it into view.
  • The format options when exporting as code scroll sideways instead of wrapping onto a second line.
  • Read-only mode is reported reliably — the notice can no longer be swallowed, and the state corrects itself on the next license refresh.

1.1.0

Highlights

  • Know your table at a glance — and get a typed schema for it. Every open table now has a Stats panel: see its primary key, secondary indexes, and item-count and size estimates, index it so autocomplete and filters know your fields, and export an inferred schema as TypeScript, Zod, or JSON Schema.

Added

  • Inferred schema export. From an indexed table, turn your items into a typed schema in three formats — TypeScript, Zod, or JSON Schema — then copy it or save it to a file.
  • Indexed-field browser. The Stats panel lists every field it discovers — including nested ones by dotted path — with its type and whether it's required or optional, and adds a filter once the list grows long.
  • Table size at a glance. Item count, total size, and average item size sit right at the top of the Stats panel.

Fixed

  • Exported schemas no longer repeat a field that was seen more than once, and primary-key attributes are always marked required.

1.0.0

Highlights

  • DynoTable 1.0 — out of beta, officially stable. Our first production-ready release: the fast, keyboard-first way to browse and edit DynamoDB, hardened and reliable enough to be your everyday daily driver. Signed and notarized on macOS, with native Windows and Linux builds.
  • A clearer, quicker AI agent. Every action the agent proposes now carries a keyboard shortcut, and its thinking, steps, and proposals read cleanly as it works.

Added

  • Time-to-live at a glance. Items that expire now show a TTL marker across the data grid, PartiQL and Smart Table results, the item editor, and Flow view — so you can see what's about to expire without digging.
  • Per-column formatting. Render any column as raw text, a number, or a date, and flip any column back to its raw value.
  • A smoother column picker. Key and TTL attributes are marked so they're easy to find, it stays fast on wide tables, and there's no limit on how many columns you can show.
  • Keyboard shortcuts on every AI suggestion — accept, open, or dismiss what the agent proposes without reaching for the mouse.

Fixed

  • The column picker no longer opens blank when reopened, and its search clears correctly.
  • PartiQL now remembers the columns you've chosen to show.

0.4.0

Beta

Highlights

  • Automatic single-table design. DynoTable now recognizes the entity types in your table and lets you filter by them — no configuration, no setup.

Added

  • An entity-type badge on every row, derived automatically from your key prefixes.
  • Faceted filtering — narrow the table to a single entity type in one click.
  • Composite keys are split into readable parts, so multi-part keys are easy to scan.
  • Partition and sort key columns are pinned to the left to keep you oriented as you scroll.

Fixed

  • Re-running a query now keeps your current rows on screen while it refreshes, instead of flashing an empty grid.
  • Steadier streaming — more predictable Load more and Stop behavior on large tables.

0.3.0

Beta

Highlights

  • Saved queries. Name, save, and re-run your queries from a searchable menu — in both PartiQL and the SQL Workbench.

Added

  • Save and rename queries, scoped per table.
  • Searchable history with syntax-highlighted query rows.
  • AI-suggested names for saved queries and tabs.
  • The Workbench runs only when you hit Execute — no surprise full-table scans.

Fixed

  • Switching profiles now preserves your sidebar layout.

0.2.0

Beta

Highlights

  • Heavy SQL stays smooth. JOINs, GROUP BY, and full-table aggregates run without freezing the interface, even on large tables.

Added

  • Exact whole-table aggregates by reading the entire table on demand.
  • Faster, more responsive results for complex Workbench queries.