TaskTime Pro local agent bridge

OpenClaw And Agent Platform Integration

Install the native TaskTime Pro OpenClaw plugin, pair the browser app once, and keep one Gateway-owned local bridge available across ordinary agent turns.

Recommended Installation

Install the complete first-party plugin. It contributes the TaskTime skill, generated native tools, and one Gateway-lifecycle bridge service. You do not need a global bridge binary or a separate terminal window.

openclaw plugins install @tasktimepro/openclaw
openclaw gateway restart
openclaw plugins inspect tasktime --runtime

Confirm the plugin is active and the TaskTime skill/tools are visible.
Call tasktime__get_pairing_status to obtain the active bridge's short-lived launch URL.
Open that URL and approve Account > Agent Access in TaskTime Pro.
Make a read-only call such as tasktime__list_projects before normal writes.

Skill File

Agent platforms that support skill files can fetch /agents/skill.md. It points to the manifest, MCP tool catalog, quickstart, security notes, and debugging guide. It also tells the agent to keep TaskTime Pro local-first, use MCP tools before UI automation, and preserve TaskTime Pro approval semantics for sensitive actions.

To install the standalone TaskTime Pro skill from ClawHub, use the owner-qualified reference:

openclaw skills install @tasktimepro/tasktime-agent

What The Plugin Owns

@tasktimepro/openclaw is a native OpenClaw plugin. Its supervised service starts one vendored bridge for the Gateway/profile lifetime and routes generated tasktime__* tools through the same MCP validation, scopes, approvals, rate limits, and browser-owned command execution as the generic bridge.

Native manifest: openclaw.plugin.json with startup activation.
Skill root: skills/tasktime/SKILL.md.
One Gateway-owned loopback bridge with a dynamic port.
Stable agent identity: tasktime.agent.openclaw, label OpenClaw on this device.
Secret-free, owner-only operational discovery status; pairing URLs remain ephemeral setup output.
Bounded child restart behavior; a new bridge instance requires pairing again.

The package retains .mcp.json and the Codex-compatible marker for compatible non-native hosts. OpenClaw's native format takes precedence, so those artifacts must not start a second OpenClaw bridge.

Connection Lifetime

Event	Expected behavior
Later OpenClaw turn	The same Gateway-owned bridge remains active.
Refresh TaskTime	The current tab resumes from a bounded `sessionStorage` record.
Close and reopen TaskTime in the same browser profile	A non-exportable browser key proves possession and receives a fresh short-lived session; no bearer token is stored durably.
Another browser profile/device	Pair explicitly.
Disconnect, revoke, disable, forget, or expiry	Authorization ends and pairing is required.
Gateway/bridge restart	The old in-memory authorization is gone; pair once to the new bridge instance.

First-Run Recovery

When TaskTime Pro reports no connected app session, OpenClaw should not ask the user to run a separate terminal bridge. It should use tasktime__get_pairing_status, open the returned launchUrl, and retry the TaskTime Pro tool after the user approves. If the pairing expired or was consumed by a stale browser attempt, call tasktime__refresh_pairing and use the new launch URL.

If the plugin reports legacy_mcp_conflict, disable the older mcp.servers.tasktime entry explicitly and restart the Gateway. The plugin will not kill or silently rewrite user-owned processes or configuration. A stable agent ID and dynamic loopback port are not authentication.

mkdir -p ~/.openclaw/backups
chmod 700 ~/.openclaw/backups
openclaw backup create --only-config --verify --output ~/.openclaw/backups
openclaw config get mcp.servers.tasktime
openclaw config unset mcp.servers.tasktime --dry-run
openclaw config unset mcp.servers.tasktime
openclaw config validate
openclaw gateway restart
openclaw plugins inspect tasktime --runtime

If the diagnostic names mcpServers.tasktime, use that exact historical path instead. Keep the verified backup and saved TaskTime value until the native flow works. Rollback is explicit: disable the native plugin, preview and restore the saved value with openclaw config set, validate, and restart. Never enable both owners together.

If CLI and Gateway versions differ, run openclaw --version, which openclaw, and openclaw gateway status --deep before changing TaskTime configuration.

Publishing Notes

Describe TaskTime Pro as a local-first task, time tracking, expense, invoice, report, and planning app.
Use “TaskTime Pro MCP”, “local agent bridge”, and “local-first invoicing agent” in package metadata where accurate.
Point human setup docs to /agents/quickstart/.
Point security review docs to /agents/security/.
Point machine readers to /agents/mcp-tools.json.

Consent Boundary

OpenClaw-style launch assistance can reduce setup friction, but it must not create silent first-use access. A user still explicitly grants TaskTime Pro bridge access before an agent can read or mutate local TaskTime Pro data.

For later sensitive operations, a chat confirmation can produce a TaskTime Pro approval token only when a trusted local grant exists. The browser app remains the final verifier and can reject stale, replayed, tampered, under-scoped, or revoked approval tokens.