Skip to content

feat(context): rich context composer#151

Merged
SutuSebastian merged 6 commits into
mainfrom
feat/rich-context-start-here
May 27, 2026
Merged

feat(context): rich context composer#151
SutuSebastian merged 6 commits into
mainfrom
feat/rich-context-start-here

Conversation

@SutuSebastian
Copy link
Copy Markdown
Contributor

@SutuSebastian SutuSebastian commented May 27, 2026

Summary

Ships the full rich context composer:

  • start_here on non-compact context / MCP / HTTP — inline index summary, intent-ranked query_recipe cards, hub leaders with export signatures
  • Adaptive caps via resolveContextBudget(file_count) on hubs, hub_leaders, markers, and signature length
  • Debug intent biases sample_markers toward FIXME/TODO
  • MCP/HTTP include_snippets — one-line export previews on hub leaders
  • hubs + hub_leaders share readFanInHubs() (registered fan-in recipe, respects project shadows)

Test plan

  • bun test src/application/context-engine.test.ts
  • bun test src/application/mcp-server.test.ts
  • bun test src/application/http-server.test.ts (context + include_snippets)
  • bun run typecheck
  • Patch changeset added
  • Manual: codemap context on indexed repo
  • Manual: codemap context --for "refactor auth"

Non-compact context/MCP/HTTP envelopes now include intent-ranked
query_recipe cards and top hub files with export signatures so one
bootstrap call replaces a common show → explore chain.
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 27, 2026

🦋 Changeset detected

Latest commit: ee57ddf

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@stainless-code/codemap Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 27, 2026

Warning

Review limit reached

@SutuSebastian, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 9 minutes and 4 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d50c75bf-1d47-43ab-abec-09111de258c7

📥 Commits

Reviewing files that changed from the base of the PR and between 41a4184 and ee57ddf.

📒 Files selected for processing (15)
  • .changeset/rich-context-start-here.md
  • docs/agents.md
  • docs/architecture.md
  • docs/glossary.md
  • docs/roadmap.md
  • src/application/context-engine.test.ts
  • src/application/context-engine.ts
  • src/application/http-server.test.ts
  • src/application/mcp-server.test.ts
  • src/application/mcp-server.ts
  • src/application/tool-handlers.test.ts
  • src/application/tool-handlers.ts
  • src/cli/cmd-context.ts
  • templates/agent-content/mcp-instructions.md
  • templates/agent-content/skill/10-recipes-context.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/rich-context-start-here

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Add inline index_summary, debug-biased sample_markers, adaptive hub/signature
caps via resolveContextBudget, and MCP/HTTP include_snippets previews.
Retire the shipped plan; mark roadmap item complete.
Route hubs and hub_leaders through readFanInHubs (registered fan-in recipe
with adaptive LIMIT); add intent/start_here and HTTP integration tests.
@SutuSebastian SutuSebastian changed the title feat(context): rich context composer — start_here (slice 1) feat(context): rich context composer May 27, 2026
Preserve legacy hubs at the fan-in recipe default while budget-capping
start_here.hub_leaders, add safe snippet reads, and expand tests/docs.
Treat whitespace-only intent as no-intent on MCP/HTTP, truncate snippet
one-liners to signature_max_chars, dedupe tests, and expand coverage.
Add multi-hub fixture, large-repo marker cap test, MCP compact/intent
smoke, marker_limit unit assertions, and skill doc alignment.
@SutuSebastian SutuSebastian merged commit e717652 into main May 27, 2026
11 checks passed
@SutuSebastian SutuSebastian deleted the feat/rich-context-start-here branch May 27, 2026 11:25
@github-actions github-actions Bot mentioned this pull request May 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant