dsh-plugin-radicale
为 DeepSeek Harness agents 提供 CalDAV 管理：一个 radicale 工具，可列出日历集合和事件、读取 ICS，并在 Radicale server 上创建或更新事件——绝不会删除任何内容。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:paulalesius/dsh-radicale#2fadbfcc0cb4ab79d3bc30409ab7995e55cda040Plugin Radicale 以 dsh-plugin-radicale 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A plugin for DeepSeek Harness (dsh) that gives your agent one radicale
tool to manage your local Radicale calendar server. You can ask your
agent things like "what's on my calendar?", "add a meeting on Thursday at
10", "make a new calendar for my work stuff", or "cancel the dentist
appointment" and it will list, read, create, update, and search your events
for you.
The tool has eight actions:
The plugin never deletes. It has no delete action, and nothing it can
send to the server can remove an entry. Cancelling an event is not a
delete: the event is moved into an archive collection (by default
/caldav/cancelled, configurable) and its own file gets two small
X-DSH- lines recording when it was cancelled and where it came from.
That is the traceability: the event is still there, readable, and
restorable, and uncancel reverses the move and strips those lines. If
the event really should be gone, do that in your calendar client.
With the dsh command, from the directory containing this checkout:
dsh plugin --profile web add /path/to/radicale
When running dsh from source:
pnpm dsh plugin --profile web add /path/to/radicale
The install is inert: the plugin row ships disabled. Enable it in one of two spots (pick one, never both):
Every session. In your profile's patch layer
(~/.dsh/profiles/web/cordis.patch.yml, append to your existing file):
- id: radicale
disabled: false
One preset only. In that preset's own file
(~/.dsh/.agent-presets/<preset>/agent.cordis.yml, append):
- id: radicale
name: dsh-plugin-radicale
No other configuration is needed for a server installed with the
defaults below - the plugin and Radicale both use the same default
address out of the box. If your server listens somewhere else, add a
config block with baseUrl set to your server's address, like:
- id: radicale
disabled: false
config:
baseUrl: http://<your-server-address>
Then restart the server.
| key | default | meaning |
|---|---|---|
baseUrl | the default local address (matches a Radicale server installed with the defaults) | Your Radicale server's address, if it listens somewhere else. Host and port in one value, for example http://<server>:<port>. |
maxItems | 100 | How many events one list or search call may fetch. Lists that hit the cap are flagged truncated. |
cancelledCollection | /caldav/cancelled | The archive collection cancel moves events into. A bare name (cancelled) resolves under /caldav; an explicit path is kept as-is. It is created automatically the first time something is cancelled. |
The config block replaces the plugin's defaults wholesale - list
every key you want to keep.
The plugin assumes the server is reachable without a password. That is the right setup for a local server (below); it does not carry any credential configuration of its own.
Radicale is a small, self-contained Python program. You install it into a dedicated virtual environment with uv:
uv venv ~/venv-caldav
source ~/venv-caldav/bin/activate
uv pip install radicale
That one command also brings in its only runtime dependency (vobject), so there is nothing else to install.
Create a config file (for example ~/.radicale-config) with:
[storage]
# Where the calendar data lives: one plain .ics file per event,
# easy to back up by copying the folder.
type = multifilesystem
filesystem_folder = ~/.radicale
[rights]
# Let the owner write. Without this line the server is read-only and
# the agent can list but not create or update events.
type = owner_write
[auth]
# No password: the dsh plugin connects without credentials.
type = none
radicale -c ~/.radicale-config
That is all: the server starts, prints a line with its address, and keeps running until you stop it (Ctrl-C). To have it start at boot, run it under systemd, tmux, or whatever service manager you already use.
Once it is up, open a session and ask your agent to list the collections
Developing the plugin: see AGENTS.md.