feat: enhance branding and layout for ship deployment and status bar#61
Merged
Conversation
… and optimize key usage in lists
The original integration attempted to deploy contracts by setting contractAddress: 0x000...0 in a KeeperHub Workflow node, reverse-engineering an undocumented schema. KeeperHub does not support contract creation as an action type, so this approach never worked. Removes: - backend ship API (ship.ts, route mount in index.ts) - mcp-deployer KeeperHub REST client (keeperhub-client.ts) - Ship* event types from agent-events (ShipSimulated, ShipStatus, ShipConfirmed) - Frontend ship row components and inspector ship section
Replaces the hand-rolled REST shim with a direct connection to KeeperHub's official hosted MCP server via @ai-sdk/mcp HTTP transport. - backend/inference.ts: reads KEEPERHUB_API_KEY + KEEPERHUB_MCP_URL env vars and passes them through to runAgentTurn - agent/loop.ts: per-turn createMCPClient with Bearer auth; tools namespaced keeperhub_* via toolToServer map; logs connected tool count on success, warns without crashing when unavailable - agent/system-prompt.ts: Workflow C rewritten for KeeperHub post-deploy automation; Workflow B2 (Sepolia) added; deploy_sepolia in standard workflows; unverified-contract ABI guidance added
Adds a new deployer tool that deploys compiled contracts to Sepolia (chainId 11155111) using a funded wallet — the same pattern as deploy_og_chain but targeting Ethereum Sepolia instead of 0G Galileo. Also strips the now-deleted ship/KeeperHub tools from the deployer server. New env vars on the deployer node: - SEPOLIA_DEPLOY_PRIVATE_KEY (required to enable the tool) - SEPOLIA_RPC_URL (optional, defaults to https://rpc.ankr.com/eth_sepolia) Returns address, txHash, gasUsed, chainId 11155111, and Etherscan Sepolia URL. Deployment is recorded in the session registry under network 'sepolia'.
FEEDBACK.md: 5 grounded feedback items from actually using the hosted MCP (Bearer vs OAuth friction, chainId string format, walletId discovery, no CREATE action type, missing output schemas in list_action_schemas). Adds 'What worked very well' section. README.md, ARCHITECTURE.md, todo.md: remove Ship-to-Sepolia references; position KeeperHub as the post-deploy automation layer. Update architecture table and Phase 4 tracking.
WhyAsh5114
force-pushed
the
feat/51-keeperhub-ship-ui
branch
from
cfeafc4 to
dd444c8
Compare
Co-authored-by: Copilot <copilot@github.com>
…ia + Sepolia for KeeperHub
…+ deploy_sepolia approach; mark mcp-mesh shipped
sundaram123krishnan
approved these changes
May 3, 2026
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
3 participants
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.
This pull request updates both the product documentation (
README.md) and integration feedback (FEEDBACK.md) for Crucible's integration with KeeperHub. The changes clarify the architecture and workflow of Crucible's agentic development environment, especially how it interacts with KeeperHub for on-chain automation, and provide detailed feedback and suggestions for KeeperHub's API and developer experience.Key changes include:
Documentation and Product Narrative Updates
Integration Feedback and Suggestions for KeeperHub
networkfield (should be a stringified chainId, not a name or int), the need to cross-link wallet integration discovery forwalletId, and the lack of contract creation actions in the action-schema.Thematic Grouping of Feedback
Consistency and Clarity