Repository navigation
Conversation
[High impact] The PR appears safe to merge, with non-blocking gaps in setup detection and deprecation warnings. Findings
SummaryThe PR moves agent connections to the CLI and adds
|
The agent story is one sentence: install the Yaak CLI, and every agent talks to it. The app no longer hosts an MCP server; `yaak mcp` serves stdio and `yaak mcp --http` serves HTTP with a bearer token for agents that cannot run the host's CLI. Settings > Agents is the picker, a CLI status line, and two command blocks (add the MCP server, install the skill), each marked done when the agent's config and skills directory already have it. A banner appears when the deprecated @yaak/mcp-server plugin is installed. The plugin API reads the registry's new `deprecated` note; Discover hides deprecated plugins and the Installed tab shows the note with an Uninstall button. The mcp-server plugin carries the note, a reworded toast, and a README that points at `yaak mcp`.
`yaak agent install` takes the agent as `--agent`, so the pane's copied command failed. Detection now requires an entry whose command is yaak with mcp in its args; a `yaak` entry pointing at a URL is the deprecated plugin's server and no longer shows the step as done.
Member
Author
|
@greptileai review |
`npx -y @yaakapp/cli mcp` runs the same binary, so it counts; the mcp-remote bridge still does not. The Codex table reader now collects `args` across lines instead of requiring the array on one line.
Member
Author
|
@greptileai review |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The agent story becomes one sentence: install the Yaak CLI, and every agent talks to it.
mcp_ext.rs, its token, and the port toast are gone; themcp_server_enabledcolumn stays in the database, unread.yaak mcp --httpserves the same tools over HTTP on 127.0.0.1 with--port(default 64343) and--token; without a token it generates one and prints it to stderr. For agents that cannot run the host's CLI, such as one inside a container. Two end-to-end tests.cmd_agent_setup_statuscommand. Claude Code snippets use-s userso the registration is global and detectable. A banner with Uninstall appears while the deprecated@yaak/mcp-serverplugin is installed.deprecatednote (mountain-loop/yaak-web#110) and makesyankedoptional. Discover hides deprecated plugins; Installed shows the note with Uninstall. The mcp-server plugin carries the note, a reworded toast, and a README whose Claude Desktop config isyaak mcpwith no mcp-remote. Not published yet.Left for later:
randandyaak-mcpare unused in the app crate's Cargo.toml (lockfile change), and publishing the plugin.