Product
"What does Andocs do?"
Read a concise explanation from the indexed product documentation and open the overview used for the answer.
Product overviewREADME
Questions over repository documentation
Find the answer in the docs.
Add one public GitHub repository or supported files, wait for indexing and ask the question as you would ask a colleague. Krynia returns a short answer with links to the material it used.
Questions that fit the current product
The source is bounded. The wording does not have to be.
You do not have to remember a page title or copy a term exactly. The answer still stays limited to the repository or files already indexed in the workspace.
Engineering
"Which parts of the product use document templates?"
Find the relevant sections in repository documentation without guessing which file contains the template notes.
Template documentationSigning workflow
New teammates
"Where should I start with the signing flow?"
Get the short answer first, then open the cited documents instead of reading the repository from the top.
Signing workflowProduct overview
Project leads
"What changed in the signing flow?"
Answer from the release or workflow notes that are actually present in the indexed source, with links for verification.
Workflow updateRelease notes
Answer path
Index first. Answer second.
The source state is visible, and the final answer links back to the material that was ready at the time.
01
Ask in your own words
Use the wording that makes sense to you instead of guessing the document title or exact keyword.
02
Search the indexed source
Krynia searches only the public GitHub repository or supported files already indexed in the workspace.
03
Prepare a short answer
Relevant sections are passed to the answer step instead of sending every document in the source.
04
Open the cited material
The response links back to the supporting file. GitHub citations point to the indexed commit.
Demo workspace
A sample workspace for trying the question-to-source flow.
The sample contains public product material about Andocs. It demonstrates questions, answers and source links; it does not prove that future private connectors are available.
Sample knowledge
0.1M
kept in the demo workspace
Active sources
5
safe product summaries and docs
Available connectors
0
public GitHub today
Related pages
Common reasons to search repository documentation.
Find the first document to read
Let a new teammate ask where to start, then open the cited repository documents in a useful order.
Answer a product question from maintained docs
Use the indexed product documentation as the source and check it before repeating the answer elsewhere.
Find a change in repository notes
Ask what changed, then review the release or workflow note cited from the connected source.
Try the current workflow