▶️ Getting Started
How to submit your first remote job from the portal. Three entry points, one execution engine.
Prerequisites
Before submitting jobs, ensure Bifrost is running:
| Check | How |
|---|---|
| Bifrost is online | Look for the green 🟢 indicator in the portal sidebar (next to the gear icon). If red, Bifrost is offline. |
| CLI is installed | Claude CLI (claude) or Gemini CLI (gemini) must be available on the Bifrost
server. |
| Health check | Visit bifrost.mipos.io:4003/health — should return {"status":"ok"} |
Entry Point 1: Remote Page
The dedicated job submission interface. Best for full control over all job parameters.
Steps
| # | Action |
|---|---|
| 1 | Navigate to the Remote tab in the portal sidebar |
| 2 | Click New Job button |
| 3 | Select a Job Type (session, research, workflow, clara, autopilot) |
| 4 | Write your Prompt — be specific and self-contained |
| 5 | Optionally set LLM Provider, Model, and Effort |
| 6 | Click Submit |
All options available: The Remote page exposes every job parameter — type, prompt, backend,
model, effort, and linked task. Use it when you need precise control.
Entry Point 2: Inbox Compose
Quick dispatch from the Inbox. Best for research tasks, workflow runs, and Clara sweeps.
Steps
| # | Action |
|---|---|
| 1 | Open the Inbox tab |
| 2 | In the Compose area, write your prompt |
| 3 | Use the type selector to choose research, workflow, or other type |
| 4 | Submit — the job is created in D1 and picked up by Bifrost |
Clara shortcut: The Clara button in the Inbox header dispatches a Clara sweep job directly —
no prompt needed. It uses your default LLM settings.
Entry Point 3: Task Modal
Launch a job directly from a task card. Best for running work on a specific task autonomously.
Steps
| # | Action |
|---|---|
| 1 | Click any task card in Dashboard or Backlog to open the Task Modal |
| 2 | Click the ▶ Start Remote button |
| 3 | Choose job type and optionally customize the prompt |
| 4 | Submit — the job is automatically linked to the task via task_id |
Auto-linking: Jobs started from the Task Modal automatically set
task_id, so the
job appears in the task's job history and is visible in the Channels tab.
After Submission
Once you submit a job, here's what happens:
Job created in D1
→
Bifrost picks it up
→
CLI spawned
→
SSE streams output
| What | Where to See It |
|---|---|
| Job status updates | Remote tab — pending/running/done tabs |
| Live output stream | Click the running job card → SSE viewer opens |
| Progress messages | Channels tab → #job-{id} channel |
| Start/complete notifications | Channels tab → #dev channel |
| Cancel a job | Click Stop button on the running job card |
Writing Good Prompts
Remote jobs are autonomous — the agent can't ask follow-up questions. Write prompts that are self-contained:
| Do | Don't |
|---|---|
| Be specific: "Add a delete button to the TaskModal that calls DELETE /api/tasks" | Be vague: "Improve the task page" |
| Include context: "The button should match the existing red badge style" | Assume context: "Make it look like the other one" |
| Set scope: "Only modify TaskModal.jsx and tasks.js" | Leave scope open: "Fix everything" |
| Define done: "Commit and deploy when complete" | Leave it hanging: no ending instruction |
Remember: Every prompt automatically gets an "Execute without asking for confirmation"
suffix. The agent will act autonomously on the full prompt.