Changelog
Changelog
What changed in each version of Sextant, including changes to permissions, privacy, network behaviour and stored data.
Published releases
Every published version, with the SHA-256 of the package that was uploaded and its software bill of materials.
| Version | Date | Package SHA-256 | SBOM |
|---|---|---|---|
| 1.1.1 | 2026-10-26 | 15a58d93c2c355b3189b3bba3bd7fea935b56c141e9963a29540d064a8492b8b | 645f197c2bb9d92d5d6799dd09036c0c311d7cbf3623313654f464f13e529b75 |
| 1.1.0 | 2026-10-25 | 2ee8a7423761100683ac8c558e3f01e8818b8bdb12f3e2f568775b57fd44b472 | 17fce56c97fc98c7268d14c0d09982f09c378fb46fefcc55732424e5ca920eb9 |
| 1.0.1 | 2026-09-29 | 0c7eca5b04bf05a78dd749183912041dd031ee8a8b0656ff439b8bd9ca9db03e | ccc8152bd183ac7fb85073b816451d157c3489259f166f82b6cad14c74fefd27 |
| 1.0.0 | 2026-09-28 | b1988e3fa33378a3aac65874ce251bad096dcc0aa2fe46c5e45c268f9551a808 | 06cd4b4eb52dfbc6d1604609f42b768ebea9d306f292c2878eacd288fca6719c |
1.1.1 2026-10-26
Sextant does much less work when you move between records in a large org, uses less memory, and can hand a translation problem to your team's tracker as text.
Added
- Lighter when you move between records in a large org. Each time a page shows an object Sextant has not read recently, it reads that page's metadata and saves it. Saving used to go through everything Sextant knew about the org, several times; it now touches only what changed, and does nothing when nothing changed. Measured on a synthetic org of 94,000 components: from about 1.5–2.9 seconds of background work per save to about 0.6 seconds. Real orgs differ; this is the part of Sextant that grew with the size of the org.
- Translate All on large orgs. Text on the page that is not a label (record values, names, dates) is now ruled out at once instead of being compared with everything Sextant knows. On the same synthetic org, marking a page went from about 30 seconds of background work to under half a second.
- Copy as issue. In the Inspector, under a component's translations: copies its name, API name, type, org and Setup link, and its values in your languages, as text for Jira, Azure DevOps, Teams or an e-mail. Nothing is sent anywhere; it goes to your clipboard.
Changed
- Uses less memory for the same answers: the lookup behind hover and Translate All is about a tenth of the size it was on a large org.
- Translate All keeps up on pages that never stop changing (a ticking clock, a spinner) instead of waiting for them to settle.
Fixed
- After hovering a label, Sextant no longer keeps that part of the page alive in memory once you let go of Shift.
- In the comparison, the summary's tiles sit two to a row on a narrow screen instead of one per row.
- The guided tour of the online demo no longer reports a step ready while its highlight is still moving.
Privacy
- Nothing new is collected or sent anywhere. Copy as issue writes only to your clipboard, and leaves out the page's address and any record data.
Storage
- Sextant now keeps an org's revision bookkeeping beside its index instead of inside it, so reading the small part no longer reads the large one. Existing data is converted the first time Sextant saves for that org; nothing is lost and nothing needs to be done.
Known issues
- The Japanese interface has not been reviewed by a native speaker. Dates still follow your computer's settings, a few messages that come from Salesforce or from Sextant's background work are still in English, and lists are joined with commas.
- With the default setting, Search on an org you have not used Sextant on yet starts complete only once you open it: the first opening shows what is already read and fills in as the org is read.
- Editing covers Custom Labels, custom (
__c) fields and their picklist values, global value sets, record types, custom buttons and links, quick actions, layout sections, custom tabs and apps. Object labels, related lists, field help text and text inside flows are read-only for now; standard buttons and the record page's standard tabs are Salesforce's own translations and stay read-only. - Text inside a Flow is not identified, on hover or in Search: Salesforce puts nothing on the page that ties it to its metadata, and Sextant does not guess.
- A save through the Metadata API takes about a minute, almost all of it Salesforce's own deploy queue. Custom Labels use a faster path.
- Not validated against Professional Edition or orgs using API Access Control restrictions.
- The performance figures above come from a synthetic org; how much a given org gains depends on its size and how its pages are built.
1.1.0 2026-10-25
Sextant stays out of Salesforce's way when you are not using it, the interface is available in Japanese, and comparing translations across orgs shows what is missing from an org.
Added
- Lighter on Salesforce when you are not using Sextant. An open Salesforce tab now makes Sextant read only what hovering on that page needs: the page's own metadata and your Custom Labels. The rest of an org (the full catalog that Search uses, translation checks, change checks) is read while you use Search, the Workspace or Activity on that org, and for a quarter of an hour after. Sextant also no longer copies what it saves into every open Salesforce tab, no longer checks the page's address twice a second, and does nothing in tabs you are not looking at until you switch to them. Measured on a heavy test page with three Salesforce tabs left idle for two minutes, the processor time of Sextant's background work fell from about half a second to a few hundredths, the browser's own work returned to what it is without Sextant, and nothing was written to storage.
- The interface in Japanese. Choose Japanese in Settings → Interface language. It uses Salesforce's own Japanese names for Custom Labels, Translation Workbench, picklist values and the rest, so what Sextant says matches what a Japanese Setup shows. The Japanese translation has not yet been reviewed by a native speaker, and Sextant says so where you choose it; Automatic still means English.
- Comparing translations across orgs shows what is not in an org. A component that exists in one org and not in another (a field in development that never reached UAT) is now shown as not in this org, in the table, in the sentence that explains each row and in the export. The comparison can also be downloaded as a CSV file that opens correctly in Excel, in every language.
Changed
- Keep reading orgs in the background (Settings → On the Salesforce page) brings back the previous behaviour for anyone who wants Search complete before opening it, at the cost of more requests while Salesforce is open.
- Language names, the page language and Japanese text are set correctly for Japanese, so kanji use Japanese glyph forms.
- The organisation picker in the comparison now shows which orgs can be compared (those read whole), and when.
Fixed
- Typing Japanese, Chinese or Korean no longer saves or closes things by accident. Pressing Enter to confirm a conversion saved a translation half-typed; Escape under a conversion cancelled the editor or closed the panel around it; confirming a search with Enter opened a result. Keys an input method is still composing with now belong to it, in every editor, search box and panel.
- Thirteen Spanish texts showed
{etiqueta}instead of the component's name (Añadir {etiqueta} a tu Workspace). They show the name. - In the comparison: a lost answer now says nothing was compared and offers Try again (it used to show Comparing… as an error); a table cell containing
|or a line break no longer breaks the Markdown export; an org's missing count matches what its filter shows. - Activity's footnote no longer ends a Japanese sentence with an English full stop.
Privacy
- Nothing new is collected or sent anywhere. Sextant still keeps what it reads on this device only, in the browser's extension storage.
- Salesforce tabs now learn only the names of the settings and stores that changed and read what they show, instead of receiving every value Sextant saves.
Security
- One new internal message lets the on-page Search tell Sextant that you are using it on that page's org. Like every message from a Salesforce page, it is accepted only for the page's own org.
Permissions
- No new permission.
Compatibility
- Same browsers as 1.0.1. On Chrome or Edge versions older than 102, Sextant falls back to checking the page's address periodically, as before.
Known issues
- The Japanese interface has not been reviewed by a native speaker. Dates still follow your computer's settings, a few messages that come from Salesforce or from Sextant's background work are still in English, and lists are joined with commas.
- With the default setting, Search on an org you have not used Sextant on yet starts complete only once you open it: the first opening shows what is already read and fills in as the org is read.
- Editing covers Custom Labels, custom (
__c) fields and their picklist values, global value sets, record types, custom buttons and links, quick actions, layout sections, custom tabs and apps. Object labels, related lists, field help text and text inside flows are read-only for now; standard buttons and the record page's standard tabs are Salesforce's own translations and stay read-only. - Text inside a Flow is not identified, on hover or in Search: Salesforce puts nothing on the page that ties it to its metadata, and Sextant does not guess.
- A save through the Metadata API takes about a minute, almost all of it Salesforce's own deploy queue. Custom Labels use a faster path.
- Not validated against Professional Edition or orgs using API Access Control restrictions.
1.0.1 2026-09-29
Every key you type reaches Sextant on a Salesforce page, Refresh recovers after a lost connection and waits for slower orgs, Search answers however soon you start typing, and paste is paste again in New Custom Labels.
Fixed
- Every key reaches Sextant's text fields on a Salesforce page. Salesforce's own single-key shortcuts —
eto edit the record,/to search, and others in console apps — were taking letters typed into the hover editor, Translate All and Search, most visiblye. What you type into Sextant now stays in Sextant; Salesforce's shortcuts keep working everywhere else on the page. - Search no longer gets stuck while the org's index loads. Typing before the index had finished loading left Search on Reading this org's index…, without answers, until it was closed. It now answers what you typed as soon as the index is read, over a Salesforce page and in the toolbar menu alike.
- Refresh works on the first press after the connection to Salesforce comes back. The first Refresh after a lost connection could finish with most of its checks skipped and had to be pressed again. It now checks the connection first: if Salesforce answers, the Refresh runs in full; if it still does not, the Refresh stops at once and says so.
- Translation Workbench edits are checked on slower orgs. Refresh waited only about 30 seconds for Salesforce to hand over the files that show an edit made in Translation Workbench. On an org that takes longer, every Refresh ended Translation Workbench edits couldn't be checked, and such an edit was never picked up. Refresh now waits as long as Salesforce is working on them.
- A Refresh that loses the connection says it couldn't refresh. It used to finish as a partial check that named whichever part came first; now it says Couldn't refresh and keeps showing the last read. A Refresh that finds nothing changed is still Up to date.
- Paste is paste again in New Custom Labels. Ctrl+V (Cmd+V on a Mac) in the grid could be taken for a spreadsheet import: a value with a
|was split into columns, one cell copied from Excel replaced the rows below, and two lines of text were refused as not being a spreadsheet. Pasting into a cell now always pastes the text. To bring in rows from Excel or Google Sheets, use Paste from spreadsheet: the rows are added after the ones already in the grid.
Known issues
- Editing covers Custom Labels, custom (
__c) fields and their picklist values, global value sets, record types, custom buttons and links, quick actions, layout sections, custom tabs and apps. Object labels, related lists, field help text and text inside flows are read-only for now; standard buttons and the record page's standard tabs are Salesforce's own translations and stay read-only. - Text inside a Flow is not identified, on hover or in Search: Salesforce puts nothing on the page that ties it to its metadata, and Sextant does not guess. The flow itself is found in Search by its name.
- A save through the Metadata API takes about a minute, almost all of it Salesforce's own deploy queue. Custom Labels use a faster path.
- Not validated against Professional Edition or orgs using API Access Control restrictions.
1.0.0 2026-09-28
The first public release. Sextant answers one question from the Salesforce page itself — what is this text, and what does it say in every other language? — and keeps track of what changed.
Added
- Hold-to-inspect hover. Point at any label, field, button or picklist value in Lightning and see what metadata it is, its API name, and its translations in the languages you choose. One answer or none: where a string cannot be identified with confidence, Sextant shows nothing instead of offering a list of guesses.
- Edit in place for Custom Labels, custom (
__c) fields and custom picklist values, with every save re-reading the org's current value first so a colleague's more recent edit is never silently overwritten. When Salesforce refuses a write, you see the org's own message. - Translate All annotates every translatable element on the page at once, filters to Missing, Identical or Complete, and steps through the issues with the page scrolling to each in turn.
- Search goes from a translated string — the one quoted in the ticket — back to the component it belongs to, across the org's metadata rather than only its translatable slice.
- Workspace captures every edit automatically, with before/after history, a
package.xmlexport ready to deploy, and a portable export of the whole session. A component you kept is marked when it moves in the org after you captured it, naming the language that changed. - Activity shows what has happened in the org, built from evidence rather than inference, and notices a deployment landing — including one this browser did not start. You choose how long it remembers (7, 30 or 180 days, or until you delete it), and, when you ask, it imports Salesforce's own Setup Audit Trail into a separate panel: who changed what in Setup and when, in Salesforce's words, kept apart from what Sextant observed.
- Compare environments: one component across several orgs as a table, with a consensus value and an exception set; two reads of the same org over time, always stating which two moments are compared.
- Create Custom Labels with their translations in one grid, checked against the org as you type.
- Settings → Privacy & security. See what Sextant keeps in your browser and how much space it uses, export it (never with your Salesforce session), delete it by scope, and read every permission Sextant asks for and why.
- Light, Dark and System themes; English and Spanish.
Changed
- The index says how old it is and how much of the org it covered, rather than implying freshness it cannot vouch for. Large orgs are read incrementally and the read resumes across browser restarts.
- Saving straight to a production org always asks first. Don't ask me again does not apply to a production org, or to an org Sextant has not identified yet.
- Automatic interface language. A new install follows the browser's language when Sextant has it; choosing a language in Settings keeps that choice.
- New metadata appears without a full read. Coming back to Sextant or opening its toolbar menu asks Salesforce what changed since the last read and reads again only what changed — a field created a minute ago appears in Search once that one object has been read, not after the next full read of the org.
- Refresh makes the org current. After it succeeds, every kind of metadata Sextant supports is current for that org — including deleted components, translations edited in Translation Workbench and standard picklist values, which no change record reports — or it names what it could not check. Its progress never goes backwards, and it can be stopped.
- Search filters by Picklist Value, and a field's help text no longer takes the field's place in the results.
- Absence is distinguished from failure throughout: "there is nothing here" and "we could not find out" are different sentences, never the same empty state. A translation Sextant has not read yet says Not read yet or Checking… until it has.
Fixed
- Activity no longer attributes a colleague's change to you because you had pinned the component.
- The Workspace's search box matches the label you see on the row, not only its API name.
- API names and object names no longer clip mid-word in rows that have room for them.
- The Workspace's row summaries follow the interface language.
- Search finds every value of a custom picklist — including values your profile cannot see, inactive values, and the values of the global value set a field uses — not only the ones Salesforce showed your own profile.
Privacy
- No backend, no account, no telemetry, no analytics, no third-party requests. The only host Sextant contacts is your own Salesforce org, using your own session, making the requests Setup already makes. Everything Sextant keeps stays in this browser profile.
- The privacy policy (version 6) covers the extension, the website and the interactive demo, in English and Spanish, and a generated
DATA_HANDLING.mdlists every item Sextant stores.
Security
- The browser enforces where Sextant can send requests. A content security policy limits Sextant's pages and background process to Salesforce, and forbids scripts from anywhere else and string evaluation. It is verified in a real browser on every release build.
- Every request is checked against the org it belongs to before your session is attached; the session is never written to storage, logs, messages or exports.
- Messages to Sextant's background process are checked against their sender; imported files are size-limited and validated field by field; links built from org data are validated before they open.
- Developer diagnostics are off until you turn them on and strip anything shaped like a credential.
Permissions
storage,unlimitedStorage,activeTab,cookies,alarms, and access to*.lightning.force.com,*.my.salesforce.comand*.salesforce.com. What each one is for, and what it does not do, is inPERMISSIONS.md.- The
tabspermission — the one that makes Chrome say read your browsing history — is not requested. The toolbar menu names the org you are looking at through Sextant's Salesforce site access alone, which a browser test verifies on every release build.
Compatibility
- Chrome or Edge (Chromium), Manifest V3. Lightning Experience only; Sextant does not run in Classic.
- API Enabled on your user, and Setup → Session Settings → "Lock sessions to the domain in which they were first used" disabled — with it on, the background process's session is rejected, which is the most common reason a fresh install appears not to connect.
- Translation Workbench enabled, with at least one language, for translation data to exist at all.
Known issues
- Editing covers Custom Labels, custom (
__c) fields and their picklist values, global value sets, record types, custom buttons and links, quick actions, layout sections, custom tabs and apps. Object labels, related lists, field help text and text inside flows are read-only for now; standard buttons and the record page's standard tabs are Salesforce's own translations and stay read-only. - Text inside a Flow is not identified, on hover or in Search: Salesforce puts nothing on the page that ties it to its metadata, and Sextant does not guess. The flow itself is found in Search by its name.
- A save through the Metadata API takes about a minute, almost all of it Salesforce's own deploy queue. Custom Labels use a faster path.
- Not validated against Professional Edition or orgs using API Access Control restrictions.