Skip to content

pixelbyaj/GyroSpace

Repository files navigation

GyroSpace

GyroSpace — your AI coding co-pilot with memory, a voice, and a personality

Persistent engineering memory for AI-assisted software development — now with Gyro, a voice-driven desktop assistant.

Release License Platform Built with Node React Donate

GyroSpace combines AI CLIs, terminal workflows, repository intelligence, and commit-linked context into a shared workspace where engineering knowledge survives across sessions, developers, branches, and time.

It supports Claude Code, Gemini CLI, Codex, Aider, and custom AI agents inside a VS Code-style desktop environment — while continuously building a searchable memory layer around your repository.


Table of Contents


The Problem

AI coding tools are powerful, but software teams still lose critical engineering knowledge every day. Current AI workflows suffer from:

  • AI sessions forgetting previous work
  • Lost debugging history
  • Repeated architectural discussions
  • Re-analysis of repositories every session
  • Developer handoff friction
  • Lost terminal knowledge
  • Lost reasoning behind commits
  • Expensive token usage for repeated context loading
  • Knowledge disappearing when developers leave

Git stores what changed. GyroSpace stores:

  • why it changed
  • how it was debugged
  • what the AI suggested
  • which approaches failed
  • what architectural decisions were made
  • how problems were solved

What GyroSpace Is

GyroSpace is a persistent engineering memory layer for software teams.

Every AI interaction, terminal command, debugging workflow, architecture discussion, review session, and commit explanation becomes searchable project knowledge. The repository becomes capable of remembering its own engineering history.

Future developers can ask:

  • "Why was this parser redesigned?"
  • "What issue caused this migration?"
  • "What did Claude recommend during the Kafka refactor?"
  • "Which prompts fixed the validation bug?"
  • "How was this environment issue resolved?"
  • "Which files are risky to modify together?"

GyroSpace reconstructs answers from AI conversations, terminal history, commit-linked summaries, repository analysis, debugging workflows, architecture discussions, and generated knowledge snapshots.


Meet Gyro

Gyro — the GyroSpace mascot

Gyro is your built-in, voice-driven desktop assistant — an animated co-pilot that lives on your desktop and runs the work for you. Talk to it, and it acts.

  • 🎙️ Voice commands — "Gyro, run the tests", "review my diff", "take a snapshot", "open the terminal". Just start with "Gyro, …".
  • 🧠 Offline brain — ask it anything; with a local LLM (Ollama) it answers privately, no cloud.
  • 🖥️ Desktop tasks — "open VS Code", "open Downloads", "search the web", "lock the screen", "volume up", "take a screenshot".
  • 📝 Voice notes — dictate notes Whisper-style, saved alongside your project.
  • 🗣️ Robotic voice + reactions — Gyro talks back, animates while it works, and reacts when you poke it. Mute anytime.
  • ✏️ Learns your voice — mis-heard a word? Edit it in chat and Gyro remembers the correction for next time.
  • 📌 Always there — floats on top as a desktop pet, starts with your computer, and stays in the system tray after you close the window.

Press F1 in the app → What Gyro Can Do for the full command list. Every command is editable under Settings → Gyro Commands.

Avatars

Make Gyro yours — pick from three original characters under Settings → Gyro. Your choice follows you across the chat avatar, the in-app mascot, the floating desktop pet, and the splash screen.

Gyro avatars — Robot, Capsule Pal, and Cartoon, each with their characteristics

Avatar Vibe Characteristics
🤖 Robot (default) Sharp & techie The original Gyro — neon look, CSS-animated moods and tap reactions, gear + antenna + status LED.
🟡 Capsule Pal Friendly & playful A warm capsule character with goggle eyes and dungarees, keeping Gyro's signature gear and green LED.
Cartoon Animated & expressive A hand-authored Lottie character with squash-and-stretch motion, a think-bulb, and a jump-with-confetti celebration that reacts to what Gyro is doing.

All three are GyroSpace's own original designs. Robot and Capsule Pal are lightweight SVGs; Cartoon adds full Lottie animation to the in-app mascot.


Quick Start

  1. Install GyroSpace — see Installation below.
  2. Add a folder — click + Folder in the sidebar. Pick the project directory you want to work on.
  3. Pick an AI CLI — Claude Code is the default. If it's not installed yet, you'll see a one-click install banner.
  4. Sign in to your CLI — for Claude Code: claude /login. Other CLIs: see the in-app User Guide (F1Signing In).
  5. Take your first snapshot — open the 📸 Snapshots tab, give it a name like first-day, click Take Snapshot. You'll find it at <your-project>/.gyrospace/snapshots/manual/.

For everything else, press F1 inside the app to open the User Guide.


Installation

Windows

Download the latest GyroSpace-Setup-*.exe from the Releases page and run it.

The installer is a standard NSIS wizard:

  1. Welcome screen
  2. Install location — defaults to %LocalAppData%\Programs\GyroSpace, you can change it
  3. Shortcuts — Start Menu (under "GyroSpace" folder) and Desktop, both on by default
  4. Install progress
  5. Finish — option to launch GyroSpace immediately

After install, GyroSpace shows up in:

  • Windows Search (type "gyrospace") — the Start Menu shortcut is indexed
  • Start Menu under the GyroSpace folder
  • Settings → Apps for clean uninstall

Per-user install — no admin rights required, no UAC prompt.

macOS

Download the .dmg from Releases, drag GyroSpace into /Applications.

Linux

Download the .AppImage and chmod +x it. AppImage runs without root.

Build from source

git clone <repo-url> gyrospace
cd gyrospace
npm install
npm run dev      # development mode with hot reload
npm run build    # production build into out/
npm run package  # platform-specific installer (Windows: NSIS via electron-builder)

Requirements

Dependency Version
Node.js 22.x or newer
Operating system Windows 10+, macOS 12+, or modern Linux
Disk ~150 MB for the app, plus growth in .gyrospace/ per project
One AI CLI on PATH Claude Code, Gemini CLI, OpenAI Codex, Aider, or your own

GyroSpace will install Claude Code / Gemini / Codex / Aider for you with one click via the install banner — you don't need to do that yourself.


Configuration

GyroSpace runs out of the box with no required configuration. Folder-specific settings live in the ⚙ Settings sidebar tab once a folder is added; cross-app preferences live in <userData>/gyrospace-state.json.

Folder settings

Setting Where Effect
AI CLI Folder modal Which CLI launches in the terminal
Model Folder modal Per-folder model override
Auto-run on startup Folder modal Auto-launch CLI when folder is opened
Custom command Folder modal Free-form command for Custom CLI
Quick prompts Quick Prompts bar One-click prompts above terminal

Environment

Variable Set by Purpose
GYROSPACE_FOLDER GyroSpace (in spawned PTY) Absolute path of the active folder, available to scripts inside the terminal

.gitignore for .gyrospace/

A reasonable starter block to exclude the noisy / derived parts:

.gyrospace/snapshots/auto/
.gyrospace/sessions/
.gyrospace/search/
.gyrospace/temp/

context.md, snapshots/manual/, commits/, and memory/ are usually worth committing — that's how engineering memory travels with the repo.


Keyboard Shortcuts

Action Shortcut
Toggle sidebar Ctrl+B (Cmd+B on macOS)
Find inside the active terminal Ctrl+F
Find next / previous (bar focused) Enter / Shift+Enter
Find next / previous (terminal focused) Ctrl+G / Shift+Ctrl+G
Semantic search across sessions / snapshots / commits / memory Ctrl+Shift+F
Open the User Guide F1
Quit Ctrl+Q (Cmd+Q on macOS)

Right-click a folder in the sidebar for: Show History, Restart Terminal, Open Folder in OS, Edit Settings, Remove.


Auto Snapshot

Invisible background memory system. Small + efficient. Stored at .gyrospace/snapshots/auto/.

Triggers

  • Periodic: every 30 minutes
  • Git events: commit, branch switch, merge, pull, rebase
  • AI workflow events: long AI response completed, architecture discussion detected, debugging session detected, AI review completed
  • Terminal events: critical error, test failures, deploy commands, Docker / K8s commands, migration scripts
  • Session events: app close, inactivity timeout (15 min), workspace switch, session end

A 5-minute per-folder cooldown prevents spam.

Automatic snapshots are what make GyroSpace truly intelligent — knowledge is captured even when you forget to capture it.


Manual Snapshots

Human-curated milestones with rich summaries and labels. Stored at .gyrospace/snapshots/manual/<timestamp>_<slug>/.

You're prompted for a name when taking one — pick something memorable like before-mq-refactor, v1-cut, or incident-2026-05-08.


Core Concepts

Persistent Engineering Memory

GyroSpace continuously captures and preserves AI prompts and responses, terminal activity, debugging workflows, architectural decisions, repository analysis, code review discussions, generated documentation, commit reasoning, implementation attempts, and session summaries.

Knowledge survives across terminal restarts, AI model changes, developers, branches, pull requests, onboarding, and long-running projects.

Commit-Linked Context Intelligence

Every commit can carry engineering reasoning alongside code changes. GyroSpace automatically associates AI prompts, terminal commands, debugging workflows, generated explanations, review discussions, architecture notes, patch analysis, and implementation summaries with commits, branches, pull requests, files, and sessions.

This creates a searchable historical intelligence layer on top of Git.

Developer → Uses Claude to debug parser
Developer → Runs migration commands
Developer → Commits changes

GyroSpace automatically:
- captures engineering reasoning
- summarizes implementation decisions
- stores debugging context
- links knowledge to the commit
- updates repository memory

Repository Intelligence

GyroSpace continuously builds a live understanding of the repository: services, APIs, workflows, dependencies, frameworks, architectural boundaries, frequently modified modules, debugging patterns, and AI-generated implementation history.

The repository becomes queryable through natural language:

"Where is ISO 20022 validation implemented?"
"Which module handles Kafka acknowledgements?"
"Show payment-processing flow."
"Which services depend on RabbitMQ?"

AI Session Continuity

Most AI coding sessions are temporary. GyroSpace provides long-term AI continuity by preserving prior reasoning, implementation attempts, debugging progress, architecture discussions, terminal workflows, preferred prompts, and generated summaries.

AI assistants can resume work from previous sessions without expensive re-analysis of the repository.


Features

AI CLI Workspace

  • One persistent AI terminal per folder
  • Claude Code, Gemini CLI, Codex, Aider support
  • Custom AI CLI integration
  • Live terminal preservation
  • Auto-run models on startup
  • One-click CLI installation
  • Multi-folder workspace
  • Split-pane terminal views
  • Session-aware terminal restoration

Context Handoff System

  • AGENTS.md — lightweight, AI-readable project memory at the repo root
  • .gyrospace/context.md — full repository memory and engineering audit trail, designed to be committed

Semantic Engineering Search

Cross-session natural-language search across AI conversations, terminal history, commits, debugging logs, architecture discussions, generated summaries, and repository analysis. Examples:

"Find discussion about pacs.008 validation."
"Who changed MQ retry logic?"
"Show previous attempts to fix this issue."
"Find all Kafka-related debugging sessions."

AI-Assisted Handoff

Before leaving a task, generate a snapshot the running AI fills in itself with: work summaries, pending tasks, debugging status, implementation notes, architecture updates, and a repository snapshot. Future developers immediately continue from the same context.

Context-Aware Terminal Replay

GyroSpace stores commands, outputs, errors, AI suggestions, fixes, and debugging workflows so developers can replay historical debugging sessions and environment fixes.

Workspace Snapshots

Capture complete development states including AI context, terminal state, selected files, open tasks, architecture notes, and debugging progress. Useful for onboarding, bug investigations, architecture reviews, long-running migrations, and enterprise audit trails.


Storage

All persistent GyroSpace intelligence is stored at <repo-root>/.gyrospace/ — committable, portable, and the entire reason knowledge survives across machines and developers.

Full specification: docs/STORAGE.md — paths, file formats, snapshot structure, commit intelligence schema, immutability guarantees, and what to commit vs. ignore.


Repository Analysis Engine

Automatically detects languages, frameworks, manifests, dependency graphs, runtime environments, project boundaries, architectural patterns, and AI-generated workflow history.

Supported ecosystems include TypeScript, JavaScript, Python, .NET, Java, Go, Rust, PHP, Ruby, Swift, Kotlin, Electron, React, Angular, ASP.NET Core, Spring Boot, FastAPI, and more.


AI Agent Generation

Automatically generates reusable AI agents at .claude/agents/:

  • code-reviewer
  • lint-checker
  • standards-keeper
  • architecture-reviewer (coming)
  • security-reviewer (coming)
  • performance-reviewer (coming)
  • migration-assistant (coming)

Existing files are never overwritten.


Source Control Intelligence

Integrated Git panel with AI-enhanced workflows: branch status, ahead/behind tracking, staging controls, commit + push, recent commit history, diff review, AI patch analysis, commit-context generation.

Ask AI About My Diff

GyroSpace can export patch files, inject review prompts into active AI sessions, and request architecture / security / performance / migration reviews.


Privacy & Local-First Design

  • Nothing leaves your machine by default
  • Session analysis runs locally
  • Repository analysis runs locally
  • Context generation runs locally
  • No automatic cloud synchronization
  • Config files are referenced but never dumped
  • Sensitive configuration values are excluded from repository memory
  • No telemetry, no analytics, no automatic update checks

Vision

GyroSpace aims to become the memory operating system for AI-assisted software engineering.

Future roadmap:

  • multi-model orchestration
  • repository knowledge graphs
  • semantic engineering search (TF-IDF v0 shipped; embeddings next)
  • autonomous engineering agents
  • AI workflow automation
  • architecture reconstruction
  • onboarding copilots
  • enterprise audit trails
  • cross-repository memory
  • local-first vector indexing
  • MCP integration
  • team intelligence graphs
  • engineering analytics
  • AI reasoning timelines
  • autonomous repository maintenance

See ROADMAP.md for the live tracker.


FAQ

Q: Does GyroSpace send my code anywhere? No. GyroSpace itself sends nothing. Whatever your AI CLI sends to its provider is between you and that vendor. Session logs, snapshots, commit intelligence, and repository memory all live on disk locally.

Q: Why is AGENTS.md at the repo root and not under .gyrospace/? AI CLIs auto-discover AGENTS.md from the repo root. Putting it under .gyrospace/ would break that discovery. The rest of GyroSpace's intelligence lives under .gyrospace/ as the storage spec requires.

Q: How do I disable auto-snapshots? There's no global off-switch yet. You can keep them out of git via .gitignore:

.gyrospace/snapshots/auto/

Q: Can I run multiple AI CLIs at once? Yes. Each folder has its own persistent terminal — open two folders, configure different CLIs, both run in parallel. Use Split in the pane header to view both side-by-side.

Q: What happens to my data if I uninstall GyroSpace? Anything inside your project's .gyrospace/ directory stays where it is. Per-machine state in <userData>/gyrospace-state.json and the legacy session log location can be deleted by hand.

Q: How big does .gyrospace/ get? Manual snapshots are ~50 KB to a few MB depending on the diff. Auto snapshots are ~10–50 KB. Repository memory is small (KBs). The largest grower is sessions/archived/ — gitignore it if you don't want it tracked.

Q: Does it work without Claude / OpenAI / Google? Yes. The Custom CLI option lets you point GyroSpace at any command on PATH. Use Aider with a local model, Ollama, or your own wrapper.

Q: Does GyroSpace itself talk to an AI? No. GyroSpace orchestrates your CLI; it doesn't make API calls of its own. The "Generate Handoff" feature, for example, just types a prompt into the running CLI session.


Philosophy

Git tracks code. GyroSpace tracks engineering knowledge.

Git remembers what changed. GyroSpace remembers why.


Support the Project

GyroSpace (and Gyro!) is built and maintained in the open by a single developer. If it saves you time — or you'd just like to keep Gyro's gears turning — a small donation goes a long way. 🙏

Donate with PayPal

paypal.me/pixelbyajwa — thank you for the support! ⚙️


License

MIT © 2026 Abhishek Joshi

About

Folder-scoped terminals for Claude Code, Gemini CLI, Codex, Aider, and any other AI CLI — wrapped in a VS Code-style desktop app.

Resources

License

Contributing

Stars

3 stars

Watchers

0 watching

Forks

Packages

 
 
 

Contributors