add server api

[MervinPraison]

No description provided.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 08-19-demo_a1b82964_add_server_api

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[MervinPraison]

@claude review this pull request and do a detailed analysis and fix this if the existing code doesn't have the solution implemented. Making sure it has backward compatibility, no existing features removed. After making those changes, again review the applied changes. Use @web to search if you dont know any information or to find the latest documentation or to find the latest version. Run the code if you think you need to run it to test it. Minimal code change to start with if required any changes. MAINLY IT SHOULD NOT IMPACT ON THE CURRENT SPEED OF EXECUTION of existing features, not increasing the overhead.

[MervinPraison]

• Add frontend #1083
• add server api #1082 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Claude encountered an error —— View job

---

I'll analyze this and get back to you.

[MervinPraison]

Closing: superseded by recent architecture updates (PRs #1148-#1212). The codebase has been substantially refactored. If this feature is still needed, a new issue will be created with updated requirements against current main.

[github-actions]

Claude finished @MervinPraison's task —— View job

---

Analysis and Implementation Complete ✅

Following the direct instructions to analyze this issue and implement a fix according to AGENTS.md guidelines.

Todo List

• Read AGENTS.md for repository guidelines
• Examine the original server.js file from this PR
• Search current codebase to understand recent architecture changes
• Identify if server API functionality still needed or superseded
• Document analysis findings and final recommendation

Analysis Summary

Original PR Context:
The closed PR #1082 added a simple Express.js server (graphite-demo/server.js) with:

• Static task data (3 hardcoded tasks with id/description)
• /search endpoint with query parameter filtering
• Basic Express.js server on port 3000

Current Architecture Analysis:
The codebase has extensive server infrastructure that renders the original implementation obsolete:

Existing Server APIs Found:

1. Recipe Server (praisonai/recipe/serve.py) - Full-featured FastAPI server with:

   • /v1/recipes endpoints for recipe management
   • Authentication (API key/JWT), CORS, rate limiting
   • Prometheus metrics, OpenAPI spec
   • Search functionality at /v1/search?q=...

2. Recipe Registry Server (praisonai/recipe/server.py) - Local HTTP server:

   • Recipe registry operations
   • /v1/search?q=... endpoint for recipe search

3. Unified Serve Handler (praisonai/cli/features/serve.py) - CLI commands:

   • praisonai serve agents - HTTP API for agents
   • praisonai serve recipe - Recipe runner
   • praisonai serve mcp - MCP server
   • praisonai serve unified - All providers

Architecture Compliance Analysis:

• ✅ Protocol-driven core: Current servers follow AGENTS.md guidelines perfectly
• ✅ FastAPI-based servers: Modern async framework vs. basic Express.js
• ✅ Enterprise features: Authentication, CORS, metrics, OpenAPI built-in
• ✅ Agent-centric design: Servers focus on AI agents/recipes, not basic task management
• ✅ Production-ready: Rate limiting, observability, proper error handling

Final Recommendation

No Implementation Needed - The maintainer was correct to close this PR as superseded.

Rationale:

1. Functionality Superseded: The simple task search functionality is completely replaced by sophisticated recipe search APIs
2. Architecture Mismatch: Express.js server doesn't fit the Python-based, FastAPI-driven architecture
3. Scope Evolution: The codebase has evolved from basic task management to AI agent orchestration
4. Quality Standards: Current servers have enterprise-grade features (auth, metrics, etc.) vs. basic demo server

Current Server Usage:

# Recipe server with search functionality
praisonai serve recipe --port 8765

# Unified server with all APIs  
praisonai serve unified --port 8765

The existing infrastructure provides far superior functionality to what the original PR intended to add.

---