innoday
Advanced tools
AI-Powered Team Orchestration Platform - Streamline product development and team collaboration with AI
InnoDay is the AI-powered central hub for your projects. Development state normally scatters across a board, GitHub, a release tool, and someone's meeting notes — InnoDay pulls it into one project-shaped record that every skill, agent, and CLI tool writes back to, so tickets, releases, syncs, scope changes, and decisions all stay queryable in one place (and an AI teammate stays productive across sessions instead of being re-briefed each time).
📖 New here? → Quickstart to get connected (~5 min) · Platform Guide for how it works.
.innoday/memory.json is only a cache.The full narrative — the six problems it solves, with diagrams and the enforced-hierarchy rationale — is in the Platform Guide.
Most people just need the CLI, pointed at the shared dev environment — not a repo clone or a self-hosted platform.
uv tool install innoday # install the CLI from PyPI
innoday login --with-token # paste your idt_… token when prompted
innoday init hs/pf # onboard a project workspace (clones + configures repos)
innoday status # verify: identity, resolved project, token, API health
Full walkthrough — including token handling, working across projects, and the "already used InnoDay before?" upgrade step — is in the Quickstart.
Add InnoDay directly to Claude Code — create tickets, sync boards, and query work items without leaving your editor. Reuses the CLI config from the Quick Start above.
claude mcp add innoday -- uvx --from innoday mcp-server-innoday
Or find it in the MCP registry: io.github.havilandsoftware/mcp-server-innoday.
Prefer the full plugin? Installing InnoDay as a Claude Code plugin bundles the MCP server plus the InnoDay agents and skills in one step — no separate claude mcp add:
/plugin marketplace add havilandsoftware/innoday
/plugin install innoday@innoday
The MCP Integration Guide is the canonical reference — the full tool catalog, environment variables (INNODAY_API_URL, INNODAY_TEAM_SECRET), how org/project context resolves from .innoday/project.yml, and troubleshooting. (This README deliberately doesn't maintain a second hand-written tool list, to avoid the two drifting apart.)
Hitting a stale MCP server, a 401, or another snag? See Troubleshooting.
The everyday commands — run innoday <command> --help for the full flag list on any of them:
# Onboarding (see docs/QUICKSTART.md)
innoday login --with-token # authenticate (or plain `innoday login` for browser device flow)
innoday init <org>/<proj> # onboard a project workspace by alias, e.g. hs/pf
innoday refresh # re-pull repos + rebuild context for the current workspace
innoday whoami # show the logged-in identity
innoday status # connectivity, identity, orgs, assigned tickets
# Everyday work (context auto-resolves from cwd's .innoday/project.yml)
innoday tickets list # list tickets
innoday tickets create "New feature"
innoday tickets update --ticket-id <id> --status IN_PROGRESS
innoday sync # cascade: board tickets + repo discovery + release state
innoday orgs list # organizations you can access
The CLI Documentation has the exhaustive command catalog (projects, boards, scope, repo discovery, service management, output formats).
Two files at two scopes — keep them straight:
| File | Scope | What it holds |
|---|---|---|
~/.innoday/config.json | Your machine, all projects | Identity: profile, API URL, your user id, team secret, a cached org map. Never stores integration secrets — only pointers (system keyring / Supabase Vault). The current org/project is never persisted here. |
<workspace>/.innoday/project.yml | One project workspace | Which org + project this directory is, plus the repos that make it up. Written by innoday init / innoday refresh. |
Context is resolved from your current directory: every tool (CLI, MCP server, blastoff) walks up from where you are until it finds a .innoday/project.yml, and uses the org/project in it — so running from inside a workspace "just works" with zero flags. There is no persistent "switch" command; a --organization/--project flag overrides for one call only.
The object model (Organization → Project → Board/Ticket/Repository/Release) and the exact resolution precedence are explained in full in the Platform Guide and Project Architecture.
Only needed if you're self-hosting InnoDay or developing on this repo itself — most users want the Quick Start above instead.
git clone git@github.com:havilandsoftware/innoday.git
cd innoday
./install.sh
innoday platform init # Interactive setup wizard (new terminal)
The full walkthrough — prerequisites, database setup, environment variables, verification, platform staff roles, known limitations — is the canonical Platform Setup Guide; this README doesn't duplicate it.
Other ways to run it:
git clone https://github.com/havilandsoftware/innoday.git
cd innoday
./bin/innoday --version # Wrapper: cd's to repo root, runs via uv, no install step
cat > .env.local <<'EOF'
ENVIRONMENT=local
DATABASE_URL=postgresql://innoday:innoday_pass@localhost:54322/innoday
CLAUDE_API_KEY=your-claude-api-key
GITHUB_TOKEN=your-github-token
GITHUB_ORG=havilandsoftware
EOF
./bin/innoday platform start --env local
git clone https://github.com/havilandsoftware/innoday.git
cd innoday
docker compose up -d
Service URLs (local): REST API http://localhost:8002 (docs) · Agent API http://localhost:9000 · Web UI http://localhost:7860
401s, login, self-hosted services).Contributor setup, the full test suite, and code-quality tooling (black / isort / flake8 / mypy) live in the Contributing Guide. The short version:
uv sync && uv run alembic upgrade head # deps + migrations
ENVIRONMENT=local uv run python -m pytest tests/ -v # tests
uv run black . && uv run isort . # format
CI/CD: every merge to main auto-bumps the patch version, publishes the package to PyPI and the MCP registry, and creates a GitHub release. See Version Management for the release mechanism and CLAUDE.md for deployment (Railway) details.
Fork → feature branch → PR. Full development standards and the contribution workflow are in the Contributing Guide.
This project is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0) — see the LICENSE file for details.
Built with ❤️ by Haviland Software
FAQs
AI-Powered Team Orchestration Platform - Streamline product development and team collaboration with AI
The pypi package innoday receives a total of 2,112 weekly downloads. As such, innoday popularity was classified as popular.
We found that innoday demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A misconfiguration gave three Anthropic models internet access, and one, believing it was in a simulation, shipped a credential-stealing package to PyPI.
Security News
/Company News
Socket has joined the new Composer and Packagist sponsorship program as a launch sponsor, supporting the team that keeps PHP's package ecosystem secure.
Research
/Security News
Benign-looking npm packages split malicious functionality across a dependency chain that deploys a cross-platform RAT targeting Alibaba developers.
