How to use dsh-time-context
Opt-in durable per-step context with the current time and elapsed time
This article is auto-derived from indexed fields (wiki / faq / compatibility_json), not freshly AI-generated.
This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.
Quick start
Opt-in durable per-step context with the current time and elapsed time
— source: plugins.ai_summary
Install & verify
dsh plugin --profile web add npm:@deepseek-ai/dsh-time-context
Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.
— source: plugins.install
Key points
- id: time-context
- Prompt provenance only — browser-zone context guides natural-language interpretation but does not silently supply another tool's required zone field.
- Mixed turns ask — if one open turn contains prompts from different browser zones, the model is told to clarify rather than guess which one owns an unqualified time.
- Fallback is not user authority — the configured or process zone formats the clock when browser provenance is missing or mixed, but the model-facing policy still says to clarify.
- Whole-second display — timestamps and durations omit sub-second precision even though durable event times retain milliseconds.
— source: plugin_wiki.readme_en (fallback readme_raw)
Pitfalls
Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.
— source: general rule