curo1305 51029d4a2d test: add coverage for config TUI, ConfigField, schema changes, and CLI auto-setup
- test_config.py: GeneralConfig defaults, plugin_settings round-trip
- test_config_field.py: ConfigField dataclass, BasePlugin.config_fields() no-op,
  plugin subclass override
- test_config_tui.py: _get/_set_nested, _fid/_pfid helpers, GENERAL_FIELDS validity,
  ConfigApp general tab rendering, save handler, plugins table, plugin tab visibility,
  q key exit — using Textual run_test() + Pilot
- test_cli.py: auto-setup wizard on first run, skip wizard when config exists,
  /config in _STATIC_COMMANDS

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-18 21:53:19 +02:00
2026-05-17 12:48:32 +02:00
2026-05-17 12:48:32 +02:00

Pyra

A personal AI assistant CLI with vault-first security. Combines multi-provider AI chat with long-term memory and (coming) automation skills.

Quick Start

pip install -e .      # or: pipx install .
pyra setup            # choose your AI provider
pyra chat             # start talking

Providers

Local (no API key needed):

  • LM Studio — http://localhost:1234
  • Ollama — http://localhost:11434
  • llama.cpp server — http://localhost:8080

Cloud:

  • Anthropic (Claude), OpenAI (GPT), Google (Gemini), DeepSeek, Qwen

Commands

Command Description
pyra setup Run the provider setup wizard
pyra chat Start interactive chat
pyra memory list List memory files
pyra memory read <name> Read a memory file
pyra memory write <name> <content> Write a memory file
pyra memory append <name> <content> Append to a memory file

In-chat slash commands

Command Description
/help Show available commands
/memory list List memory files
/clear Clear conversation history
/quit or /exit Exit Pyra

Security

  • API keys live in ~/.pyra/vault/ — the AI cannot read this directory
  • config.yaml never contains credentials — only provider ID, model name, and base URL
  • Prompt injection scanner — warns on suspicious AI output, logs to ~/.pyra/security.log
  • Path sandboxing — the AI can only reference memory files by name; traversal is blocked

Memory

Pyra reads your memory files at the start of each session and injects them as context. Files are plain Markdown stored in ~/.pyra/memory/:

~/.pyra/memory/
├── user/profile.md     ← who you are
├── context/            ← ongoing projects
└── knowledge/          ← general notes

~/.pyra/ Directory

~/.pyra/
├── config.yaml         ← provider + model (no secrets)
├── security.log        ← injection event log
├── memory/             ← AI-readable long-term memory
├── skills/             ← automation scripts (Stage 2)
└── vault/              ← secure, AI-inaccessible storage
    └── secrets/api_keys.json

Roadmap

  • Stage 1 (now): Core CLI, multi-provider chat, memory, vault security
  • Stage 2: Skills — shell/PowerShell/Python automations with user approval gates
  • Stage 3: Vault encryption with age
  • Stage 4: Security audit sub-agent
  • Stage 5: Web UI, embedding-based memory search
S
Description
No description provided
Readme 516 KiB
Languages
Python 100%