dsh-tripsy
在 DeepSeek Harness 工作区面板中浏览您的 Tripsy 行程：行程安排、活动、住宿、交通和费用。该面板专为只读设计——如需创建和编辑，请向使用 Tripsy MCP 工具的代理提出请求。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:ta-www/dsh-tripsy#6acfd404c182ec607915e557beabd15fc1950d73Tripsy 以 dsh-tripsy 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Browse your Tripsy trips inside a DeepSeek Harness panel: itinerary, activities, lodging, transport and expenses — with the times converted into each item's own timezone.
中文说明 | English
A sidebar entry and a center-column page with two tabs.
行程浏览 / Browse — pick a trip on the left. The right side shows a cover hero with the trip name, countdown, duration and date range; a day-grouped timeline with an icon per stop; and a cost card totalling each category from the items' own prices. Every time is rendered in its own IANA timezone.
AI 管理 / Manage — describe the change you want in plain language. The tab composes a precise instruction for the selected trip (id, dates and timezone included) and hands it to the DSH composer, so the agent does the work with the Tripsy MCP tools and you see every step. The panel itself never writes to your account: creating and editing stay in the conversation, where the agent confirms what it is about to change.
Your account details never reach the browser. /api/dsh-tripsy/health returns only the auth summary and the account currency — not the name, e-mail or avatar the Tripsy profile carries.
┌ Tripsy ─────────────────────────────────┐
│ 行程浏览 │ AI 管理 │
├──────────────┬──────────────────────────┤
│ New York City│ ╔══════════════════════╗ │
│ 2026-10-11 │ ║ cover + NYC ║ │
│ │ ╚══════════════════════╝ │
│ │ ＋ ✈️ 🛏️ 💳 │
│ │ 10月11日 星期日 │
│ │ ● ✈️ LAX → JFK 05:57 │
│ │ │ 🚗 驾车到酒店 15:00 │
│ │ ● 🏨 Aman 16:00 │
└──────────────┴──────────────────────────┘
dsh plugin --profile web add github:ta-www/dsh-tripsy
Refresh the page. Tripsy appears in the sidebar. The first time, click 登录 Tripsy / Sign in — the browser opens once for the OAuth handshake, and the token then refreshes itself indefinitely.
The host half registers a small route family and reuses the same OAuth + MCP code as the tripsy-mcp CLI, so there is exactly one implementation of the OAuth dance and one place a token is refreshed.
lib/index.js | host half: /api/dsh-tripsy/{health,trips,trip,login} |
lib/client.js | browser half: the sidebar row and the panel page |
lib/tripsy/*.mjs | OAuth 2.1 (PKCE + dynamic client registration), Streamable HTTP MCP client |
cordis.patch.yml | inserts the plugin row |
Credential at rest: $DSH_HOME/tripsy-auth.json (override with the authFile config). It is never sent to the browser — the panel only ever sees the data, never the token.
Requests are refused unless they come from loopback. Set allowRemote: true in the plugin config if you deliberately serve the UI over a LAN address.
- id: ui-tripsy
name: dsh-tripsy
config:
authFile: 'C:\Users\you\.dsh\tripsy-auth.json' # where the token lives
allowRemote: false # keep loopback-only
enabled: true