Browser-based graphical shell and control plane for a Linux server you own — real terminal, file manager, live metrics and BYOK AI in one mobile-first workspace. Next.js 16 · React 19 · node-pty · Tailwind v4 · shadcn/ui. Public alpha, self-hosted.
TypeScript browser-shellcontrol-planefile-managerhomelabmobile-firstnextjsptyreactself-hostedserver-managementshadcn-uisysadmintailwindcssterminaltypescriptvpsweb-desktopweb-terminal
import process from "node:process";
import { state } from "./mso-agent-api.mjs";
import { persistSession, resumeArg, startupSession } from "./mso-agent-session-ui.mjs";
import { agentRound } from "./mso-agent-turn.mjs";
// One-shot runs without a composer, without a viewport and without the alternate screen: it is
// one prompt in, text or JSON out, so it stays here rather than inside the interactive entrypoint.
export async function runOneShot(opts) {
const requested = resumeArg(process.argv.slice(2));
const [s, agentSession] = await Promise.all([state(), startupSession(requested)]);
if (!agentSession || agentSession.source !== "cli") throw new Error("could not establish a CLI MSO Agent session");
const session = {
state: s, agentSession, history: Array.isArray(agentSession.history) ? agentSession.history : [],
pendingSkill: null, activeSkill: null, lastInvokedSkill: null,
titleOverride: requested ? (agentSession.title || null) : null,
usage: { apiCalls: 0 }, lastRouting: null, lastElapsedMs: 0, statusBar: false,
permission: "ask", pendingApproval: null,
};
session.history.push({ role: "user", text: opts.prompt });
// `--thinking` is a REPORTING flag only: the stream exposes reasoning token counts,
// not reasoning text, so nothing here changes the turn. Passing `thinking` into
// agentRound would be dead config, so the flag is consumed in the payload below.
const result = await agentRound(null, session, null, undefined, null, { quiet: true, approvalScope: opts.approvalScope });
// A bookkeeping failure must not discard a completed answer.
await persistSession(session).catch(() => undefined);
// `ok` is derived, never assumed. It used to be the literal `true`, so a run whose only write was DENIED
// or whose tool returned ok:false still reported success and exited 0: an agent driving this saw
// "no output, success" and moved on. A turn that hit its limit is also not a success.
const calls = Array.isArray(result?.calls) ? result.calls : [];
const failedCalls = calls.filter((call) => call && call.ok === false);
const ok = failedCalls.length === 0 && !result?.turnLimitReached;
const payload = {
ok, sessionId: session.agentSession.id,
model: `${s.config?.provider || ""}/${s.config?.model || ""}`.replace(/^\//, ""),
approvalScope: opts.approvalScope, text: result?.text || "", rounds: result?.rounds || 0,
toolCalls: calls, usage: result?.usage || session.usage, routing: session.lastRouting, elapsedMs: result?.elapsedMs || session.lastElapsedMs,
...(failedCalls.length ? { failedCalls: failedCalls.map((call) => call.name || "tool") } : {}),
// Prove what was actually attached instead of leaving --file unverifiable.
...(opts.files?.length ? { files: opts.files } : {}),
// `--thinking` surfaces the reasoning ACCOUNTING the provider really reported.
// Streams capture reasoning tokens, not reasoning text, so claiming a reasoning
// block here would be invented output.
...(opts.thinking ? { thinking: true, reasoningTokens: (result?.usage ?? session.usage)?.reasoningTokens ?? null } : {}),
...(result?.turnLimitReached ? { turnLimitReached: true } : {}),
};
if (opts.json) process.stdout.write(`${JSON.stringify(payload)}\n`);
else process.stdout.write(`${payload.text}${payload.text.endsWith("\n") || !payload.text ? "" : "\n"}`);
// Exit code carries the outcome, so a script can branch without parsing stdout.
return ok;
}