Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid assistant ID error prevents replying to an email #11

Open
justinwiley opened this issue Jan 17, 2025 · 3 comments
Open

Invalid assistant ID error prevents replying to an email #11

justinwiley opened this issue Jan 17, 2025 · 3 comments

Comments

@justinwiley
Copy link

justinwiley commented Jan 17, 2025

I'm following the youtube tutorial and readme, using the hosted version of agent inbox.

I've set it up in the hosted version of agent inbox and plugging in my langsmith api key, I see threads. After receiving an email, I see a question that requires an action, I click reply after entering some text and see "invalid assistant ID". Settings doesn't have any option to add an assistant ID.

Looking in the rewrite task I see its used for namespace in some way:

async def rewrite(state: State, config, store):
    model = config["configurable"].get("model", "gpt-4o")
    llm = ChatOpenAI(model=model, temperature=0)
    prev_message = state["messages"][-1]
    draft = prev_message.tool_calls[0]["args"]["content"]
    namespace = (config["configurable"].get("assistant_id", "default"),)  # no value for this in config.yaml
    result = await store.aget(namespace, "rewrite_instructions")
    prompt_config = get_config(config)

How can I set this?

@Culpable
Copy link

Is this the Assistant/Graph ID that comes up when you go into Settings > Add Inbox in the agent inbox UI?

@justinwiley
Copy link
Author

There was no pre-filled value when I did this, I think. This is what it looks like when I click it:

Image

@hwchase17
Copy link
Contributor

Is this still an issue? I remember we had some issue, but i think fixed. May need to clear cache/hard reload agent inbox UI

@hwchase17 hwchase17 reopened this Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants