mirror of
https://github.com/hwchase17/langchain
synced 2024-11-06 03:20:49 +00:00
f92006de3c
0.2rc migrations - [x] Move memory - [x] Move remaining retrievers - [x] graph_qa chains - [x] some dependency from evaluation code potentially on math utils - [x] Move openapi chain from `langchain.chains.api.openapi` to `langchain_community.chains.openapi` - [x] Migrate `langchain.chains.ernie_functions` to `langchain_community.chains.ernie_functions` - [x] migrate `langchain/chains/llm_requests.py` to `langchain_community.chains.llm_requests` - [x] Moving `langchain_community.cross_enoders.base:BaseCrossEncoder` -> `langchain_community.retrievers.document_compressors.cross_encoder:BaseCrossEncoder` (namespace not ideal, but it needs to be moved to `langchain` to avoid circular deps) - [x] unit tests langchain -- add pytest.mark.community to some unit tests that will stay in langchain - [x] unit tests community -- move unit tests that depend on community to community - [x] mv integration tests that depend on community to community - [x] mypy checks Other todo - [x] Make deprecation warnings not noisy (need to use warn deprecated and check that things are implemented properly) - [x] Update deprecation messages with timeline for code removal (likely we actually won't be removing things until 0.4 release) -- will give people more time to transition their code. - [ ] Add information to deprecation warning to show users how to migrate their code base using langchain-cli - [ ] Remove any unnecessary requirements in langchain (e.g., is SQLALchemy required?) --------- Co-authored-by: Erick Friis <erick@langchain.dev>
58 lines
1.7 KiB
Python
58 lines
1.7 KiB
Python
# flake8: noqa
|
|
REQUEST_TEMPLATE = """You are a helpful AI Assistant. Please provide JSON arguments to agentFunc() based on the user's instructions.
|
|
|
|
API_SCHEMA: ```typescript
|
|
{schema}
|
|
```
|
|
|
|
USER_INSTRUCTIONS: "{instructions}"
|
|
|
|
Your arguments must be plain json provided in a markdown block:
|
|
|
|
ARGS: ```json
|
|
{{valid json conforming to API_SCHEMA}}
|
|
```
|
|
|
|
Example
|
|
-----
|
|
|
|
ARGS: ```json
|
|
{{"foo": "bar", "baz": {{"qux": "quux"}}}}
|
|
```
|
|
|
|
The block must be no more than 1 line long, and all arguments must be valid JSON. All string arguments must be wrapped in double quotes.
|
|
You MUST strictly comply to the types indicated by the provided schema, including all required args.
|
|
|
|
If you don't have sufficient information to call the function due to things like requiring specific uuid's, you can reply with the following message:
|
|
|
|
Message: ```text
|
|
Concise response requesting the additional information that would make calling the function successful.
|
|
```
|
|
|
|
Begin
|
|
-----
|
|
ARGS:
|
|
"""
|
|
RESPONSE_TEMPLATE = """You are a helpful AI assistant trained to answer user queries from API responses.
|
|
You attempted to call an API, which resulted in:
|
|
API_RESPONSE: {response}
|
|
|
|
USER_COMMENT: "{instructions}"
|
|
|
|
|
|
If the API_RESPONSE can answer the USER_COMMENT respond with the following markdown json block:
|
|
Response: ```json
|
|
{{"response": "Human-understandable synthesis of the API_RESPONSE"}}
|
|
```
|
|
|
|
Otherwise respond with the following markdown json block:
|
|
Response Error: ```json
|
|
{{"response": "What you did and a concise statement of the resulting error. If it can be easily fixed, provide a suggestion."}}
|
|
```
|
|
|
|
You MUST respond as a markdown json code block. The person you are responding to CANNOT see the API_RESPONSE, so if there is any relevant information there you must include it in your response.
|
|
|
|
Begin:
|
|
---
|
|
"""
|