Developer : connecting your text editor

The /developpeur page

Developer mode opens one more door in your left-hand bar, and nothing else. It grants no permissions: what it lets you read from your text editor is exactly what you already read from the screen, not one document more, not one space more.

Turning it on

In Settings, the Developer mode checkbox. It is off on a new account, and it is set for you alone: your neighbour will not see the menu appear on their side. Your company may have closed the option for everyone; in that case the checkbox says so, and nothing lights up.

This machine's key

One key per machine, named: "laptop", "office desktop". It is displayed only once, at the moment you mint it. That is not a display oversight: the product keeps only its fingerprint, and that is what gives revocation any meaning. If a key could be read back, cutting it would mean nothing to whoever had already read it.

• Lost it? Mint another and cut the old one.
• Eight live keys at most: beyond that, people stop revoking and start hoarding, and a keyring nobody reviews is a keyring nobody cuts.
• A cut key stops at the next call, with no delay.

The connection test

Paste the key back and ask for the test: green or red, straight away. It commits nothing, no tokens consumed, no data moved. Its verdict carries its date and expires after twenty-one hours: a "green" from last week no longer says anything true.

What your editor can do

Three tools, read only: search the corpus, recall your memory, list documents. None of them writes, none of them administers anything. A key sitting in a configuration file, on a machine you carry around, must not be able to suspend an account.