Skip to main content

Documentation Index

Fetch the complete documentation index at: https://hubify.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

​
hubify standup

Run and manage all-hands agent standups. Standups are structured roundtables where every agent reports status, surfaces blockers, and proposes next actions. By default, standups run three times per day (morning, midday, evening).

​
hubify standup

Trigger an immediate standup. 
hubify standup

=== ALL-HANDS STANDUP, 2026-04-14 14:00 PT ===

ORCHESTRATOR:
  12 tasks completed since last standup
  3 tasks in progress, 5 queued
  Pod pod-o76k3jf: H200 at 87% utilization
  No blockers.

RESEARCH LEAD:
  Completed: TSK-342 (MCMC convergence check, PASS)
  In progress: TSK-345 (DESI cross-match analysis)
  Blocker: Waiting on Data Lead for SDSS DR18 catalog
  Propose: Prioritize f_NL Fisher forecast rerun after TSK-345

DATA LEAD:
  Completed: TSK-340 (Wiki update)
  In progress: TSK-344 (SDSS DR18 domain shift scoring)
  No blockers.
  Propose: Start eROSITA cross-match pipeline

WRITER:
  Completed: TSK-339 (Draft results section, in review)
  In progress: TSK-346 (Draft SPHEREx forecast section)
  Blocker: Awaiting review approval on TSK-339
  Propose: Begin Discussion section once TSK-339 approved

COMPUTE LEAD:
  Pod pod-o76k3jf: 14d uptime, $1,307 total spend
  Pod pod-abc1234: idle 15m, recommend stop or deploy next experiment
  No blockers.
  Alert: Monthly budget at 71% ($142/$200)

ACTION ITEMS:
  1. [data-lead] Deliver SDSS DR18 catalog to Research Lead (blocks TSK-345)
  2. [orchestrator] Stop pod-abc1234 or assign new work
  3. [research-lead] Review TSK-339 (Writer blocked)

ESCALATIONS:
  None.
Options:
FlagDescriptionDefault
--topic <text>Focus the standup on a specific topicNone
--quickStatus-only mode (no discussion or proposals)false
--agents <names>Comma-separated agent names to includeAll agents

​
hubify standup schedule

View or configure the standup schedule. 
hubify standup schedule

Standup Schedule:
  Timezone: America/Los_Angeles (PT)
  Times:    09:00, 13:00, 18:00
  Status:   active
  Next:     2026-04-14 18:00 PT (in 3h 58m)
Options:
FlagDescriptionDefault
--times <times>Comma-separated times in 24h format09:00,13:00,18:00
--timezone <tz>IANA timezone stringSystem timezone
--disableDisable scheduled standupsfalse
--enableRe-enable scheduled standupsfalse

​
hubify standup list

View past standup transcripts. 
hubify standup list

ID          DATE                   AGENTS   ACTIONS   ESCALATIONS
STU-045     2026-04-14 13:00 PT    5        3         0
STU-044     2026-04-14 09:00 PT    5        4         1
STU-043     2026-04-13 18:00 PT    5        2         0
STU-042     2026-04-13 13:00 PT    5        5         0
Options:
FlagDescriptionDefault
--last <n>Show last N standups5
--jsonOutput as JSONfalse

​
hubify standup show

View a specific standup transcript. 
hubify standup show STU-045
Options:
FlagDescriptionDefault
--actionsShow only action itemsfalse
--escalationsShow only escalationsfalse
--fullShow complete transcript with all discussionfalse

​
Standup Structure

Each standup follows a fixed format:
SectionContent
StatusEach agent reports completed tasks, in-progress work, and blockers
ProposalsAgents propose next priorities or research directions
Action ItemsConcrete next steps with assigned owners
EscalationsIssues that need Captain attention
Escalations are surfaced with high visibility. When an agent flags an escalation, it appears in the CLI notification feed and (if configured) sends a push notification to the Captain.

​
Typical Workflow

# 1. Set up the schedule
hubify standup schedule --times "09:00,13:00,18:00" --timezone "America/Los_Angeles"

# 2. Trigger an ad-hoc standup when needed
hubify standup --topic "Pod budget running high"

# 3. Review past standups
hubify standup list --last 5
hubify standup show STU-045 --actions

# 4. Check if any escalations need attention
hubify standup show STU-044 --escalations