Local-first
Everything runs on your machine. No cloud dependency, no data leaving your control.
Ecosystem
GNO is not meant to live alone. These companion projects extend the same local-first, AI-native workflow around planning, spreadsheet automation, and communication. All open source, all composable, all built around the same principles.
Claude Code marketplace plugin for structured development workflow. Research agents, gap analysis, disciplined execution. Most engineering failures come from weak planning — Flow fixes that.
Flow's research agents can query GNO via the MCP server or the agent skill. The context-scout and repo-scout agents pair with `gno query` for comprehensive research while Flow keeps the plan disciplined.
/plugin marketplace add https://github.com/gmickel/gmickel-claude-marketplace/plugin install flowgno mcp install --target claude-desktopFast, deterministic CLI for Google Sheets. Key-based updates instead of fragile row indices. Batch operations for atomic workflows. JSON everywhere. Installs as a skill for Claude Code and Codex.
Export GNO search results to a tracking sheet. AI agents can query your knowledge base with GNO, then write structured findings to Google Sheets for downstream reporting or review.
gno query 'Q4 budget projections' --json | sheets-cli append --sheet 'Research Log'gno similar doc.md --json | sheets-cli upsert --sheet 'Related' --key idLocal CLI bridge for Outlook Classic automation via COM. AI-assisted email and calendar management from Claude Code. No API keys, no OAuth — just your existing authenticated session.
Find the right context in your GNO index before drafting a reply. AI agents can query your knowledge base to surface the meeting note, decision doc, or policy before composing an email.
gno query 'authentication decision' --answeroutlookctl draft --to team@company.com --subject 'Auth approach'The pattern
These tools aren’t a suite. They’re independent projects that happen to compose well because they share the same four principles.
Everything runs on your machine. No cloud dependency, no data leaving your control.
Structured input and output for automation. AI agents parse results reliably, humans pipe them with jq.
Both human-usable at the terminal and AI-usable as a skill or MCP server. Same tool, two interfaces.
Each tool does one thing well. Combine them for workflows that were too much work to script otherwise.
Example workflow
# 1. Search your knowledge base
gno query "performance optimization" --json > results.json# 2. Write to the tracking sheet
sheets-cli append --sheet Research --data @results.json# 3. Generate a cited summary
gno ask "what did we learn" --answer# 4. Draft the follow-up email
outlookctl draft --to lead@team.com --subject "Research"Build your own
Open an issue on the GNO repository. We love hearing about local-first, AI-native tools that compose with GNO’s CLI, REST API, or MCP server.