[PD1-668] Add ability to add agent post

[amy-nihao]

Description

Add the ability to push agent posts to the frontend by going through cvec-backend endpoint. In the future I think we should add the ability to get/update the posts, or internally allow edits in the frontend. Currently the only way to fix a mistake in a post is to edit it from supabase or delete and make a new one.

Risk

We are making the process to add agent posts public by adding it here. This is not ideal and we should have a private sdk repo soon

Test

Tested with https://github.com/CVector-Energy/cvec-backend/pull/88

[linear]

PD1-668 ATEK Ops Agent Page

The demo version exists in jetson, we need to remake one for the actual frontend

[gemini-code-assist]

Summary of Changes

Hello @amy-nihao, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the CVec client by integrating the capability to create and publish agent posts. It introduces a new add_agent_post method, allowing external systems or agents to programmatically submit structured content, including titles, authors, content bodies, and optional recommendations and tags, to the frontend via the cvec-backend. This change lays the groundwork for more dynamic content generation and communication within the platform.

Highlights

• New Agent Post Creation: Introduced the add_agent_post method to the CVec client, enabling the creation of agent posts through the cvec-backend endpoint.
• Agent Post Data Models: Added new Pydantic models (AgentPost, AgentPostRecommendation, AgentPostTag, Severity) to define the structure and content of agent posts.
• Example Usage: Included an example script (add_agent_post_example.py) demonstrating how to programmatically add an agent post with recommendations and tags.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds the ability to create agent posts through the SDK. The overall implementation is good, but I've identified a critical issue that would cause an ImportError and break the package. Additionally, there are a few high and medium severity issues related to type consistency and code maintainability. I have provided specific comments and code suggestions to address these points, which should improve the robustness and clarity of the new functionality.

[joshuanapoli]

Thank you.

I tested this in the context of https://github.com/CVector-Energy/cvec-data-analysis/pull/2