Work on GitHub Projects in Matrix OS

Authenticate and inspect everything on the Matrix VPS, preserve existing work, and push or open a PR only when explicitly requested. Prefer hosted Matrix MCP tools with the client's browser OAuth flow. Keep the separately authenticated CLI fallback optional.

MCP-first execution

1. Call list_computers and target one explicit runtimeSlot for every operation.
2. Use run_command with its command argv array for repository probes and short work that needs captured output. Hosted HTTP defaults to and caps commands at 45 seconds; run longer Git operations and tests in persistent terminals.
3. Use create_terminal, create_terminal_tab, select_terminal_tab, and send_terminal_input for long-running or user-observable work. Report the terminal/tab identity.
4. Use bounded file tools only for Matrix-home content; never move local credentials or accept arbitrary local paths.
5. Use read-only chat tools when a prior Matrix chat is necessary to recover project context.

If HTTP MCP authentication fails, use codex mcp login <configured-server-name> or Claude Code's /mcp browser authentication. matrix login repairs only stdio/CLI login. If hosted tools are absent or unavailable, offer the CLI fallback explicitly; never copy credentials between transports.

CLI fallback session policy