Jestor Docs is a full text editor built into the system, with heading, list, image, grid, and quote blocks, plus three permission levels per document. In Jestor, this removes the need for a separate text tool just to jot down an idea or document a process. The problem with documentation
Training an agent with documents means attaching files — a vacation policy, an HR manual — to an AI agent, so it can answer questions based on that content, even without a linked table. In Jestor, the same agent keeps context across follow-up questions in the same conversation. The problem with
An internal chatbot linked to a table is a conversational agent set up in a few clicks, with a custom logo, colors, and tone of response, able to sum, filter, and list records from a specific table when asked. In Jestor, it's different from Builder AI: one queries
Pie charts and donut charts represent exactly the same data — the difference is purely visual, with the donut leaving an empty space in the center. In Jestor, both formats are available with the same level of color, border, and legend customization. The problem with having only one circular chart format
Direct calculation on the gauge chart is the chart's own ability to pull and calculate values — sum, average, min, max, or count — with filters applied right in the setup, without needing to prepare that calculation in another field beforehand. In Jestor, each gauge value can have its own
Duplicating a table means creating a copy of its fields and automations without bringing over any existing data — different from cloning, which copies structure and records together. In Jestor, this distinction avoids exposing data from an old process when reusing a template for a new client. The problem with reusing
Top navigation bar style is the choice between different visual formats — rounded, icons only, text with colored selection — for the tabs at the top of the system. In Jestor, there are seven different options, with adjustable position and background color. The problem with a single fixed navigation style A navigation
Conversation history is access to previous interactions with Builder AI, letting you pick up exactly where a build left off without having to explain everything again. In Jestor, you can have several separate conversations, each tied to a different project or app. The problem with losing context between sessions Without
Requesting fields and views by AI means describing, in a simple text list, which fields you need to add to a table that already has data, or asking for a view like Kanban, without manually configuring each element. In Jestor, the AI automatically identifies which field should organize the phases
Vibe building means describing, in plain text, what you want to build or change in an existing system, and letting the AI execute it without you having to code. It's different from "vibe coding" (asking for finished code without understanding what was generated): in Jestor, every
Customizing connected fields means choosing exactly which columns from a connected table appear in a record's side tab, reordering them, and deciding whether they can be edited there or stay reference-only. In Jestor, you can also apply filters to reduce the amount of information shown. The problem
Following a table means turning on an option that alerts you every time any record in that table is changed by someone else, with no automation to build. In Jestor, this notification ignores your own changes — it only alerts you to changes made by others. The problem with needing automation