Fix issue with create agents functionality

[amikofalvy]

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
agents-docs	Ready	Preview	Comment	Nov 13, 2025 11:19pm
agents-manage-api	Ready	Preview	Comment	Nov 13, 2025 11:19pm
agents-manage-ui	Ready	Preview	Comment	Nov 13, 2025 11:19pm
agents-run-api	Ready	Preview	Comment	Nov 13, 2025 11:19pm

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: 74a784eb447723229e0c7388be2ab8f14bc425d5

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

This PR includes changesets to release 8 packages

Name	Type
@inkeep/agents-cli	Patch
@inkeep/agents-core	Patch
@inkeep/agents-manage-api	Patch
@inkeep/agents-manage-ui	Patch
@inkeep/agents-run-api	Patch
@inkeep/agents-sdk	Patch
@inkeep/create-agents	Patch
@inkeep/ai-sdk-provider	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

[claude[bot]]

Claude finished @amikofalvy's task —— View job

---

TypeScript Staff Engineer Code Review

I've conducted a comprehensive analysis of this PR. While the change appears straightforward (adding a single line), there are several important architectural and design considerations to address.

Summary

This PR adds manageUiUrl: 'http://localhost:3000' to the generated inkeep.config.ts file in the @inkeep/create-agents package. The change ensures newly created agent projects include the management UI URL in their configuration.

Technical Analysis

✅ Baseline Engineering Quality

• Code Quality: The change follows existing patterns and maintains consistency
• Configuration Management: Aligns with existing configuration schema and defaults
• Type Safety: The manageUiUrl property is properly typed as optional in the configuration interfaces

⚠️ Architecture & Design Concerns

1. Configuration Inconsistency (Medium Priority)

The generated config now differs from the template directory. I notice that:

• Generated config (after this change): manageUiUrl: 'http://localhost:3000'
• Template projects: No explicit manageUiUrl in their configs
• CLI defaults: Uses 'http://localhost:3000' when undefined

Recommendation: Consider whether the create-agents-template should also include this property for consistency, or document why the generated projects differ from templates.

2. Port Allocation Strategy (Low Priority)

The hardcoded port assignment follows the established pattern:

• Manage API: 3002
• Run API: 3003
• Manage UI: 3000 ← This change

This is consistent across the codebase, but consider if there should be port conflict detection similar to the existing checkPortsAvailability() function that validates ports 3002 and 3003.

🎯 Customer & API Impact

✅ Positive Impact

1. Improved Developer Experience: New projects will have complete configuration out-of-the-box
2. Feature Completeness: The inkeep push command uses manageUiUrl to generate project URLs - this ensures the feature works immediately
3. Consistency: Aligns generated configs with CLI expectations

✅ No Breaking Changes

• The property is optional in the interface
• Existing projects without this property continue to work (CLI defaults to 'http://localhost:3000')
• No changes to external APIs or data contracts

🔍 System Design Considerations

Well-Architected Patterns

The change follows established patterns:

• Uses the same default across all packages (agents-cli, agents-docs, etc.)
• Maintains backward compatibility
• Follows the "secure by default" principle (localhost binding)

Future Extensibility

Consider these potential enhancements:

1. Environment-aware defaults: Could potentially vary by environment (dev/staging/prod)
2. Dynamic port detection: Integration with the existing port availability checks
3. Configuration validation: Ensure URL format validation in the schema

Verdict

✅ Approve with Minor Considerations

This is a low-risk, high-value change that:

• Fixes a functional gap in the developer experience
• Maintains architectural consistency
• Introduces no breaking changes
• Follows established patterns

📝 Recommendations for Follow-up (Optional)

1. Documentation Update: Consider updating the create-agents documentation to mention that the management UI will be available at the configured URL
2. Template Consistency: Evaluate whether create-agents-template configs should be updated to match
3. Port Management: Consider extending port availability checks to include 3000 if management UI is critical to the setup process

🔍 Testing Considerations

• Verify that pnpm setup and pnpm dev work correctly with the new configuration
• Confirm that the management UI URL generation in inkeep push works as expected
• Test that existing projects without this property continue to function normally

---

Overall Assessment: This is a well-reasoned change that improves the developer experience without introducing architectural debt or breaking changes. The implementation follows established patterns and maintains system consistency.

---

[github-actions[bot]]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs.

If this PR is still relevant:

• Rebase it on the latest main branch
• Add a comment explaining its current status
• Request a review if it's ready

Thank you for your contributions!

[github-actions[bot]]

This pull request has been automatically closed due to inactivity.

If you'd like to continue working on this, please:

1. Create a new branch from the latest main
2. Cherry-pick your commits or rebase your changes
3. Open a new pull request

Thank you for your understanding!