Skip to content

v0.1.0

Choose a tag to compare

View all tags
@ruslanmv ruslanmv released this 15 Nov 01:34
· 177 commits to master since this release
v0.1.0
72fa1b0

GitPilot v0.1.0— Initial Release 🎉

GitPilot v0.1.0 is the first public release of the GitPilot AI coding assistant: a local, multi-LLM powered tool that plans and applies changes to your GitHub repositories through a simple web UI.

🚀 What’s included

1. Agentic planning & chat workspace

  • Chat-based “mini frontend” for describing changes in natural language
    e.g. “Add a new API endpoint for user logins.”

  • Backend generates a structured multi-step plan using CrewAI:

    • High-level goal and summary
    • Ordered steps with descriptions
    • Associated file list per step

  • UI displays the plan in a dedicated Plan view alongside the chat history.

  • Approve & Execute button wired to a backend executor (currently a safe stub).

2. GitHub repository integration

  • Uses a GitHub token (GITPILOT_GITHUB_TOKEN or GITHUB_TOKEN) to access user repos.

  • Repository selector to browse and select a repo to work on.

  • File tree viewer powered by:

    • GET /api/repos – list accessible repositories
    • GET /api/repos/{owner}/{repo}/tree – list files in the repo

  • API endpoints prepared for file operations:

    • GET /api/repos/{owner}/{repo}/file
    • POST /api/repos/{owner}/{repo}/file (for future editing support)

3. Multi-provider LLM support

Configurable from the Admin / LLM Settings page and/or environment variables:

  • OpenAI

    • API key + model configurable
    • Uses OPENAI_API_KEY and GITPILOT_OPENAI_MODEL env vars as fallback

  • Claude (Anthropic)

    • API key + model configurable
    • Uses ANTHROPIC_API_KEY and GITPILOT_CLAUDE_MODEL env vars as fallback

  • IBM watsonx.ai

    • API key, project ID, and model ID configurable
    • Uses WATSONX_API_KEY, WATSONX_BASE_URL, GITPILOT_WATSONX_MODEL as fallback

  • Ollama

    • Local model support via configurable base_url and model
    • Uses OLLAMA_BASE_URL and GITPILOT_OLLAMA_MODEL as fallback

All providers are normalized to the model formats expected by CrewAI (e.g. openai/..., anthropic/..., watsonx/..., ollama/...).

4. Flow viewer (Agent graph)

  • Flow Viewer page showing a visual graph of the internal multi-agent workflow using React Flow:

    • Nodes for planner, repo reader, code writer, reviewer, and GitHub tools.
    • Edges describe how information flows between agents.

  • Backed by GET /api/flow/current which returns a structured node/edge definition.

This makes the “agentic” architecture transparent and easier to reason about.

5. Admin & settings management

  • Centralized App Settings backed by a JSON file in the user’s home directory.

  • LLM Settings page:

    • Choose active provider: OpenAI, Claude, watsonx, or Ollama.
    • Configure per-provider settings from the browser.
    • Save changes via PUT /api/settings/llm.

  • Quick provider switching via:

    • GET /api/settings
    • POST /api/settings/provider

6. Frontend & developer experience

  • React + Vite frontend (npm run dev) with:

    • Chat workspace (chat + plan)
    • Repo selector & file tree
    • LLM settings admin page
    • Flow viewer page

  • Built assets bundled into the Python package and served by FastAPI:

    • gitpilot/web/index.html
    • Static JS/CSS assets under gitpilot/web/assets

  • Python CLI entrypoints:

    • gitpilot – start API + UI locally
    • gitpilot-api – start API-only server

⚠️ Known limitations in v0.1.0

  • Plan execution is still a stub

    • The “Approve & execute” action returns a textual stub and does not yet apply real changes to GitHub.

  • No explicit per-file CREATE/MODIFY/DELETE actions

    • Plans list files per step, but file actions are not yet strongly typed at the UI level.

  • No persistent execution log

    • Execution responses are shown in chat but not yet stored as a detailed log or commit history summary.

  • UI polish & layout

    • “Answer vs Action Plan” split, richer project context panel, and footer CTA are planned for upcoming releases.

💡 Next steps (planned for future versions)

  • Implement a real plan executor that safely applies changes via the GitHub API.
  • Introduce structured file actions (CREATE/MODIFY/DELETE) in both backend plan schema and frontend UI.
  • Add a richer Project Context panel (branch, file count, last analysis time).
  • Improve the chat layout with separate Answer and Action Plan sections in each assistant reply.
  • Add a footer with “⭐ Star our GitHub project” CTA and links to Docs & GitHub.
Assets 4
Loading