Feat/codra code v0.1.2 - #46
Conversation
- Replaced zip command with PowerShell Compress-Archive - Fixed Windows release packaging on GitHub Actions
- Added Codra Code section with install and quick start - Added cross-platform download instructions - Added slash commands reference - Added provider setup examples for Codra Code - Updated roadmap with completed items - Updated current status with v0.1.4 features - Updated ecosystem section with Codra Code
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 23e735bcf8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| See [crates/codra-cli/README.md](crates/codra-cli/README.md). | ||
|
|
||
| ## Installable CLI roadmap | ||
| The installable npm wrapper also exposes `codra understand` for local repo graphing. See [docs/UNDERSTAND.md](docs/UNDERSTAND.md) and [docs/CLI.md](docs/CLI.md). |
There was a problem hiding this comment.
Restore the README links to existing docs
This new README section links users to docs/UNDERSTAND.md and docs/CLI.md, and later to docs/HARNESS.md, docs/MODEL_PROVIDERS.md, docs/OSS_MODE.md, and docs/SECURITY_MODEL_CONFIG.md, but those files are not present in the repo; I searched docs/ for understand/cli/harness/provider/oss/security docs and found no matches. These links now send users to 404s from the main project README, so either add the referenced docs in this change or point to the existing documentation.
Useful? React with 👍 / 👎.
| - `codra harness init` | ||
| - `codra harness status` | ||
| - `codra harness doctor` |
There was a problem hiding this comment.
Remove the unsupported harness commands
These new harness instructions advertise codra harness init/status/doctor, but repo-wide search only finds harness mentions in docs/demo assets and the actual CLI help/dispatcher in crates/codra-cli/src/terminal.rs/main.rs has no harness command. Following this section currently just falls through to generic help, so users cannot create the advertised .codra/harness state.
Useful? React with 👍 / 👎.
| codra --oss | ||
| codra --provider ollama | ||
| codra provider list |
There was a problem hiding this comment.
Don't advertise provider switches the CLI lacks
In the Codra CLI setup, codra --oss, codra --provider ollama, and codra provider list are not implemented: crates/codra-cli/src/main.rs only recognizes provider check and treats unknown top-level commands/options as help. Users following this block won't actually select Ollama or list providers, leaving provider setup unconfigured.
Useful? React with 👍 / 👎.
| - [x] Local workspace connection and project indexing | ||
| - [x] Planner, executor, verifier, and repair loop |
There was a problem hiding this comment.
Keep roadmap checkboxes aligned with the roadmap
This marks repo indexing and the planner/executor/verifier/repair loop as complete, but the full roadmap linked directly above still has basic repo context/indexing unchecked in docs/ROADMAP.md:10 and planner, executor, verifier, and repair loop unchecked in docs/ROADMAP.md:19-22. Readers of the main README will now believe these agent-loop capabilities are shipped even though the project still tracks them as in progress or not done.
Useful? React with 👍 / 👎.
|
|
||
| ## Use Codra with OpenAI-compatible, local, or custom providers | ||
|
|
||
| Codra can run against OpenAI-compatible APIs, proxies, OpenRouter, Mistral, xAI, DeepSeek, Ollama, LM Studio, and future providers using the global config file at `~/.codra/config.toml`. |
There was a problem hiding this comment.
Point provider config docs at files the tools read
This says provider setup uses ~/.codra/config.toml, but I found no TOML loader or config.toml reference; Codra Code reads environment variables plus ~/.codra/config.json / .codra/config.json, and the Rust provider service reads workspace .codra/provider_config.json. Users who create the documented TOML file will have their provider settings ignored.
Useful? React with 👍 / 👎.
No description provided.