Implement Observation Agent with Claude Sonnet 4 and BentoML Hook

Prompt detail, context, and execution controls for real reuse instead of one-off copying.

implementationMulti-Agent Warehouse Optimization Public prompt

Operator-ready prompt for reuse, tuning, and workspace runs.

This item is set up for developers who want to inspect the original language, fork it into Workspace, and adapt the evidence model without losing the source prompt structure.

Best for

Implementation handoffs, eval setup, and prompt tuning where you need the original structure intact.

Reuse pattern

Inspect first, copy once, then fork into Workspace when you want variants, notes, and model settings attached to the same run.

Before first run

Swap domain facts, examples, and any hard-coded entities for your own context.

Tighten the evidence or verification requirement if this is headed toward production.

Decide which failure mode you want to evaluate first before you branch the prompt.

Operator lens

This prompt already carries implementation detail, tool context, and a final-output instruction. Keep that structure intact when you tune it, or your comparison runs get noisy fast.

Best practice: keep one pristine source version, then branch variants around evaluation criteria, evidence thresholds, and output format.
Inspect linked challenge context
Run Profile

Open this prompt inside Workspace when you want a live iteration loop.

Copy for quick reuse, or run it in Workspace to keep prompt variants, model settings, and prompt-history changes in one place.

Structured source with 30 active lines to adapt.

Already linked to a challenge workflow.

Sign in to keep private prompt variations.

View linked challenge

Prompt content

Original prompt text with formatting preserved for inspection and clean copy.

Source prompt
30 active lines
5 sections
No variables
1 code block
Raw prompt
Formatting preserved for direct reuse
Implement the 'Observation Agent' using Mastra AI. This agent will simulate receiving input from a 'curious AI' camera/drone, which you will model as an inference endpoint deployed on BentoML Cloud (for this prompt, a simple function call will suffice, but conceptualize it as a BentoML service). The agent should use Claude Sonnet 4 to interpret observation data (e.g., 'item detected at location X') and update its internal memory. Integrate a simple tool to 'report_observation' to the Inventory Agent.

```typescript
import { createAgent } from '@mastra-ai/core';

// Simulate a BentoML inference call
async function callBentoMLInference(imageData: string): Promise<{ detected_item: string, location: string }> {
  // In a real scenario, this would be an HTTP call to your BentoML service
  console.log(`Simulating BentoML inference for image data: ${imageData}`);
  return { detected_item: 'SKU12345', location: 'Aisle 3, Shelf 5' };
}

const observationAgent = createAgent({
  name: 'observationAgent',
  llm: 'claude-sonnet-4',
  actions: {
    processObservation: async (ctx, imageData: string) => {
      const inferenceResult = await callBentoMLInference(imageData); // Call simulated BentoML service
      ctx.memory.set('last_observation', inferenceResult); // Update agent's memory
      // Use LLM to interpret and potentially call another tool/agent
      const response = await ctx.llm.chat([{
        role: 'user',
        content: `Interprete this observation: Item ${inferenceResult.detected_item} detected at ${inferenceResult.location}. What should I do?`
      }]);
      // Example tool call or message to another agent based on LLM's response
      // await ctx.send('inventoryAgent', { type: 'item_detected', payload: inferenceResult });
      return response.content;
    }
  },
  // ... other configurations like memory providers, etc.
});

// Example usage: observationAgent.actions.processObservation('drone_feed_001');
```

Adaptation plan

Keep the source stable, then branch your edits in a predictable order so the next prompt run is easier to evaluate.

Keep stable

Hold the task contract and output shape stable so generated implementations remain comparable.

Tune next

Update libraries, interfaces, and environment assumptions to match the stack you actually run.

Verify after

Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.

Safe workflow

Copy once for a pristine source snapshot, then move the prompt into Workspace when you want variants, run history, and side-by-side tuning without losing the original.

Prompt diagnostics

Quick signals for how structured this prompt already is and where adaptation work is likely to happen first.

Sections
5
Variables
0
Lists
0
Code blocks
1
Reuse posture

This prompt already mixes executable detail with instructions, so the safest path is to tune examples and interfaces before you rewrite the overall scaffold.

Linked challenge

Multi-Agent Warehouse Optimization

This challenge tasks developers with creating a multi-agent system for autonomous warehouse monitoring and optimization, inspired by 'curious AI' for drones. Using Mastra AI, you will design a team of agents that simulate real-time observation, inventory management, and logistical pathfinding. The system will integrate real-time (simulated) data from 'curious' camera/drone agents, allowing for dynamic adjustments to inventory placement and pick-up routes. Mastra AI's built-in memory and tool-use capabilities will be crucial for agents to maintain a consistent understanding of the warehouse state and interact with simulated external systems (like inventory databases or drone control APIs). Claude Sonnet 4 will power the agents' real-time decision-making and provide a human-readable interface through Coplay AI for supervisors to monitor and, if necessary, intervene in operations. BentoML Cloud will be used to deploy and serve simulated 'curious AI' inference modules, demonstrating scalable edge intelligence.

Workflow Automation
advanced
Prompt origin
Why open it

Use the challenge page to recover the original task boundaries before you tune the prompt. That keeps your variants grounded in the same evaluation target instead of drifting into a different problem.

Open challenge context