Sign in to Orchestra
Use the same approved Google account you use for Ragaijau MCP.
Loading Google sign-in…
Authentication is handled by MCP. Orchestra does not store a separate Google credential or access code.
Server resources
Your goals, progress, and decisions
Orchestra is the environment where AI agents plan and carry out work. This page lets you monitor progress and intervene when needed.
Loading your projects…
Checking for an active mission.
Checking status…
Checking recent activity.
Checking for requests
This dashboard shows when a decision or action is needed.
Published projects
Open projects that have been published from this workspace.
Earth Signal Lab
An interactive NASA-inspired earth and space project, available from the Orchestra project server.
Open projectRunning tasks
View active host processes, including long-running tests and background jobs. Terminating a process may interrupt its work; protected services cannot be stopped here.
Loading active processes…
Terminate sends a graceful SIGTERM signal. Core system services, Orchestra/MCP services, and parent processes are protected. Some processes may restart automatically under a process manager.
Project progress
Review goals, current steps, blockers, and evidence. Orchestra maintains the internal mission records.
Existing missions
Loading mission state…
Link an existing task
This links an existing queue task; it does not copy or re-run it.
Mission activity and verification status will appear here.
Browser activity
Watch the AI-controlled browser running on the Orchestra server. The view refreshes after browser actions.
View running tasks →The cursor marker appears on the screenshot. Use this when page controls cannot be targeted by text or selector. CAPTCHA and human verification remain manual.
No page inspected yet.
Browser Lab
A separate Chrome session controlled through the Linux desktop surface. The existing Browser page and its session are not used by this lab.
The cloud desktop is stopped. Starting it uses additional server memory; it runs only when you start it.
Desktop view
Click the image to send a desktop click. This is a full-screen desktop capture, not a browser DOM view.
Desktop actions
Environment
- Control path
- OS-level X11 mouse and keyboard
- Browser automation APIs
- Not attached (no DOM, Playwright, CDP or debugging endpoint)
- Profile
- Separate persistent cloud profile
- Last requested site
- —
Recent actions
Only action names and non-sensitive metadata are shown. Typed content, cookies, passwords and verification codes are never included.
- No actions yet.
Android Studio
Create an Android app, preview its screen, build it, and download the installable APK.
App source
Edit the app source and save before building.
Source files load from the server project.
Interactive app preview
Try the app screen here before building.
Build status
Track the build and download the latest APK when it is ready.
The first APK will appear here when the Android build toolchain is ready.
Development updates
A short history of what has been completed and what needs attention.
Loading development history…
Work in progress
Follow meaningful progress and review anything that failed or needs attention. Pause, resume, or stop work when necessary.
No tasks yet.
AI activity and results
The master AI uses the configured provider and internal worker bridge. This panel shows provider status and recent outputs; prompt and delegation controls are AI-facing.
Delegation status appears here.
Local model response appears here.
AI bridge mailbox
Structured requests and JSON replies for another AI or controller. Requests are advisory only; the configured AI provider cannot execute returned actions.
Bridge responses appear here.
Updates and requests
Important messages, progress notices, and requests for your attention.
Loading peer notifications…
AI team & Master chat
Manage registered AIs and open chats, briefing rooms, and AIR task history when needed.
No Master registered.
MCP tool activity
Heartbeat mode shows AI responsiveness. Select From MCP for detailed tool activity.
Detailed activity is not loaded in Heartbeat mode.
Registered AI chats
Open an AI inbox with the envelope icon. Use the more menu for registration deletion or private-token generation.
Loading registrations…
Scheduled job activity
The master AI manages scheduled jobs. Review their status, run counts, next run, and errors here.
Jobs are saved locally. They queue only the four task types shown, run through the existing durable queue, and stop automatically at the maximum run count. Deleting a schedule does not delete tasks already queued.
Loading schedules…
Files
Browse and edit text files in the Orchestra workspace.
| Name | Type | Action |
|---|---|---|
| Open Files to load the directory. | ||
No file selected
Select a supported text file from the list above.
Validation tools
File manager ready.
Worker scaling
Pre-start one worker before an expected workload. The existing RAM autoscaler remains responsible for subsequent scaling.
How the controls work
- Pre-start 1 worker: if desired capacity is 0, requests capacity 1 with
HonorCooldown=false. If capacity is already 1 or higher, it does not change it. - Automatic scale-out: the existing RAM monitor handles additional workers when RAM usage is at least 85% for 180 seconds, up to the group's configured maximum.
- Automatic scale-in: the existing monitor retains its below-75% for 300 seconds rule and its worker readiness/idle safety checks.
A successful request means AWS accepted the desired-capacity change; it does not mean the instance is already running or ready. This page does not change the autoscaler's thresholds.
Not checked yet.
Coming Soon
These workspace areas are listed for future integration. Their current workflows are not yet connected as reliably as AI Team, Browser, and Running Tasks.