Skip to content
| Marketplace
Sign in
Visual Studio Code>Chat>FIP Team Chat for VS CodeNew to Visual Studio Code? Get it now.
FIP Team Chat for VS Code

FIP Team Chat for VS Code

pmiskulin

|
4 installs
| (0) | Free
Integrirani timski chat za Visual Studio Code. Olakšava suradnju, razmjenu poruka i dijeljenje koda izravno u vašem razvojnom okruženju.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

FIP Team Chat Extension for VS Code

Overview

The FIP Team Chat Extension for VS Code supercharges your development workflow by embedding a robust real-time messaging and collaboration hub directly into Visual Studio Code. Effortlessly communicate with your FIP team, share vital code snippets, discuss critical project details, and significantly boost productivity—all without ever leaving your editor. This VS Code extension is meticulously designed for efficient team collaboration, real-time chat, and streamlined communication, featuring robust support for UNC path configurations and project-specific chat settings for a tailored experience.

Resolving UNC Path Issues

If you encounter this error, you have two options:

  1. Update VS Code Security Settings:
    • Go to Settings (Ctrl+, or Cmd+, on Mac)

    • Search for "Security: Restrict UNCAccess"

    • disable that

    • !!! OPTIONAL !!!

    • Search for "security.allowedUNCHosts"

    • Add your UNC host to the list: ["*"] to allow all hosts or ["192.168.11.42"] for a specific host

    • Restart VS Code

!!! OPTIONAL !!! 2. Enable UNC Support in Extension Settings:

  • Go to Settings (Ctrl+, or Cmd+, on Mac)
  • Search for "FIP-Chat: Allow UNC Paths"
  • Enable the setting

Note: VS Codium and Cursor may have different default security settings for UNC paths, which is why the extension might work in those editors without additional configuration.

Features

  • Integrated VS Code Chat Sidebar: Instantly access your FIP team chat directly from the VS Code activity bar for quick messaging, real-time updates, and seamless collaboration.
  • Real-Time Team Communication & Collaboration: Engage in live discussions, share ideas, and resolve development issues faster with an intuitive real-time messaging platform built for teams.
  • Secure & Encrypted Messaging: Ensure confidential team communication with robust AES-256 encryption protecting all your conversations and shared data.
  • Effortless Code Snippet Sharing: Easily share, discuss, and review code snippets directly within the chat interface, improving code quality and team understanding.
  • Project-Specific Chat Configuration via package.json: Define unique chat file locations per project using package.json, enabling version control and consistent shared configurations for your entire development team.
  • Flexible UNC Path Support: Securely store and access chat files from network locations (UNC paths), with easily configurable security settings within both VS Code and the extension for enterprise environments.
  • Customizable Chat Storage Location: Designate a specific local or network folder for storing chat history and messages, giving you full control over your data.
  • Quick Command Palette Access: Swiftly access all chat functionalities—sending messages, configuring settings, and showing the chat view—via the VS Code command palette (Ctrl+Shift+P).
  • Customizable Notifications: Stay informed without being overwhelmed. Receive optional notifications for new messages, complete with sound alerts and adjustable message preview lengths.

Installation

  1. Open Visual Studio Code.
  2. Go to Extensions → Click on the ... menu (top-right corner).
  3. Select Install from VSIX....
  4. Choose the chat-extension-0.0.1.vsix file from your system.

Usage

  1. Open the command palette (Ctrl+Shift+P or Cmd+Shift+P on Mac).

  2. Use the following commands:

    • FIP-Chat: Configure Chat: Set up the chat folder.
    • FIP-Chat: Send Message: Send a new message.
    • FIP-Chat: Show Chat: Open the chat view.
  3. Access the chat view from the activity bar under the FIP-Chat section.

Package.json Configuration (New Feature)

You can now specify the chat file location directly in your project's package.json file. This allows you to:

  1. Version control your chat file location
  2. Use project-specific chat files
  3. Share the same chat configuration with all team members

Add one of the following sections to your project's package.json:

{
  "fip-chat": {
    "chatPath": "path/to/chat.json" 
  }
}

OR

{
  "chat-extension": {
    "chatPath": "path/to/chat.json"
  }
}

The path can be:

  • A relative path from your workspace root (e.g., .vscode/chat.json)
  • An absolute path to any location (e.g., C:/Chat/project-chat.json)

When the extension starts, it will automatically check for this configuration and use it if found.

Network Path Support (UNC Paths)

This extension supports storing chat files on network locations (UNC paths). However, due to VS Code's security settings, you may encounter the following error:

Error configuring chat folder: UNC host 'x.x.x.x' access is not allowed. Please update the 'security.allowedUNCHosts' setting if you want to allow this host.

Development

Running the Extension

  1. Clone the repository and open it in Visual Studio Code.
  2. Press F5 to launch a new VS Code window with the extension loaded.
  3. Use the command palette to test the extension.

Scripts

  • npm run compile: Compile the TypeScript code.
  • npm run watch: Watch for changes and recompile automatically.
  • npm run lint: Run ESLint to check for code quality.
  • npm run test: Run tests for the extension.

Debugging

  • Set breakpoints in src/extension.ts to debug the extension.
  • Use the debug console to view logs and errors.

Contributing

Contributions are welcome! Feel free to open issues or submit pull requests to improve the extension.

License

This project is licensed under the MIT License.

Contact

For questions or feedback, please contact the publisher: pmiskulin.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2025 Microsoft