this is not the way forward

[dikkietrom]

Pre-submission Checklist

• I have verified this would not be more appropriate as a feature request in a specific repository
• I have searched existing discussions to avoid duplicates

Your Idea

first we had tools , then mcp, which are not agents, which will be added later. it is getting out of hand and nobody can follow this. the fact that there is a handfull of messages here proves my point. we are in AI phase now and still with json configs, it makes zero sense to me, things are supposed to be more easy and it is hard to grasp what mcp is anyways. defacto it is a manner of connection "something" through a standarised protocol, while we need no standards we need dsl. everything is an agent and every agent has unique dsl so that agents can also program eachother, which is insanly more powerfull than what you are doing now with the mcp. all that is needed is that the agent publishes its language spec , do this in me, classic inversion of control that is proven to work very well. that would really move things forward, this mcp thing is not going to break any wall. great thing about dsl is that the llm defines the dsl for you and can implement the language, the dsl can run in a wasm os in the browser and asembled to a virtual cpu instructions set with prompt and hard code instruction for the concrete os pipeline to binary machine code.
the v8 runtime does the same with optimised code and rich high level instructions. adding prompting to it is not out of the ordinary. the modern pc arch is an organisation that is extremely wel managed and under control, it makes perfect sense to hop on that bandwagon and not invent the wheel again. pc were made for humans and agents mimic humans so they should act like humans with a dsl and a user account on the system, instead of reinventing security and sandboxing. such an virtual ai-os can run in wasm vm in the browser and we have the ai-os that we need, anyways i am making it now with help of mainly claude and will push the whole thing somewhere the coming weeks, it would be great to discuss this idea here with like minded spirits about how to move this forward and de-standarise instead of sticking to the old way of doing things with rigid unreadable json structures.

Scope

• Protocol Specification
• SDK Features
• Documentation
• Developer Experience
• Other

[dikkietrom]

also the fact that it is TS or python more than not is a burden, a subset of bash what i call ai script makes most sense, it is the highest level of abstraction closest to the metal. these compiled languages and oo concept was made for humans to deal with complexity but ai does not need that, worse it is burdened by it. python is a disaster with lib dependencies just as node. bash is all you need. the ai script spec will also be published the coming time. problem with bash is the too rich syntax that can make script unreadable hence ai script is a subset and not really something different than bash code. eg

==============================================================# TypeScript Server Setup

Directory Structure

typescript-server/
├── package.json
├── tsconfig.json
├── src/
│ ├── server.ts
│ ├── routes/
│ │ └── index.ts
│ └── middleware/
│ └── logger.ts
└── dist/

1. Initialize Project

mkdir typescript-server
cd typescript-server
npm init -y
npm install express typescript @types/express @types/node ts-node nodemon
npm install --save-dev jest @types/jest ts-jest

2. Configuration Files

package.json

{
"name": "typescript-server",
"version": "1.0.0",
"scripts": {
"start": "node dist/server.js",
"dev": "nodemon src/server.ts",
"build": "tsc",
"test": "jest",
"lint": "eslint . --ext .ts"
},
"dependencies": {
"express": "^4.18.2",
"typescript": "^5.0.0",
"@types/express": "^4.17.17",
"@types/node": "^18.15.11",
"ts-node": "^10.9.1"
},
"devDependencies": {
"@types/jest": "^29.5.0",
"jest": "^29.5.0",
"ts-jest": "^29.1.0",
"nodemon": "^2.0.22",
"@typescript-eslint/eslint-plugin": "^5.58.0",
"@typescript-eslint/parser": "^5.58.0",
"eslint": "^8.38.0"
}
}

tsconfig.json

{
"compilerOptions": {
"target": "es6",
"module": "commonjs",
"outDir": "./dist",
"rootDir": "./src",
"strict": true,
"esModuleInterop": true,
"skipLibCheck": true,
"forceConsistentCasingInFileNames": true,
"moduleResolution": "node",
"resolveJsonModule": true,
"declaration": true,
"sourceMap": true
},
"include": ["src//*"],
"exclude": ["node_modules", "/*.test.ts"]
}

.eslintrc

{
"parser": "@typescript-eslint/parser",
"plugins": ["@typescript-eslint"],
"extends": [
"eslint:recommended",
"plugin:@typescript-eslint/recommended"
]
}

3. Source Code

src/middleware/logger.ts

import { Request, Response, NextFunction } from 'express';

export const logger = (req: Request, res: Response, next: NextFunction) => {
console.log(${new Date().toISOString()} - ${req.method} ${req.path});
next();
};

src/routes/index.ts

import { Router, Request, Response } from 'express';

const router = Router();

router.get('/', (req: Request, res: Response) => {
res.send('Hello World!');
});

router.get('/health', (req: Request, res: Response) => {
res.json({ status: 'ok' });
});

export default router;

src/server.ts

import express from 'express';
import routes from './routes';
import { logger } from './middleware/logger';

const app = express();
const port = process.env.PORT || 3000;

app.use(express.json());
app.use(logger);
app.use('/', routes);

app.listen(port, () => {
console.log(Server running at http://localhost:${port});
});

4. Build and Run Commands

# Development
npm run dev

# Production
npm run build
npm start

# Testing
npm test

################################################################################

Bash Server Setup - Complete Version

1. Create server file

touch server.sh
chmod +x server.sh

2. Full server implementation

#!/bin/bash
while true; do
echo -e "HTTP/1.1 200 OK\r\n\r\nHello\r\n" | nc -l 3000;
done