Back to directory

tulip agent

A reference implementation of an LLM agent that keeps a large number of tools in a searchable vector-store library rather than listing them all in every prompt, cutting cost and getting around tool-set limits on context or API size.

tulip agent

tulip agent introduces a tool library combining a vector store for semantic search among tools with tool execution, alongside a function-analysis component that generates OpenAI API-compatible tool descriptions for Python functions through introspection. Several agent variants are provided for comparison: baseline agents with no tool library, including one with no tool access at all and one that includes descriptions of every available tool, and several tulip agents that instead search the tool library directly, with a separate tool call, or after a planning step that first decomposes the request into subtasks; one fully autonomous variant can also create and modify its own tool library through create, read, update and delete operations.

An evaluation module covers math problems and a robotics evaluation built on tools created for a related project called AttentiveSupport.

Configuration is done through a .env file specifying the model-serving mode; if no provider is configured, it fails with a clear configuration hint rather than silently falling back to OpenAI. It is written in Python and released under the BSD-3-Clause license.

More in Agent frameworks

See all 902
  • Recurse

    recurse.run

    A serverless harness that lets a coding agent design, test, and deploy its own specialist sub-agents as tools, MCP servers, or bots, defined by a schema-validated manifest.

  • ProofForge

    shulgin.is-a.dev

    An AI-agent pipeline that decomposes a mathematics problem, proves each piece, and formalizes the result in Lean 4 and Mathlib until the Lean kernel accepts it, with six of its proofs already merged into Google DeepMind's formal-conjectures repository.

  • local-coder

    github.com

    Builds a local coding-agent team on top of Ollama and OpenCode by detecting the machine's hardware, recommending models for seven specialist roles, and testing whether each assigned model can actually use tools, edit a repository and pass verification.