Skip to content

locus-sdk 5.2.0 — Oracle Agentic Harness SDK: OCI GenAI Sandboxes as a coding-harness workspace, the OCI tool-call-only turn fix, a2a-mesh on A2A v1.0

Choose a tag to compare

@fede-kamel fede-kamel released this 29 Oct 19:51
dbb7e59

Added

  • OCI GenAI Sandboxes as a coding-harness workspace.
    locus.harness.OCISandboxBackend runs the harness tools in an OCI
    Enterprise AI sandbox (pip install "locus-sdk[oci-sandbox]", oci
    2.189.0+). create(project_id, ...) makes a sandbox and deletes it on
    close(); connect(sandbox_id, ...) attaches to one; extend() adds
    lifetime. Commands stream with their output order kept, run under an
    in-sandbox deadline, and return at most 900 kB of output, because the
    service loses larger output. Background state lives in
    /workspace/.locus-harness (/tmp is read-only there), now in
    SKIP_DIRS.

Changed

  • locus-sdk-security ships from the repository, not from PyPI. The
    5.1.0 notes said the release workflow publishes it; the upload needs a
    PyPI project that does not exist, and the package is one install line
    from the repository at the matching tag, so the workflow publishes
    locus-sdk alone again and the install instructions say so.

  • Documentation site: the coding harness has its own section, and the
    site reads on a phone.
    Concepts gains a "The coding harness" group with
    an overview and one page each for OCI GenAI Sandboxes and NVIDIA OpenShell;
    the home page names the sandbox in its hero, in the Oracle Cloud grid and
    in the harness grid with an end-to-end snippet. Every page was re-laid for
    360 to 768 px: the title gets the full column with the page actions on
    their own row, diagrams fit the column and expand full-screen at their
    design width, tables that cannot be read at phone width render as cards,
    filter inputs are 16 px so iPhone Safari does not zoom, and touch targets
    are finger-sized. The header shows the released version from the build
    instead of a badge image that could be served stale from a cache.

Fixed

  • OCI Generative AI, OpenAI-compatible transport: a tool-call-only
    assistant turn no longer breaks the conversation.
    Such a turn has no
    text; OpenAI accepts "content": null for it, OCI's endpoint answers
    400 Invalid type for 'messages[n].content': expected an object, but got null, and since the history is replayed on every later turn one tool call
    ended the run. The transport now sends "" for every vendor on OCI.
  • Cognitive router: a capability listed twice compiles once. An
    extractor that repeats a capability id made the compiler bind the same tool
    twice and the agent's registry rejected it (Tool already registered).
    Ids are de-duplicated before binding.
  • The a2a-mesh example routed no requests, and spoke only the pre-v1.0
    surface.
    A2AClient.get_agent_card() returns v1.0 cards whose skills
    are AgentSkill objects, but the orchestrator matched them as strings, so
    every query failed with "No peer advertises skill". The orchestrator now
    routes on skill ids, prints each peer's protocolVersion and
    supportedInterfaces, and talks A2A v1.0 JSON-RPC: SendMessage, with
    the reply read from the task's artifacts, and SendStreamingMessage for
    --stream. --legacy keeps the flat /a2a/invoke and /a2a/stream
    endpoints to show backwards compatibility. The web console does the same:
    it discovers peers from /.well-known/agent-card.json, sends with
    SendMessage and renders the SendStreamingMessage task events. Tests
    cover the v1.0 card, both methods and routing on v1.0 skill ids (#274).