Skip to main content
Glama
qddfxp

task-checkpoint

by qddfxp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TC_GITNoSet to 'off' to completely skip creating refs/checkpoints/... references.on
TC_STORENoStorage directory for checkpoints.<workspace>/.checkpoints
TC_WATCHNoSet to 'off' to disable background automatic recording.on
TC_SHA_REUSENoSet to 'on' to reuse sha from index when mtime+size unchanged; risk of missing content changes.off
TC_GIT_VERIFYNoSet to 'off' to skip git fingerprint verification; then git.unchanged in responses is null.on
TC_DRIFT_MAX_WAITNoMaximum quiet period in seconds.60
TC_WATCH_INTERVALNoBackground check interval in seconds.15

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
tc_initA

创建任务。已有活动任务会挂起而不是关闭。

tc_switchB

切换活动任务。closed 任务会被拒绝。

tc_saveB

保存一个任务层步骤。close=true 时关闭任务且不再接受保存。

tc_captureA

立即记录当前文件变化,不等静默期。

tc_showA

列出任务层步骤;include_drift=true 时同时列出变更层。index 可精确查看单步。

tc_restoreB

按任务层序号或变更层编号恢复。index 与 drift_id 二选一;apply=false 只预览。

tc_resumeA

只读返回目标、当前步骤、未落档路径和下一步。

tc_exportB

导出交接包到一个已存在的目录。敏感文件内容不会导出。

tc_importA

导入 tc_export 生成的交接包,在另一个目录或机器上接续任务。会校验任务 id 与工作区路径,拒绝重复任务、.. 穿越与符号链接目标;失败时撤销已写入的文件。

tc_compressA

回收存档空间:删掉超过保留期的变更层内容。被回收的变更层不能再 restore,步骤基线不受影响。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 10 tools

Disambiguation4/5

Most tools target clearly distinct operations (init, import, export, compress, switch, restore). Minor overlap exists between tc_capture (record live changes) and tc_save (persist a step), and between tc_resume (status) and tc_show (list steps), but the two-layer model (task layer vs change layer) largely keeps them separable.

Naming Consistency5/5

Every tool uses the same tc_ prefix followed by a single concise verb (init, import, capture, compress, export, restore, resume, save, show, switch). The pattern is perfectly predictable throughout.

Tool Count5/5

Ten tools is well-scoped for a task-checkpoint lifecycle. Each tool maps to a distinct lifecycle concern (create, persist, capture, resume, inspect, restore, clean, hand off) with no filler.

Completeness4/5

The lifecycle is broadly covered: create, save/close, capture, status, list, switch, restore, compress, and export/import handoff. Closing a task is folded into tc_save (close=true) rather than a dedicated tool, and there is no explicit task deletion, but these are minor workable gaps.

Maintenance

ActivityMaintained
ResponsivenessNo issues