Session 7: Introduction to AI Tools
Date: December 5, 2025
Duration: ~35 minutes
Speaker: Scott Pei (International Logistics Core)
Quiz Host: Aimee Li
Recording: Watch Session Recording
📋 Overview
In this session, Scott Pei from the International Logistics (IL) Core team introduced AI Tools, a suite his team has been building to streamline AI-assisted development at WiseTech Global. The tool is integrated directly into CW Tools — once released, team members simply download and update CW Tools within CargoWise to start using it. The project is still in its early stages, and the team actively welcomes feedback and suggestions.
Scott walked through the three core capabilities available today — the Workspace Launcher, environment setup, and MCP service management — and shared the roadmap for upcoming features, including import/export of customizable prompts and a no-code Q&A experience for non-developer product teams.
🎯 Key Topics Covered
1. AI Tools Overview & CW Tools Integration
- Unified Distribution: AI Tools ships as part of CW Tools, so there's no separate installation. After release, users download or update CW Tools inside CargoWise to access the latest features.
- Early-Stage Project: The suite is in an early development phase, and the team encourages the wider group to try it out and share constructive feedback.
- Three Core Feature Areas: The current release focuses on launching workspaces, setting up environments, and managing MCP services.
2. Workspace Launcher
The Workspace Launcher is the main entry point of AI Tools.
- One-Click Open in VS Code: Launch a preconfigured workspace directly in VS Code with a single click.
- Supported Workspaces: Currently supports the CargoWise and Glow project workspaces.
- Bundled Prompts & Instructions: Each workspace comes with its own set of prompts and instruction files tailored to that project.
- CargoWise Workspace Prompt Folders: Includes
WTG.AI.Prompts.CargoWise,Development, andPersonalprompt collections.
3. Environment Setup
- Guided Configuration: AI Tools helps set up a consistent development environment so team members can get productive quickly.
- Reduced Onboarding Friction: Standardized setup minimizes manual configuration across machines and teams.
4. MCP Service Management
- Managed MCP Services: AI Tools lets you configure and manage Model Context Protocol (MCP) servers from a single place.
- Currently Configured Services: EdiProd and WTG Knowledge MCP services are available out of the box, enabling agent-mode workflows against internal systems.
5. Knowledge Base Best Practices
Best practices reinforced during the session for building AI-friendly knowledge bases:
- Naming Convention: Follow the
team-name-contentconvention when creating a documentation repository for a knowledge base. - Avoid Image-Heavy Content: Screenshots and images are hard for AI to process — prefer text-based explanations and diagrams to ensure the best AI retrieval and processing quality.
6. Future Roadmap
- Import / Export Customizable Prompts: A planned feature to let teams share and reuse custom prompt collections across workspaces.
- No-Code Q&A Experience: For product teams who prefer not to work in VS Code or other code-oriented tools, the goal is a simple question box — ask a question, click, and get an answer from AI.
- Building on Knowledge Search: The existing Knowledge Search already answers EdiProd-related questions. The plan is to extend AI Tools so it can also handle business-specific information and custom prompt-driven learning that Knowledge Search does not currently cover.
🧠 Quiz Activity
Following the presentation, Aimee Li hosted a live quiz with five questions drawn from Scott's talk. Answers reinforced the key facts about AI Tools:
| # | Question | Answer |
|---|---|---|
| 1 | What functionality will AI Tools support in the future? | Import/export customizable prompts (Launch Workspace, Setup Environment, and Manage MCP Service are already supported) |
| 2 | Which MCP services are currently configured in AI Tools? | EdiProd and WTG Knowledge |
| 3 | What naming convention should a knowledge base documentation repository follow? | team-name-content |
| 4 | What type of content should you avoid when using GitHub Copilot with a knowledge base? | Screenshots and images |
| 5 | Which prompt folders does the CargoWise workspace contain? | WTG.AI.Prompts.CargoWise, Development, and Personal |
🔗 Featured Resources
🔑 Key Takeaways
- Zero-Friction Distribution: AI Tools ships inside CW Tools — no separate install. Just update CW Tools in CargoWise to get the latest features.
- Workspace Launcher: One-click access from VS Code to the CargoWise and Glow workspaces, each bundled with its own tailored prompts and instructions.
- Built-In MCP Services: EdiProd and WTG Knowledge MCP services are configured out of the box, enabling agent-mode workflows against internal systems.
- Knowledge Base Discipline: Follow the
team-name-contentnaming convention and avoid image-heavy content — text and diagrams process far better with AI. - Roadmap Focus: Import/export of custom prompts and a no-code Q&A experience are the next priorities, extending value to non-developer product teams.
- Early & Open: The project is in an early stage — the team actively welcomes feedback and contributions.
Session 7 | December 5, 2025 | Introduction to AI Tools | Crossroad AI Team