/community/guides/the fundamentals
innernet
docsskillscommunitycompanydeveloperssecurityprivacytermscontact

the fundamentals · step 5 of 5

capture without trying

how memory gathers on its own — from your commits, from your conversations, and from one word in a terminal — and how netti folds it in.

/community/guides/capture-without-trying
5 of 5
step 1 of 53 minmeet innernetwhat innernet is, the three parts it is made of, and what you will have done by the end of this walk.
step 2 of 53 mincreate your nettisign up, hold the cell, name the creature that will keep your memory, and walk through the door.
step 3 of 53 minyour first memorymake a memory from a conversation, open it, read and edit its pages, and meet the folders netti keeps inside it.
step 4 of 52 minask it anythinghow your ai finds what you need in your memory, how to ask so it finds the right thing, and what it means when it finds nothing.
step 5 of 51 mincapture without tryinghow memory gathers on its own — from your commits, from your conversations, and from one word in a terminal — and how netti folds it in.

you don't run innernet. it runs on the things you were doing anyway.

on every commit

npx innernet installs one post-commit hook in the repository. each commit lands its message and diffstat as a capture — no prompt, no friction, backgrounded so it can never slow a commit. the moments you would normally lose — why did we drop that dependency, what was the migration plan — get written down as a side effect of committing.

in any conversation

every connected ai can save on your behalf. say what you mean in plain words:

save what we decided about the pricing page to innernet.

the ai calls innernet_save_context or innernet_capture under the hood. small things become captures; a full write-up lands as a page. you can also tell a project how to behave — its capture protocol — so an ai working there knows what is worth keeping without being asked each time.

from a terminal

innernet capture "the auth bug was the case-sensitive bearer scheme"

one line, straight into the project this folder belongs to.

then netti folds it in

captures pile up in a project's inbox. consolidation happens on the server, when it should — not on every keystroke and not so rarely it forgets. netti reads what arrived, decides which pages it touches, and rewrites those pages so each one describes the present; a dated line under ## history records what was superseded. nothing is overwritten silently, and nothing has to be tidied by hand.

activity → river: every capture as it lands, from your commits, your chats and netti.
activity → river: every capture as it lands, from your commits, your chats and netti.

how to see it happened

open the project. the pages carry what you captured; the activity view shows the fold. if something looks wrong, that page's history line says what changed and from what.

the next chapterconnecting your ai

every chapter

the fundamentals5 guidesconnecting your ai5 guidesthe dashboard4 guidesfor builders3 guidessharing3 guides

one memory, every ai tool.

innernet is memory your ai tools read live: every project, every decision, every skill, in one place, connected once.

start your innernetevery guide