Learn how to share and execute trails in the Overlook
The overlook is a publicly shareable web app and farcaster miniapp.
Executing a trail is fairly straightforward (reference an example trail here). This can be shared as a web link or as a Farcaster Mini App by pasting the trail link (click the share button in the top left on the canvas after publishing).The user of a trail will only see user_input fields, unless they click “Advanced” which will show all inputs that the creator has pre-filled as well.
Users walking the trail can simulate a step which provides an AI summary as well as Tenderly Simulation results before confirming the transaction.
If there are any read nodes, then there will also be a “read data” section where you can test calling a read node.
When you submit a read node or transaction step, you will see a preview of the results.
You’ll notice this comes with a “LLM prompt”, which is targeted at helping any AI you are working with integrate a read node/transaction step into your app. You can also copy the curl request for testing out API calls easily.Clicking confirm on the main transaction form will bring you an overview on the inputs to be sent onchain:
Clicking “send” will then send the transaction payload to your wallet for signing.
You can view and fork a trail by clicking the trail “view” icon on the top left of the trail, and then clicking “fork” at the top of the trail. Forking will copy everything from the trail you’re looking at into a trail that you own and manage. We keep track of fork history, which will be used for better attribution towards creators in the future.
Once you press “Start Trail” with a connected wallet, an execution instance is saved on our end. You can click the “txns” button in the top left to access your executions. Each “execution” stores all steps executed with the transaction data.Clicking on an execution will pull up the execution details with links to the transactions. You can manually paste transactions into an execution or turn on “Test Mode” to manually set any transaction hashes in the trail for easier testing. Take note that executing in “Test Mode” does not save any executions.
You can “fork” an execution anytime by clicking “re-execute this step” on the top right of any step you have already executed. This will pull all data from previous steps into a new execution which allows you continue executing from there.