Document extraction
The development scope includes HWP/HWPX, PDF, Office files, images, text, and email. OCR is used for supported image-based material.
FINDOC
A desktop document search app for local folders and NAS shares, now being prepared for release.
In development · Preparing for release
Findoc is designed around folders, shared drives, scanned papers, and office files people already use.
The development scope includes HWP/HWPX, PDF, Office files, images, text, and email. OCR is used for supported image-based material.
After indexing, keyword and semantic search can run on the user’s device. A network connection is not required for local searching.
File type, date, and path filters help users move from a broad result list to a document they can inspect.
The path from file to result stays visible.
Select local folders or a configured shared location.
Extract available text and prepare it for search.
Review results, filters, and the original document.
Illustrative planned workflow
Question: “When is the renewal notice due?”
Answer: cited clause from a selected contract, or withheld if unsupported
Next: open the original file to verify context
Claude Code is used now in development. A Claude API feature is planned as a separate, opt-in cloud query flow.
Claude Code helps structure requirements, inspect implementation and documentation, and run review and verification steps. Release decisions stay with the team.
A user would search relevant passages locally, see the proposed transmission range, and consent before a server sends a question and minimum selected text to the Claude API.
The planned response will cite a file and passage, reducing time spent comparing several files while keeping the original source one click away. When selected material does not support an answer, it should withhold an answer.
Local search is designed to work offline. Any future cloud question flow is separate, shows its scope, and requires a user choice before sending selected text.
Before expansion, we plan to assess source accuracy, appropriate “I don’t know” responses, latency, and request cost. No performance level is promised here.
Product conversation