Skip to content

Reference

Supported file types, limits, troubleshooting, and frequently asked questions.

Upload files to give the agent more context. Click the attachment icon in the chat panel and select your files.

CategoryFormatsMax size
Text.txt, .md, .markdown, .csv, .rst, .html, .htm, .adoc, .asciidoc50 MB
Office.doc, .docx, .xls, .xlsx, .ppt, .pptx, .rtf50 MB
PDF.pdf50 MB
Images.jpg, .jpeg, .png, .gif, .webp, .tiff, .bmp50 MB
FormatsMax size
.mp4, .webm, .mov, .avi, .mpeg, .mpg, .ogg500 MB
  • Text-based PDFs — Text is extracted instantly
  • Scanned PDFs — Processed with optical character recognition (OCR), which may take longer
  • Images — Text extracted via OCR
  • Video — Transcribed and summarized (processing time varies with length)

I don’t see Docs Agent in the navigation

Section titled “I don’t see Docs Agent in the navigation”

Docs Agent is in beta. Email support@ekline.io with your organization name to request access.

The agent doesn’t understand my repository structure

Section titled “The agent doesn’t understand my repository structure”

Be more specific in your prompt:

  • Reference file paths: "Look at src/api/auth.ts"
  • Mention the framework: "This is a Next.js project using App Router"
  • Describe the architecture: "API routes are in src/pages/api, components in src/components"

Generated content doesn’t match my documentation style

Section titled “Generated content doesn’t match my documentation style”

The agent learns from your existing docs. If styles are inconsistent, results may vary.

Try:

  • Reference a specific doc as an example: "Match the style of docs/getting-started.md"
  • Be explicit about formatting: "Use numbered steps, not bullet points"
  • Specify tone: "Technical but approachable, similar to Stripe's docs"

Verify that:

  1. The integration is connected in Settings > Integrations
  2. You have access to the Slack channel, Notion page, or ticket
  3. The URL or reference ID is correct.

Verify that:

  • Your repository is connected to EkLine
  • You have write access to the repository
  • The branch you’re targeting exists
  • The PR title is at least 5 characters

If the issue persists, contact support@ekline.io.

Video processing time depends on length. For a 10-minute video, expect 2-3 minutes of processing.

If processing fails:

  • Verify that the file format is supported.
  • Check that the file is under 500 MB.
  • Try re-uploading the file.

Repositories connected to your EkLine organization. Manage repository access in Settings > GitHub Integration.

No. The agent generates content in the editor. You review and edit the content, then create a pull request. The agent never pushes changes directly to your repository.

Can I use Docs Agent for private repositories?

Section titled “Can I use Docs Agent for private repositories?”

Yes. The agent respects your repository permissions and only accesses repositories you’ve connected and authorized.

How does the agent know my documentation style?

Section titled “How does the agent know my documentation style?”

The agent analyzes your existing documentation to understand patterns:

  • Heading structure and hierarchy
  • Code example conventions
  • Terminology and voice
  • File organization and naming

For best results, maintain consistent style in your existing docs or reference a specific file as a style example.

Files are processed to extract content and used to inform the agent’s response. Files are stored securely and associated with your session. They are not shared with other users or organizations.

Can I use Docs Agent without creating a pull request?

Section titled “Can I use Docs Agent without creating a pull request?”

Yes. You can copy content directly from the editor or download the generated files. The PR workflow is optional.

For issues not covered here, contact support@ekline.io with:

  • A description of what you’re trying to do.
  • The prompt you used.
  • Any error messages you received.
  • Screenshots if applicable.