GoCalc.AI — All Agents Home
User Tutorial

GoCalc.AI — All Agents

A master AI orchestrator that connects Excel, AutoCAD, ETABS, and Revit in a single chat window. Give one instruction and the AI coordinates all four applications automatically.

📊 Excel · 📐 AutoCAD · 🏗 ETABS · 🏢 Revit Cross-software automation in natural language OpenAI · Claude · Gemini · Ollama Live connection status per application

1 What is All Agents?

All Agents is a special mode in GoCalc.AI that acts as a master orchestrator. Instead of talking to one software at a time, you talk to a single AI that decides which application(s) to use — and in what order — to complete your request.

The Four Specialised Agents

📊 Excel Agent
📐 AutoCAD Agent
🏗 ETABS Agent
🏢 Revit Agent

Each agent is a full GoCalc.AI specialist that can read data, run actions, and control its target application. The All Agents orchestrator wraps all four and routes your requests to whichever agents are needed.

How It Differs from Individual Plugin Windows

Individual plugin windowAll Agents window
One software at a timeUp to four simultaneously
You choose which app to openAI decides which agent(s) to call
Direct tool accessAgent-to-agent delegation
Best for deep single-app tasksBest for cross-software workflows
💡

When to use All Agents vs. individual windows: Use All Agents when your task involves more than one application — for example, reading ETABS results and writing them to Excel. Use individual windows for focused, deep work within a single application.

2 Launch & Setup

All Agents appears as a button in the GoCalc.AI plugin selector. You do not need to open individual plugin windows first.

Step-by-Step Launch

  1. Open the applications you want to use Start any combination of Excel, AutoCAD, ETABS, and Revit on your machine. Only the applications that are running can be connected. You do not need to open all four — just the ones relevant to your task.
  2. Launch GoCalc.AI and click 🤖 All Agents The All Agents chat window opens. The top bar shows four status indicators — one per application — all starting as (not connected).
  3. Click the reconnect button to open the Connect Agents dialog A popup appears listing all four applications. Click ⟳ Connect next to each application that is currently running. The status changes to when the connection succeeds.
  4. Ensure your API key is configured Click the Options button in the main GoCalc.AI selector and enter at least one AI provider key (OpenAI, Anthropic, Google, or Ollama). The All Agents window uses the same key configuration as all other plugin windows.
  5. Type your cross-software request and press Enter Example: "Read the beam loads from ETABS and paste them into column B of my Excel sheet." The orchestrator calls each agent in turn and returns a combined result.
⚠️

Applications must be running. GoCalc.AI connects to live, already-running software processes. If an application is not open, clicking Connect for that agent will show a connection error. Open the application and click Connect again.

⚠️

API key required. The orchestrator uses the same AI provider key as all other GoCalc.AI windows. Configure your key via the Options button in the plugin selector before sending any messages.

3 Interface Overview

The All Agents window uses the same familiar chat layout as the other GoCalc.AI windows, with one key addition: a live connection status bar in the top-right corner showing all four applications at a glance.

🗂

Left Sidebar — History

Saved conversations listed by title and date. Click to reload, × to delete.

💬

Chat Area

Your messages appear on the right. The AI reply and a log of which agents were called appear on the left.

⌨️

Composer

Enter sends your message. Shift+Enter inserts a new line.

🔴

Stop Button

While the AI is processing, a red Stop button replaces Send. Click it to cancel the response and re-enable the input immediately.

Top Bar — Connection Status Indicators

The top-right corner shows a live status badge for each of the four applications:

🏢 Revit
📐 AutoCAD
📊 Excel
🏗 ETABS
IndicatorMeaning
Name ✓Agent is connected to the running application. The orchestrator can call this agent.
Name ✗Not connected. The application may not be open, or Connect has not been clicked yet.

Toolbar Button Reference

ButtonWhat it does
📎 Attach filesAttach images or documents to include in your next message.
🗑 Clear filesRemove all pending attachments.
➕ New conversationStart a fresh chat. The current conversation is auto-saved to the sidebar.
ℹ AboutView the version and support contact details.
📌 Always on topKeep the All Agents window floating above all other windows.
⟳ (top-right)Open the Connect Agents dialog to connect or reconnect individual applications.
ℹ️

The Actions button is intentionally hidden in the All Agents window. Each specialist agent manages its own actions. Use the individual plugin windows (Excel, AutoCAD, ETABS, Revit) to browse or create actions for a specific application.

4 Connecting to Software

Click the button in the top-right corner to open the Connect Agents dialog. Each application has its own independent connect button — you only need to connect the applications you plan to use.

Connect Agents
📊 Excel ✓ Connected to Excel
📐 AutoCAD ✗ AutoCAD offline
🏗 ETABS Connecting…
🏢 Revit ✓ Connected to Revit

How to Connect an Application

  1. Open the target application on your computer Excel, AutoCAD, ETABS, or Revit must be running before you click Connect. For Excel, a workbook must be open and active. For Revit, the GoCalc.AI Revit server must be running inside Revit.
  2. Click in the All Agents window top bar The Connect Agents dialog opens. Each row shows the current connection status for one application.
  3. Click ⟳ Connect next to the application The status field shows "Connecting…" while the agent tries to attach. On success it shows ✓ Connected and the top bar indicator turns green. On failure it shows the error reason in red.
  4. Repeat for each application you need You can connect any combination of the four agents independently. The orchestrator only calls agents that are successfully connected.
💡

You don't need all four. Connect only the applications relevant to your current task. For example, if you only need to move data from ETABS to Excel, connect just those two. The orchestrator will not attempt to call disconnected agents.

⚠️

If an application closes mid-session, its agent will return a connection error on the next orchestrator call. Open the application again and click ⟳ Connect in the dialog to re-establish the connection without restarting the chat.

5 How the Orchestrator Works

When you send a message, the orchestrator AI analyses your request, breaks it into subtasks, and delegates each subtask to the appropriate specialist agent. Results from one agent can be passed directly as input to the next.

The Delegation Flow

Your message
Orchestrator AI
ask_etabs / ask_excel / …
Specialist agent runs tools
Result back to orchestrator
Final reply to you

What Happens Step by Step

  1. You send a natural-language request The orchestrator receives your message. You do not need to specify which application to use — the AI infers this from your request.
  2. Orchestrator decides which agents to call The AI analyses the task and decides which specialist agent(s) to call and in what sequence. For a simple ETABS query, it calls only ask_etabs. For a cross-software workflow, it may call two or more agents in sequence.
  3. Specialist agent executes the subtask Each called agent runs its own internal agentic loop — calling its own tools (COM actions, API calls, etc.) against the live application. The specialist agent's full reply is returned to the orchestrator.
  4. Orchestrator passes results between agents If the task requires multiple steps, the orchestrator includes the first agent's result in the message to the next agent. For example, ETABS beam data is passed verbatim as context to the Excel agent.
  5. Orchestrator summarises and replies After all agents have completed their work, the orchestrator writes a final natural-language summary of what was done and shows the tool log for each agent call.

The Four Agent Tools

Tool nameDelegates toWhat it can do
ask_excelExcel AgentRead/write workbook data, run spreadsheet calculations, create custom Excel actions
ask_autocadAutoCAD AgentDraw, modify, and query elements in an AutoCAD drawing
ask_etabsETABS AgentRead structural model data, frames, loads, analysis results from ETABS
ask_revitRevit AgentCreate and manage BIM elements — columns, beams, floors, walls, grids, levels
ℹ️

Each specialist agent runs its own full agentic loop, including tool calls and AUTOFIX. The orchestrator does not see the individual tool calls — it only receives the specialist's final reply. The tool log in the chat shows which agents were called and a preview of each reply.

6 Cross-Software Workflow Examples

These examples show the kinds of multi-application tasks All Agents can handle in a single prompt.

Example 1 — ETABS Results → Excel

Read the beam section forces from ETABS and write them into column B of my Excel sheet, starting from row 2.
I'll get the beam data from ETABS first, then write it to Excel.
→ ask_etabs
• get_frame_section_forces
Got 48 beam results from ETABS. Writing them to Excel now.
→ ask_excel
• write_range → B2:B49
Done. 48 beam section force values have been written to column B of your active Excel sheet, starting from row 2.

Example 2 — Revit Model → Excel Schedule

Get the list of column types from Revit and create a schedule table in Excel with their names and dimensions.
Fetching column types from Revit, then I'll build the schedule in Excel.
→ ask_revit
• list_column_types
Found 6 column types in Revit. Creating the schedule table in Excel now.
→ ask_excel
• write_range → A1:C7 (headers + 6 rows)
Schedule created. Column A: Type Name, Column B: Width (mm), Column C: Height (mm). 6 column types listed from row 2 onward.

Example 3 — Excel Input → AutoCAD Drawing

Read the grid coordinates from my Excel sheet and draw the structural grid in AutoCAD.
Reading grid coordinates from Excel first.
→ ask_excel
• describe_workbook_data · read_range → A2:C20
Read 18 grid points from Excel. Drawing the structural grid in AutoCAD now.
→ ask_autocad
• draw_grid_framework
Structural grid drawn in AutoCAD with 18 intersection points based on the coordinates in your Excel sheet.

Example 4 — ETABS + Revit Comparison

How many columns are in ETABS vs Revit? Are the numbers the same?
→ ask_etabs
• count_total_frames
→ ask_revit
• count_elements (columns)
ETABS has 64 frame elements total (including beams). Revit has 32 column elements. If only columns are counted in ETABS, the numbers likely match — please confirm column-only filtering in ETABS if an exact comparison is needed.
💡

Be specific about what data to transfer. For example, say "column B, starting from row 2" rather than "the data". The more specific you are, the more accurately the orchestrator can pass the right data between agents.

7 AI Models

All Agents uses the same AI model selected in the Options dialog. The orchestrator and all specialist agents share this model — there is no separate model setting per agent.

🟢

OpenAI (ChatGPT)

GPT-4.1, GPT-4o, o3, o4-mini. Strong reasoning and tool use — well suited for orchestration tasks.

🟣

Anthropic (Claude)

Claude Opus, Sonnet, Haiku. Excellent at multi-step planning and long-context reasoning across agents.

🔵

Google (Gemini)

Gemini Pro and Flash. Good balance of speed and capability for shorter multi-agent workflows.

Ollama (Local/Cloud)

Qwen3, DeepSeek, Mistral, Kimi, and 25+ models. Use for privacy or offline scenarios.

💡

Recommended: Use a capable reasoning model (Claude Sonnet, GPT-4o, or Gemini Pro) for All Agents. Orchestration requires the AI to break tasks into steps and coordinate multiple agents — smaller or faster models may miss steps or misroute requests.

⚠️

Token usage is higher in All Agents mode. Each agent call makes at least one separate AI API request. A task that involves three agents may use 3× the tokens of a single-agent task. Use the Stop button to cancel if a response is taking too long or going in the wrong direction.

8 Keyboard Shortcuts

ShortcutAction
EnterSend message
Shift + EnterInsert a new line in the message
Ctrl + VPaste an image from clipboard into attachments
Click StopCancel the current AI response and re-enable input immediately
Click (top bar)Open the Connect Agents dialog
Click × in sidebarDelete a saved conversation

9 Tips & Best Practices

🔌

Connect before you ask

Always connect your applications first via the ⟳ dialog before sending a cross-software request. If an agent is disconnected, the orchestrator will report the error and stop.

🎯

Be specific about targets

Name the exact sheet, column, Revit category, or ETABS load case you want to use. Vague requests like "put the data somewhere" force the AI to guess.

🔁

Break big tasks into steps

For complex workflows, send one step at a time and verify each result before continuing. This avoids compounding errors across multiple agents.

🛑

Use Stop to save tokens

If the orchestrator is going in the wrong direction, click Stop immediately. This prevents unnecessary sub-agent calls from running and consuming API quota.

📋

Verify in the source application

After a write operation, switch to the target application and visually confirm the result. The orchestrator reports what the agent returned — always do a quick sanity check.

🤖

Use stronger models for orchestration

Claude Sonnet or GPT-4o produce better multi-step plans. Fast/small models may skip steps or call the wrong agent. Open Options to switch the model at any time.

📌

Always on top

Enable "Always on top" so the All Agents window stays visible while you work across multiple applications simultaneously.

🧹

New conversation for new tasks

Start a fresh conversation when switching to a completely different workflow. A clean context reduces the chance of the AI mixing up data from earlier tasks.

Example Prompts to Try

# Data transfer between applications "Read the beam loads from ETABS and paste them into column B of my Excel sheet starting at row 2." "Get all column dimensions from Revit and create a schedule table in Excel." "Read the grid coordinates from Excel and draw the structural grid in AutoCAD." # Model comparison and verification "How many floors are defined in ETABS vs Revit? Do they match?" "What is the total number of columns in the ETABS model?" "List all load cases in ETABS and all view names in Revit." # Multi-step workflows "Read the slab thickness from ETABS, update the value in Excel, then draw the updated floor plan in AutoCAD." "Export the Revit column schedule to Excel and format it with headers in bold." "Check if the beam count in ETABS matches the beam count in Revit and report any discrepancy." # Questions that span multiple apps "What structural data do I currently have available in ETABS and Revit?" "Summarise what's open across all connected applications."
💡

You don't have to name the agents. Write your request in natural language and let the orchestrator decide which agents to use. You can, however, explicitly direct it: "Ask the Excel agent to…" or "Use ETABS to…" if you want precise control.