MCP tools: stax, next actions, goals, dates, people
read and write stax, next actions, goals, dates and people
Live tools/list seen through a connected HeyStax MCP client on 2026-10-25: stax_list/get/create/update/delete, stax_audit_log, next_actions_list/add/update/complete/delete, goals_, dates_, people_*
MCP tools: records, record grants, record audit log
typed records, with grants and an audit log
Live tools/list on 2026-10-25: record_add/get/list/update/delete, record_grant, record_audit_log, records_schema_get
Today set (pick today’s actions)
your Today list
Live tools/list on 2026-10-25: today_get, today_set, today_clear
Shared stax with roles and @handles
share a stax and assign by @handle
stax_get on the TabStax stax returns people with roles owner and agent and @handles (2026-10-25)
Attention lanes (Must, Should, Good, Meh)
Must, Should, Good, Meh
stax_get returns attention.priority and lane_position (2026-10-25)
Bundled in production mcp v28 on 2026-10-26; fresh authenticated tools/list and behaviour check still needed
Timesheet approval by a lead
approval is coming
CHANGELOG: approval RPC added, production activation remains separate (tabstax root #976, web #142/#143)
Invoices from approved time, invoice nudges, invoice PDF
invoicing is partly built
CHANGELOG roots #978 and #982: production activation remains separate; render-invoice-pdf function exists; epic tabstax#354
Owner-authorized agent assignment and private agent audit (tabstax#986)
internal pilot boundary; public grants remain planned
Migration 20261015020650 applied and catalog/RLS checks passed on 2026-10-25; outside-user boundary #1005 remains open
Memory capture and import (tabstax#932-934)
schema live; user journey unverified
All four 20261005 migrations applied and catalog-verified on 2026-10-25; fresh MCP behaviour check remains
Agents with their own identity: agent_register, agent_whoami, stax_join, stax_leave, next_actions_claim, next_actions_report
agent peer commands are discoverable; claim/report and browser journey still need verification
Root PR #995 merged; mcp ACTIVE v28. Authenticated production initialize → initialized → tools/list returned all six names on 2026-10-26 (evidence/agent-peer-tools-list-2026-10-26.json); agent calls and owner/worker browser journey remain unverified (help #36). Claim/report races are tracked in tabstax#1011
One column per agent on the stax page
web code deployed; signed-in display still to verify
webapps PR #198 merged and its main production deployment READY on 2026-10-25; signed-in agent-column browser check remains (help #36)
Claim rules for agents: owner access levels (read, work, full), five open claims per stax, locked once claimed, deauthorize releases claims, re-authorize refused while claims are open
claim rules are in production; the owner and two-agent journey still needs a browser check
tabstax main 74fbf44: migrations 20261027104402 (grants), 20261027201500 (claim/report), 20261028021204 and 20261028021206 (authority end), 20261029154500 (rejoin guard), 20261029200000 (add/assign); mcp agent-authorize.ts and agent-peers.ts. Release applied to production 2026-11-02. No owner or two-agent browser journey verified yet (help #50)
Planned
Capability
Docs wording
Evidence
@heystax/hey CLI package
do not tell readers to install @heystax/hey yet
cli/package.json names @heystax/hey 0.1.0; npm returns Not found (2026-10-25)
Automatic HookTunnel delivery and @mention dispatch to worker agents
automatic delivery is planned; start or poll a worker for current pickup
tabstax#1008/#1006 and hooktunnel-web#170 are parked; mcp v28 supports manual/poll pickup, not signed push delivery (2026-10-26)
Reading claim, report and release events back over MCP or in the dashboard
claim events are recorded; a way to read them back is planned
Claim, report, release and grant events are written to the stax audit log, but MCP stax_audit_log returns record events only (shared-stax.ts) and no dashboard audit view is observed (2026-11-02)
Claim leases that expire when an agent run dies
planned
Design on tabstax branch spec/agent-runs-leases, Gate A passed with stipulations, not built (2026-11-02)
Hosted bots pick up work on their own; /heystax-connect; pause switch and runs-per-hour cap
planned
tabstax#1015, #1016, blocked on #995
@notify Telegram agent
planned; say ‘the HeyStax Telegram bot’ for what exists
Roadmap FEAT #696 / #682 not started in May snapshot; the Telegram bot is a separate shipped surface