NexusDesk is a self-hosted agent platform whose first complete application turns customer support conversations into retrieved answers, tool calls, and confirmed tickets on your own infrastructure. An agent takes a request, retrieves context from your knowledge base, decides what to do, calls business tools, asks a human to confirm consequential actions, executes, records everything, and feeds evaluation, all as one visible loop rather than a black-box chat. The Harness around that loop is the engineering control layer: it governs permissions and execution boundaries, manages agent memory, routes human handoffs, and keeps an audit trail, so autonomy stays inside lines you drew. You configure, publish, and roll back agents, manage documents, chunks, indexes, and published knowledge versions, and connect Chat, Embedding, Rerank, OCR, and speech models through versioned profiles. Business APIs plug in as tools with their own credentials, parameters, and permissions, and support staff can take over a conversation, draft a ticket from it, and confirm follow-up work without leaving the flow. Channels and application APIs with server-sent events expose the same capabilities to your other systems, while execution records, model and tool call logs, and evaluation results show what the agent actually did. One PostgreSQL handles storage, job queues, and cross-process messaging, and one Compose file starts the stack. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Point the gh CLI at your private Githome server and it works identically to github.com, because every REST v3 and GraphQL v4 endpoint returns byte-for-byte compatible JSON shapes, headers, Link pagination, and ETag caching. A single compiled Go binary serves the REST API under /api/v3, GraphQL under /api/graphql, git smart-HTTP transport, and a server-rendered web UI implementing the GitHub Primer design system with full functionality when JavaScript is disabled. The web interface provides repository browsing with Markdown rendering and syntax highlighting, issue tracking, pull requests with unified diffs and inline code review threads, full-text search, user profiles, and a notifications inbox. Authentication supports personal access tokens with prefix-based identification, OAuth device and web flows, and scoped permissions on every response header with only token hashes stored. The pull request system implements the complete lifecycle including async mergeable state computation, squash, merge, and rebase strategies, commit statuses, check runs, and statusCheckRollup fields. Webhooks deliver events with X-Hub-Signature-256 verification, SSRF protection, and at-least-once retry semantics. Storage supports SQLite for single-node deployments or PostgreSQL for production configurations. Performance optimizations include batch loaders replacing N+1 queries, keyset pagination, FTS-backed search, and GraphQL dataloaders. Docker deployment pulls the official multi-arch container image from GitHub Container Registry. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

PandaDOS is a self-hosted control plane that turns Claude Code and Codex into long-running coding agents you direct through an issue queue from any browser, instead of babysitting a terminal. You file an issue with the outcome and acceptance criteria, and PandaDOS clarifies missing requirements, plans the work, picks the agent, and drives implementation, verification, and delivery in stages. Three approval levels, cautious, balanced, and automatic, decide which actions proceed alone; safe reversible steps continue automatically while destructive, irreversible, production, or secret-related decisions always come back to you. The browser workspace shows the real agent conversation, a native terminal, project files, Git history and diffs, and an execution summary, so you can inspect or intervene at any moment from a phone or laptop. Agents run on local or SSH-connected executor machines inside tmux sessions, and work sharing one repository is serialized while independent projects proceed in parallel without conflicting edits. Modules keep one assigned agent and durable project knowledge, so context from finished issues carries into the next task instead of evaporating when a chat ends. Teams can sign in through Feishu, ask the project manager questions in chat, and receive subscription notifications and approval cards on their phones. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

BlogFactory is the first open-source agent control plane purpose-built for multi-site content operations, shipping 16 distinct capabilities across four operational pillars — Operate, Grow, Control, and Deliver — in its v0.1.0 release. The platform keeps source evidence, AI-generated drafts, revisions, SEO metadata, human review, preflight checks, and CMS delivery destinations in one workspace while enforcing a server-side authority ceiling that prevents agents from ever publishing live content, accessing credentials, or performing administrative actions. AI agents connect through a Streamable HTTP MCP endpoint with OAuth authentication and site-scoped tool discovery, compatible with Codex, ChatGPT, and any MCP-capable client. Content creation supports single articles from keywords, titles, URLs, PDFs, text, or YouTube sources, batch campaigns, and programmatic content via reusable templates with structured data rows. The Search Growth module connects Google Search Console complete-day data to ranked optimization opportunities, 30-day growth plans, content classification by signal type (growing, low-CTR, almost-ranking, page-two, zero-click), indexing checks, and semantic internal-link suggestions. Brand Voice separates global voice rules, writer profiles, knowledge context, and brand guidelines from article mechanics. Approved drafts are delivered as CMS drafts to WordPress, Ghost, Wix, or Framer through idempotent, optimistic-locking-protected handoffs with explicit destination selection and preflight validation. The stack runs on React/Vite, a Hono/TypeScript API, PostgreSQL, and MinIO via Docker Compose, with providers including OpenRouter, OpenAI, and Google services under a bring-your-own-AI model. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Describe the task in plain words, pick the sources and model it may use, and an agent plans the workflow before running it. That is the core loop: agents build editable visual workflows from a task description, execute them on demand or on a schedule, and keep everything traceable. Prefer building by hand and the canvas offers 17 preconfigured steps, branching, undo and redo, JSON import and export, plus eight starter templates. Feed it real work by importing PDF, DOCX, XLSX, CSV, JSON, and text files, or by connecting folders, HTTP endpoints, and approved local programs. Upload a screen recording and it identifies the actions with timestamps, turning a demonstrated process into an editable workflow you can refine. Model calls go to the endpoint you choose: Ollama, LM Studio, vLLM, or any OpenAI-compatible service, local or cloud with your own credentials. Every run can be inspected step by step, cancelled mid-flight, and exported as JSON, CSV, or Markdown reports. Observations from completed runs land in a knowledge and learnings store, where you review them and promote the useful ones into reusable skills for the next task. The Docker release bundles the application with FFmpeg and local Whisper support, and your documents stay on your own machine. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache License 2.0 licensed.