fips-agents-cli 0.4.0__tar.gz → 0.6.0__tar.gz

{fips_agents_cli-0.4.0 → fips_agents_cli-0.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: fips-agents-cli
-Version: 0.4.0
+Version: 0.6.0
 Summary: CLI tool for creating and managing FIPS-compliant AI agent projects
 Project-URL: Homepage, https://github.com/rdwj/fips-agents-cli
 Project-URL: Repository, https://github.com/rdwj/fips-agents-cli
@@ -38,7 +38,7 @@ A command-line tool for creating and managing FIPS-compliant AI agent projects.
 ## Features
 
 - 🚀 Quick project scaffolding from templates
-- 📦 MCP server, AI agent, and ModelCar project generation
+- 📦 MCP server, AI agent, Go gateway, chat UI, sandbox, and ModelCar project generation
 - 🔧 Automatic project customization (pyproject.toml, module names, entry points)
 - ⚡ Component generation (tools, resources, prompts, middleware) with Jinja2 templates
 - 🎨 Beautiful CLI output with Rich
@@ -100,6 +100,15 @@ fips-agents create mcp-server my-mcp-server
 # AI agent
 fips-agents create agent my-research-agent
 
+# Go HTTP gateway (proxies to an agent backend)
+fips-agents create gateway my-gateway
+
+# Chat UI (connects to a gateway or agent)
+fips-agents create ui my-chat-ui
+
+# Code execution sandbox (sidecar for agents)
+fips-agents create sandbox my-sandbox
+
 # ModelCar (HuggingFace model as container)
 fips-agents create model-car ibm-granite/granite-3.1-2b-instruct \
     quay.io/user/models:granite-3.1-2b-instruct
@@ -143,9 +152,9 @@ fips-agents patch --help
 
 The `create` command group scaffolds new projects from templates.
 
-#### Shared Options (mcp-server and agent)
+#### Shared Options (mcp-server, agent, gateway, ui)
 
-Both `create mcp-server` and `create agent` accept the same options:
+All `create` subcommands (except `model-car`) accept the same options:
 
 | Option | Description |
 |--------|-------------|
@@ -219,6 +228,81 @@ fips-agents create agent my-agent --github --org redhat-ai-americas
 fips-agents create agent my-agent --yes --local
 ```
 
+#### `create gateway`
+
+```bash
+fips-agents create gateway <project-name> [OPTIONS]
+```
+
+Creates a Go HTTP gateway project from the [gateway-template](https://github.com/redhat-ai-americas/gateway-template) repository. The gateway proxies OpenAI-compatible `/v1/chat/completions` requests to an agent backend, with SSE streaming support, heartbeat keepalives, health/readiness probes, and an A2A agent discovery card.
+
+**Arguments:**
+
+- `project-name` — Name for your gateway project
+
+**Options:** Same shared options as above.
+
+**Examples:**
+
+```bash
+# Create gateway project
+fips-agents create gateway my-gateway
+
+# Create with GitHub repo
+fips-agents create gateway my-gateway --github --org my-org
+```
+
+#### `create ui`
+
+```bash
+fips-agents create ui <project-name> [OPTIONS]
+```
+
+Creates a chat UI project from the [ui-template](https://github.com/redhat-ai-americas/ui-template) repository. A Go server with embedded HTML/CSS/JS that provides a browser-based chat interface. Includes a built-in reverse proxy to the backend API, SSE streaming, and markdown rendering.
+
+**Arguments:**
+
+- `project-name` — Name for your UI project
+
+**Options:** Same shared options as above.
+
+**Examples:**
+
+```bash
+# Create UI project
+fips-agents create ui my-chat-ui
+
+# Create with GitHub repo
+fips-agents create ui my-chat-ui --github --private
+```
+
+#### `create sandbox`
+
+```bash
+fips-agents create sandbox <project-name> [OPTIONS]
+```
+
+Creates a code execution sandbox project from the [code-sandbox](https://github.com/fips-agents/code-sandbox) repository. The sandbox provides a FastAPI-based sidecar for secure code execution inside agent pods, with multiple language profiles (base, data-science).
+
+**Arguments:**
+
+- `project-name` -- Name for your sandbox project
+
+**Options:** Same shared options as above.
+
+**Examples:**
+
+```bash
+# Create sandbox project
+fips-agents create sandbox my-sandbox
+
+# Create with GitHub repo
+fips-agents create sandbox my-sandbox --github --private
+
+# Non-interactive mode
+fips-agents create sandbox my-sandbox --yes --local
+```
+
 #### `create model-car`
 
 ```bash
@@ -551,6 +635,36 @@ pytest
 # See AGENTS.md for the /plan-agent slash command workflow
 ```
 
+### Gateway
+
+```bash
+cd my-gateway
+make build           # Build the Go binary
+make run             # Run locally (set BACKEND_URL to your agent)
+make build-openshift PROJECT=my-gateway  # Build on OpenShift
+make deploy PROJECT=my-gateway           # Deploy via Helm
+```
+
+### Chat UI
+
+```bash
+cd my-chat-ui
+make build           # Build the Go binary
+make run             # Run locally (set API_URL to your gateway/agent)
+make build-openshift PROJECT=my-chat-ui  # Build on OpenShift
+make deploy PROJECT=my-chat-ui           # Deploy via Helm
+```
+
+### Sandbox
+
+```bash
+cd my-sandbox
+make install             # Install dependencies
+make test                # Run tests
+make build               # Build container
+make build PROFILE=data-science  # Build with profile
+```
+
 ### ModelCar
 
 ```bash
@@ -625,7 +739,7 @@ fips-agents-cli/
 │       ├── cli.py          # Main CLI application
 │       ├── version.py      # Version information
 │       ├── commands/       # CLI command implementations
-│       │   ├── create.py   # create mcp-server, create agent
+│       │   ├── create.py   # create mcp-server, agent, gateway, ui
 │       │   ├── generate.py # generate tool/resource/prompt/middleware
 │       │   ├── model_car.py # create model-car
 │       │   └── patch.py    # patch command
@@ -747,6 +861,14 @@ MIT License - see LICENSE file for details
 
 ## Changelog
 
+### Version 0.5.0
+
+- Feature: Added `create gateway` command for scaffolding Go HTTP gateway projects from the gateway-template
+- Feature: Added `create ui` command for scaffolding chat UI projects from the ui-template
+- Feature: Go project customization pipeline (`customize_go_project`) handles go.mod, Helm charts, Containerfile, Makefile, and static HTML
+- Fix: Agent scaffolding now replaces `agent-template` in all Helm chart templates, preventing resource name collisions
+- Fix: Agent scaffolding now replaces `OWNER/REPO` placeholder in Containerfile with actual GitHub repo
+
 ### Version 0.4.0
 
 - Feature: Added `create agent` command for scaffolding AI agent projects from the agent-loop template

{fips_agents_cli-0.4.0 → fips_agents_cli-0.6.0}/README.md

@@ -5,7 +5,7 @@ A command-line tool for creating and managing FIPS-compliant AI agent projects.
 ## Features
 
 - 🚀 Quick project scaffolding from templates
-- 📦 MCP server, AI agent, and ModelCar project generation
+- 📦 MCP server, AI agent, Go gateway, chat UI, sandbox, and ModelCar project generation
 - 🔧 Automatic project customization (pyproject.toml, module names, entry points)
 - ⚡ Component generation (tools, resources, prompts, middleware) with Jinja2 templates
 - 🎨 Beautiful CLI output with Rich
@@ -67,6 +67,15 @@ fips-agents create mcp-server my-mcp-server
 # AI agent
 fips-agents create agent my-research-agent
 
+# Go HTTP gateway (proxies to an agent backend)
+fips-agents create gateway my-gateway
+
+# Chat UI (connects to a gateway or agent)
+fips-agents create ui my-chat-ui
+
+# Code execution sandbox (sidecar for agents)
+fips-agents create sandbox my-sandbox
+
 # ModelCar (HuggingFace model as container)
 fips-agents create model-car ibm-granite/granite-3.1-2b-instruct \
     quay.io/user/models:granite-3.1-2b-instruct
@@ -110,9 +119,9 @@ fips-agents patch --help
 
 The `create` command group scaffolds new projects from templates.
 
-#### Shared Options (mcp-server and agent)
+#### Shared Options (mcp-server, agent, gateway, ui)
 
-Both `create mcp-server` and `create agent` accept the same options:
+All `create` subcommands (except `model-car`) accept the same options:
 
 | Option | Description |
 |--------|-------------|
@@ -186,6 +195,81 @@ fips-agents create agent my-agent --github --org redhat-ai-americas
 fips-agents create agent my-agent --yes --local
 ```
 
+#### `create gateway`
+
+```bash
+fips-agents create gateway <project-name> [OPTIONS]
+```
+
+Creates a Go HTTP gateway project from the [gateway-template](https://github.com/redhat-ai-americas/gateway-template) repository. The gateway proxies OpenAI-compatible `/v1/chat/completions` requests to an agent backend, with SSE streaming support, heartbeat keepalives, health/readiness probes, and an A2A agent discovery card.
+
+**Arguments:**
+
+- `project-name` — Name for your gateway project
+
+**Options:** Same shared options as above.
+
+**Examples:**
+
+```bash
+# Create gateway project
+fips-agents create gateway my-gateway
+
+# Create with GitHub repo
+fips-agents create gateway my-gateway --github --org my-org
+```
+
+#### `create ui`
+
+```bash
+fips-agents create ui <project-name> [OPTIONS]
+```
+
+Creates a chat UI project from the [ui-template](https://github.com/redhat-ai-americas/ui-template) repository. A Go server with embedded HTML/CSS/JS that provides a browser-based chat interface. Includes a built-in reverse proxy to the backend API, SSE streaming, and markdown rendering.
+
+**Arguments:**
+
+- `project-name` — Name for your UI project
+
+**Options:** Same shared options as above.
+
+**Examples:**
+
+```bash
+# Create UI project
+fips-agents create ui my-chat-ui
+
+# Create with GitHub repo
+fips-agents create ui my-chat-ui --github --private
+```
+
+#### `create sandbox`
+
+```bash
+fips-agents create sandbox <project-name> [OPTIONS]
+```
+
+Creates a code execution sandbox project from the [code-sandbox](https://github.com/fips-agents/code-sandbox) repository. The sandbox provides a FastAPI-based sidecar for secure code execution inside agent pods, with multiple language profiles (base, data-science).
+
+**Arguments:**
+
+- `project-name` -- Name for your sandbox project
+
+**Options:** Same shared options as above.
+
+**Examples:**
+
+```bash
+# Create sandbox project
+fips-agents create sandbox my-sandbox
+
+# Create with GitHub repo
+fips-agents create sandbox my-sandbox --github --private
+
+# Non-interactive mode
+fips-agents create sandbox my-sandbox --yes --local
+```
+
 #### `create model-car`
 
 ```bash
@@ -518,6 +602,36 @@ pytest
 # See AGENTS.md for the /plan-agent slash command workflow
 ```
 
+### Gateway
+
+```bash
+cd my-gateway
+make build           # Build the Go binary
+make run             # Run locally (set BACKEND_URL to your agent)
+make build-openshift PROJECT=my-gateway  # Build on OpenShift
+make deploy PROJECT=my-gateway           # Deploy via Helm
+```
+
+### Chat UI
+
+```bash
+cd my-chat-ui
+make build           # Build the Go binary
+make run             # Run locally (set API_URL to your gateway/agent)
+make build-openshift PROJECT=my-chat-ui  # Build on OpenShift
+make deploy PROJECT=my-chat-ui           # Deploy via Helm
+```
+
+### Sandbox
+
+```bash
+cd my-sandbox
+make install             # Install dependencies
+make test                # Run tests
+make build               # Build container
+make build PROFILE=data-science  # Build with profile
+```
+
 ### ModelCar
 
 ```bash
@@ -592,7 +706,7 @@ fips-agents-cli/
 │       ├── cli.py          # Main CLI application
 │       ├── version.py      # Version information
 │       ├── commands/       # CLI command implementations
-│       │   ├── create.py   # create mcp-server, create agent
+│       │   ├── create.py   # create mcp-server, agent, gateway, ui
 │       │   ├── generate.py # generate tool/resource/prompt/middleware
 │       │   ├── model_car.py # create model-car
 │       │   └── patch.py    # patch command
@@ -714,6 +828,14 @@ MIT License - see LICENSE file for details
 
 ## Changelog
 
+### Version 0.5.0
+
+- Feature: Added `create gateway` command for scaffolding Go HTTP gateway projects from the gateway-template
+- Feature: Added `create ui` command for scaffolding chat UI projects from the ui-template
+- Feature: Go project customization pipeline (`customize_go_project`) handles go.mod, Helm charts, Containerfile, Makefile, and static HTML
+- Fix: Agent scaffolding now replaces `agent-template` in all Helm chart templates, preventing resource name collisions
+- Fix: Agent scaffolding now replaces `OWNER/REPO` placeholder in Containerfile with actual GitHub repo
+
 ### Version 0.4.0
 
 - Feature: Added `create agent` command for scaffolding AI agent projects from the agent-loop template

fips_agents_cli-0.6.0/planning/agent-registry-roadmap.md

@@ -0,0 +1,156 @@
+# Agent Registry — Research and Roadmap
+
+**Date:** 2026-04-10
+**Status:** Research complete, not yet planned for implementation
+
+## Concept
+
+`fips-agents create registry my-registry` deploys a self-hosted registry to OpenShift with a UI for browsing and managing registered agents, MCP servers, tools, and prompts. Teams register their deployed services with `fips-agents register`, making them discoverable across the organization.
+
+## Industry Landscape (April 2026)
+
+### What exists
+
+**Agent discovery standards:**
+- **A2A Agent Cards** — JSON metadata at `/.well-known/agent.json` describing an agent's capabilities, endpoints, and auth. Linux Foundation stewardship. No registry standard yet (active discussion in a2aproject/A2A#741).
+- **MCP Server Cards** — `.well-known` metadata for MCP servers, on the 2026 MCP roadmap. The official MCP Registry (registry.modelcontextprotocol.io) has ~2,000 entries but is public/community-oriented, not enterprise.
+- **Agent Connect Protocol (ACP)** — Cisco-led (AGNTCY/Linux Foundation), defines REST/OpenAPI for invoking and configuring agents. Complements A2A.
+
+**Cloud provider registries:**
+- **AWS Agent Registry** (preview April 2026) — private governed catalog for agents, tools, skills, MCP servers. Semantic search, approval workflows, IAM + OAuth, CloudTrail audit. Auto-discovers from live A2A/MCP endpoints.
+- **Microsoft Entra Agent Registry** — agent identity and governance in the Microsoft ecosystem.
+- **Google Vertex AI Agent Builder** — tool governance layer with admin-curated catalogs.
+
+**Open source:**
+- **mcp-gateway-registry** (agentic-community) — OAuth (Keycloak/Entra), per-tool RBAC, audit trails, reverse proxy to MCP servers. Closest to what we'd want.
+- **kagent** — Kubernetes-native agentic AI, CRD-based. Early stage.
+
+**Prompt registries:**
+- MLflow Prompt Registry, Langfuse, PromptLayer, LangSmith — versioning, environment aliases, A/B testing. Standalone products, not integrated with agent/tool registries.
+
+**Red Hat direction:**
+- MCP registry, catalog, and gateway stack planned for OpenShift AI
+- MCP servers as items in the AI Assets catalog
+- Longer-term "MCP-as-a-Service" vision
+
+### What's missing
+
+No single open-source system unifies agents, MCP servers, tools, and prompts in one governed catalog with Kubernetes-native lifecycle. The pieces exist in isolation:
+- AWS has the richest registry but is cloud-locked
+- MCP has a public registry but no enterprise governance
+- Prompt registries are standalone products
+- RBAC is protocol-specific (no cross-protocol standard)
+- A2A deliberately punts on the registry problem
+
+### RBAC for agents
+
+Traditional RBAC is insufficient — agents chain multi-step plans autonomously. Emerging model is **dynamic RBAC**: bind an agent's declared purpose + operational context + verified identity to minimal, temporary permissions. Per-tool RBAC (mcp-gateway-registry), relationship-based access (Oso ReBAC), and IAM-based governance (AWS) are the main approaches.
+
+## What We'd Build
+
+### Phase 1: Discovery registry (near-term, after composable capabilities)
+
+A lightweight catalog service that stores and serves metadata:
+
+```
+fips-agents create registry my-registry    # Deploy to OpenShift
+fips-agents register                       # Register current project
+```
+
+**What it stores:**
+- Agent Cards (A2A-compatible JSON) — name, description, capabilities, endpoint, version
+- MCP Server Cards — name, tools list, endpoint, transport
+- Tool manifests — name, description, parameters, which agent/MCP server provides them
+- Prompt entries — name, description, version, variables, template preview
+
+**How registration works:**
+- `fips-agents register` reads the current project type and metadata:
+  - Agent: reads `/.well-known/agent.json` from the running service (or generates from agent.yaml)
+  - MCP server: reads tool list from the running server (or from project structure)
+  - Prompts: reads from `prompts/` directory
+- Pushes the metadata to the registry's API
+- Registry stores it and makes it browsable
+
+**UI:**
+- Browse agents, MCP servers, tools, prompts in a web dashboard
+- Search by name, capability, description
+- View agent cards, tool schemas, prompt templates
+- Show deployment status (healthy/unhealthy via health probes)
+- Links to OpenShift console for the underlying deployments
+
+**Tech stack:**
+- Go server (consistent with gateway/UI templates) or Python FastAPI
+- PostgreSQL for metadata storage
+- OpenShift Route for the UI
+- Helm chart for deployment
+- Periodic health checks against registered endpoints
+
+### Phase 2: Governance (later)
+
+Add approval workflows, RBAC, and audit:
+- Admin approval required before an agent/tool is visible to others
+- Role-based access: who can register, who can discover, who can invoke
+- Audit trail: who registered what, when, who accessed it
+- Integration with OpenShift RBAC (ServiceAccounts, Roles)
+- Keycloak/OIDC for auth (follow mcp-gateway-registry pattern)
+
+### Phase 3: Enterprise tool/prompt catalog (distant)
+
+- Curated enterprise tools that any agent can use (governed, versioned)
+- Enterprise prompt library with approval workflows
+- Agent RBAC: which agents can use which tools (policy-based)
+- Integration with Red Hat's AI Hub / OpenShift AI catalog
+
+## CLI Integration
+
+```bash
+# Deploy a registry
+fips-agents create registry my-registry
+cd my-registry && make deploy PROJECT=my-registry
+
+# Register the thing you're working on
+cd ../my-agent
+fips-agents register                          # auto-detect project type, register with default registry
+fips-agents register --registry my-registry   # explicit registry
+fips-agents register --type agent             # force type
+fips-agents register --type mcp-server
+
+# Browse
+fips-agents registry list                     # list all registered items
+fips-agents registry list --type agent        # filter by type
+fips-agents registry search "web search"      # semantic search
+```
+
+The `register` command could also be a post-deploy hook in the Makefile:
+```makefile
+deploy: ## Deploy to OpenShift and register
+	helm upgrade --install ...
+	fips-agents register --registry $(REGISTRY_URL)
+```
+
+## Open Questions
+
+1. **Storage**: PostgreSQL vs CRDs? CRDs are more Kubernetes-native but harder to query. PostgreSQL is simpler for search and UI.
+2. **Health monitoring**: Should the registry actively poll registered endpoints, or rely on passive registration updates?
+3. **Scope**: Should the registry be namespace-scoped, cluster-scoped, or multi-cluster?
+4. **Red Hat alignment**: How does this relate to Red Hat's planned MCP catalog in OpenShift AI? Complement or conflict?
+5. **Standards**: Should agent cards be A2A-native, or a superset that includes MCP/tool/prompt metadata?
+6. **Auth for registration**: How does `fips-agents register` authenticate with the registry? OpenShift token? API key?
+
+## Relationship to Other Roadmap Items
+
+- **HTTP mode** (Phase 1 of composable capabilities) must ship first — agents need `/.well-known/agent.json` to be registerable
+- **A2A agent cards** are already in the gateway template — the registry reads these
+- **MCP server template** already produces discoverable tools — the registry catalogs them
+- **Multi-agent orchestration** benefits most from a registry — orchestrator agents can discover specialized agents dynamically
+
+## References
+
+- A2A Protocol: https://a2a-protocol.org/latest/specification/
+- A2A Registry Discussion: https://github.com/a2aproject/A2A/discussions/741
+- MCP Registry: https://registry.modelcontextprotocol.io/
+- MCP 2026 Roadmap: https://blog.modelcontextprotocol.io/posts/2026-mcp-roadmap/
+- mcp-gateway-registry: https://github.com/agentic-community/mcp-gateway-registry
+- AWS Agent Registry: https://aws.amazon.com/blogs/machine-learning/the-future-of-managing-agents-at-scale-aws-agent-registry-now-in-preview/
+- AGNTCY ACP Spec: https://github.com/agntcy/acp-spec
+- kagent: https://kagent.dev/