Show up on a 3D globe in real time while you code.
Official extensions for devglobe.xyz
VS Code · JetBrains · Zed · NeoVim · Claude Code · Codex · OpenCode
DevGlobe is a free, open-source platform for developer metrics, insights and time tracking — automatically generated from your coding activity. Every developer lights up a live marker on a worldwide 3D globe while coding, and gets a public profile that showcases their stats, projects and links.
| Visibility | Networking | Motivation | Projects |
|---|---|---|---|
| Your own public profile with your GitHub, X, projects and links. A shareable page that shows what you're building. | See who's coding right now and in which language. Click a marker to open a developer's profile and projects. | Track your coding time, streaks and badges. Your stats keep you coming back. | Publish your projects with tech stack and teammates. Get discovered, upvoted and discussed by the community. |
1. Sign in on devglobe.xyz with GitHub, X (Twitter), or Google
2. Copy your API key from the profile settings
3. Install the extension in your IDE and paste the key
That's it — your marker appears on the globe.
The extension sends a heartbeat every 30 seconds while you code. Stop typing for 1 minute and heartbeats pause. After 10 minutes of inactivity, you disappear from the globe.
All extensions read your API key from ~/.devglobe/config.toml and let you toggle local privacy flags (hide_file_names, hide_branch_names, hide_project_names) there. Globe-side visibility (anonymous mode, repo sharing, profile mode) is managed on devglobe.xyz/dashboard/settings.
- Install from the VS Code Marketplace
- Open the DevGlobe sidebar (globe icon in the activity bar)
- Paste your API key → Connect
- Login — masked API key field + link to get your key on devglobe.xyz
- Dashboard — live coding time, active language, status message, start/stop tracking, disconnect
Available from the Command Palette (Ctrl+Shift+P / Cmd+Shift+P):
DevGlobe: Set Status MessageDevGlobe: Show Coding TimeDevGlobe: Open Globe
- VS Code 1.80+ — also works with Cursor, Windsurf, VSCodium, Positron, Antigravity and other VS Code forks
- Zero external dependencies
Compatible with all JetBrains IDEs: IntelliJ IDEA, WebStorm, PyCharm, GoLand, Rider, PhpStorm, CLion, RubyMine, DataGrip, Android Studio, RustRover.
- Install from the JetBrains Marketplace or download the
.zipfrom the Releases - For manual installation: Settings → Plugins → ⚙️ → Install Plugin from Disk
- Open the DevGlobe tool window (right sidebar)
- Paste your API key → Connect
- IDE builds 242 — 263.* (2024.2 to 2026.3)
- Java 17+
Pending review for the Zed marketplace (PR #5841). Install manually as a dev extension for now.
Option A — Standalone repo (no build required):
git clone https://github.com/devglobe-xyz/zed-devglobe.gitIn Zed: Cmd+Shift+P → "zed: install dev extension" → select the zed-devglobe/ folder.
Option B — From this repo (requires build):
cd devglobe-core && npm install && npm run build
cd ../zed-extension/server && npm install && npm run buildIn Zed: Cmd+Shift+P → "zed: install dev extension" → select the zed-extension/ folder.
Run the setup command from your terminal:
node /path/to/zed-extension/server/dist/server.js setup devglobe_YOUR_KEY_HEREThis writes your key to ~/.devglobe/config.toml (mode 0600). Or create the file manually:
mkdir -p ~/.devglobe
cat > ~/.devglobe/config.toml <<'EOF'
api_key = "devglobe_YOUR_KEY_HERE"
EOFOpen a project in Zed, trust the worktree when prompted, and start coding. You'll appear on the globe within 30 seconds.
- Node.js 18+
- Zed editor
lazy.nvim:
{
"Nako0/devglobe-extension",
event = "BufEnter",
build = "cd devglobe-core && npm install && npm run build",
config = function()
vim.opt.rtp:append(vim.fn.stdpath("data") .. "/lazy/devglobe-extension/neovim-plugin")
vim.cmd("runtime plugin/devglobe.lua")
require("devglobe").setup()
end,
}devglobe-core is built automatically on install. Requires Node.js 18+.
:DevGlobe setup devglobe_YOUR_KEY_HEREOr create ~/.devglobe/config.toml manually with api_key = "...".
| Command | Description |
|---|---|
:DevGlobe setup KEY |
Configure your API key |
:DevGlobe status MSG |
Set your status message |
:DevGlobe today |
Show your coding time today |
:DevGlobe open |
Open the globe at devglobe.xyz/space |
:DevGlobe debug true|false |
Toggle debug logging |
:DevGlobe log |
Open ~/.devglobe/devglobe.log |
:DevGlobe config |
Open ~/.devglobe/config.toml |
Visibility settings (anonymous mode, repo sharing on the live globe, profile mode) are managed on devglobe.xyz/dashboard/settings.
- NeoVim 0.9+
- Node.js 18+
In Claude Code, run:
/plugin marketplace add Nako0/devglobe-extension
/plugin install devglobe@devglobe
After installing, restart Claude Code (/exit, then reopen) so the plugin and its commands are loaded.
/devglobe:setup YOUR_API_KEY
Get your API key at devglobe.xyz — sign in, then open your profile settings.
| Command | Description |
|---|---|
/devglobe:setup YOUR_API_KEY |
Configure the plugin with your API key |
/devglobe:status MESSAGE |
Set a status message on your DevGlobe profile |
In Codex, run:
$skill-installer --repo Nako0/devglobe-extension --path codex-plugin
After installing, restart Codex so the skill and its hooks are loaded.
$devglobe setup YOUR_API_KEY
Get your API key at devglobe.xyz — sign in, then open your profile settings.
This saves your key, installs heartbeat hooks, and enables the codex_hooks feature flag.
| Command | Description |
|---|---|
$devglobe setup YOUR_API_KEY |
Configure the skill with your API key and install hooks |
$devglobe status MESSAGE |
Set a status message on your DevGlobe profile |
$devglobe check |
Verify the installation |
$devglobe uninstall |
Remove DevGlobe hooks from Codex |
Visibility settings (anonymous mode, repo sharing on the live globe, profile mode) are managed on devglobe.xyz/dashboard/settings.
Add the plugin to your opencode.json:
{
"plugin": ["opencode-devglobe"]
}OpenCode installs it automatically on startup via npm.
Restart OpenCode and ask:
setup devglobe with my key YOUR_API_KEY
Get your API key at devglobe.xyz — sign in, then open your profile settings.
Just ask in natural language — the plugin registers tools that the AI agent calls on your behalf:
| What you say | Tool | Description |
|---|---|---|
| "setup devglobe with key X" | devglobe_setup |
Configure API key |
| "set my devglobe status to X" | devglobe_status |
Set a status message on the globe |
| "check devglobe" | devglobe_check |
Verify installation |
Visibility settings (anonymous mode, repo sharing on the live globe, profile mode) are managed on devglobe.xyz/dashboard/settings.
100% open source. We never read your code.
What the extension sends to DevGlobe:
- Programming language detected by the IDE
- Editor + operating system name
- Coding time (per heartbeat, every 30 s)
- Origin remote URL of your current git repo (when present)
- Branch name (when present)
- File path relative to your repo root — never the absolute home path
- Status message (only what you set explicitly)
What the extension never sends:
- Source code, file contents, keystrokes
- Files outside any git repository (no path leaks for scratch files / local folders)
- Commit messages, environment variables, SSH keys
Local privacy flags — edit ~/.devglobe/config.toml:
api_key = "YOUR_API_KEY"
[privacy]
hide_file_names = false # omit the file field
hide_branch_names = false # omit the branch field
hide_project_names = false # omit repo + branch (project-level hiding implies branch hiding)Globe visibility (anonymous mode, repo sharing on the live globe, profile mode) is managed on devglobe.xyz/dashboard/settings — not in the extension.
API keys are stored in your OS keychain (VS Code SecretStorage, JetBrains PasswordSafe) or in a local config file under ~/.devglobe/ (Zed, NeoVim, Claude Code, Codex, OpenCode). Config files are created with 0600 permissions.
Network: HTTPS only (TLS 1.2+), no telemetry, no third-party trackers.
Read the full Privacy & Security documentation →
Contributions are welcome — fixes, new features, documentation.
- Fork the repository
- Create your branch (
git checkout -b fix/something) - Commit your changes
- Open a Pull Request
MIT