Skip to content

feat: Separate Eliza agent mode into dedicated page#11

Merged
wtfsayo merged 1 commit intomainfrom
feat/eliza-agent-mode
Oct 7, 2025
Merged

feat: Separate Eliza agent mode into dedicated page#11
wtfsayo merged 1 commit intomainfrom
feat/eliza-agent-mode

Conversation

@wtfsayo
Copy link
Member

@wtfsayo wtfsayo commented Oct 7, 2025

🎯 Overview

This PR separates the Eliza agent mode from the text generation studio into its own dedicated page for better organization and user experience.

📋 Changes

New Files

  • app/dashboard/eliza/page.tsx - Dedicated Eliza agent page route
  • components/chat/eliza-page-client.tsx - Client component wrapper for Eliza interface

Modified Files

  • components/layout/sidebar-data.ts - Added Eliza Agent menu item under Agent Development section
  • components/chat/text-page-client.tsx - Removed Eliza tab, simplified to AI SDK only

🏗️ Architecture Changes

Before:

/dashboard/text → Tab switcher [AI SDK | Eliza]

After:

/dashboard/text → AI SDK chat interface only
/dashboard/eliza → Dedicated Eliza agent interface

✅ Benefits

  1. Clearer Separation - Each mode has its own dedicated space
  2. Better UX - Users can access each mode directly from sidebar
  3. Simpler Code - Removed tab switching logic and conditional rendering
  4. Better Organization - Eliza grouped with other agent development tools

📊 Statistics

  • 4 files changed
  • 63 insertions(+), 43 deletions(-)
  • No linter errors

🧪 Testing

  • ✅ Linter checks pass
  • ✅ TypeScript compiles successfully
  • ✅ Both pages work independently
  • ✅ Sidebar navigation updated correctly

- Create new /dashboard/eliza page with ElizaPageClient component
- Add Eliza Agent menu item to Agent Development sidebar section
- Remove Eliza tab from text-page-client, keep only AI SDK mode
- Update page headers and metadata for both pages
- Eliza agent now completely separate from text generation studio
@vercel
Copy link

vercel bot commented Oct 7, 2025

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

Project Deployment Preview Comments Updated (UTC)
eliza-cloud-v2 Ready Ready Preview Comment Oct 7, 2025 7:04pm

@coderabbitai
Copy link

coderabbitai bot commented Oct 7, 2025

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Note

Free review on us!

CodeRabbit is offering free reviews until Wed Oct 08 2025 to showcase some of the refinements we've made.

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

@wtfsayo wtfsayo merged commit f9a8b69 into main Oct 7, 2025
3 of 4 checks passed
lalalune added a commit that referenced this pull request Dec 13, 2025
- Add Social Media Automation section (Platform Feature #11)
- Document all 11 supported platforms with capability matrix
- Add API examples for posting, liking, replying, deleting
- Add required environment variables per platform
- Reference docs/social-media-api-keys.md for detailed setup
- List available MCP tools and A2A skills
- Add Social Media to API Reference section
lalalune pushed a commit that referenced this pull request Dec 13, 2025
feat: Separate Eliza agent mode into dedicated page
lalalune added a commit that referenced this pull request Dec 13, 2025
- Add Social Media Automation section (Platform Feature #11)
- Document all 11 supported platforms with capability matrix
- Add API examples for posting, liking, replying, deleting
- Add required environment variables per platform
- Reference docs/social-media-api-keys.md for detailed setup
- List available MCP tools and A2A skills
- Add Social Media to API Reference section
0xbbjoker added a commit that referenced this pull request Jan 29, 2026
Security fixes:
1. Add MAX_METADATA_SIZE (10KB) check to prevent DoS via large payloads
2. Normalize phone numbers before DB insertion to ensure only valid
   E.164 formatted data is stored, mitigating SQL injection risk
   in subqueries that use this data

Fixes Claude security review issues #1 (SQL injection) and #11 (metadata size)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
odilitime added a commit that referenced this pull request Feb 10, 2026
This commit addresses several performance, security, and maintainability issues identified in code review:

**Performance Improvements:**
- Parallelize batch cost calculation (issue #10)
  - Extract unique methods from batch requests
  - Fetch costs concurrently with Promise.all
  - Reduces latency for batches with duplicate methods (e.g., 20 getBalance calls now 1 DB query)

**Pagination Support:**
- Add offset pagination to service pricing audit history (issue #11)
  - Support limit and offset query params in GET /api/v1/admin/service-pricing/audit
  - Enable efficient pagination for services with many pricing updates

**Configuration Management (issue #12):**
- Create centralized config module (lib/services/proxy/config.ts)
  - Extract hardcoded values to PROXY_CONFIG
  - Support environment variable overrides:
    - PRICING_CACHE_TTL / PRICING_CACHE_STALE_TIME (pricing cache)
    - UPSTREAM_TIMEOUT_MS (fetch timeout)
    - MAX_BATCH_SIZE (batch request limit)
    - HELIUS_MAINNET_URL / HELIUS_DEVNET_URL (provider URLs)
  - Makes configuration visible and testable

**Security Enhancement (issue #13):**
- Add startup validation for admin devnet bypass
  - Prevent production (NODE_ENV=production) from running with DEVNET=true
  - Protects against accidental admin bypass in production
  - Fails fast on startup with clear error message

**Bug Fixes:**
- Fix cache.set API calls in pricing.ts and engine.ts
  - Correct signature: set(key, value, ttlSeconds) not set(key, value, {ex: ttl})
  - Resolves type errors

All changes are backward compatible. No breaking changes to API contracts.

Co-authored-by: Cursor <cursoragent@cursor.com>
0xSolace added a commit that referenced this pull request Mar 9, 2026
Critical bugs fixed:
- #1: resolveContainer() now hydrates from DB after restart instead of
  falling back to first node. Added findBySandboxId() and listByNodeId()
  repository methods for DB-backed container resolution.
- #2: create() now uses DockerNodeManager.getAvailableNode() for
  least-loaded placement instead of random env-var selection. Increments
  allocated_count on create, decrements on stop. Falls back to env var
  only when DB has no nodes registered.
- #3: Port allocation now queries DB for ports already assigned on the
  target node. allocatePort() takes an exclusion set and retries until
  it finds a free port.

Security fixes:
- #4: runCommand() now shell-escapes cmd and each arg individually via
  shellQuote() before passing to SSH exec. Container names also quoted
  in docker exec/stop/rm commands.
- #5: Added validateAgentId() check (UUID-safe chars only, max 128)
  called before any shell interpolation of agentId. getVolumePath()
  validates before constructing path.

Functional fixes:
- #6: checkHealth() now polls with retry loop (3s interval, 60s total
  timeout) matching Vercel provider behavior, instead of single-shot
  8s request.
- #7: getContainerName() now uses full agentId instead of truncated
  first-8-chars to eliminate collision risk.

Code quality fixes:
- #8: Exported DockerSandboxMetadata interface for strongly-typed
  metadata. milaidy-sandbox.ts imports and narrows with it instead
  of Record<string, unknown> + as casts.
- #9: Fixed step numbering in create() comments (was 8→10, now 8→9→10).
- #10: SSH pool key changed from hostname-only to hostname:port to
  prevent collisions when nodes share hostname with different ports.
- #11: parseDockerNodes() result now cached at module level, only
  re-parsed when MILAIDY_DOCKER_NODES env var changes.
- #12: Moved DOCKER_HEADSCALE_PLAN.md and DOCKER_PROVISIONING_SUMMARY.md
  from repo root to docs/ directory.

No new type errors (tsc --noEmit passes with only 2 pre-existing errors).
0xSolace added a commit that referenced this pull request Mar 9, 2026
Fixes all 11 findings from the automated review:

Critical:
- (#1) Fix migration number references: 0034 → 0046 in schema comments and docs
- (#2) Port race TOCTOU: add partial UNIQUE index on (node_id, bridge_port)
  for active sandboxes. allocatePort() already retries; DB constraint is the
  safety net for concurrent provisioning
- (#3) SSH pool serverless compat: add idle timeout (5min) eviction on
  getClient(), track lastActivityMs on exec()

Security:
- (#4) Remove `as any` cast on statusFilter — validate against known status
  set, return 400 for invalid values, cast to MiladySandboxStatus type
- (#5) Add SENSITIVE_KEYS set to redact TS_AUTHKEY, DATABASE_URL, etc. from
  any logged docker run commands
- (#6) Document MILADY_DOCKER_NODES fallback as seed-only path with no load
  balancing — production should use Admin API node registration

Code quality:
- (#7) Remove ssh! non-null assertions in health check route — use definite
  assignment after early-return guard
- (#8) Migration already uses IF NOT EXISTS on all statements ✓
- (#9) Unit tests noted as follow-up work (not blocking)

Nits:
- (#10) Add logger.warn fallback when Vercel sandbox has neither shutdown()
  nor close() method
- (#11) PR draft status — will mark ready after fixes are confirmed
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