Repository navigation
chore: remove Zepto integration - #192
Conversation
7cf2a1e to
26e6866
Compare
|
@codex review |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
- Remove Zepto tools, auth, skill, and configuration - Remove the Node bridge from the production image and deploy flow - Preserve generic MCP, Gmail, and privacy behavior
26e6866 to
296866b
Compare
What
Remove the Zepto integration and its host-side Node MCP bridge from Blacki. This PR is rebased onto
mainafter #191 merged.Why
Zepto is no longer needed. Removing it also drops the Node runtime and bridge-only deployment settings while retaining generic ADK MCP skill support.
How
agent_browsertool, task-worker removal, Chromium/agent-browser sandbox image, and sandbox boundary from feat: add direct browser tool and drop worker #191.Rebase
mainat5d1a049after feat: add direct browser tool and drop worker #191 was squash-merged.26e6866).Tests
uv run ruff format --checkuv run ruff checkuv run mypy .(212 source files)uv run pytest --cov=src(2,032 passed, 0 skipped, 100% line and branch coverage)uv run --no-sync mkdocs build --strictuv run pytest tests/test_deployment_contract.py(28 passed)bash -n setup.sh entrypoint.shdocker compose -f compose.yaml -f compose.prod.yaml config --quietblacki-stacked-test:latest/readysmoke test passed on attempt 2Related Issues