Parent Epic
#159 — [Epic] Obsidian CLI 集成 — 研究知识管理
Summary
Add an Obsidian export panel to the Research workspace so users can hand off saved papers / active track exports into a local Obsidian workflow without leaving the dashboard.
Why here
The right placement is the Research workspace, not DeepCode Studio:
- export scope is defined by active Track + saved papers
- the Research page already owns paper save/export actions
- Studio is code-generation-centric and does not own library/export state
Proposed UX
- Add an
Obsidian action in the Research workspace export area
- Show current export scope: active track or global saved library
- Provide a copyable local CLI command, for example:
paperbot export obsidian --track-id <id> --vault "/path/to/vault"
- Provide a markdown fallback download using the existing paper export route
- Explain that filesystem write happens through local CLI, not the hosted dashboard
Acceptance Criteria
Parent Epic
#159 — [Epic] Obsidian CLI 集成 — 研究知识管理
Summary
Add an Obsidian export panel to the Research workspace so users can hand off saved papers / active track exports into a local Obsidian workflow without leaving the dashboard.
Why here
The right placement is the Research workspace, not DeepCode Studio:
Proposed UX
Obsidianaction in the Research workspace export areapaperbot export obsidian --track-id <id> --vault "/path/to/vault"Acceptance Criteria
TrackvsGlobal) and paper countpaperbot export obsidian ...command