Microsoft Teams: the SphereHarness app
Talk to your CAD from Microsoft Teams exactly as you would in the SphereHarness chat on your PC. Message SphereHarness in a 1:1 chat, or @mention SphereHarness in a group chat or a team channel — the request runs on your own PC, with the AI you chose there, and the answer comes back to the same chat.
New to channels? Read Channels & Messaging first. You need the desktop agent version 1.3.5 or later on your PC.
How a message travels
Step 1 — add the app to Teams Teams admin
The SphereHarness Teams app is not in the Teams Store. It is an app package your organisation adds to Teams itself: download SphereHarness-Teams.zip (also on sphereharness.io/teams/add and behind the desktop agent’s Add to Teams button).
Upload it for the organisation (a Global administrator or Teams administrator): Teams admin center → Teams apps → Manage apps → Upload new app → Upload → pick the zip. It appears in Teams under Built for your org.
Choose who may use it: in Manage apps open SphereHarness and set its availability (everyone, or specific users or groups). Microsoft makes an uploaded app available “after a few hours”; availability changes can take up to 24 hours.
Check the organisation’s app settings (Teams apps → Manage apps → Org-wide app settings): users may interact with custom apps, and third-party apps are not blocked.
Optional — install it for everyone: Teams apps → Setup policies → the Global (or a group’s) policy → Installed apps → Add apps → SphereHarness (and pin it if you like).
In a team channel: add the app to the team (… → Manage team → Apps → Get more apps → SphereHarness → Add to a team).
Updating to the 1.3.6 package (file sending). SphereHarness 1.3.6 lets the AI send you files in your 1:1 chat, which needs the new package (app version 1.3.6; it turns on supportsFiles). Teams keeps the version that was uploaded until an administrator replaces it: download the zip again, then Teams admin center → Teams apps → Manage apps → open SphereHarness → Upload file → the new zip. A person who side-loaded the app uploads the new zip the same way they added it. Until then, everything else keeps working; only file sending is missing.
No Microsoft Entra admin consent is needed: the app asks for no Microsoft Graph permission. The package holds only the app’s name, icons and the SphereHarness bot’s id.
Without an administrator (sideload). Where your organisation allows it, one person can add the app alone: Teams → Apps → Manage your apps → Upload an app → Upload a custom app → the zip. That needs the organisation’s custom-app setting and an app setup policy with Upload custom apps on — Off by default in most organisations — and is not available in GCC High, DoD or Teams operated by 21Vianet. If it is not allowed, Submit an app to your org (same menu) sends it to your Teams admin for approval.
Step 2 — connect your Teams account Each person, once
Install the desktop agent (version 1.3.5 or later) and sign in to SphereHarness with the same e-mail address as your Microsoft work sign-in name (for example
anna@contoso.com). Your SphereHarness e-mail must be verified. Any licensed or trial account can use Teams.In the agent: Settings → Channels → Microsoft Teams via SphereHarness → on. The agent then keeps a connection to the SphereHarness server so your Teams messages can reach it.
In Teams open SphereHarness (Chat → New chat → SphereHarness) and send a message.
SphereHarness matches you by e-mail. Microsoft tells our server the sign-in name (UPN) of the person who sent the message; it must be the verified e-mail of exactly one SphereHarness account. There is no code to type.
Your PC asks once: “Teams account anna@contoso.com wants to work on this PC - Accept / Not me”. Accept runs the message. Not me refuses it, and the e-mail match does not make that link again. Each PC asks once for each Teams account.
Never matched automatically: a guest from another tenant, a sign-in name ending in .onmicrosoft.com, a Teams account from another tenant than the message came from, and a SphereHarness account whose e-mail is not verified. Two SphereHarness accounts with the same e-mail are never guessed between.
Using it
One conversation with your PC (1.3.7): a Teams message continues the conversation in the SphereHarness chat on that PC, exactly as if you had typed it there — the same AI session and history, your saved memories, the CAD session chosen in the chat’s Target box, the same model, and the same commands. Your message appears in the chat on the PC marked [from Teams], and the answer is shown there and sent back to Teams, as complete as in the chat (only tables, code blocks and diagrams, which Teams cannot show, are left out). Teams sends only your new message, never its own chat history, so it does not matter that Teams is a different conversation per PC. A message sent while an answer is still running is passed into it, like typing in the chat; /stop stops the running answer at once (and everything it started), /pause pauses it (it saves and says what was left), a long request sends its checkpoint lines here and continues by itself, /clear starts the conversation over (on the PC too), and /unattended always / /unattended off switch unattended mode on that PC (shown in its chat and written to its unattended log).
Files, pictures and voice messages (1.3.7): send them in the Teams message and they reach the chat on your PC like a file you attach there (up to 5 per message, 10 MB each, 20 MB together; anything over is named in the message instead). A voice message is turned into text on your PC, with the speech-to-text you chose for the chat’s microphone, and sent as your message; Teams shows what was heard. The files pass through the SphereHarness server in memory only and are never stored there.
- 1:1 chat: every message is for SphereHarness. Channel or group chat: only messages that @mention SphereHarness are read; it routes by the sender, so each person’s message runs on that person’s PC; the answer is visible to everyone in that chat — use the 1:1 chat for anything private.
- The status line names the PC: “Working on it on LAPTOP-7 …”, updated while it works, then the answer.
- Pictures: a small picture (up to 80 KB) is shown in Teams directly; larger pictures come from a link that works for one hour and then is gone — it was held in memory only. Only the pictures the answer is about are sent — not every screenshot the AI took to check its work.
- Files (1.3.6): ask for a file — “send me the recording”, a PDF, a STEP model, any type up to 250 MB — and in your 1:1 chat SphereHarness posts a file card with its name and size. Click Allow and your PC uploads the file straight into your own OneDrive; Teams then shows it in the chat. The file goes from your PC to Microsoft and never passes through SphereHarness — our server only passes on the upload address and the result. Each file needs its own Allow; Decline sends nothing; an unanswered card closes after an hour. In a channel or group chat files are not sent — ask in the 1:1 chat. The AI never sends key, password or sign-in files.
- Approvals are asked on your PC as always; Teams says it is waiting for your approval there.
Several PCs — which one answers (/pc)
With the switch on in more than one PC, your message goes to (1) your preferred PC if it is connected, else (2) the PC that answered you last, else (3) the only PC that is connected; with several connected and none chosen the app asks you which one. Send /pc to list them — each with its short id, online or not connected, last seen 7 min ago, and which one runs your requests (“WS-A - runs your requests · id 3f9a1c · online”) — and /pc NAME (or /pc 3f9a1c) to make one your preferred PC.
To send one message to another PC without changing your choice, start it with the PC: /pc NAME message or @NAME message (an @ that names none of your PCs is an ordinary message). A PC that is not connected is named in the answer and nothing runs.
Your PC is off
Teams answers at once: “Your PC NAME is not connected to SphereHarness right now. Start the SphereHarness agent there and send your message again.” Nothing is queued on our server — send it again once the agent runs.
Licence
Teams works for any SphereHarness account with an active licence or trial. With an expired licence the app answers with the licence sentence and nothing is delivered.
Organisations: claim your Microsoft 365 tenant Org admin, optional
An organisation that wants control claims its Microsoft 365 tenant in the org portal (the Teams panel: the tenant ID from Microsoft Entra admin center → Overview, and Enabled). Then only active members of that organisation can use the SphereHarness app from that tenant — anyone else in the tenant is told to ask their administrator, and no member is ever named — and the org admin can switch Teams off for the whole tenant. A tenant nobody claimed works person by person, by the e-mail match.
Disconnect
Turn Microsoft Teams via SphereHarness off in Settings → Channels to stop a PC receiving Teams messages. Disconnect in the agent’s Teams channel settings removes the link between your Teams account and your SphereHarness account; deleting your SphereHarness account removes it too. Your Teams admin can remove or block the app in the Teams admin center.
Your own Azure Bot for Teams: not offered
Setting up your own Azure Bot for Teams — on your PC (a tunnel, your router or a company relay) or on your organisation server — is no longer offered. Use the SphereHarness Teams app: there is nothing to register in Azure. WhatsApp and Telegram are unchanged: WhatsApp, Telegram.
Troubleshooting
| Symptom | Cause and fix |
|---|---|
| People cannot find SphereHarness in Teams | The package was not uploaded, its availability excludes them, or custom / third-party apps are blocked (Step 1); allow up to 24 hours after a change. |
| “Upload a custom app” is missing | Your organisation does not allow personal upload (the default). Ask your Teams admin, or use Submit an app to your org. |
| Teams says no SphereHarness account matches you | Your Microsoft sign-in name is not the verified e-mail of exactly one SphereHarness account, or you are a guest or .onmicrosoft.com account. Sign in to SphereHarness with your work e-mail and verify it. |
| “… is not connected to SphereHarness right now” | The agent is not running, not signed in, or the Teams switch is off on that PC. |
| The status line waits and nothing happens | The PC is showing Accept / Not me or another approval — answer it there. |
| No file card appears, or “Files can be sent only in your 1:1 chat” | Ask in your 1:1 chat with SphereHarness. If the card still never appears, your organisation runs a package older than 1.3.6 — ask your Teams admin to upload the new package. |
| “… could not be uploaded” after Allow | The reason follows: the upload window ended (ask again and click Allow sooner), your OneDrive is full, or the PC lost its connection. |
| The wrong PC answers | /pc, then /pc NAME. |
| “Ask your administrator” | Your organisation claimed the tenant and you are not an active member, or Teams is switched off for it. |
| It answers in 1:1 but not in a channel | The app is not added to that team, or the message did not @mention SphereHarness (pick it from the @ list). |
Related
- Channels & Messaging
- WhatsApp · Telegram
- What goes where — every data flow
- Verifying Results — always confirm geometry, never trust the wording of a reply