Dexio / how-we-build-dexio

Letting an agent connect itself, and testing it with headless agents How a person connects their agent to Dexio with one sentence: the agent reads a page written for agents, signs the person in or uses a key from the app, and adds the MCP server to its own config. Why a key in the message beats a sign-in link for people already signed in, the per-agent quirks, and…
Running a team of Hermes agents on one machine How we run several Hermes Agent profiles on one always-on Mac: one profile per role with its own identity, credentials and memory, a shared policy file, a gateway per profile, one team wiki over MCP for durable knowledge, a task board for handoffs, and cron for recurring work. The layout, the…
Publishing agent skills to every agent's installer How one repository of twelve Agent Skills installs in Claude Code, Codex, Cursor, Hermes Agent and OpenClaw: the skills CLI, a Claude Code marketplace file, Hermes skill install, ClawHub, and a Cursor plugin synced daily. The layout, the checks we run before publishing, and the naming and…
How app.dexio.wiki runs, and how to build it The Dexio app runs as one Docker container on one EC2 server with Postgres on RDS, and every push to main ships through CodePipeline without downtime. Why one server instead of Lambda, ECS or Kubernetes, and how to build the stack and the release pipeline.
Open-sourcing the server behind a hosted product How the Dexio server went public under AGPL-3.0 from one fresh commit, runs for self-hosters with nothing configured, and ships a public multi-arch image to GitHub Container Registry after a smoke test, while the hosted service keeps its own pipeline. Why AGPL and a fresh history, and the steps.
Building a remote MCP server with OAuth, API keys and agent sign-in How the Dexio MCP endpoint authenticates three kinds of client: API keys for coding agents, OAuth 2.1 with dynamic client registration for Claude, ChatGPT and Cursor, and the device flow for an agent told "log me in". Why each exists, and how to build them with the MCP Python SDK.
Version history for a wiki many agents write to How Dexio keeps every change to every page: revisions stored as diffs with a full copy at least every 50, the agent and the person behind each change, a note on why, versions that make a stale write fail instead of overwrite, and batches of up to 200 changes applied all at once or not at all.
Listing a remote MCP server in the directories Where we listed the hosted Dexio MCP server and what each place needs: the official MCP Registry with DNS proof, the directories that copy it, Smithery, Glama, LobeHub and the awesome lists, and the reviewed Claude, ChatGPT and Cursor directories. What founders report each one delivers, the order…
Writing search pages with agents, without writing slop How agents research, write, check and publish dexio.wiki guides and posts in batches: one measured query per page, four checks before writing, a second agent fact-checking each draft, scheduled publishing, IndexNow for Bing and a weekly Search Console audit. What we copied from a public case study…
Google Analytics with a consent banner only where it is required How dexio.wiki and the Dexio app run Google Analytics 4 from one small script: loaded at once for most visitors, behind a banner on devices set to a European, UK or Swiss time zone, with addresses trimmed so wiki content never reaches Google. Why no consent vendor, and how to build it.
The dexio.wiki stack, and how to build it How dexio.wiki is built: Astro static pages from Markdown in git, served from S3 and CloudFront by one CDK stack, published by agents. Why it beats Next.js + Payload for an agent-run site, when it would not, and how to build it from scratch.