🚀 Loading Coderva...

Documentation: the Coderva platform wiki

The documentation wiki explains how the Coderva platform works and how to get the most out of it. It covers the main building blocks such as agents, workflows, tools and apps, along with setup guidance for common configurations. It is meant to be the first place your team looks when it needs an answer.

Read the documentation

What you will find

  • Explanations of agents, the Agent Builder and how prompts, tools and knowledge fit together.
  • Guidance on creating, running and scheduling workflows and reading execution history.
  • Reference information about tools, apps and platform concepts.
  • Searchable pages grouped into sections, with deep links to each page.
  • Links from each guide into the matching screens of the platform.

How it works

  1. Open Documentation from the Coderva navigation.
  2. Browse the wiki sections or look for the topic you need.
  3. Read the relevant page and follow the steps in the platform alongside it.
  4. Use the links in each guide to jump to the matching screen in the platform.
  5. Share a deep link to a page with a colleague using its page address.

Who it is for

Documentation serves everyone who touches the platform: administrators configuring an organization, builders designing agents, and operators watching workflows. New team members can use it to learn the vocabulary and structure, while experienced users can use it as a quick reference when they try a feature they have not used before. Keeping this knowledge in one wiki reduces repeated questions and makes onboarding more consistent across teams.

Key capabilities

  • A single wiki covering the main platform areas.
  • Task-oriented guidance that maps to actual screens and features.
  • Links from guides into the related screens of the platform.
  • A shared reference that keeps onboarding consistent when new people join your organization.
  • Search across page titles and content.
  • Search the wiki: Type a word and the Contents list narrows to the pages that mention it.
  • One layout for every guide: Each page answers what it is, why to use it, how to use it and the benefits.
  • Jump into the app: Link chips at the end of a guide open the matching page in the workspace.

What the documentation gives you

A map of the whole platform

The Contents sidebar groups the guides by area, so a new teammate can see everything Coderva does without opening a single feature.

  • Getting started: Platform overview, Workspace home and Quick start checklist.
  • Agents & studio: Agent Studio, Agent Builder, Agent chat, Coderva AI Assistant and Org AI Assistant.
  • Workflows, Discover (App Store), Organizations and Account & billing.
  • Reference: Designer tools reference and Help & support.
A bar chart of 17 documentation pages across 7 sections: Getting started 3, Agents and studio 5, Workflows 1, Discover 1, Organizations 2, Account and billing 3 and Reference 2

Search that reads the whole page

The Search documentation box matches the page title, its summary and all of the body text, not only the headings.

  • The sidebar filters as you type, keeping only sections with a match.
  • Matching ignores upper and lower case.
  • It runs in the browser, so results appear immediately.
  • If nothing matches, the sidebar says "No topics match your search."
The Search documentation box with the word csv typed in, and a sidebar narrowed to Platform overview, Agent Builder, Agent chat and Designer tools reference, with 4 of 17 pages shown

The same shape on every page

Feature guides follow one structure, so once you have read one you know where to look in the next.

  • What is it? explains the feature in plain words.
  • Why use it? gives the reason, and How to use it lists numbered steps.
  • Benefits closes the page, with tips, callouts and sub-headings where needed.
  • Link chips at the bottom take you to the real screen.
A Quick start checklist article with the headings What is it, Why use it, How to use it and Benefits and an API keys callout, beside a list of block types: paragraph, heading, bullets and steps, callout and link chips

Links you can share

Selecting a topic puts its page id in the address, so you can send a teammate the exact page rather than the whole wiki.

  • Open /documentation#agent-builder to land on the Agent Builder guide.
  • The address updates as you click through the sidebar.
  • An unknown or empty id opens the Platform overview.
  • Help & support itself points readers to these hash links.
A browser address ending in documentation hash agent-builder opening the Agent Builder article with its sidebar item highlighted, and notes on clicking a topic and on unknown ids falling back to the overview

From a question to an answer

The wiki needs no setup. Open it, find the topic, read it, and follow the steps in the product.

  1. Open the Guide: Use Guide under Help & Guide in the sidebar, or go to /documentation. The page also opens without signing in.
  2. Browse the Contents: Pick a topic from the sidebar. The open page is highlighted with a chevron.
  3. Or search: Type in Search documentation... to keep only the pages that mention your term.
  4. Read the article: Work through What is it, Why use it, How to use it and Benefits, plus any tip or callout.
  5. Follow along and share: Use the link chips to open the feature, and copy the #page-id address to share the page.

Open, find, read, do, share

Five stages: open Guide from the sidebar, browse the Contents or search, read the four-part article, follow the steps in the app through link chips, then share the page by its hash link, with a reminder to ask the Coderva AI Assistant or email support

How the wiki is built

The documentation is typed content bundled with the web app. A single React page renders the sidebar and the article, search runs in the browser, and the address hash chooses the page.

Six layers: the React documentation page with sidebar, search box and article view; typed content with sections, pages and block types; client-side search; hash-based navigation; role-based page visibility; and link chips that hand readers over to the app
  • Interface: DocumentationPage at /documentation shows a Search documentation box, a Contents sidebar and an article panel. The sidebar stacks above the article on narrow screens.
  • Content: Each page has an id, title, summary and section. Pages are built with a helper that lays out What is it, Why use it, How to use it and Benefits.
  • Block types: Articles are made of paragraphs, sub-headings, bullet lists, numbered lists, info or tip callouts and link chips.
  • Search: Search checks the title, summary and the text of every block in the browser. No network request is made.
  • Navigation: The page id lives in the URL hash. Clicking a topic updates it, and a hash change opens the matching page, falling back to the overview.
  • Access and hand-off: The route is not behind sign-in. Pages can be limited by role and are then left out of the sidebar, search and links. Link chips open workspace routes such as /agent-studio and /workflows.

The screens you will use

Mock-ups use real page titles, steps and labels from the wiki.

Agent Builder guide

A typical feature guide: a summary, numbered steps for the wizard, canvas and Test tab, and a link to Agent Studio.

  • Seven steps from opening the builder to Deploy.
  • A Tool categories sub-heading lists what can be attached.
  • The Agent Builder item is highlighted in the sidebar.
The Agent Builder wiki page with a sidebar of Agents and studio topics, seven numbered steps under How to use it, a Tool categories paragraph and an Open Agent Studio link chip

Designer tools reference

A reference page that groups built-in tool IDs by category, with a short How to use it for choosing and testing them.

  • Categories include Data & search, Communication, Development and Files.
  • IDs such as web_search, github and csv_database.
  • Test each tool in the Agent Builder Test panel before deploying.
The Designer tools reference page with tool ID chips grouped under Data and search, Communication, Development and Files, and a How to use it note about testing before deploying

Organizations guide

Steps for joining and approval, a Roles list and link chips to the join page and the Org dashboard.

  • Roles: org_admin, org_member and org_member_pending.
  • The sidebar shows neighbouring topics such as Org knowledge.
  • Link chips open Join organization and Org dashboard.
The Organizations wiki page with four numbered join steps, a Roles list of org_admin, org_member and org_member_pending, and Join organization and Org dashboard link chips

What people use the wiki for

Each card maps to pages that exist in the wiki today.

  • Get a first agent live: Quick start checklist takes you from sign-in to a template agent, a deployment and a first chat in five steps.
  • Learn to build: Agent Studio and Agent Builder explain templates, drafts, deployments, tools, MCP, the canvas and the Test panel.
  • Chain agents together: The Workflows guide shows how to build a composite workflow from deployed agents, run it and schedule it.
  • Set up a team: Organizations and Org knowledge cover joining, roles, approvals and the sources behind the Org AI Assistant.
  • Understand credits: Usage & billing, Plans & pricing and Settings explain the credit balance, usage events, plans and your account options.
  • Pick the right tool: The Designer tools reference lists built-in tool IDs by category so you attach the right ones.

What the guides explain

Only systems named in the wiki pages are listed.

  • Gemini
  • Groq
  • OpenAI
  • Perplexity
  • MCP servers
  • GitHub
  • Slack
  • Email
  • SMS
  • Calendar
  • CSV and PDF files
  • Wikipedia
  • News API
  • Org knowledge sources

Everything in the wiki

  • Search documentation: A search box above the sidebar that filters pages by title, summary and body text.
  • Contents sidebar: Sections and topics in one list, with the open page highlighted and sticky on wide screens.
  • Hash deep links: Open /documentation#page-id to land on a specific guide, and copy the address to share it.
  • Numbered how-to steps: How to use it lists the actions in order, using the real tab and button names.
  • Tips and info callouts: Short highlighted notes, such as the API keys reminder in Quick start checklist.
  • Link chips: Jump from a guide to Workspace Home, Agent Studio, Workflows, App Store, Billing and more.
  • Personal greeting: Signed-in users see Welcome back with their first name; visitors see Coderva Documentation.
  • Layered help: Help & support points to this wiki first, then the Coderva AI Assistant, then email support.

Frequently asked questions

Is the documentation different from Agent Studio?

Yes. Documentation is a reference for how the platform works and how to configure it. Agent Studio is the hands-on environment where you build and test agents using that knowledge.

Where should a new team member start?

Begin with the overview page, then the pages on agents and workflows, and try Agent Studio with a template. Once comfortable, read the tools reference to see what your agents can use.

Does the documentation cover individual apps?

It covers the platform concepts and setup that apps rely on. For app-specific information, such as trading or email management, also review the app pages and the guided setup inside each app.

Related

Read the documentation