mirror of
https://github.com/hansjone/dsh-ops-cron.git
synced 2026-10-09 04:40:48 +08:00
oliver
933bad9201
Without udsAuth, trusted HTTP uses a synthetic __local__ viewer that sees all jobs; with uds-auth, keep multi-user empNo isolation and admin folders. Document that IM channels are not default UDS accounts. Co-authored-by: Cursor <cursoragent@cursor.com>
64 lines
3.3 KiB
Markdown
64 lines
3.3 KiB
Markdown
# dsh-ops-cron
|
||
|
||
Scheduled-task plugin for DeepSeek Harness (fork of [dsh-cron-tasks](https://github.com/Whale-Zhang/dsh-cron-tasks)).
|
||
|
||
- Sidebar **定时任务** under New Session
|
||
- Agent tools: `cron_create` / `cron_list` / `cron_pause` / `cron_resume` / `cron_delete`
|
||
- Per-job delivery: **DSH** (new root session) or **IM** (`ctx.dshIm.send`)
|
||
- After each fire, mirrors the summary into the **origin effective session** (creator Web chat or WhatsApp peer binding) so follow-ups share context
|
||
|
||
See [FORK.md](FORK.md) for install notes. Do **not** install upstream `@dsh-external/dsh-cron-tasks` in the same profile.
|
||
|
||
## Install
|
||
|
||
```sh
|
||
dsh plugin --profile web add -w "github:hansjone/dsh-im-ops"
|
||
dsh plugin --profile web add -w "github:hansjone/dsh-ops-cron"
|
||
# restart dsh web
|
||
```
|
||
|
||
## Auth modes (uds-auth is optional)
|
||
|
||
`uds-auth` is a soft dependency. Cron and IM plugins work without it.
|
||
|
||
| Mode | When | Behavior |
|
||
|------|------|----------|
|
||
| **standalone / local** | `udsAuth` not provided | Trusted local/same-origin HTTP works with synthetic `__local__` identity; all jobs visible; flat sidebar (no user folders); create does not force an empNo |
|
||
| **multi-user** | `uds-auth` installed and providing `ctx.udsAuth` | Jobs carry `ownerEmpNo`; Web login required; isolation matches workspace ACL |
|
||
|
||
### Multi-user isolation (with uds-auth)
|
||
|
||
| Role | Sees |
|
||
|------|------|
|
||
| `super_admin` / `fallback_admin` | All users’ jobs (sidebar groups by empNo folder) and their run sessions |
|
||
| `admin` / `user` | Only own jobs and runs |
|
||
|
||
Create stamps the logged-in empNo. Legacy / unclaimed jobs stay `__unassigned__` (super-only until claimed by session/cwd evidence). Fire cwd prefers the owner’s provisioned workspace under `user-workspaces/<empNo>`.
|
||
|
||
**Channel / IM sessions are not a UDS account.** New WhatsApp/IM chats use the bot workspace (`workspaces.json`); they are not mapped to `administrator` or any empNo by default. IM cron jobs stay peer-scoped (or unassigned for Web ACL).
|
||
|
||
## Delivery defaults
|
||
|
||
| Created from | Default delivery | Effective-session mirror |
|
||
|--------------|------------------|--------------------------|
|
||
| WhatsApp / IM session | `im` → reuse or **auto-create** a 投递目标 for that chat (group→group, DM→DM) | Live session for that `conversationKey` (latest binding) |
|
||
| Web / plain DSH session | `dsh` → sidebar history session | Creator session pinned as `origin.sessionId` |
|
||
| Explicit `delivery` / `im_bot_id`+`im_target_id` | as specified | Same mirror rules when `origin` / peer can be resolved |
|
||
|
||
You usually do **not** need to paste botId/targetId when creating from WhatsApp — omit `delivery` and the job binds to the current chat.
|
||
|
||
**Execution session ≠ effective session.** Each fire still opens a fresh root Session for the Agent turn (visible under 定时任务 history). The mirrored notice is what makes the WhatsApp/Web chat you actually use able to continue from the result.
|
||
|
||
## Agent preset
|
||
|
||
| Source | Behavior |
|
||
|--------|----------|
|
||
| Explicit `agent_preset` / sidebar field | pinned on the job |
|
||
| WhatsApp / IM create (omit) | inherit chat/group override → bot preset → Host default |
|
||
| Sidebar leave empty | Host default at each fire |
|
||
|
||
Scheduled runs mount `job.agentPreset` (or Host default when empty).
|
||
|
||
## License
|
||
|
||
MIT (upstream MIT retained).
|