do you ever hit your pro quota?

Never hit pro quota yet, huge repo. Have multiple projects on the go locally and in cloud.

Feel like this is going to be thr $1000 plan soon

I'm thinking about switching to ChatGPT Pro also. Any idea what maxes it out before I need to pay via the API instead? For context I'm using about 1b tokens a month so likely similar to you by the sounds of things.

On pro tier have not been able to trigger the usage cap.

Pro

Local tasks: Average users can send 300-1,500 messages every 5 hours with a weekly limit. Cloud tasks: Generous limits for a limited time. Best for: Developers looking to power their full workday across multiple projects.

Thank you, that's very helpful. I think I could get close to that in some coding sessions where I'm running multiple in parallel but I suspect it's very very rare. Even with token efficient gpt5-codex my OpenAI bill is quite high so I think I will switch to Pro now.

Thanks to the 1948 British Nationality Act anyone from the Commonwealth, such as India or Pakistan, could migrate without visa. This caused the first wave of migrants as a response for the huge demand of doctors, nureses and workers (as in other European countries). Now, to explain the delayed effect, chain migration is the factor, the first generation brings their wifes and children, building communities, attracting the next generation to move abroad, and so on, taking place over decades. I've seen it with Turkish communities in Germany, the first generation came for the same reasons as in the UK, now they constitute 3% of the German population, but they deeply assimilated into German culture.

So we have our answer - it wasn't caused by "imperialism", but by specific laws passed by politicians, against the will of natives [1]. And we know how the economics worked out in countries that bothered to look [2].

[1] Between 1962 and 1971, as a result of popular opposition to immigration by Commonwealth citizens from Asia and Africa, the United Kingdom gradually tightened controls on immigration by British subjects from other parts of the Commonwealth. - https://en.wikipedia.org/wiki/British_Nationality_Act_1948

[2] https://emilkirkegaard.dk/en/2024/02/fiscal-impact-of-immigr...

Those laws were themselves a direct consequence of imperialism. Without the empire there would have been no Commonwealth migration to legislate about. Public opinion might explain why the laws were tightened, but it’s irrelevant to the causal chain.

Speaking of causality, Kirkegaard did not perform any kind of causal inference, so his analysis is based on correlation only, not on identified causal effects. He compares group averages and finds correlations with outcomes like employment or fiscal contribution, but that’s descriptive statistics. There are no counterfactuals, no identification strategy, and no attempt to separate selection effects, institutional factors, or assimilation dynamics. In other words, it’s not causal evidence — just patterns that he interprets as if they were.

The Ottoman empire caused tons of Muslim migrants to enter its core provinces. Empires always managed and reshaped migration. The Romans resettled conquered peoples across their empire to strengthen borders and repopulate cities. The Habsburgs moved ethnic groups into borderlands against the Ottomans. The Russian Empire orchestrated mass movements of Tatars, Circassians, and others. In all these cases, imperial expansion created migration streams that later fed into demographic and political conflicts.

Those percentages are shaky (especially Tokyo and Turkey), and even if roughly true, they don’t negate the fact that empires like the Ottoman, Roman, and Russian actively engineered huge population movements. High present-day homogeneity doesn’t mean migration wasn’t empire-driven.

I don’t see a contradiction, causal impact can unfold over decades.

It's possible to call the API locally:

  const response = await fetch("http://localhost:8000/api/jobs/run", {
    method: "POST",
    headers: {
      "Content-Type": "application/json",
    },
    body: JSON.stringify({
      workflow_id: workflowId,
      params: params,
    }),
  });

  const outputs = await response.json();

See here for more details: https://github.com/nodetool-ai/nodetool

We'll be launching a cloud version soon that let's you deploy your workflow in the cloud with easy API access.