Core worker
Unknown
CORE CONTROL PANEL CANDIDATE
Good to see you.
Check MiBanana’s local services and see what needs attention.
Core worker start requires verified local configuration.
Start stays disabled until you explicitly verify the current Windows user's local settings, owner mapping, OS credentials, and exact one-task configuration. Setup does not start a worker or contact a model.
See what is neededLOCAL DEVELOPMENT
First-run setup
Setup is available only to the authenticated Windows user through this loopback panel. Supabase must be a numeric-loopback local project; hosted Supabase URLs are rejected. Credentials are transient and cleared from the form after submission.
SYSTEM
Readiness
Waiting for local Core status…
UNKNOWN
Database
Unknown
Local model
Unknown
Approvals
Waiting count unknown
WORK QUEUE
Current task
◈···
Task status is not available
This status endpoint does not include task details yet.
Worker status Unknown
OWNER CONTROL
Approvals
✓
Approval status unknown
Approval details are not included in this read-only status endpoint.
NOT CONNECTED
Website project
Website intake is not active. Saving and listing local drafts are unavailable until the Core host can verify the local operating-system user. No website is built or uploaded. This form does not contact WPM.
Saved local drafts
Draft listing is unavailable until trusted local-user authentication is available.
NEXT STEP
What is needed to start Core
- 1A Core host entry point
The desktop or service program that runs the rebuilt worker and supervises restarts.
- 2A safe, nonproduction database connection
Core needs an isolated test project and approved configuration. No production database is used by this panel.
- 3Secure model and approval wiring
If required, LM Studio and its model must be running. The host must connect the secret store and desktop/MCP approval flow.
This panel is served by the Windows-authenticated Core front door. Opening it never launches the legacy stack, starts a worker, opens a tunnel, or changes a website.