Open Connector
User Guide
Build Your Own Tools with the Descrybe Open Connector
Give your AI coding agent the repository, describe your idea, and let it guide the setup
The Open Connector helps you build your own legal research tools with Descrybe Legal Engine—even if you would rather describe what you want than write the code yourself.
Overview
A simple way to build with Descrybe
The Open Connector lets you turn an idea for a legal research tool into something that can use Descrybe Legal Engine. You do not need to be a software developer to get started.
If you are using an AI coding agent, the easiest path is to give it the Open Connector GitHub repository and describe what you want in everyday language. The repository includes instructions written for coding agents, so the agent can work out the technical setup with you.
Watch the Open Connector demo on YouTube for a walkthrough of building with Descrybe Legal Engine.
You can start with an idea, not code
Paste the repository link into your coding agent and say what you would like to make. For example: "Help me build a simple tool that researches a legal question with Descrybe and shows me the supporting sources."
Give the Open Connector repository to your AI agent as the starting point for your build.
One person, one secure connection
When the tool needs Descrybe access, each person should sign in with their own Descrybe account. Your coding agent has instructions for handling this correctly, and you remain in control of the browser sign-in.
The easiest way: give the repository to your AI agent
Open your AI coding agent, paste in the GitHub link, and describe the tool you have in mind. The repository contains instructions the agent can read, so you do not need to explain the technical connection or account setup.
Point your AI agent at the Open Connector repository and tell it what you want to build.
- 1
Paste in the GitHub link
Tell the agent: "Please read this repository before we start."
- 2
Describe your idea normally
Explain who will use the tool and what you want it to help with. You can describe the workflow the same way you would explain it to a colleague.
- 3
Let the agent read the instructions
The repository tells the agent how to connect Descrybe, how sign-in should work, which research tools are available, and how to check its work.
- 4
Sign in when asked
When a Descrybe browser window opens, sign in yourself and approve the connection. The agent can handle the remaining setup and confirm that everything works.
Only if your agent cannot open GitHub
Ask the agent to install the Open Connector package and run dle init-agent-instructions. That creates a file containing the same instructions, which you can give directly to the agent.
If you prefer to set it up yourself
- 1
Install the package
Ask your coding agent to install descrybe-legal-engine, or run pip install descrybe-legal-engine yourself. The repository README has the current setup details.
- 2
Connect your Descrybe account
Run dle login. A browser window will open so you can sign in to Descrybe and approve the connection.
- 3
Check the connection
Run dle doctor and dle list-tools. These checks confirm that the connection works without showing your private sign-in information.
- 4
Call Legal Engine from Python
Tell your coding agent what you want the tool to do. It can use the connected Legal Engine package to add the appropriate research tools.
- 5
Log out when testing is done
Run dle logout when you want to remove the local token profile from that machine.
A tool for you versus a tool for a group
A tool just for you
If the tool runs on your computer for your own use, you can connect it with dle login and use your own Descrybe account.
A tool other people will use
If colleagues or clients will use the tool, each person should connect their own Descrybe account. Tell your coding agent that the tool will have multiple users; the repository explains the safe setup.
The important boundary
Sharing one person's Descrybe connection with other people violates the Descrybe Terms of Service. Your coding agent should follow the repository instructions for a separate connection for each person.
A working example your agent can learn from
The repository includes a small working web app under examples/simple-web-app. Your coding agent can study or copy this example when it needs a starting point for account connection and legal research.
The example is intentionally simple. It shows the basic pattern, but a tool used by a firm or the public will still need its own sign-in rules, permissions, and security review.
Open the Open Connector repository on GitHub to read the current example-app instructions.
Troubleshooting
The connection check says Connected: no
Run dle login, complete the Descrybe sign-in in your browser, and try the check again.
The terminal cannot open a browser
Use dle login --no-browser and paste the printed URL into a browser manually.
Descrybe asks you to sign in again
Run dle login again, complete the browser sign-in, and then ask your agent to retry the connection check.
A tool will be used by more than one person
Tell your coding agent that the tool has multiple users. Each person should connect their own Descrybe account rather than sharing one person's connection.