Quickstart
Create a project, connect your agent, and save a first result you can inspect in Venom.
Start with a small planning task. You’ll create a project, connect your agent, and save a checklist in that project.
Before you start.
- Create a Venom account, or sign in to your existing one.
- Choose a client from the setup instructions.
Let your agent set it up.
Paste this into Claude Code, Codex, Cursor or Gemini CLI: Set up Venom for me: https://venomlabs.dev/setup.md. Your agent installs the connection and opens the sign-in in your browser. You sign in with Google or an emailed code, and Venom creates your organization. Your agent then offers to create a first project and invite your teammates.
Set up Venom.
Choose an organization and team.
Create your organization when prompted, or select one you already belong to.
Open Settings → Teams. In a new organization, create your first team, for example Core. Otherwise, join an existing team or ask an owner or admin to create one. Projects need an owning team.
Create a project.
Open Projects → New project. Name it Checkout redesign, use the key checkout, and choose your team.
Give the project an Overview:
Improve our checkout. Start with a discovery checklist.
Do not change application code yet.Connect your agent.
Open Settings → Agent connection. Follow the instructions for your client; the plugin README includes the available host packages and adapters.
For Claude Code, run both in a Claude Code session to install Venom Full:
/plugin marketplace add venomlabs-dev/plugin
/plugin install venom-full@venomVenom Full adds hooks to the venom plugin, which holds the connection and the venom skill. Claude Code installs venom with it.
For Codex, run these in your terminal to install Venom Full. Codex needs both plugins:
codex plugin marketplace add venomlabs-dev/plugin
codex plugin add venom@venom
codex plugin add venom-full@venomCodex’s lifecycle hooks also need to be enabled in its configuration. For other clients, use the MCP setup guide.
Authorize the connection.
Start a new agent session. Complete the sign-in flow and select the organization containing checkout. In Codex, trust the Venom hooks once in /hooks.
Save a first result.
Ask your agent:
Read the checkout project in Venom. Create a task to write five questions
we should answer before redesigning checkout. Use the project overview
as the starting point. Save the checklist as a task artifact, and record
where to find it. Do not change application code.Approve tool calls as your client requires. If a call fails, resolve that error before relying on a saved result.
Check the result.
Open the project in Venom. Inspect the new task, its brief, and the checklist artifact. The log identifies who saved each update and which agent they used.
To continue later, give your agent the actual task reference, such as checkout-1, and ask it to read the task before working.
Next, add a shared skill or connect a tool your team uses.