Inside nectar mark
how it works

Inside nectar

nectar turns your source tree into something an agent can search by meaning. It reads each file, describes what it does, and stores that on Deeplake so recall matches purpose instead of file names.

How a file becomes findable

  1. 01

    Read

    nectar reads enough of each file to understand what it does, without memorizing your source line by line.

  2. 02

    Mint identity

    Each file gets a stable, daemon-minted identity that survives renames, moves, and refactors, so recall does not break when the tree changes.

  3. 03

    Describe

    An LLM writes a short plain-language description of what the file does, and nectar stores it alongside the identity on Deeplake.

  4. 04

    Recall by meaning

    When an agent asks a question, the descriptions are searched by meaning through honeycomb's hybrid recall, so the right file surfaces even when its name never says so.

Stays current as the code moves.

Code changes constantly, and a stale map is worse than none. nectar re-reads files as they change, so the description an agent sees always matches the code that is there now. Build the understanding once and your whole team inherits it when they pull the project, with no per-person re-indexing.

See how honeycomb recalls

Under the hood

daemon
127.0.0.1:3854
per file
stable identity plus a plain-language description
recall
hybrid by meaning, shared with honeycomb
storage
Activeloop Deeplake

Common questions

How does nectar describe a file?

It reads enough of each file to understand its purpose and writes a short plain-language description. It does not memorize your source line by line, it captures what the file is for.

What is the stable file identity for?

Each file gets an identity that survives renames, moves, and refactors, so recall keeps pointing at the right code even when the tree changes.

How do results reach my agent?

Through honeycomb's shared memory and the same hybrid recall. No separate search box: you ask your assistant a plain question and the right files come back.

Make your codebase searchable by meaning.

nectar installs with the rest of the stack. Ask a plain question and get the right file back.

Windows (PowerShell): irm https://get.theapiary.sh/install.ps1 | iex

Download