Give Your Coding Agent the Open Connector
Start with the repository URL and one narrow goal instead of an enormous specification.
You will know how to start an agent from a blank folder and ask for the smallest app that proves the Descrybe connection.
Begin with an empty project
Open a blank folder in your coding tool. The video uses Codex, but the basic approach is the same in other agentic coding tools: give the agent a workspace, describe the immediate goal, and let it inspect the relevant instructions before it writes code.
The Descrybe Open Connector repository includes instructions intended for coding agents. Copy the repository URL and include it in your request so the agent has a concrete technical source to inspect.
https://github.com/descrybe-com/descrybe-legal-engine-pythonAsk only for the connection first
Do not ask for the complete brief checker yet. The connection is the most important dependency, so establish it before adding screens and legal workflows on top.
A smaller request gives you a shorter path to something testable. It also makes failures easier to diagnose because fewer parts changed at once.
Use the Descrybe Open Connector repository at https://github.com/descrybe-com/descrybe-legal-engine-python to build a small local proof-of-concept web app that connects to Descrybe Legal Engine. Start only with the connection and a simple way to confirm that it works. Read and follow the repository instructions before changing files. Do not build the brief checker yet. When you are finished, tell me which files you created or changed, what tests you ran, and the exact commands I should use to run the app.Read the agent’s work notes
The agent will usually explain what it is inspecting, what it plans to build, and what it changed. Some technical terms may be unfamiliar at first. You do not need to understand every implementation detail before continuing.
You should still read the notes. Watch for choices that differ from what you expected, assumptions about the app, unanswered questions, failed tests, and any instruction that requires you to do something manually.
- Ask what an unfamiliar term means.
- Ask why the agent chose a framework or approach.
- Ask whether a warning matters before ignoring it.
- Ask for a shorter explanation if the summary is too technical.
Your first review checkpoint
When the agent finishes, it should identify the files it created, the checks it ran, and the commands needed to launch the app. Treat that summary as a handoff, not as proof that the feature works.
Before requesting anything else, look at the new files and move to the next lesson to run the app yourself.