# Docs Agent reference: file types, limits, and FAQ

import { Aside } from '@astrojs/starlight/components';

## Supported file types

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

### Documents

| Category | Formats | Max size |
|----------|---------|----------|
| Text and markup | `.txt`, `.md`, `.markdown`, `.csv`, `.html`, `.htm`, `.adoc`, `.asciidoc`, `.tex`, `.latex` | 50 MB |
| Data and configuration | `.json`, `.yaml`, `.yml`, `.toml`, `.log`, `.sql`, `.ini`, `.config` | 50 MB |
| Office | `.doc`, `.docx`, `.xls`, `.xlsx`, `.ppt`, `.pptx`, `.rtf` | 50 MB |
| PDF | `.pdf` | 50 MB |
| Images | `.jpg`, `.jpeg`, `.png`, `.gif`, `.webp`, `.tiff`, `.tif`, `.bmp` | 50 MB |

### Code files

| Language | Formats | Max size |
|----------|---------|----------|
| Python | `.py`, `.ipynb` | 50 MB |
| JavaScript / TypeScript | `.js`, `.jsx`, `.ts`, `.tsx`, `.css` | 50 MB |
| JVM | `.java`, `.kt`, `.kts`, `.scala` | 50 MB |
| C family | `.c`, `.cpp`, `.cxx`, `.h`, `.hpp`, `.cs` | 50 MB |
| Systems and scripting | `.rs`, `.go`, `.rb`, `.php`, `.swift`, `.dart`, `.lua`, `.pl`, `.pm`, `.t`, `.m`, `.r`, `.rmd` | 50 MB |
| Shell | `.sh`, `.bash`, `.zsh` | 50 MB |

### Video

| Formats | Max size |
|---------|----------|
| `.mp4`, `.webm`, `.mov`, `.avi`, `.mpeg`, `.mpg`, `.ogg` | 500 MB |

### Processing notes

- **Text-based PDFs**: The agent extracts the text directly.
- **Scanned PDFs**: The agent processes these with optical character recognition (OCR), which may take longer.
- **Images**: The agent sees the image content directly. You can use images as visual context or [insert them into your documentation](/agent/create/#from-screenshots-and-images) as files.
- **Code, data, and configuration files**: Content is extracted as plain text. Files larger than 500,000 characters are truncated with a marker indicating where the content was cut.
- **Video**: The agent transcribes and summarizes the content; processing time varies with length.

### Binary files in the editor

When the agent inserts an image into your repository, select the file in the editor panel to preview it, and click the preview to open it larger. Other binary files appear as placeholders instead, but the agent adds the correct markdown reference in the surrounding document either way. Binary files commit when you [create a pull request](/agent/update-review/#create-a-pull-request).

## Session history

Each conversation with Docs Agent is a session, whether you start it in the editor, from a [GitHub pull request comment](/agent/github-integration/), or from a [Slack @mention](/agent/slack-bot/). EkLine keeps your sessions so you can return to them later instead of starting over.

Sessions stay resumable for 90 days from your last activity. Each time you interact with a session, the 90-day window restarts, so active conversations stay available as long as you keep using them.

Resuming a session keeps its full context. The agent remembers earlier messages, uploaded files, and the documentation it generated. How you resume depends on where the session runs:

- **Editor**: Reopen the session from the **Sessions** section in the sidebar and continue the conversation.
- **GitHub**: Mention `@ekline-ai` again on the same pull request. The agent resumes the existing session instead of starting a new one.
- **Slack**: Reply in the same thread with a follow-up `@EkLine` mention. The bot continues the same session.

After 90 days of inactivity, a session expires. When you try to resume an expired session, EkLine tells you the session is no longer available, and you can start a new session to continue your work.

## Limits

<Aside type="caution" title="Upload limits">
| Limit | Value |
|-------|-------|
| Document file size | 50 MB per file |
| Video file size | 500 MB per file |
| Extracted text | 500,000 characters per file |
| Files per message | 20 |
| Session history | 90 days from last activity |
</Aside>

## Troubleshooting

### The agent doesn't understand the 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"`

You can also add this kind of context permanently through [custom instructions](#can-i-give-the-agent-context-about-my-organization).

### Generated content doesn't match the 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"`

### Integration content isn't loading

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.

### Pull request creation fails

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 is slow or fails

Video processing time depends on length. For a 10-minute video, expect 2 to 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.

## FAQ

### What repositories can Docs Agent access?

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

### Does the agent modify files directly?

In the editor, no. The agent generates content that you review, edit, and then publish through a pull request.

When you start the agent from a [GitHub PR comment](/agent/github-integration/) or a [Slack @mention](/agent/slack-bot/#automatic-pull-requests), it opens a docs PR on the documentation repository you set. You still review and merge the PR before changes reach your main branch.

### Can I use Docs Agent for private repositories?

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

### Can I give the agent context about my organization?

Yes. Go to **Settings** > **Docs Agent** > **Custom instructions**. Use them for context the agent can't get from your code. For example: how your docs are organized, which versions to support, or your company's conventions. To say what each repository is for, add a [repository note](/agent/reference-documents/) under **Settings** > **Integrations**. Click **Save custom instructions** to apply changes. The agent uses your custom instructions in every new session for your organization. Any organization member can edit them, up to 20,000 characters.

### Can I package a workflow my team repeats?

Yes. Under **Settings** > **Docs Agent** > **Skills**, add a skill. A skill has a name, a description of when to use it, and the instructions to follow. Every new session gets your skills. To run one, type its slash command (`/<name>`). The agent can also use a skill when your request matches its description. See [Package a workflow as a skill](/agent/custom-skills/).

### How does the agent know my documentation style?

The agent reads your existing docs to learn their patterns:

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

For best results, keep one style across your docs. You can also use [custom instructions](#can-i-give-the-agent-context-about-my-organization) to set preferences the agent can't pick up from your code.

### What happens to uploaded files?

EkLine extracts the content of each file you upload for the agent to use, and links the file to your session. Each customer's data is isolated and never used to train models. For details, see [Security and data](/workspace/security-and-data/) and the [EkLine Trust Center](https://ekline.io/trust-center).

### Can I stop the agent or send messages while it works?

Yes. The button at the end of the chat input changes with what the agent is doing. It sends a message, stops the agent, or queues a follow-up. While the agent works, click it to stop the current turn. Its tooltip reads **Stop the agent**. Or type a follow-up and click it. The message waits until the current turn ends. See [Control the agent while it works](/agent/editor/#control-the-agent-while-it-works) for details.

### Can I use Docs Agent without creating a pull request?

Yes. Click **Copy** in the editor toolbar to copy the open file's content. The PR workflow is optional.

### How does Docs Agent select reviewers for pull requests?

The agent uses two sources to assign reviewers:

- **Default reviewers**: usernames your organization administrator sets in **Settings** > **Docs Agent** > **Reviewers**. The agent adds these reviewers to every PR it opens.
- **Auto-assign reviewer**: on by default. The agent adds the person who started the session as a reviewer. For example, if someone asks for docs from Slack, the agent finds their GitHub username. If the session started from a code PR, the agent adds that PR's author.

The agent never adds bot accounts. If it can't find a reviewer, it still opens the PR without one.

### How long can I resume a Docs Agent session?

You can resume a session for 90 days after your last activity. Each time you use a session, the 90 days start again, so a session you keep using stays available. See [Session history](#session-history) for how to resume a session from the editor, GitHub, or Slack.

## Get help

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.