checking…
Change any of this at any time from You.
desk connect
If that tab does not load, paste the whole address from its bar here.
Name one when asking - “check my personal mail”. Otherwise it uses the mailbox above.
The one folder in your Documents it may save into. It never overwrites a file. Create the folder first; clear the box to withdraw.
The one folder in your OneDrive it may file into. It never overwrites a file. Create the folder first; clear the box to withdraw.
Store your own token and it acts on GitHub as you. Left empty, the shared token is used.
On the projects board: Your assistant → create a key. It is shown once.
In the conversations app: Settings → API tokens. It is shown once.
In Coolify: profile menu → Keys & Tokens → API tokens → Create new token (Read and Deploy is enough). It is shown once.
In hPanel: profile menu → API → New token. It is shown once. The assistant only reads, but the token can change servers: keep it private.
In the expense app: You → Assistant access → Create key. It is shown once. Tick May also approve reports sent to me to approve from here.
In IT Portal: My devices → Assistant access → New assistant key. It is shown once. If you work in IT, tick Also read the IT records to ask about assets and the helpdesk queue as well.
Ask how you slept or how rested you are. Nothing reaches your diary unless you turn it on under Your time.
Create one at cloud.ouraring.com → API Applications with this redirect address:
Then paste its client id and secret. The secret is shown once.
Find photos by what is in them. Create a key on the archive; it is shown once.
Your ownCloud username and an app password, not your sign-in password.
ownCloud 10: Settings → Security. Infinite Scale: App Tokens.
Sign-ins for sites with no API, like a supplier portal you fetch invoices from. The password goes straight into the site's form; the assistant never sees it.
Walk through a portal once and it remembers the steps.
Measured from what the gateway charged rather than estimated from a price list. The chart and lists below cover the period selected.
A conversation keeps its model so the cache survives, so one difficult question early on can bill an entire conversation at the top tier. That appears above as a single conversation with many turns.
Once a week this can assess what your model use cost and what would reduce it, and file the assessment on this deployment's issue tracker for review. None of your content is included: no questions, no conversation titles, no message text - only stages, scores, model names, costs and conversation numbers.
This exceeds the length the tracker accepts, so the per-model and per-stage tables are omitted from what is sent. assistant review prints them in full.
What has been sent
A conversation keeps the model it settled on, because moving discards the cached history and pays for it again. So a short question after a difficult one is answered on the same dear model. It drops back after half an hour idle, and New starts from nothing.
Nothing here is required now, and nothing is lost by closing it. Configuration completed on any other screen counts: this reports what is actually configured, not which buttons were last pressed.
Four questions. Only the first is required by the rest; after that you may stop at any point and return later.
Time is reserved in the gaps between your meetings, and moved when a meeting is booked over it.
09:00-17:00
09:00-12:00, 13:00-17:00
Resume a conversation where it stopped, or search across all of them.
This removes the transcripts. What the assistant has learned is held separately and is retained; see Memory, where each belief can be forgotten individually.
Take notes during a meeting. Nothing entered here is answered or acted on; it is recorded, and at the end becomes a document you can download.
Nothing here has been answered or acted on, including anything the recording captured. Finishing writes it up with no tools at all: it cannot send or book anything.
Work the assistant went off to do while you carried on. Each one sends its own answer when it is done. Stopping one ends it at the next step it can stop on, and what it had got to is kept but not sent.
Answers you have kept. They are copies: they outlive both the conversation they came from and the transcripts, which are removed after ninety days.
Named lists - groceries, packing, a reading list - each with items to check off. Ticking an item here or by request updates the same list.
The reference numbers a desk will ask for. Abbreviated until you press Show, which is cover from the person behind you in the queue and not a lock: you are signed in, and can ask the assistant for the same details.
A belief's origin determines how far it is trusted. Something you stated is an assertion; something an email claimed is attributed and remains so. Forget removes a belief permanently.
These run without confirmation. Ask again restores it.
The camera runs only while this window is open, and no picture is taken until you press Capture. The result is an attachment like any other and can be removed before sending.
Goes to the team as a GitHub issue.