Visual feature guide#
See the DevDesk screen before you use it. Every illustration on this page is built from HTML and CSS, follows the current dark workspace interface, and contains sample content only. No screenshot contains a real project, account, secret, or connector address.
Recognise the screen. Understand its job. Open the exact guide.#
Use this atlas when a name such as Canvas, Graph, Diagram Studio, Source Control, or API Studio is unfamiliar. The picture shows the layout; the linked guide explains the safe workflow.
- 1Find the screen or tool below.
- 2Compare the picture with DevDesk.
- 3Open the focused guide and follow its steps.
Feature atlas#
16 feature guides shown
Project files and contextual tools#
Use the Project tree, open compatible files, and add tools that inherit the selected workspace without mixing independent data.
Learn the workspace tool modelWorkbench tabs and hidden-tab menu#
Keep five useful tabs visible, open the rest from the numbered dropdown, and use close or reopen actions without losing unsaved work.
Learn tab managementLocal and workspace graph#
Explore linked notes, apply filters and color groups, adjust forces, and replay either graph scope from the panel or floating play control.
Use the graph controlsDiagram Studio#
Create flowcharts, software diagrams, mind maps, research maps, and study plans with searchable shapes and portable source.
Create a professional diagramVisual Canvas#
Arrange text, file, link, and group cards freely when spatial thinking matters more than a formal process diagram.
Use Visual CanvasList, Table, Cards, Board, Calendar, Timeline, Outline, and Map#
Change the projection without creating duplicate tasks or notes. Every view reads the same Markdown-backed items.
Choose a structured viewMarkdown edit, preview, outline, and relationships#
Write portable text, follow links and backlinks, and keep project changes conflict-aware.
Edit workspace MarkdownProject search#
Find indexed file names and content inside the active workspace without mixing unrelated folders.
Search this workspaceAPI Studio and saved workspaces#
Organize requests, environments, assertions, extraction, runner results, and protected values.
Use saved API testingOpenAPI Studio#
Inspect Swagger or OpenAPI JSON/YAML, browse operations, and generate a collection deliberately.
Inspect an API contractJSON Tools#
Format, validate, inspect, and explicitly save compatible project JSON without changing unrelated files.
Use JSON ToolsFocused utilities#
Decode JWT, test Regex, convert Base64, encode URLs, convert timestamps, or generate UUIDs in clear input/output tools.
Browse the first utility guideSource Control, history, branches, and Diff#
Inspect real repository state, compare files, and run explicit Git actions only inside a trusted local Windows workspace.
Understand Source ControlAI Agent Connector#
Assign one workspace per session, enable only needed permissions, observe activity, and review proposals before any write.
Connect a compatible agentStructure checks (OKF)#
Analyze optional portable structure, separate required findings from advice, and preview recoverable improvements.
Use structure checksSettings, privacy, updates, and recovery#
Control appearance and device-local choices, verify update sources, and export a recovery kit before reinstalling.
Review settings and recoveryWhich visual tool should I choose?#
| Your goal | Choose | Why |
|---|---|---|
| Show a formal sequence, decision, system, organization, or research process | Diagram Studio | Shapes, connectors, templates, auto layout, and PNG/SVG export |
| Arrange ideas, notes, files, links, and loose groups spatially | Visual Canvas | Freeform cards in the portable JSON Canvas format |
| Explore relationships already written in Markdown | Knowledge graph | Derived nodes and links with Local/Workspace scope, filters, groups, and timeline |
| Compare the same tasks or notes in rows, cards, status columns, dates, or locations | Structured views | Different projections over the same source items |
Visuals are guidance, not fake screenshots#
The illustrations intentionally use sample names such as Architecture.md and api.example.dev. They explain layout and purpose without claiming that a user performed an action or that a real request, Git operation, agent connection, verification, or file write succeeded. The focused guide remains the source for exact platform limits and safety steps.