Reason in the cloud.
The model interprets the evidence and proposes the next check or action. Each turn goes through Rapport’s gateway, with tenant model settings, session limits and usage records.
Model credentials stay server-side.“The app is running. Let’s check what’s happening underneath.”
Investigate device issues, understand the evidence, and take controlled action—all in one conversation. Rapport combines cloud AI with an agent on your device, so you can see what was checked, review proposed changes, and verify the result.
Create an account. Connect your first device. Bring a real question.Your people. Their devices.
Finally on speaking terms.
Rapport pairs cloud AI with a working harness on each enrolled device. The harness is the local software that manages the tool loop, checks proposed commands and runs permitted tools. You work with both through one conversation.
The model interprets the evidence and proposes the next check or action. Each turn goes through Rapport’s gateway, with tenant model settings, session limits and usage records.
Model credentials stay server-side.Describe the problem. Challenge a hypothesis. Inspect the evidence and approve or decline held commands. Keep the investigation connected to the person experiencing the issue.
Your question. Your judgment. Your next step.The native agent reads device state, gathers diagnostic evidence and executes permitted tools. It classifies shell commands locally before execution; the model’s request alone is not permission.
Local execution. Policy checked on the endpoint.Your question Cloud reasoning Local policy check Permitted device work Evidence for the next turn
Allowed read-only checks can run automatically. Mutating or elevated shell commands are held for approval. Commands classified as destructive or disallowed are refused.Experience scores and fleet signals tell you where to look. The workspace lets you investigate the next question on that device, gather fresh evidence and review a tailored action. Enabled tools can address a question without a prewritten workflow for that exact issue.
Conversation context and bounded tool results travel through the gateway to our AI provider, Anthropic. Output scrubbing reduces exposure; it does not guarantee that all sensitive data stays on the device.
Explore execution and data boundariesThe agent runs tools on the selected endpoint as it investigates. The workspace keeps your question, its checks, proposed actions and returned results together.
“Why is this device slow?” Start with the problem. Continue with follow-up questions in the same conversation.
Inspect device checks and tool output alongside the explanation. Keep an observation separate from a suspected cause.
Inspect the exact command and target when an action needs approval. Approve or decline that request in the workspace.
Review the execution result and fresh device evidence. A completed command is not the same as a confirmed resolution.
“The Business account is active again. Personal is still healthy. Please check that the original file reached its destination.”
The conversation can propose a device change. The workspace shows the request for a person to review; a chat message is not a substitute for the required approval.
See the workspace’s security boundariesTenant-scoped access and MFA-backed operator sessions.
Enabled tools, session limits and bounded results—not unrestricted access.
Review the requested action and its target. Approve or decline the individual request.
Follow the messages, tool calls, approval decisions and returned results.
The workspace leads. Device context, diagnostic tools, controlled actions and fleet operations support the core experience: working through an issue with the device.
Experience scores and telemetry help you choose where to start the conversation.
Performance · stability · connectivityDiagnostic observations help the assistant explain what it found and what to check next.
Observations · findings · next checksSupported actions turn a conversation into a reviewable next step on the device.
Target · proposed action · returned resultWhen the next step is a wider change, stage the rollout and review each ring.
Staged rings · health evidence · rollout gatesKeep the endpoint agent itself under your tenant’s release and adoption policy.
Approval · automatic adoption · holdCollection policy and access controls define the boundaries around the work.
Collection scope · operator access · recordsCreate your account, connect a device you manage, and bring the question you already want answered. The setup guides walk you through enrollment, access and AI configuration.
Try Rapport Read the getting-started guideRapport pairs cloud AI with a local device harness in a conversational workspace for IT. The harness manages the tool loop and permitted execution on each enrolled device. Ask a device why it is slow: the agent runs diagnostic tools on demand on that endpoint, explains what it finds and proposes the next step. Inspect the results, review a proposed action and continue the conversation. Device intelligence, diagnostics, remediation and fleet controls support that central Agent Workspace experience.
No. The homepage shows short, illustrative conversations based on internal workflows. The detailed Agent Workspace walkthroughs condense real internal sessions, with identities removed and wording edited for clarity. Neither connects to a device or executes an action. Supporting fleet examples use fictional data. In your configured workspace, the endpoint agent runs the tools and the gateway calls our AI provider, Anthropic.
Workspace access requires a tenant operator with an MFA-verified session. Enabled tools and configured limits govern the work; held commands are shown for an approve or decline decision. Approval applies to the individual requested command, not every later action. The agent is a privileged service, so these controls do not replace careful scoping of operator access.
No. The AI model runs in the cloud, and the device runs only the tools you permit. AI features are off until your administrator turns them on. When they are on, prompts, conversation context and bounded tool results go through Rapport’s gateway to our AI provider, Anthropic, in the United States. Under our agreement, Anthropic does not keep this data after processing or use it to train models. Provider keys stay server-side, and conversation history is stored in Rapport in the United States. See the AI Use Statement.
Choose Try Rapport to create your account and organization directly. Verify your email and complete multi-factor authentication, then install the signed agent on a supported device using your organization’s enrollment token. Configure AI access and the permitted tools before starting an Agent Workspace conversation. The getting-started guide and illustrated documentation cover each step.
Rapport supports eligible Windows and macOS devices, with Windows MSI and macOS PKG deployment paths. Linux is available as a preview. Measurements and actions vary by operating system and configuration. Check the deployment page for OS versions, installation privileges, hardware guidance and network requirements before enrolling a device.
Routine monitoring never collects keystrokes, screen content, clipboard contents, browsing history, or the content of documents or messages, and Rapport does not score individual productivity. Workforce activity is off unless your organisation turns it on, and is shown only for groups of at least five devices. Support tools that IT staff use when needed (scripts, file transfer and the AI assistant) can access device content, so tell employees how you use them. Our Employee Privacy Notice template helps.
No. AI-assisted investigations use read-only diagnostics to assemble observations and recommend next steps. Device changes follow the enabled endpoint policy and applicable approval and verification requirements. A finding's confidence is an aid to review, not a guarantee of root cause or a permission to execute.
Yes. Patch deployments use maintenance windows, staged rings and evidence gates. Agent releases have a separate choice of individual approval, explicit automatic adoption or hold, with rollout and timing controls. A hold stops future eligible update attempts; an installation already in progress may finish. Device-management administrators still control packages they deploy directly.
Make the next conversation about your own device. Create your account and follow the setup guide to your first investigation.