Skip to content

How it works

Architecture

Cysic CyClaw combines hosted runtime infrastructure with native Cysic inference support:

  • Inference layer: CyClaw uses Cysic Inference as its native inference service.
  • Hosting layer: Each user's CyClaw instance runs on Cysic-managed servers.
  • User access layer: Users interact with their instance through supported channels such as Telegram, Discord, and Feishu.

This gives users a managed CyClaw experience without requiring local deployment.

Security model

Security is a key part of the design:

  • Cysic-managed API access: CyClaw itself does not need to expose raw external access directly.
  • Instance isolation: Each instance runs in an isolated environment, similar to a long-lived sandbox.
  • Reduced local risk: Users do not need to grant high local machine permissions just to keep CyClaw running.

Service flow

mermaid flowchart LR User[User] --> Channel[Telegram / Discord / Feishu] Channel --> Instance[Hosted CyClaw Instance] Instance --> Inference[Cysic Inference] Instance --> Skills[Installed Skills] Instance --> Billing[Cysic Billing]

CyClaw instance status

ClawStatus

The runtime status of a CyClaw instance.

Status Description
CreatePending Resources locked and payment deducted; newly created instance is pending.
StartPending Resources available; instance startup is pending while the system executes creation.
WaitPending No resources available; creation/startup is pending while waiting for free resources.
Running Instance is running normally.
Stopped Instance is stopped. A stopped instance will not be charged. It can be restarted; billing resumes only after the current period expires. A instance enters this state when it expires and the account balance is insufficient for auto-renewal, or when the user manually triggers a stop.
TerminatePending Shutdown command is being executed.
Deleted Instance has been permanently deleted and will no longer appear in the user's instance list.
CreateError An error occurred during creation. A refund will be issued automatically.
StartError Instance failed to start, typically due to environment damage. Try Reset Config to recover.
WaitError No resources became available after an extended wait.
Unknown Unknown status (fallback value).