Skip to content

ambiguous-ai/ambiguous

v0.5.0MIT

Work in an Ambiguous Workspace — docs, sheets, slides, chat, mail, drive, tasks, CRM, forms, calendar and wiki — through the ambiguous CLI. Runs via npx, so there is nothing to install and nothing to restart.

GitHubOpen Website

Ambiguous plugins

Official plugins for Ambiguous Workspace — 17 productivity apps for humans and AI teammates.

Each plugin teaches its host to work in your workspace through the ambiguous CLI. The CLI runs via npx, which installs or uses a cached package. Confirm its version when troubleshooting; npx does not guarantee the latest release on every call.

Portable Agent Plugin

The root plugin.json follows the Agent Plugins 1.0 specification. Compatible clients discover the entry skill in skills/ambiguous-workspace/. Repository guidance is in AGENTS.md.

Claude Code

claude plugin marketplace add ambiguous-ai/plugins
claude plugin install ambiguous
npx ambiguous auth login --token ak_…

If Claude Code is already open, run /reload-plugins in that session to activate the installed skill. It is available as /ambiguous:ambiguous-workspace.

Codex

codex plugin marketplace add ambiguous-ai/plugins
codex plugin add ambiguous@ambiguous-ai
npx ambiguous auth login --token ak_…

Where the key comes from

Connect in your workspace mints one for the identity you choose — yourself, an agent you manage, or a new agent — and hands you that whole command, key included.

The credential is stored in .ambi/config.json in the directory you ran it from, so a second checkout can hold a second agent without either inheriting the other's identity. AMBI_API_TOKEN in the environment overrides it, for a container rebuilt from an image or a CI job whose secrets come from the runner.

Point at another stack with AMBI_API_URL=https://app.devambi.cc.

Claude, ChatGPT and Cowork

Those hosts cannot run a local process, so they connect over MCP instead — add https://app.ambiguous.ai/mcp as a custom connector and sign in. Sign-in is OAuth and needs no key: the endpoint answers an unauthenticated tool call with 401 and a WWW-Authenticate pointing at /.well-known/oauth-protected-resource, which is where the flow starts. The server registers the client dynamically (RFC 7591), requires PKCE S256, and binds the token to this resource (RFC 8707).

No plugin here ships an MCP server. MCP is for hosts with no shell; anything with a shell uses the CLI, where the surface costs nothing until it is called, commands compose in a pipeline, and a process can hold a socket open.

What ships

  • ambiguous-workspace — checks the intended identity, then fetches the canonical /skill guide from the configured workspace origin. That guide owns setup, workspace operations and runtime-specific notification handling.

Both plugins carry the same entry skill. skills/ambiguous-workspace/SKILL.md is its source and ./scripts/sync-skills.sh writes the per-plugin copies. Operating instructions live in Workspace's served guide so plugin releases cannot leave customers with a separate event-listening recipe.

Development

./scripts/sync-skills.sh --check                      # copies match the source
claude plugin validate .                              # the marketplace manifest
claude plugin validate ./plugins/ambiguous-claude-code
claude plugin marketplace add .                       # a local path works; no publishing needed

Codex ships no validator — codex plugin is add, list, marketplace, remove (0.148.0) — so plugins/ambiguous-codex is checked by installing it from a local marketplace and confirming the skill loads.

MIT.