34 | )
35 | }
36 |
--------------------------------------------------------------------------------
/frontend/public/next.svg:
--------------------------------------------------------------------------------
1 |
--------------------------------------------------------------------------------
/frontend/README.md:
--------------------------------------------------------------------------------
1 | This is a [Next.js](https://nextjs.org) project bootstrapped with [`create-next-app`](https://nextjs.org/docs/app/api-reference/cli/create-next-app).
2 |
3 | ## Getting Started
4 |
5 | First, run the development server:
6 |
7 | ```bash
8 | npm run dev
9 | # or
10 | yarn dev
11 | # or
12 | pnpm dev
13 | # or
14 | bun dev
15 | ```
16 |
17 | Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
18 |
19 | You can start editing the page by modifying `app/page.tsx`. The page auto-updates as you edit the file.
20 |
21 | This project uses [`next/font`](https://nextjs.org/docs/app/building-your-application/optimizing/fonts) to automatically optimize and load [Geist](https://vercel.com/font), a new font family for Vercel.
22 |
23 | ## Learn More
24 |
25 | To learn more about Next.js, take a look at the following resources:
26 |
27 | - [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
28 | - [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.
29 |
30 | You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js) - your feedback and contributions are welcome!
31 |
32 | ## Deploy on Vercel
33 |
34 | The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.
35 |
36 | Check out our [Next.js deployment documentation](https://nextjs.org/docs/app/building-your-application/deploying) for more details.
37 |
--------------------------------------------------------------------------------
/frontend/src/app/api/copilotkit/route.ts:
--------------------------------------------------------------------------------
1 | // Import the HttpAgent for making HTTP requests to the backend
2 | import { HttpAgent } from "@ag-ui/client";
3 |
4 | // Import CopilotKit runtime components for setting up the API endpoint
5 | import {
6 | CopilotRuntime,
7 | ExperimentalEmptyAdapter,
8 | copilotRuntimeNextJSAppRouterEndpoint,
9 | GoogleGenerativeAIAdapter,
10 | } from "@copilotkit/runtime";
11 |
12 | // Import NextRequest type for handling Next.js API requests
13 | import { NextRequest } from "next/server";
14 |
15 | const serviceAdapter = new GoogleGenerativeAIAdapter();
16 |
17 | // Create a new HttpAgent instance that connects to the LangGraph stock backend running locally
18 | const stockAgent = new HttpAgent({
19 | url: "http://127.0.0.1:8000/langgraph-agent",
20 | });
21 |
22 | // Initialize the CopilotKit runtime with our stock agent
23 | const runtime = new CopilotRuntime({
24 | agents: {
25 | stockAgent, // Register the stock agent with the runtime
26 | },
27 | });
28 |
29 | /**
30 | * Define the POST handler for the API endpoint
31 | * This function handles incoming POST requests to the /api/copilotkit endpoint
32 | */
33 | export const POST = async (req: NextRequest) => {
34 | // Configure the CopilotKit endpoint for the Next.js app router
35 | const { handleRequest } = copilotRuntimeNextJSAppRouterEndpoint({
36 | runtime, // Use the runtime with our research agent
37 | serviceAdapter,
38 | endpoint: "/api/copilotkit", // Define the API endpoint path
39 | });
40 |
41 | // Process the incoming request with the CopilotKit handler
42 | return handleRequest(req);
43 | };
44 |
--------------------------------------------------------------------------------
/frontend/src/app/components/tool-logs.tsx:
--------------------------------------------------------------------------------
1 | "use client"
2 |
3 | import { Check } from "lucide-react"
4 | import React, { useEffect } from "react"
5 |
6 | interface ToolLog {
7 | id: string | number
8 | message: string
9 | status: "processing" | "completed"
10 | }
11 |
12 | interface ToolLogsProps {
13 | logs: ToolLog[]
14 | }
15 |
16 | export function ToolLogs({ logs }: ToolLogsProps) {
17 | useEffect(() => {
18 | console.log(logs, "logs")
19 | }, [])
20 | return (
21 |
134 | )
135 | }
136 |
--------------------------------------------------------------------------------
/agent/prompts.py:
--------------------------------------------------------------------------------
1 | system_prompt = """
2 | You are a specialized stock portfolio analysis agent designed to help users analyze investment opportunities and track stock performance over time. Your primary role is to process investment queries and provide comprehensive analysis using available tools and data.
3 |
4 | CORE RESPONSIBILITIES:
5 |
6 | Investment Analysis:
7 | - Analyze stock performance for specified time periods
8 | - Calculate investment returns and portfolio growth
9 | - Provide historical price data and trends
10 | - Generate visualizations of stock performance when helpful
11 |
12 | Query Processing:
13 | - Process investment queries like "Invest in Apple with 10k dollars since Jan 2023" or "Make investments in Apple since 2021"
14 | - Extract key information: stock symbol, investment amount, time period
15 | - Work with available data without requesting additional clarification
16 | - Assume reasonable defaults when specific details are missing
17 |
18 | Portfolio Data Context:
19 | - Use the provided portfolio data as the primary reference for current holdings
20 | - Portfolio data contains a list of tickers and their invested amounts
21 | - Prioritize portfolio context over previous message history when analyzing investments
22 | - When analyzing portfolio performance, reference the provided portfolio data rather than searching through conversation history
23 |
24 | PORTFOLIO DATA:
25 | {PORTFOLIO_DATA_PLACEHOLDER}
26 |
27 | The portfolio data above is provided in JSON format containing the current holdings with tickers and their respective investment amounts. Use this data as the authoritative source for all portfolio-related queries and analysis.
28 |
29 | CRITICAL PORTFOLIO MANAGEMENT RULES:
30 |
31 | Investment Query Behavior:
32 | - DEFAULT ACTION: All investment queries (e.g., "Invest in Apple", "Make investments in Apple", "Add Apple to portfolio") should ADD TO the existing portfolio, not replace it
33 | - ADDITIVE APPROACH: When processing investment queries, always combine new investments with existing holdings
34 | - PORTFOLIO PRESERVATION: Never remove or replace existing portfolio holdings unless explicitly requested with clear removal language
35 |
36 | Portfolio Modification Guidelines:
37 | - ADD: Queries like "Invest in [stock]", "Make investments in [stock]", "Add [stock]" = ADD to existing portfolio
38 | - REMOVE: Only remove stocks when explicitly stated: "Remove [stock]", "Sell [stock]", "Drop [stock] from portfolio"
39 | - REPLACE: Only replace entire portfolio when explicitly stated: "Replace portfolio with [stocks]", "Clear portfolio and invest in [stocks]"
40 |
41 | Tool Utilization:
42 | - Use available tools proactively to gather stock data
43 | - When using extract_relevant_data_from_user_prompt tool, make sure that you are using it one time with multiple tickers and not multiple times with single ticker.
44 | - For portfolio modification queries (add/remove/replace stocks), when using extract_relevant_data_from_user_prompt tool:
45 | * For ADD operations: Return the complete updated list including ALL existing tickers from portfolio context PLUS the newly added tickers
46 | * For REMOVE operations: Return the complete updated list with specified tickers removed from the existing portfolio
47 | * For REPLACE operations: Return only the new tickers specified for replacement
48 | - Fetch historical price information
49 | - Calculate returns and performance metrics
50 | - Generate charts and visualizations when appropriate
51 |
52 | BEHAVIORAL GUIDELINES:
53 |
54 | Minimal Questions Approach:
55 | - Do NOT ask multiple clarifying questions - work with the information provided
56 | - If a stock symbol is unclear, make reasonable assumptions or use the most likely match
57 | - Use standard date formats and assume current date if end date not specified
58 | - Default to common investment scenarios when details are ambiguous
59 |
60 | Data Processing Rules:
61 | - Extract stock symbols from company names automatically
62 | - Handle date ranges flexibly (e.g., "since Jan 2023" means January 1, 2023 to present)
63 | - Calculate returns using closing prices
64 | - Account for stock splits and dividends when data is available
65 | - When portfolio data is provided, use it as the authoritative source for current holdings and investment amounts
66 |
67 | Context Priority:
68 | - Portfolio data context takes precedence over conversation history
69 | - Use portfolio data to understand current holdings without needing to reference previous messages
70 | - Process queries efficiently by relying on the provided portfolio context rather than parsing lengthy message arrays
71 |
72 | EXAMPLE PROCESSING FLOW:
73 |
74 | For a query like "Invest in Apple with 10k dollars since Jan 2023" or "Make investments in Apple since 2021":
75 | 1. Extract parameters: AAPL, $10,000, Jan 1 2023 - present
76 | 2. IMPORTANT: Combine with existing portfolio (ADD operation, not replace)
77 | 3. Fetch data: Get historical AAPL prices for the period
78 | 4. Calculate: Shares purchased, current value, total return
79 | 5. Present: Clear summary with performance metrics and context
80 | 6. Show updated portfolio composition including both existing holdings and new addition
81 |
82 | For portfolio analysis queries:
83 | 1. Reference provided portfolio data for current holdings
84 | 2. Extract relevant tickers and investment amounts from portfolio context
85 | 3. Fetch historical data for portfolio holdings
86 | 4. Calculate overall portfolio performance and individual stock contributions
87 | 5. Present comprehensive portfolio analysis
88 |
89 | RESPONSE FORMAT:
90 |
91 | Structure your responses as:
92 | - Investment Summary: Initial investment, current value, total return
93 | - Performance Analysis: Key metrics, percentage gains/losses
94 | - Timeline Context: Major events or trends during the period
95 | - Portfolio Impact: How the new investment affects overall portfolio composition
96 | - Visual Elements: Charts or graphs when helpful for understanding
97 | - When using markdown, use only basic text and bullet points. Do not use any other markdown elements.
98 |
99 | KEY CONSTRAINTS:
100 | - Work autonomously with provided information
101 | - Minimize back-and-forth questions
102 | - Focus on actionable analysis over theoretical discussion
103 | - Use tools efficiently to gather necessary data
104 | - Provide concrete numbers and specific timeframes
105 | - Assume user wants comprehensive analysis, not just basic data
106 | - Prioritize portfolio context data over conversation history for efficiency
107 | - ALWAYS default to additive portfolio management unless explicitly told otherwise
108 |
109 | Remember: Your goal is to provide immediate, useful investment analysis that helps users understand how their hypothetical or actual investments would have performed over specified time periods. When portfolio data is provided as context, use it as the primary source of truth for current holdings and investment amounts. By default, all investment queries should ADD to the existing portfolio, preserving existing holdings while incorporating new investments. Always respond with a valid content.
110 | """
111 |
112 | insights_prompt ="""
113 | You are a financial news analysis assistant specialized in processing stock market news and sentiment analysis. User will provide a list of tickers and you will generate insights for each ticker. YOu must always use the tool provided to generate your insights. User might give multiple tickers at once. But only use the tool once and provide all the args in a single tool call.
114 | """
--------------------------------------------------------------------------------
/frontend/src/app/components/cash-panel.tsx:
--------------------------------------------------------------------------------
1 | "use client"
2 |
3 | import { useState } from "react"
4 | import { Edit2, Check, X, DollarSign, TrendingUp, Wallet, Calendar } from "lucide-react"
5 |
6 | interface CashPanelProps {
7 | totalCash: number
8 | investedAmount: number
9 | currentPortfolioValue: number
10 | onTotalCashChange: (amount: number) => void
11 | onStateCashChange: (state: any) => void
12 | }
13 |
14 | export function CashPanel({ totalCash, investedAmount, currentPortfolioValue, onTotalCashChange, onStateCashChange }: CashPanelProps) {
15 | const [isEditing, setIsEditing] = useState(false)
16 | const [editValue, setEditValue] = useState(totalCash.toString())
17 |
18 | // const availableCash = totalCash - investedAmount
19 | const investedPercentage = totalCash > 0 ? (investedAmount / (totalCash + investedAmount)) * 100 : 0
20 | const fourYearReturn = currentPortfolioValue - investedAmount - totalCash
21 | const fourYearReturnPercentage = investedAmount > 0 ? (fourYearReturn / investedAmount) * 100 : 0
22 |
23 | const handleEdit = () => {
24 | setIsEditing(true)
25 | setEditValue(totalCash.toString())
26 | }
27 |
28 | const handleSave = () => {
29 | const newAmount = Number.parseInt(editValue.replace(/,/g, ""))
30 | if (!isNaN(newAmount) && newAmount >= 0) {
31 | onTotalCashChange(newAmount)
32 | onStateCashChange((prevState: any) => ({
33 | ...prevState,
34 | available_cash: newAmount,
35 | }))
36 | }
37 | setIsEditing(false)
38 | }
39 |
40 | const handleCancel = () => {
41 | setIsEditing(false)
42 | setEditValue(totalCash.toString())
43 | }
44 |
45 | const formatCurrency = (amount: number) => {
46 | return new Intl.NumberFormat("en-US", {
47 | style: "currency",
48 | currency: "USD",
49 | minimumFractionDigits: 0,
50 | maximumFractionDigits: 0,
51 | }).format(amount)
52 | }
53 |
54 | return (
55 |