-
Notifications
You must be signed in to change notification settings - Fork 219
Comparing changes
Open a pull request
base repository: Dicklesworthstone/pi_agent_rust
base: main
head repository: terraphim/pi_agent_rust
compare: main
- 9 commits
- 20 files changed
- 3 contributors
Commits on May 25, 2026
-
Fix clippy warnings: unnecessary_map_or and uninlined_format_args
- Use is_some_and() instead of map_or(false, ...) for Option check - Use inline format args with {previous_id} in format! macro
Alex committedMay 25, 2026 Configuration menu - View commit details
-
Copy full SHA for 478c8c2 - Browse repository at this point
Copy the full SHA 478c8c2View commit details
Commits on Jun 28, 2026
-
Merge remote-tracking branch 'upstream/main'
Alex committedJun 28, 2026 Configuration menu - View commit details
-
Copy full SHA for 542c5b0 - Browse repository at this point
Copy the full SHA 542c5b0View commit details -
feat(models): add kimi-k2.7 to kimi-for-coding default candidates
Kimi-K2.7 is the current frontier Kimi release. Add it as the newest-first candidate in PROVIDER_DEFAULT_MODELS for the kimi-for-coding provider, mirroring how k2.6/k2.5 are already handled (resolved by the provider at runtime via the stable kimi-for-coding virtual id).
Alex committedJun 28, 2026 Configuration menu - View commit details
-
Copy full SHA for e5a28d8 - Browse repository at this point
Copy the full SHA e5a28d8View commit details -
docs(agents): drop obsolete master-sync rule
The legacy master branch was deleted (2026-06-28); main is now the sole long-lived branch. Update the branching section to reflect that master no longer exists and must not be recreated or pushed to.
Alex committedJun 28, 2026 Configuration menu - View commit details
-
Copy full SHA for 48de429 - Browse repository at this point
Copy the full SHA 48de429View commit details
Commits on Jun 29, 2026
-
feat(terraphim): add project-local .terraphim KG + thesaurus for terr…
…aphim-grep KG-driven search configuration specific to pi_agent_rust so terraphim-grep works offline (no server) with project-aware concept boosting. - .terraphim/kg/: 13 project concepts (provider, session, extension, tool, sse, model-registry, acp, interactive-tui, conformance, hashline-edit, auth, asupersync, pi-terraphim-router), each with description + synonyms:: - .terraphim/thesaurus.json: 180 compiled entries (synonym -> {id, nterm}) - .terraphim/config.json: Pi Agent Rust Engineer role -> project KG + Ripgrep haystack terraphim-grep loads the thesaurus (180 entries), fff-search scans the repo, and matched concepts (e.g. 'extension','hostcall') boost relevant chunks above the baseline score. Requires terraphim-grep built with the code-search feature (fff-search); without it search_code is compiled out.
Alex committedJun 29, 2026 Configuration menu - View commit details
-
Copy full SHA for 5d6908a - Browse repository at this point
Copy the full SHA 5d6908aView commit details -
feat(terraphim): enrich KG with ast-grep code anchors + refresh script
Structurally-derived identifiers (pub struct/enum/trait + impl Provider) mined via ast-grep now back each concept, so terraphim-grep matches real code tokens (ReadTool, AnthropicProvider, ModelRegistry, AuthStorage, ...) instead of prose only. KG-boosted chunks now rank the actual definition files (e.g. providers/anthropic.rs, tools.rs) above baseline. - kg/*.md: appended curated, name-selective code anchors per concept (provider/session/extension/model-registry/sse/acp/auth/interactive-tui/ tool/hashline-edit). Thesaurus grew from 180 -> 409 entries. - scripts/refresh-anchors.sh: repeatable, idempotent refresh — re-runs the ast-grep extraction, appends new anchors, regenerates thesaurus.json. Run it whenever the code changes to keep the KG aligned. Anchors are selective (name patterns, not file-wide dumps) to keep the thesaurus signal-rich. Idempotent: a second run appends 0.
Alex committedJun 29, 2026 Configuration menu - View commit details
-
Copy full SHA for ba07485 - Browse repository at this point
Copy the full SHA ba07485View commit details
Commits on Jul 28, 2026
-
fix(providers): raise zai-coding-plan max_tokens/context_window to ma…
…tch zai zai-coding-plan routing defaults were stuck at context_window=128_000, max_tokens=16_384 -- stale values that silently capped every response from models like glm-5.2 at a fraction of their real capacity. The sibling zai provider already registers glm-5.2 with context_window= 1_000_000, max_tokens=131_072 (same underlying model, same real API limits). Aligned zai-coding-plan to context_window=262_144 (matching zai/glm-5.1, a safe uniform default for the provider) and max_tokens= 131_072. Verified empirically: a long-generation stress test that previously hit stopReason=length at exactly 4096 tokens on every attempt now completes with zero length-truncations across 500+ turns. Also required rebuilding and redeploying the local pi-rust binary, which was 5 weeks stale (v0.1.16 vs source v0.1.20) and missing an already-fixed max_tokens registry-seeding bug from an earlier commit.
forge-admin committedJul 28, 2026 Configuration menu - View commit details
-
Copy full SHA for 4b8c184 - Browse repository at this point
Copy the full SHA 4b8c184View commit details -
Merge remote-tracking branch 'origin/main'
forge-admin committedJul 28, 2026 Configuration menu - View commit details
-
Copy full SHA for 83dde70 - Browse repository at this point
Copy the full SHA 83dde70View commit details
Commits on Aug 14, 2026
-
feat(pi): exit 4 (EXIT_CODE_EMPTY_OUTPUT) when --mode json produces n…
…o MessageEnd events (terraphim-agents#80, D4) Companion to terraphim-agents PR #106 (merged 2026-08-14 as f46c9c4). Adds EXIT_CODE_EMPTY_OUTPUT = 4 + cooperative upstream signal. Round-1 author self-review (3/5); round-2 independent review (5/5) confirmed correct race handling and retry semantics. P1 follow-up for orchestrator-side recognition of exit_code == 4 filed as separate terraphim-agents task.
Configuration menu - View commit details
-
Copy full SHA for 6eb150c - Browse repository at this point
Copy the full SHA 6eb150cView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff main...main