dev

Files	Last commit	Last update
agent-plugins.mdx	feat: support portable Agent Plugins (#3594)	2 months ago
chatgpt.mdx	docs: make MCP Gateway, client, and AI Gateway pages hyper-focused (#5378) Signed-off-by: Benjamin Shafii <ben@prologe.io>	1 month ago
claude-code.mdx	docs: make MCP Gateway, client, and AI Gateway pages hyper-focused (#5378) Signed-off-by: Benjamin Shafii <ben@prologe.io>	1 month ago
claude-desktop.mdx	docs: make MCP Gateway, client, and AI Gateway pages hyper-focused (#5378) Signed-off-by: Benjamin Shafii <ben@prologe.io>	1 month ago
codex.mdx	docs: make MCP Gateway, client, and AI Gateway pages hyper-focused (#5378) Signed-off-by: Benjamin Shafii <ben@prologe.io>	1 month ago
cursor.mdx	docs: make MCP Gateway, client, and AI Gateway pages hyper-focused (#5378) Signed-off-by: Benjamin Shafii <ben@prologe.io>	1 month ago
gemini-cli.mdx	docs: make MCP Gateway, client, and AI Gateway pages hyper-focused (#5378) Signed-off-by: Benjamin Shafii <ben@prologe.io>	1 month ago
opencode-plugin.mdx	docs: add Integrations with OpenCode, Cursor and Codex status (#5873) * docs: add client integrations and published OpenCode plugin setup * docs: tighten Integrations wording	27 days ago
opencode.mdx	feat(opencode-plugin): OpenWork models and MCP in OpenCode 2 (#5838) * feat(den): let the OpenCode plugin sign in as its own device client Behind opencodePlugin (cloud and self-hosted, off). Den accepts the openwork-opencode-plugin device client only while the flag is on; the /device page names it "OpenWork - OpenCode Plugin" and, for that client only, returns the browser to a loopback return_to after Approve or Deny. The redirect carries the outcome only; the client still gets its session by polling Den. * feat(opencode-plugin): OpenWork Cloud models and MCP in OpenCode 2 New opencode-openwork package: an OpenCode 2 plugin that registers the openwork integration (opencode auth login openwork, browser or code device sign-in) and, on every start, injects the member's AI Gateway providers with their gateway key and the openwork-cloud and openwork-direct-* MCP servers from Den. Adds a docs page and a tag-driven npm publish workflow (opencode-openwork-v*). * test(evals): OpenCode signs in to OpenWork and returns from the browser * fix(opencode-plugin): keep tokens on HTTPS and pin the device return page The plugin only sends the Den session, device token or MCP token over HTTPS, or plain HTTP to a Den on this machine, and trims base URLs without a backtracking pattern. Den web returns the browser only to http://127.0.0.1:<port>/openwork/callback for the plugin's client, so a crafted link cannot aim it at other local services. * fix(opencode-plugin): never publish another account's cached inventory On start the plugin used the cached gateway key and MCP token without checking they belong to the signed-in account. After an account switch while OpenCode was closed, it could publish the previous account's credentials until the first refresh. The cache is now used only when it was fetched for the active connection.	28 days ago
vs-code.mdx	docs: make MCP Gateway, client, and AI Gateway pages hyper-focused (#5378) Signed-off-by: Benjamin Shafii <ben@prologe.io>	1 month ago
windsurf.mdx	docs: make MCP Gateway, client, and AI Gateway pages hyper-focused (#5378) Signed-off-by: Benjamin Shafii <ben@prologe.io>	1 month ago
zed.mdx	docs: make MCP Gateway, client, and AI Gateway pages hyper-focused (#5378) Signed-off-by: Benjamin Shafii <ben@prologe.io>	1 month ago