Component
TinyOffice (web portal)
Problem or Motivation
Problem
TinyOffice currently assumes TinyClaw is already running, but provides limited control over the running system.
Users still need the CLI for start/stop/restart workflows and process-level operations.
Proposal
Add a runtime control panel in TinyOffice.
Suggested scope:
- Show status of daemon / API / queue / heartbeat
- Show per-channel running state
- Restart queue
- Restart heartbeat
- Restart individual channels
- Show whether config changes require restart
- Optionally expose stop/start controls where safe
Why this matters
If TinyOffice is meant to become the main operational surface, it needs to cover basic runtime management instead of only observing state.
Notes
Even if full process control is deferred for safety reasons, TinyOffice should at least explain what is running, what is unhealthy, and what action the user should take.
Proposed Solution
Add a runtime control panel in TinyOffice.
Alternatives Considered
No response
Additional Context
No response
Component
TinyOffice (web portal)
Problem or Motivation
Problem
TinyOffice currently assumes TinyClaw is already running, but provides limited control over the running system.
Users still need the CLI for start/stop/restart workflows and process-level operations.
Proposal
Add a runtime control panel in TinyOffice.
Suggested scope:
Why this matters
If TinyOffice is meant to become the main operational surface, it needs to cover basic runtime management instead of only observing state.
Notes
Even if full process control is deferred for safety reasons, TinyOffice should at least explain what is running, what is unhealthy, and what action the user should take.
Proposed Solution
Add a runtime control panel in TinyOffice.
Alternatives Considered
No response
Additional Context
No response