Customizations

Manual Adjustments

To customize an AiAgentNexus-based application, you’ll need to either make direct code edits or configure environment variables. At present, no dedicated admin interface is available for “managed” customizations in an enterprise setting.

When Direct Code Modifications Are Needed	When Environment Variables Are Sufficient
- Customizing or replacing persona definitions - Changing UI themes - Introducing or altering features	- Configuring API keys in environment variables - Enabling/disabling functionalities through environment variables
Apply modifications within the source code before building the application	Adjust these settings after the build process, typically on local machines or in the cloud, right before starting the application

Editing the Source Code

Begin by forking the AiAgentNexus repository to your own GitHub account. AiAgentNexus primarily uses Next.js and React on the front end, and Node.js (Next.js edge functions) on the back end. Familiarity with these frameworks is recommended for any deeper customizations.

Adding Authentication

To implement authentication, you must rename specific files and make certain code changes before initiating a build. Instructions are in deploy-authentication.md.

Extending Vercel Functions Timeout

If you’re deploying on Vercel and need more time for longer processes, you can purchase a plan that allows extending the default function execution limit. This particularly benefits features such as web browsing or content sharing, which might occasionally exceed 10 seconds.

At the time of writing, AiAgentNexus uses Node.js-based functions for two main tasks:

1. Browsing and fetching web content

2. Sharing data

Both can surpass Vercel’s 10-second default, especially if the site being fetched is large or slow to respond.

We supply a vercel_PRODUCTION.json file that increases the timeout to 25 seconds. To activate it:

1. Rename vercel_PRODUCTION.json to vercel.json before building.

2. Optionally, from your Vercel project settings under “General” → “Build & Development Settings,” you can set a custom build command such as:

   mv vercel_PRODUCTION.json vercel.json; next build

Adjusting Personas

Within src/data.ts, you’ll find the default personas used by the application. Feel free to modify, remove, or add new personas to suit your project’s needs.

• Edit src/data.ts to configure default personas.

Updating the User Interface

If you want to change the overall style, add or remove UI elements, or integrate new functions, you can modify the following files:

• src/common/app.theme.ts to edit colors, spacing, animations, etc.

• src/common/app.config.tsx to rename the application or adjust general settings.

• src/common/app.nav.tsx to modify the navigation bar.

---

Testing & Deployment

Test your custom application in your local environment (see README.md for build instructions). Deployment can be done on platforms like Vercel, within Docker containers, or on any Node.js-compatible hosting service that supports Next.js edge runtime.

• deploy-cloudflare.md covers Cloudflare Workers deployment

• deploy-docker.md provides Docker-based guidance

• deploy-k8s.md offers Kubernetes instructions and samples

---

Debugging

For in-depth insights into your application’s environment and configuration (including API keys and environment variables), visit the /info/debug page. This view can help you diagnose issues quickly.

Contributing Projects & Showcasing

After you launch your custom build, we encourage you to share it with the community. We’ll happily add your link so that others can benefit from and learn about your work.

Project	Key Features	GitHub
🚀 CoolAGI: Bridging AI & Imagination	Code Interpreter, Vision, Mind Map Creation, Web Searching, Advanced Data Analysis, Large Data Handling, etc.	nextgen-user/CoolAGI
HL-GPT	Completely redesigned UI	harlanlewis/nextjs-chatgpt-app

For public-facing projects, remember to update your README.md reflecting your customizations and submit a pull request to our repository. It’s a great way to help others discover your work.

Best Practices

• Stay Current: Regularly merge updates from the main AiAgentNexus repository to incorporate bug fixes and new functionalities.

• Keep It Open Source: Consider remaining open source to encourage community involvement and collaboration.

• Collaborate with the Community: Engage on GitHub, Discord, or Reddit channels for feedback, partnerships, and to share your progress.