Skip to content
AnyAgent.
All appsWorkspaceFeaturesQuestionsSupport
Coming soon
All appsWorkspaceFeaturesQuestionsSupportPrivacyComing soon
Back to AnyAgent

ANYAGENT · HELP & SUPPORT

Support

Contact AnyAgent support and find practical help for connections, editors, privacy, and diagnostics.

Effective November 17, 2026
ON THIS PAGEContact AnyAgentA connection will not openFiles or the VS Code workspace will not openA coding agent or alert is unavailableShare diagnostics safelyManage stored information

Contact AnyAgent

AnyAgent is operated by 1Moby Co., Ltd.. Email contact@1moby.com for app questions, accessibility barriers, or a problem you cannot resolve. You do not need an AnyAgent account to get in touch.

Include your app version and build from Library, device model, OS version, the feature involved, what you expected, what happened, and steps to reproduce. For a connection issue, describe the transport and general host platform. A redacted screenshot or a diagnostic error code can help. Do not send passwords, private keys, app PINs, access tokens, unredacted server addresses, or confidential code.

For a privacy request, email contact@1moby.com. We can help with information we hold and explain app controls, but cannot log in to or erase your device, Apple account, or remote host.

Email contact@1moby.com

A connection will not open

Check the server address, port, username, selected key or password, and any jump host, proxy, or relay configuration. Confirm the server is reachable from your current network and that a required VPN is connected. Verify the host-key fingerprint through a trusted channel; do not bypass a warning simply to make a connection work.

Open the connection’s diagnostics or Library → Logs to identify the failing stage. iOS may suspend background networking. Return to the app and reconnect if a session is stale. Persistent remote tmux sessions can survive a client disconnect, but that depends on the host configuration.

Files or the VS Code workspace will not open

The native file editor and the code-server workspace use different paths. A working file editor does not confirm that code-server is installed or running. For a code-server workspace, check the selected host, remote port, remote folder, and server process. If the app offers an installation action, review its displayed command before choosing it.

Use Reconnect in the code-server editor’s actions menu after checking the server. Clear Editor Data removes matching local embedded-browser data; it does not remove files or extensions from the remote server. For a folder from Files or iCloud Drive, select an accessible folder and run Sync Folder when you intend to copy it to the remote workspace.

If the native editor reports a file conflict, compare the remote version before overwriting it. Save or discard recovery edits intentionally. Unsaved local drafts are not a backup of remote files.

A coding agent or alert is unavailable

Check that the chosen coding tool is installed and configured on the selected host, and that the optional Host Agent is installed when the feature needs it. Your coding provider’s account, entitlement, model availability, and tool permissions are managed with that provider. AnyAgent does not supply those services.

In Library → Session & Privacy, check agent alerts, optional shell program alerts, and device notification permission. Shell completion alerts require supported shell integration, a known exit status, and a command lasting at least ten seconds while the app is inactive. Background limits can delay or prevent checks. A notification or Live Activity is a last-observed status, not a guarantee that a remote operation succeeded.

Share diagnostics safely

Open Library → View and Share Logs, or the connection’s diagnostics, and inspect the report before using Share. Exporting opens the system share sheet; the destination you choose receives the copy. Logs contain bounded event metadata, not a terminal recording. Screenshots, copied command history, and files you attach separately can contain sensitive information.

To stop and remove the saved app log, open Library → Session & Privacy, set Keep diagnostics to Off, and use Delete saved diagnostics if needed. Deleting the app log cannot recall a report already shared or remove older system Console records.

Manage stored information

There is no AnyAgent account or account-deletion request flow. Your saved connections, credentials, iCloud documents, remote services, and support messages have separate controls. The Privacy Choices page explains the available controls and what each one leaves behind.

Privacy Choices and DeletionPrivacy Policy
AnyAgent.

A little more freedom.
A lot closer to your work.

ExploreThe workspaceWhat it doesGet support
Your informationPrivacy policyPrivacy & deletionTerms of use
AboutAccessibilityOpen sourceContact us
© 2026 1Moby Co., Ltd.Made for the way you work.