bot.computer.control
Generated at from
openvibe-contracts v0.177.0 and
openvibe-sdk v0.44.0.
Use a person's own computer with a Network service token naming that person in X-OV-Subject: the computer kinds of bot.command@1 (exec, fs, screen, input, browser) through POST /api/v1/robots/:id/commands, for a machine (openvibe.bot/machines) whose owner is that person and who turned on 'Let my agent use this computer'. Bot takes them from no one else (never an operator or a queue member), and the machine's owner sets on the machine itself what may happen (OpenVibe.Node's computer plugin: observe, ask, trusted or full; ask waits for the owner's approval there). The answer is bot.command-result@1's data; every command is audited, a refused one emits bot.command.refused. OpenVibe.Watch (a `node` source) may send only `probe` — one GET or one TCP connect to a private, loopback or link-local address from the machine — and only where the owner turned on "Let my watches check things from this computer".
- Owner
- bot (token audience
openvibe.bot) - Version
- 1.0
- Status
- active
- Visibility
- first-party
- Resource constraints
- none
- Quota class
- bot-control
- Permissions
- bot:computer:control
- Input
- bot.command@1
- Output
- bot.command-result@1
- Events
- bot.command.refused
- Implemented by
POST /api/v1/machines/:id/commands with kind exec, fs or screen (bot.command@1, answered by bot.command-result@1 with data)POST /api/v1/machines/:id/commands with kind probe (OpenVibe.Watch)