vision_agent.models
vision_agent.models.AgentMessage
Bases: BaseModel
AgentMessage encompases messages sent to the entire Agentic system, which includes both LMMs and sub-agents.
user: The user's message. assistant: The assistant's message. observation: An observation made after conducting an action, either by the user or assistant. interaction: An interaction between the user and the assistant. For example if the assistant wants to ask the user for help on a task, it could send an interaction message. interaction_response: The user's response to an interaction message. conversation: Messages coming from the conversation agent, this is a type of assistant messages. planner: Messages coming from the planner agent, this is a type of assistant messages. coder: Messages coming from the coder agent, this is a type of assistant messages.
vision_agent.models.CodeContext
Bases: BaseModel
CodeContext is a data model that represents final code and test cases.
code: The final code that was written. test: The test cases that were written. success: A boolean value indicating whether the code passed the test cases. test_result: The result of running the test cases.
vision_agent.models.ErrorContext
Bases: BaseModel
ErrorContext is a data model that represents an error message. These errors can happen in the planning phase when a model does not output correctly formatted messages (often because it considers some response to be a safety issue).
error: The error message.
vision_agent.models.InteractionContext
vision_agent.models.PlanContext
Bases: BaseModel
PlanContext is a data model that represents the context of a plan.
plan: A description of the overall plan. instructions: A list of step-by-step instructions. code: Code snippets that were used during planning.
vision_agent.models.TextOrImage
module-attribute
vision_agent.models.BboxInput
vision_agent.models.BboxInputBase64
vision_agent.models.Florence2FtRequest
Bases: BaseModel
vision_agent.models.JobStatus
Bases: str
, Enum
The status of a fine-tuning job.
CREATED
The job has been created and is waiting to be scheduled to run.
STARTING: The job has started running, but not entering the training phase. TRAINING: The job is training a model. EVALUATING: The job is evaluating the model and computing metrics. PUBLISHING: The job is exporting the artifact(s) to an external directory (s3 or local). SUCCEEDED: The job has finished, including training, evaluation and publishing the artifact(s). FAILED: The job has failed for some reason internally, it can be due to resources issues or the code itself. STOPPED: The job has been stopped by the use locally or in the cloud.