Client Workspace

Every client in one place.

Tasks, calendars and mail from every Google account your clients use, with a chat on Meta’s Muse models and an MCP for your coding agent.

In the picture, a message from Developer Platform arrives, it shows as a possible reply for the task that waits for it, and the task is closed as approved.

The demo’s Overview: a small agency with 3 clients and 3 projects of its own, as a message arrives for the task that waits for it.

Works with

  • GmailEvery account’s mail
  • Google CalendarEvery account’s meetings
  • Meta’s Muse modelsThe chat, when you ask
  • Any MCP coding agentOn the same projects

Every client keeps its own accounts.

Hang a Google account on the client or project it serves. Its calendar and its mail land there, beside the tasks, and an account on a client reaches every one of its projects.

In the picture, the sidebar moves from Larkspur Bakery to Studio Atlas and to Operations, and each one's page shows its own account, its next task, its meeting and its mail.

The workspace finds the reply. You decide.

Say in your words what a task waits for. What arrives with those words shows up as a possible reply, and the task stays open until you say which one answered it and how it ended.

In the picture, the task that waits for the app review shows two possible replies; the first one is chosen, and the task is closed as approved.

A chat that acts only when you ask.

It runs on Meta’s Muse models, with the tools you use: it adds tasks, records decisions and tells you what is pending. It takes your voice and your screenshots too, and every change it makes comes with its Undo.

In the picture, the person asks the chat to remind them to chase the Studio Atlas payment today; Muse adds the task, offers its Undo, and says where it put it.

Your coding agent works on the same projects.

Issue a token on a client or a project and add one block to the repository’s .mcp.json. The agent asks what changed since its last session, and what it adds shows up marked as its own.

.mcp.json

{
  "mcpServers": {
    "client-workspace": {
      "type": "http",
      "url": "https://brief.hiagencia.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${CLIENT_WORKSPACE_TOKEN}"
      }
    }
  }
}

In the picture, a coding agent asks the workspace what changed since its last session, then asks for a review of a pull request, and the review lands among today's tasks marked as the agent's.

The demo is a week at a small agency.

3 clients and 3 projects of its own, with their tasks, mail and meetings, in a workspace only you see.