tbenandClaude Opus 5.5
fefc295d15
- Coordinator tools in its own chat (super admin only): list_extensions,
set_extension_access, delete_extension, and update_skill /
update_mcp_server / update_custom_tool for what can't change where
anything is sent (on/off, names, arguments, left-out tools)
- Adding a skill, MCP server or tool, or changing a skill's words, a
server's URL or headers or a tool's kind or config, goes through
propose_skill / propose_mcp_server / propose_custom_tool: stored in
extension_proposals with the bot's background check, shown as a
[proposal:ID] chip that opens a card with Confirm and Reject
- The card's facts are worked out by the app from what Confirm saves: the
host, every {{env.KEY}} and whether it's saved, the config; for a skill
its links, hosts, tool names, mentions of secrets and a diff against
the saved runbook
- Confirming decides once and checks again; a server or tool missing a key
is saved switched off, and the outcome is posted to the bot in chat
- Never from a bot: stdio servers, a URL whose host a template decides,
envs in a prompt tool, a key's value
Co-Authored-By: Claude Opus 5.5 <[email protected]>
21 lines
494 B
TypeScript
21 lines
494 B
TypeScript
import type { ExtensionProposalView } from "@/src/types";
|
|
|
|
type Params = {
|
|
view: Pick<ExtensionProposalView, "status" | "expired">;
|
|
};
|
|
|
|
/**
|
|
* Where a proposal stands, in a word for its chip.
|
|
*/
|
|
export default function proposalStatusLabel({ view }: Params) {
|
|
if (view.expired) return "Expired";
|
|
|
|
return {
|
|
pending: "Waiting for you",
|
|
confirmed: "Confirmed",
|
|
rejected: "Rejected",
|
|
replaced: "Replaced",
|
|
failed: "Failed",
|
|
}[view.status];
|
|
}
|