Introduction

DSH plugins can integrate context, tools, and UI capabilities into the local agent. If team norms are only placed in the Aloof web page, the agent cannot reliably read them while executing tasks, nor can it return newly understood rules to the team.

dsh-aloof is used to sync Aloof’s team red lines and team manuals to the DSH agent: red lines go into system prompts, and manuals go into the skills directory; it also provides the /aloof command, a status button in the bottom right, and an interface to submit for confirmation.

It depends on a running Aloof instance and a dsh access token. When there is no Aloof instance, the plugin will only prompt that ALOOF_TOKEN is not configured.

What is this

aloof-ai/dsh-aloof is a DSH client plugin used to sync team rules from Aloof into the DSH agent.

  • Repository owner: aloof-ai
  • License: MIT
  • Requirements: Node ≥ 22, DSH, a running Aloof instance, a dsh access token
  • The server is not in this repository and is not public

Below, I will introduce what it can do, how to install, and how to configure.

Core Features

Team Rule Distribution

  1. Sync team red lines to the DSH system prompt (ctx.systemPrompt).
  2. Register the team manual to the DSH skills directory (ctx.skills.register), which the agent reads when it determines relevance.
  3. Pull from Aloof’s /api/context every five minutes.
  4. Keep the last content if it cannot be pulled; do not clear it.

Status Viewing

  • Provides the /aloof command to directly view the connection address, the first few digits of the ticket, and Aloof’s identified identity.
  • Provides a draggable floating button in the bottom right corner with traffic light status, supporting ticket replacement/clearing.

Plugin Tools

  • aloof_whoami
  • aloof_devices
  • aloof_contribute

Among them, aloof_contribute is the only write operation, used to submit items for confirmation.

Credential Configuration

  • The full access token is configured and includes the address, so there is no need to configure the server address separately.
  • Supports hot-reloading credentials via .credentials.yaml.
  • The environment variable ALOOF_TOKEN is frozen at process startup and takes precedence over .credentials.yaml.

Installation and Enabling

First, confirm the environment:

  • Node ≥ 22
  • DSH
  • A running Aloof instance
  • A dsh access token

Installation command:

dsh plugin --profile web add dsh-aloof

If you want to do local development, first clone the repository, then add it by local path:

git clone https://github.com/aloof-ai/dsh-aloof.git
dsh plugin --profile web add /absolute/path/dsh-aloof

Typical Usage

Configure Access Token

  1. Generate a dsh access token on the Aloof web page.
  2. Put the full token into the environment variable ALOOF_TOKEN, or write it into $DSH_HOME/.credentials.yaml.
  3. The access token comes with a server address, so usually there is no need to configure the address separately.

If the environment variable ALOOF_TOKEN already exists, subsequent modifications to $DSH_HOME/.credentials.yaml may not take effect, because the frozen environment variable at process startup has higher priority.

View Connection

Run in DSH:

/aloof

It will display the address this DSH is connected to, the first few digits of the ticket, and the identity identified by Aloof.

Contribute to Team

Say in the session:

把这个存成团队手册

The plugin will call aloof_contribute to submit for confirmation. After submission, it still requires admin approval to be distributed; the agent cannot directly change red lines or manuals.

Change Ticket

You can do the first method first: save a new ticket in the bottom-right card without restarting DSH.

You can also edit the file: hot-reload after modifying $DSH_HOME/.credentials.yaml.

Applicable Scenarios and Notes

This plugin is suitable for developers who already have an Aloof instance and wish to integrate team rules into the local DSH agent.

Note the following boundaries:

  • Issuing new tickets, revoking tokens, and accepting proposals can only be done on the Aloof web page; the plugin does not provide corresponding tools.
  • Access tokens are not web login tickets.
  • Changing the Aloof password will revoke all tokens under the name.
  • Tokens can be set with an expiration date; they need to be regenerated when expired.
  • Optional configurations include tokenEnv (default ALOOF_TOKEN), timeoutMs (default 20000), baseUrl (default empty, follows the ticket).
  • The package has no build steps; npm pack outputs the source code directly; restart DSH after modifying client.js.

The plugin runs with the permissions of the current DSH process. You should check the source code and license before installing.

Links

After the above steps, dsh-aloof can connect Aloof’s team rules to the local DSH agent: red lines go into system prompts, manuals go into skills directories, status can be viewed via /aloof and the bottom-right button, and knowledge can be submitted for confirmation.

  • Directory page: https://www.skillhub.cn/plugins/aloof-ai/dsh-aloof
  • GitHub: https://github.com/aloof-ai/dsh-aloof