upstash/context7

[email protected] scope: ctx7 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 1d MCP Developer Tools

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

llm mcp mcp-server vibe-coding

Affected surfaces

auth

ReleasePort's take

Light signal

editorial:auto 1d

The `--universal` flag has been removed from the `ctx7 setup` command, and a mode‑selection prompt now appears when only `--api-key` is supplied.

Why it matters: Removal of the ignored `--universal` flag eliminates silent misconfigurations; the new prompt ensures users explicitly choose CLI or Skills mode before proceeding.

Summary

AI summary

Removed unused --universal flag from ctx7 setup and restored CLI + Skills mode selection when only --api-key is provided.

Changes in this release

Type	Severity	Summary	CVE
Feature	Medium	Adds prompt for mode selection when using `ctx7 setup --api-key` without other flags. Adds prompt for mode selection when using `ctx7 setup --api-key` without other flags. Source: llm_adapter@2026-06-02 Confidence: high	—
Deprecation	Low	Adds deprecation warning to skill commands. Adds deprecation warning to skill commands. Source: llm_adapter@2026-06-02 Confidence: high	—
Bugfix	Medium	Removes silently ignored `--universal` flag from `ctx7 setup`. Removes silently ignored `--universal` flag from `ctx7 setup`. Source: llm_adapter@2026-06-02 Confidence: high	—

Full changelog

Patch Changes

2affada: ctx7 setup now properly supports --antigravity, installing skills to .agent/skills, a GEMINI.md rule section (Antigravity reads Gemini-family config), and MCP config to Antigravity 2.0's documented global path ~/.gemini/config/mcp_config.json (with httpUrl for HTTP, matching the Gemini convention). Antigravity has no documented project-level MCP file, so setup --antigravity --project --mcp writes to the global location. Also removes the --universal flag from setup, which was advertised but silently ignored — it never propagated through agent selection, so passing it (e.g. setup --cli --universal --project) caused setup to fall back to auto-detection and write to the wrong directory.
268f52f: ctx7 setup --api-key <KEY> (without --cli, --mcp, or -y) now prompts to choose between MCP server and CLI + Skills modes. Previously, passing --api-key short-circuited to MCP, locking users out of the CLI + Skills option even though that mode also accepts an API key. Explicit --mcp / --cli / --stdio / --oauth / -y still skip the prompt as before.
2e97dae: Add deprecation warning to skill commands

Breaking Changes

Removed `--universal` flag from `ctx7 setup`; it was advertised but silently ignored and could cause incorrect directory writes.

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track upstash/context7

Get notified when new releases ship.

About upstash/context7

Up-to-date code documentation for LLMs and AI code editors.

All releases →