Repository navigation
Notes
The Notes tab is for jotting down findings, credentials, endpoint quirks, and anything else worth remembering during an engagement. Notes are organized per host so that observations stay attached to the target they describe.
Every Joro instance has a local notes area. Pick or add a host, then write markdown-style notes. Notes are saved automatically. They persist on disk under the Joro data directory so they survive restarts.
A pinned General entry sits at the top of the host list for anything that is not about a particular host — engagement scope, credentials that work everywhere, a running to-do list.
When your Joro proxy is connected to a team server, the Notes page grows an additional Shared Notes tab. Shared notes live on the team server and are visible to every connected operator, organized by host with the same General bucket at the top. Changes propagate in real time.
Shared notes can be edited in place, and an edited note is marked as such. Edit and delete controls appear only on notes you wrote. This is soft ownership keyed on your nickname, not authentication — it stops operators from clobbering each other by accident, and nothing more.
See Team-Server for how to connect to a team server.
- One note per host with a running list of discovered endpoints and parameters.
- Separate notes for credentials, flags, and chains.
- Copy interesting raw requests out of History and paste them into notes so you can find them later without relying on the request log.