13 Commits (d2cf0d16b3e814e2bc86472e309c7ad81bf36cdb)

Author	SHA1	Message	Date
Nathan Azrak	26ec845921	Raise an exception in MKRL and Chat Output Parsers if parsing text which contains both an action and a final answer (#5609) ... Raises exception if OutputParsers receive a response with both a valid action and a final answer Currently, if an OutputParser receives a response which includes both an action and a final answer, they return a FinalAnswer object. This allows the parser to accept responses which propose an action and hallucinate an answer without the action being parsed or taken by the agent. This PR changes the logic to: 1. store a variable checking whether a response contains the `FINAL_ANSWER_ACTION` (this is the easier condition to check). 2. store a variable checking whether the response contains a valid action 3. if both are present, raise a new exception stating that both are present 4. if an action is present, return an AgentAction 5. if an answer is present, return an AgentAnswer 6. if neither is present, raise the relevant exception based around the action format (these have been kept consistent with the prior exception messages) Disclaimer: * Existing mock data included strings which did include an action and an answer. This might indicate that prioritising returning AgentAnswer was always correct, and I am patching out desired behaviour? @hwchase17 to advice. Curious if there are allowed cases where this is not hallucinating, and we do want the LLM to output an action which isn't taken. * I have not passed `send_to_llm` through this new exception Fixes #5601 ## Who can review? Community members can review the PR once tests pass. Tag maintainers/contributors who might be interested: @hwchase17 - project lead @vowelparrot	1 year ago
Matt Wells	1d861dc37a	MRKL output parser no longer breaks well formed queries (#5432) ... # Handles the edge scenario in which the action input is a well formed SQL query which ends with a quoted column There may be a cleaner option here (or indeed other edge scenarios) but this seems to robustly determine if the action input is likely to be a well formed SQL query in which we don't want to arbitrarily trim off `"` characters Fixes #5423 ## Who can review? Community members can review the PR once tests pass. Tag maintainers/contributors who might be interested: For a quicker response, figure out the right person to tag with @ @hwchase17 - project lead Agents / Tools / Toolkits - @vowelparrot	1 year ago
Deepak S V	5cd12102be	Improving Resilience of MRKL Agent (#5014) ... This is a highly optimized update to the pull request https://github.com/hwchase17/langchain/pull/3269 Summary: 1) Added ability to MRKL agent to self solve the ValueError(f"Could not parse LLM output: `{llm_output}`") error, whenever llm (especially gpt-3.5-turbo) does not follow the format of MRKL Agent, while returning "Action:" & "Action Input:". 2) The way I am solving this error is by responding back to the llm with the messages "Invalid Format: Missing 'Action:' after 'Thought:'" & "Invalid Format: Missing 'Action Input:' after 'Action:'" whenever Action: and Action Input: are not present in the llm output respectively. For a detailed explanation, look at the previous pull request. New Updates: 1) Since @hwchase17 , requested in the previous PR to communicate the self correction (error) message, using the OutputParserException, I have added new ability to the OutputParserException class to store the observation & previous llm_output in order to communicate it to the next Agent's prompt. This is done, without breaking/modifying any of the functionality OutputParserException previously performs (i.e. OutputParserException can be used in the same way as before, without passing any observation & previous llm_output too). --------- Co-authored-by: Deepak S V <svdeepak99@users.noreply.github.com>	1 year ago
Mindaugas Sharskus	a4d85f7fd5	[Fix #3365]: Changed regex to cover new line before action serious (#3367) ... Fix for: [Changed regex to cover new line before action serious.](https://github.com/hwchase17/langchain/issues/3365) --- This PR fixes the issue where `ValueError: Could not parse LLM output:` was thrown on seems to be valid input. Changed regex to cover new lines before action serious (after the keywords "Action:" and "Action Input:"). regex101: https://regex101.com/r/CXl1kB/1 --------- Co-authored-by: msarskus <msarskus@cisco.com>	1 year ago
Harrison Chase	aad0a498ac	Harrison/output error (#3094) ... Co-authored-by: yummydum <sumita@nowcast.co.jp>	1 year ago
Harrison Chase	db968284f8	tools refactor (#2961) ... Co-authored-by: vowelparrot <130414180+vowelparrot@users.noreply.github.com>	1 year ago
Harrison Chase	e12e00df12	use output parsers in agents (#2987)	1 year ago
Harrison Chase	9e74df2404	Fix issue#1645: Parse llm_output even there's newline (#2092) (#2099) ... Fix issue#1645: Parse either whitespace or newline after 'Action Input:' in llm_output in mrkl agent. Unittests added accordingly. Co-authored-by: ₿ingnan.ΞTH <brillliantz@outlook.com>	2 years ago
Harrison Chase	a2eeaf3d43	strip whitespace (#680)	2 years ago
Harrison Chase	1ac3319e45	simplify parsing of the final answer (#621)	2 years ago
Harrison Chase	ee3b8e89b3	better parsing of agent output (#418)	2 years ago
Harrison Chase	6eab5254e5	add docs for custom agents (#196)	2 years ago
Harrison Chase	d3a7429f61	(WIP) agents (#171)	2 years ago