Agents overview
EkLine has two agents: the Docs Agent updates your documentation, and the Marketing Agent drafts blog posts, LinkedIn posts and newsletters.
See the Docs Agent in action
Section titled “See the Docs Agent in action”What the Docs Agent and Marketing Agent do
Section titled “What the Docs Agent and Marketing Agent do”| Docs Agent | Marketing Agent | |
|---|---|---|
| What it writes | New and updated docs pages, such as guides, API references, READMEs and changelogs. It also answers questions about your docs. | Blog posts, LinkedIn posts and newsletters, in your company’s voice. |
| Where its work goes | A pull request on GitHub, or a merge request on GitLab, in a repository you listed under Where EkLine writes. | A draft in the editor that you copy or download. |
| Who approves it | Your team reviews and merges the pull request. | You publish the draft yourself. |
Docs Agent
Section titled “Docs Agent”The Docs Agent drafts its changes in the editor, where you accept, reject or edit them. When the draft is ready, click Raise PR, which puts “Open a pull request” in the message box, and send it. Sessions started from a pull request comment, Slack or an automation can open a pull request without that step. The agent writes only to the repositories under Where EkLine writes. It reads those under What else EkLine can read but does not write to them. See How EkLine opens pull requests.
The Docs Agent can also draft changes to a Confluence or Pylon knowledge base, which you publish with Update KB. See Manage a knowledge base.
Marketing Agent
Section titled “Marketing Agent”Each Marketing Agent draft opens in the editor as a document you can edit. Copy copies the open draft. Download saves the session’s drafts as Markdown, or as HTML from the menu. The agent opens a pull request only when you ask it to publish a draft to one of your documentation repositories and say where. It does not publish to your website or CMS. See the Marketing Agent overview.
Start a session
Section titled “Start a session”Docs Agent
- In the app: click New session in the sidebar, or enter a prompt in Start a conversation on the dashboard. If the composer shows Docs and Marketing, select Docs. See Work in the editor.
- From a pull request or merge request: mention
@ekline-aiin a comment. See GitHub pull requests and GitLab merge requests. - From Slack or Discord: mention EkLine in a channel or thread. See Slack and Discord.
- From Jira: a ticket that matches one of your triggers starts a session. See Jira tickets.
- On a schedule: see Automations.
- From a Journeys report: click Fix in docs on a finding. See Turn a gap into a fix.
- From an MCP client such as Claude Code or Cursor. See MCP clients.
Marketing Agent
- In the app: click New session in the sidebar, or enter a prompt in Start a conversation on the dashboard. If the composer shows Docs and Marketing, select Marketing. See Start a session.
- From a Journeys report: click Draft in Marketing on a finding, or Start the fix on a collection report. See Write a post that answers a buyer question.
- From an MCP client. See MCP clients.
Slack, Discord, Jira and pull request comments start Docs Agent sessions only. An automation starts a session of the agent it was created for, the Docs Agent or the Marketing Agent.
Who can use the agents
Section titled “Who can use the agents”Any member of your organization can start a session with either agent. Both agents are available to every organization, including free accounts.
If you don’t see Automations, Jira triggers, knowledge base management or a settings tab these pages describe, contact support@ekline.io.
See Credits and usage for how agent work is counted.
What is in this section
Section titled “What is in this section”| Part | Pages |
|---|---|
| Give agents context | Which setting to use, Company Profile and Domains, Custom instructions, Reference documents and repository notes, Skills |
| Start work | Work in the editor, Find a past session, GitHub pull requests, GitLab merge requests, Slack, Discord, Jira tickets, MCP clients, Sandbox |
| Docs Agent tasks | Create documentation, Keep docs in sync with code, Generate release notes, Manage a knowledge base, and the other pages under Docs Agent tasks |
| Marketing Agent tasks | Marketing Agent overview, Write a post that answers a buyer question, Turn shipped changes into launch content, How claims stay accurate |
| Automate | Automations, Automatic PR review, Control which PRs are reviewed |
| Review and ship | How EkLine opens pull requests, For engineers: an EkLine pull request or comment on your repository |
Which agent should I use?
Section titled “Which agent should I use?”The Docs Agent for your documentation, or a Confluence or Pylon knowledge base. The Marketing Agent for a blog post, a LinkedIn post or a newsletter.
Do the two agents share settings?
Section titled “Do the two agents share settings?”Partly. Each agent has its own custom instructions and never reads the other’s. Both read your repository notes and use your rules and skills. Both can read your Company Profile and reference documents. See Which setting to use.
Where do I see what an agent did?
Section titled “Where do I see what an agent did?”Sessions are listed under Sessions in the sidebar, grouped by date. Open one to see the agent’s messages and the changes it made. To search or filter them, see Find a past session.
Built on Potluck Docs, our open source template.